The ONLY detector for the R22 rename-drift failure mode (a symbols.us.txt rename leaves a
func_<ADDR> ref dangling in committed src; a clean rebuild fails, an incremental build masks it
with a stale .o — undetected Phase 21→23). It was RED (262 false positives) and UNWIRED. The
audit's 3 blind spots, all fixed:
#1 globbed src/**/*.c only -> now ALSO scans src/shared/*.h, where engine_core.h's 10k+ func_/D_
tokens live and one dangling ref breaks EVERY clean build at once (negative-control-proven:
an injected bare ref in a shared header IS flagged).
#2 read 2 of 138 symbol files -> now reads every REAL stacked file (config/symbols*.txt), and
correctly EXCLUDES the R13 proto files (never stacked into a build; would invent phantoms).
#3 no __asm__("label") model -> ALL 262 false positives were this class: engine_core.h binds
func_8005C324 to memcpy via `... __asm__("memcpy")`, so the ref emits the LABEL and resolves
at link regardless of the rename. asm_labeled_addrs() now recognizes it.
VERIFIED: green on HEAD (exit 0); negative control (inject a bare func_800d1bd8 -> DsMix in a
shared header) FLAGS it (exit 1) then clears on removal — detection intact, not trivially green.
Wired as a fail-closed gate in `make report` (make -n confirms), beside dedup_integrate --check.
No src/build change (report-time integrity gate) -> the byte-identical build is unaffected.
Drew T
d7d2613ae6