Brummel
8301ca3ee8
Forward-fix on5b66de7, prompted by plan-recon for intrinsic-bodies.2. Two spec-vs-reality gaps in the .2 (migration + lock) sections, both caught before the .2 plan was written: 1. Count. The spec said "18 dummy bodies" migrate to (intrinsic). That conflated the INTERCEPTS entry count with authored prelude bodies. Reality: examples/prelude.ail carries 13 authored dummy bodies — the 7 Eq/Ord instance methods (eq Int/Bool/Str/Unit, compare Int/Bool/Str) + the 6 float_* free fns. The registry has 19 entries (18 legacy + the .1 `answer`); the other 6 are not prelude dummies. 2. The strict bijection cannot hold. lt__Int/le__Int/gt__Int/ge__Int/ ne__Int (5 INTERCEPTS entries) intercept the monomorphised __Int specialisations of the polymorphic free fns lt/le/gt/ge/ne, which carry REAL bodies in the prelude (ne = (app not (app eq x y)); the four ordering helpers are (match (app compare x y) ...)). Those bodies are honest and live — lowered for every non-Int instantiation; only the Int specialisation is intercepted for a faster direct icmp. They are an optimisation class, not a compiler-supplied-body class: no lie, no source body to replace, no (intrinsic) marker. A strict bijection over all INTERCEPTS entries would be red for these 5. Corrections: - § Architecture point 6: 13 authored prelude sites (named), with the 5 icmp-family + `answer` explicitly listed as non-prelude / not migrated and why. - § Architecture point 7: the pin splits the registry into intrinsic-backed (13 prelude markers + answer = 14) and optimisation-only (the 5 *__Int, an explicit documented allowlist). The bijection holds over the intrinsic-backed class only; the pin loads the workspace + monomorphises to recover mangled names for the marker direction. - § Architecture point 8: reframed from "dead-path removal" to "dead-path confirmation" — .1's intercept-by-name already bypasses the dummy body before lower_term sees it (committed reality at52ff873), so .2 confirms no path lowers an intercepted body and deletes stale comments; the .1 Term::Intrinsic escape-guards stay. - § Components + § Testing: the two moving hash pins named (prelude_module_hash_pin.rs; mono_hash_stability.rs's 6 eq/compare pins move, its 4 show pins do not); hash_pin.rs carries no prelude-derived hash. IR snapshots do not change. Grounding-check PASS on all five corrected .2 claims against the shipped .1 baseline (count, the 5 real-bodied helpers, the three hash pins' behaviour, the already-dead path, the bijection-pin pipeline reachability). No ail/ail-json/ll fenced block changed — parse-gate a documented no-op for this revision. The deeper observation this surfaced — that INTERCEPTS conflates two concepts (compiler-supplied bodies vs. optimisation of a real body) — is noted but NOT resolved here; splitting the registry is out of scope for intrinsic-bodies and would be its own milestone.