R4 (Hookify autoloader consumer hook missing) is a canonization-blocke…
Decision
R4 (Hookify autoloader consumer hook missing) is a canonization-blocker for Bible v19.1.2, same severity class as R1/R2/R3. Do NOT canonize until all four residuals close. Mitigation for anchoring-bias flag: R4 is objectively less urgent than R1 (R4 fail-mode is narrower — Layer 1 CLAUDE.md rule covers the gap in practice) but the “bible must match reality” first-principle still forces block — Contract § 12 layer_2_hookify_autoloader: true currently reads true, behaves false.
Rationale
Same structural pattern as R1: data-side artifact created, execution-side wiring absent. Audit methodology gap exposed — Finding 2 was accepted-closed on file-existence evidence without probing end-to-end wiring. Codifying “file-existence ≠ wiring” as a new drift class is itself a bible refinement. Confidence high because (a) mechanically verified via grep for registry consumers returning zero, (b) parallel to R1 is structural not cosmetic, (c) bible’s own Contract § 12 self-contradicts current state. Anchoring bias acknowledged: R4 is lower urgency than R1 because Layer 1 behavioral rule masks the gap — but “mask” is not “fix” for a bible that other MCPs will replicate from. Rollback path: reversible — bump bible to v19.1.3 post-R1-R4 closure.
Alternatives Rejected
Outcome
Pending