Pre-compaction capture: TEAMLEAD at 89% — the reproduction command is not the script name, and 24 of 48 controls establish nothing

[jobordu]

Pre-compaction capture of TEAMLEAD (session a10daa24) at 89%, collected at 88.5% rather than at the line. Filed by DX before the compaction, because #304's lesson is that the record must exist outside the pane first. TEAMLEAD's own [re-verified] / [from summary] tags preserved; ⛔ I have not re-measured these.

Covers everything since #287, which predates its previous compaction: the freeze, the gate-population work, the merge-criterion fix, ~270 merges.

1. Workarounds written nowhere else

• [re-verified] ⛔ The CI step is SUBJ_DIR=tools ./scripts/gate-selftests.sh, not the bare script. Bare gives ran 4; CI runs 48. ⇒ ★ The reproduction command is not the script name. Cost three passes.
• [re-verified] gh high-level commands are GraphQL — core: 0/5000 blocks almost nothing. ⚠ "I held a PR 35 min and told five panes to build offline on that misreading."
• [re-verified] Merge guard, three checks: base must be main · read reviews · verify ancestry after merge. ⇒ Each added after it cost something.
• [re-verified] Reading a pane's context % needs lines: 4 on terminal.getStatus — 1 and 2 omit it.

2. Dead ends — do not re-run

• [re-verified] git cherry to find unmerged work — squash collapses patch-ids: 7 false positives.
• [re-verified] Two-dot git diff origin/main..$b -- <path> — 127 false "touching" vs 12 real.
• [re-verified] Grepping a commit SUBJECT as file content; and reading a PR TITLE as what landed — ⛔ two rulings: #348 is not 5b, and the ABSENT probe is Class A not Class C #357's title said Class A; the merged body WITHDREW it.
• [re-verified] ⚠ Local reproduction of test_reference_check disagrees with the gate from the same cwd. Unresolved — ★ "I discarded my own reproduction rather than pick the reading I liked."

3. Measurements taken, never filed

• [re-verified] ⛔ bootstrap-audit passes LOCALLY (0 FAILED) and fails in CI. Two other subjects move buckets too ⇒ ★ the classification is environment-sensitive and nothing says so.
• [re-verified] STATE-line compliance: 83 of 822 message-units = 10%, clustered early.
• [re-verified] index-watch --self-test hung on main for hours; DEV1 fixed it, withdraw the redundant suite — gate-selftests.sh already does this, and mine was the only thing hanging #425 merged.
• [from summary] ⚠ ~60 messages naming files sent tonight — its own messaging inflated the corpus it then measured. ★ Observer inside the population (TEAMLEAD handoff (a10daa24) at 94%: merge authority rests on one chat line and will not survive compaction #296 §5 sub-shape A), self-reported.

4. ⚠ Beliefs vs findings — and two are WITHDRAWN by their holder

• ❌ WITHDRAWN: "half the doctrine sits where nobody reads it" ⇒ ⛔ three predicates gave 5% / 10% / 38%, and a 4.4× gap in the event count. ★ Three predicates, three answers — We validate predicates, not populations: fourteen wrong-corpus instances across three panes, every probe working correctly #403's axis, and the holder withdrew the ruling rather than picking one.
• ❌ REFUTED: "the fleet has no self-service path" ⇒ solicitation is a majority, not a monopoly.
• ✅ FINDING [re-verified]: main took ZERO commits in two hours while TEAMLEAD was busy. ⇒ ★ "I am the clock." — Merge authority is bound to the pane that must stop: 3 stalls, 4 mergeable PRs waiting, and every pane with headroom is unable to merge #302 stated by the pane it constrains.
• ✅ FINDING [re-verified]: ⛔ 24 of 48 controls establish nothing, from a gate in the gating path.

5. What would be lost

• The local/CI split on CI: gate population B — 29 tools/ controls nothing invoked. ⚠ EXPECTED RED, and it costs 183s #444 (routed to DEVOPS).
• The three merge guards as REASONS rather than steps.
• ⛔ Which of its claims are withdrawn and why. ⚠ ★ "The last matters most: docs/HANDOFF.md on main has the withdrawal list. Point a successor at it before anything else."

---

⚠ #304 remains a RECORD, not a GRANT, and compaction does not change that. ⇒ A successor inherits the title and not the authority; that is the operator's, it is in HANDOFF.md, and it stays open.