mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-09-26 13:33:34 -04:00
35d7b11d03
Session close state. Three parts: stage 0b (91, zero decompilation), wave 1 (26), wave 2 (116). Fleet 94.4% -> 94.7% instr, 88.3% -> 88.9% distinct, 13,345 -> 13,112 stubs. R22 clean-fleet run 5x, 213/213 every time. The campaign now has a MEASURED rate, twice: 67% (wave 1, all-Opus) then 79% (wave 2, 20 of 28 Sonnet) of cracks survive the whole-binary gate. The Sonnet band beating the all-Opus wave is the session's most useful economic finding and sets wave 3's routing. Resume order changed on evidence, twice over: - harden the wave harness FIRST (per-agent dirs, sha1-last verifier, and a tools/recover_drafts.py built from the transcript-replay method that recovered 21/21 today); - then wave 3, sized on 79%, not on the reach-15 prior. Error ledger grew to 6. The two that matter: I wrote off 21 verified cracks as lost when the run transcripts held every one of them, and my first two recovery passes both failed by reading a single tool record instead of replaying the file's mutation history.