clocklisted

# clock Install (or remove, or inspect) three Claude Code settings entries: 1. A **`statusLine`** entry at the bottom of the terminal showing the active model, context-window usage, and (for Pro/Max subscribers) the **5-hour** and **weekly** quota use with reset times: `<model> · X% (Nk/Mk) · 5h N% (→HH:MM) · wk N% (→wd HH:MM)`. The 5h/wk parts only appear after the first API response of the session, and are omitted entirely on accounts where Claude Code does not deliver `rate_limits` in the statusLine envelope. Refreshes every **60 seconds** (`refreshInterval: 60000`) AND on each assistant turn boundary, so the bar stays live even during long, quiet stretches. The 60s default sits well above Windows Node cold-start (1–3s), so the harness never cancels an in-flight script — avoid sub-second tickers, those cause the bar to intermittently disappear. The clock face was dropped from this line — the chat audit-trail Stop/PostToolUse hook (`cah-stamp`) carries the timestamp instead. 2. A **chat-stamp hook** (`cah-stamp`) installed on **BOTH** `Stop` AND `PostToolUse`. It emits an `HH:MM · model · X% · 5h N% · wk N%` line as a `systemMessage` into the chat scrollback, both after every tool call AND at end of turn. This gives a fine-grained, timestamped audit trail: going back through the conversation you can see when each tool fired and how the context / 5h / weekly counters were rising at that moment. `cah-stamp` reads the