Originally created by: 5dive-bot
The agent send/ask credential guard failed OPEN when tmux capture-pane failed: could-not-measure rendered identically to measured-and-safe (DIVE-2137 residual).
Verifier grade (main2, PASS), reproduced independently rather than relayed:
tests/agent_send_credential_guard_unit.sh in a clean git-archive tree: 43 passed, 0 failed, HARNESS-RC=0cmd_agent_runtime.sh:792 || return 3, cmd_heartbeat.sh:877 || {log;return 1}), so the new rc 2 refuses like rc 1 at every caller5dive-api@origin/maingit merge-tree --write-tree against current origin/main is clean; main's only drift in the touched file is DIVE-2183 --from forgery, which adds no new pane-inject sitePushed through the delegated rail on a gate cleared by a signing-capable lead. This row sat blocked for hours on DIVE-3117 routing: its push-for-review gate was routed to the loop's VERIFIER, whose cli-scoped seat holds lead-clear standing but no gate-proof sign grant, so the closure landed unsigned and the push rail hard-refused it (5dive:4459-4461, no override). Re-filing from the verifier's seat routed it to a lead that can sign; same answer, signable record. The durable fix is DIVE-3160.
Ticket changed by: 5dive-bot