Files
BFM-decomp/phase-ends
Drew T f28a435815 docs(phase-18): CURRENT_PHASE — full Step-3b runbook + new-session banner
- 🚨 top banner: T0-T5 'unsteerable' framing SUPERSEDED; resume 3->1->2 at Step 3b
  with /effort ultracode ON; read cookbook §17 (the corrected TOOLKIT) first
- ▶ STEP-3b RUNBOOK: the §17 toolkit summary (reconstruct/array-decay/PINS/barrier +
  the MANDATORY canonical-retype gate gotcha + stub-only narrow-param), the exact gate
  pipeline + commands (match_one/harvest_verify/dedup_propagate, ov_SC01_077 good-sha
  d19c9580), the durable worked examples (engine_core.h DEFINE_func_8012B8E4/801399A8),
  the staged assets (harvest_wave_s4.js, probe_targets_s4.json, .run/ghidra_c/), fleet
  baseline 55.58%/136-of-136, and the Step 1->2 close path
- everything a fresh full-context session needs to author the upgraded wave + run it
2026-06-20 12:56:15 -06:00
..
2026-06-10 22:02:07 -06:00

phase-ends/ — the living record

  • PhaseEnd_Phase[N].md — written at each phase boundary (format defined in PROJECT_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 every PhaseEnd_*.md in numeric order, then CURRENT_PHASE.md (if present) — in that order, every session.