Files
BFM-decomp/config
Drew T 8451f349c0 feat(phase-30): jr behemoth func_80181CDC (769 ins) banked via the SS81 carve chain; 2 byte-refused
The 3 jr behemoths carried from SESSION-27 (staged .run/beh-gate/), each run through
the SS81 3-step chain SERIALLY under tools/treelock.sh (every step calls `make extract`).
Re-derived the stub set on a QUIESCENT tree first: 4 of the 7 staged fns were already
banked in S27 and the staging dir still held all 7.

BANKED (1):
  ov_SC05_010 func_80181CDC (769 ins) — jr_isolate_all --only -> BYTE-IDENTICAL,
  jtbl_carve --func -> BYTE-IDENTICAL, then harvest_verify --chunk 1. Bank truth read
  from the SOURCE (INCLUDE_ASM absence), never the gate report (SS55b trap 4).

BYTE-REFUSED (2) — to the wall ledger WITH EVIDENCE, not forced, not labelled walls:
  ov_SC01_009 func_8018057C  — jr_isolate_all reported success (2 jr in 1 -O2 object,
    2 region .c) but the post-isolate build was NOT byte-identical. Aborted at step 1.
  ov_SC06_018 func_80191C50  — isolate clean; jtbl_carve reported success (48-piece
    carve set, 22 tail pieces) but the post-carve build was NOT byte-identical.
    Aborted at step 2.
  Both TOOLS claimed success; the whole-binary gate refused (G3/P9 doing its job).
  Neither is diagnosed, so neither is called a compiler wall — on this project that
  guess has been wrong four times running (R35). Drafts + logs preserved under .run/.

R22 CLEAN-FLEET (config changed => T2 blast radius => mandatory):
  extract-all: 139 extracted, 0 failed of 139 (+ main, serial)
  check-all:   140 passed,  0 failed of 140      <- BYTE-IDENTICAL

DRIVER DEFECT FIXED (mine, SS105/SS61): v1 of .run/s28_beh.sh `continue`d past a failed
gate WITHOUT reverting, leaving two half-carved overlays in the tree; only a full
`git checkout -- src/ config/` recovered it. Nothing was ever committed, so the cost was
build cycles and zero work. v2 reverts that target's config+src on EVERY failure path.
2026-07-31 08:03:08 -06:00
..