The RUNTIME_EXEMPT landing (b82dc88) pushed runtime_registry.rs to 941
lines past the 850 cap and its post-check missed the arch tier — caught
one slice later by the full-suite re-run. Fix is structural, not a cap
raise (this file grows a justified row per corpus stone; a raise would be
a ceiling): the single-file test becomes tests/runtime_registry/{main.rs
30, registry.rs 733, coverage.rs 202} — pure motion, every doc comment
and test name verbatim; cargo keeps the same target name. registry.rs
sits above the 700 target at its structural floor (the const body + its
per-entry docs alone are 726 lines) with 14% headroom, flagged honestly.
R3's walk was already recursive — no scan extension needed, no gate
escape. Verified first-hand: arch 22/22 incl. r3 green, runtime_registry
green, fmt 0, clippy -D 0.

@@ -0,0 +212,4 @@
+                    pat,
+                    Value::Int(pattern.len() as i64),
+                    sub,
+                    Value::Int(body.len() as i64),

@@ -0,0 +133,4 @@
+        .arg("-d")
+        .arg(binary)
+        .output()
+        .expect("spawn `objdump -d`");