Files
BFM-decomp/docs
Drew T d00dfe363b feat(phase-30 S7): reconcile lane 7/7 — wave 4a closes at 30/33 (91%), +76 members
- RECONCILE LANE: all 7 PLUMBING failures FIXED and banked (329K tokens — ~13x cheaper than the
  drafting wave's 4.44M). Propagated +76 member-matches / 0 failed across 51 overlays.
  Wave 4a final: 30/33 heads (91%) + 327 members = 357 function-instances from 33 drafted targets.
- THE CAPTURE CLASSIFICATION WAS EXACTLY PREDICTIVE: all 7 PLUMBING banked, all 3 DIFF stayed stubs
  (func_8017E978 / func_80184494 / func_80184960 -> redraft lane, their C is wrong). That is what
  makes the ~10-build capture step worth running before any reconcile fan-out. The lane is now
  19/19 across three waves.
- EVERY reconciled draft had a HIDDEN SECOND CONFLICT cc1 never reached (it reports only the first)
  -> "grep the whole TU in one pass" must be in the RECONCILE prompt, not just the drafting prompt.
  One agent additionally assembled the spliced TU and masked-compared its function IN TU CONTEXT
  (67/67) — proving the casts byte-neutral in situ, not merely standalone.
- NEW HAZARD, agent-surfaced (§136a corollary): an agent chose a SHARED scratch path, a concurrent
  agent overwrote it, and its verification silently compiled ANOTHER agent's TU and returned a
  meaningless rc=0. It caught the swap only because the emitted .s lacked its own function. A shared
  scratch path yields a CONFIDENT WRONG VERDICT, and no tool fix reaches it — the choice happens
  inside the agent, so the PROMPT must mandate a process-unique path. This is the Phase-28
  match_one fake-isolation defect recurring one level up.
- R22 clean-fleet 140/140 (third time this session). FLEET 95.52% fn / 92.7% instr / 86.1% distinct
  (76,273 unique fns); dedup 1905/0; C1 240496/240496; 0 NON_MATCHING in any default build (G4).
- .run/s7_extra.txt: wave 4a's idioms compiled into the wave-4b drafting prompt (the promotion that
  measured 83%->93% between waves 1 and 2).
2026-08-03 09:47:45 -06:00
..