Originally created by: 5dive-bot
A codex seat that hits its ChatGPT usage limit mid-task was invisible to one of the two
matchers, and the 45m reaper turned the wall into a blocked row needing a human requeue.
Measured on DIVE-4119 (2026-09-09): reap [#1] at 11:20, re-nudge into the same wall at 11:30,
blocked + escalated at 12:21 — nothing was lost, but a human gate was manufactured.
_SUP_QUOTA_PAT already matched it (DIVE-4206 widened it to hit your ((monthly|weekly|daily)
spend|session|usage|5-hour) limit); verified at head and pinned as a regression arm rather than
assumed. The half still missing was the OTHER matcher: _hb_pane_is_usage_limit's ACTION arm
carried only Claude Code's copy ("Upgrade your plan"), while codex says "Upgrade to Pro" — so the
supervisor classified the seat quota-exhausted while the heartbeat's own matcher answered
"not a wall" about the identical string (_hb_usage_limit_frozen and _hb_wall_class both blind).
Added upgrade to pro to that alternation; two-signature discipline unchanged, both
single-signature non-vacuity arms asserted. _hb_wall_class deliberately stays undetermined
for codex (it names no reset time) — asserted, not left to drift into rate-limit.
_hb_reclaim rule (c) now HOLDS the claim while the seat (or a peer on its auth profile) is
quota-parked — held, not reclaimed-once, because a reclaim still spends a _hb_mark_reap tick and
a wall spanning two budgets would reach _HB_REAP_ESCALATE_AFTER by a different route. Bounded by
the same park (deadline + one tick, else the 6h fallback), so it expires on its own and rule (c)
then reaps exactly as before — asserted by a control arm in each harness. It also stops /goal clear
being nudged into the wall.
tests/heartbeat_reclaim_loop_unit.sh arm 5 is INVERTED by this row: it asserted DIVE-4104's
rule-(b)-only scope, which is the premise being reversed. Arm 5b replaces its job with the bound.
Plugins repo, dev lane; the row's own body says it can be split once (a)+(b) ship. Spec is written
into the DIVE-4171 body verbatim. (b) removes one source of thread growth (a walled seat is no
longer nudged at all), but an ordinary reclaim + re-dispatch still re-sends the goal onto the same
thread, so (c) is still owed.
On the pre-fix tree (source reverted, tests kept) the new harness reds 4/11 and reproduces the
incident exactly — row blocked, cmd_task_escalate called, two /goal clear sent into the wall.
origin/main 16b938b4)New harness 11/11. heartbeat_reclaim_loop_unit 33/33, heartbeat_reclaim_verifier_handoff_unit
6/6, heartbeat_usage_heal_unit 27/27, heartbeat_spend_cap_unit 43/43,
heartbeat_reap_escalate_latch_unit 12/12, heartbeat_dispatcher_claim_unit 30/30,
heartbeat_tier_head_of_line_unit 32/32, supervisor_unit 154/154, supervisor_classify_unit
102/102, supervisor_quota_hold_unit 53/53, quota_rotation_dispatch_boundary_unit 7/7,
worktree_reclaim_unit 28/28, runs_unit 44/44, task_first_started_at_unit 42/42. All green.
LIVE ARM STILL OWED (third acceptance bullet): "next codex wall, the heartbeat log reads
claim PARKED/claim HELD and the row never goes to blocked" needs a real wall on a real seat.
Signed as unrun, not as passed.
Compiled: community/wiki/a-park-that-narrows-one-rule-is-not-a-park.md (+ index line).
🤖 Generated with Claude Code
Ticket changed by: 5dive-bot