mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-09-27 14:02:04 -04:00
Drew T
551239bd3c
Stage 0b closed (91, zero decompilation) + Stage-1 wave 1 (8 cracks -> 26 instances). Fleet 94.6% instr / 88.8% distinct / 96.36% fn-count. Resume order changed on measured evidence: FIX THE md_ MODULE LANE FIRST. 16 of the wave's 42 member slots were unreachable for tooling reasons, not matching reasons — 12 on a carve that assumes raw data lives in <binary>/data/*.data.s (modules do not), 4 on an uncarried extern (`D_8011511A' undeclared). Both are named with verbatim errors; probe one of each before pricing (R37). Precedent: 0b's three repairs banked 91 for ~0 agent tokens; the wave spent 3.36M for 26. Also recorded: the frontier re-derivation (1,955 zero-crack families / 330,622 templatable ins), the tier-ordering correction (ins-per-crack is flat across x5-x8, so rank by templatable weight, not by tier), and the §162 harvest with its two in-place cookbook corrections.
phase-ends/ — the living record
PhaseEnd_Phase[N].md— written at each phase boundary (format defined inPROJECT_CONTEXT.md). Append-only history: build log, deviations, commit message, rules added, changelog. Never deleted.CURRENT_PHASE.md— the in-phase autonomous log: approved phase plan, per-task checkboxes, current task pointer, blockers. Created at phase start, updated after every task, absorbed into the PhaseEnd file and deleted at phase close. This is the crash/compaction recovery point.- Sessions read
PROJECT_CONTEXT.md, then everyPhaseEnd_*.mdin numeric order, thenCURRENT_PHASE.md(if present) — in that order, every session.