Fleet 96.23 -> 96.24% fn-count / 93.9% instr / 88.3 -> 88.4% distinct.
R22 clean-fleet: 140 passed, 0 failed of 140. dedup 1910/0.
func_8017D318 (184 ins) + func_80181EE0 (198 ins) both banked, + 6 members swept
(6 per-overlay variants failed — ledger material, not a lever).
THE RECONCILE DIRECTION DEPENDS ON WHERE THE TU'S DECL IS, and picking wrong
CREATES the next error (-> cookbook §138):
- decl ABOVE the splice point -> DELETE the draft's duplicate (§100).
func_8017D318: the TU defines MATRIX_/SVECTOR_8017C290, D_801EA8C0 AND a
`struct PW8017C290` tag above it; I missed the tag on the first pass, so it
took two rounds.
- decl BELOW the splice point -> KEEP a decl in the TU's EXACT shape and cast
at the use (§17a-1 D2). func_80181EE0: I removed its decl assuming the TU
provided one; the TU's `extern int func_80143C74(short *, int);` is at L5082,
~180 lines BELOW the splice at 4901, so the identifier went undeclared.
Grep the TU for the symbol and compare line numbers with the stub line first.
MY OWN §136a VIOLATION, recorded: the blocker-capture filtered the build log for
`error|conflicting|undefined reference` and reported "NO COMPILE ERROR" on a
build that was failing with `redefinition of struct PW8017C290` and
`'func_80143C74' undeclared` — neither phrase matched. A narrow keyword filter is
exactly how a real error goes unseen, which is the thing §136a exists to say.
Widened to keep any line naming a source position.
Drew T
138e21c7d4