INCIDENT (done): 19h fleet-wide compact blind spot from CC statusline format change
DONE, recorded for the plan. 2026-09-02T06:08 UTC Claude Code v2.1.251 changed the statusline from 'ctx Xk / Yk' to 'ctx X% (Yk/Zk)'. scan-context.py STATUSLINE_RE stopped matching for every -cc agent on venus at once (~18 agents, context_samples frozen at the identical timestamp; -ca/Codex unaffected). For ~19h the compact actuator (tick.py) saw 'no statusline' on the whole -cc roster and never nudged/compacted anyone - nw-venus-cc reached 217k/250k with zero nudge. Second, independent parser in the same file (is_idle footer skip-list) broke from the same change, fixed by bin-venus-cc c208111. STATUSLINE_RE fixed by monitor-context-cc, sh.git 145416e, tick.py v4.96 d5c495c. Side effect: ~74 false 'agent is dark' DMs reached Elazar. Footer shape is per-host (statusLine.command), so a sweep on one host proves nothing about the next.
Activity
-
parent=#3062
-
Fixed and pushed before filing; recorded as a done incident so the epic shows why the 190k/220k tiers never fired 09-02.
-
Correction for the record (Elazar nqla 6b, 2026-09-03): the ~74 'agent is dark / no parseable statusline' DMs the venus actuator sent 2026-09-02 07:08 -> 2026-09-03 01:09 were all false positives from this incident. No agent was dark. Hub delivery to Elazar refused (CLI-only), so this event and the CLI reply are the record.