Delete 18 unreachable pub fns from cli_run.rs

[briansrls]

Stacked on #8514 (integration/manifest-cut). −320 lines.

18 pub fns in cli_run.rs with zero call sites in Rust, zero references in the .dag corpus, and no host-builtin registration.

Discriminating control (a census without one proves nothing): known-live host builtins score dispatch=2–3 / dag=3–81 against the interpreter dispatch table and the corpus; all 18 candidates score 0 / 0.

Scope correction — the first census was wrong

The initial scan found 36 candidates. Half of them carry #[cfg(feature = "test_hooks")] or #[cfg(any(test, feature = "interp_test_witness"))] and are conditionally compiled test hooks, not dead code — a call-site scan cannot see that, because their callers sit behind the same feature gate. Those 18 are kept, and cargo check --features test_hooks is now evidence in this PR rather than an assumption.

The first deletion script was also mechanically wrong, and it is worth naming rather than quietly fixing: it walked back over // comments but stopped at attribute lines, so deleting a function left its #[cfg(...)] orphaned, which then bound to the next function and made it conditional. That produced three cannot find function in this scope errors against symbols still present in the file. The span finder now walks comments and attributes together, counts braces instead of guessing at the first column-0 }, and refuses if any span contains another top-level item.

Why these could accumulate unseen — reported, not fixed here

cargo check -p v1-compiler --all-targets does not compile on main: compiler_tests.rs:1615 imports crate::v1_tests_claim_caret_parse_smoke_test, a module deleted by the #8146 suite cutover. The crate's test targets have not built since, so nothing flagged these as unused — and -D warnings on --bin cannot see an unused pub fn in a lib.

That is a separate defect with its own remedy and is not addressed by this PR.

Verification

• RUSTFLAGS="-D warnings" cargo check -p v1-compiler --lib --bin claim_executor — clean
• cargo check -p v1-compiler --lib --features test_hooks — 0 errors (the gated 18 still compile)
• cargo fmt --all --check — clean
• Floor run pending; a dead-code deletion should not move the floor, which is exactly the claim worth executing rather than assuming, since .dag can reach host functions in ways a Rust grep cannot.

🤖 Generated with Claude Code

[gunbai-bot]

Floor verified on srv2 (full corpus, unshrunk):

planned=9135 executed=9135 terminal=9135 passed=8829 known_red_held=302 failed=0 stale_quarantine=4 budget_refused=0 host_tool_unresolved=0

failed=0. Two caveats stated rather than smoothed over:

• claims=9135 vs the 9122 I recorded on 8b20599960 is base drift — this PR deletes only Rust pub fns and cannot change .dag witness discovery. The bar I used is failed=0, not a count match against an older commit.
• known_red_held=302 / stale_quarantine=4 (vs 306/0 in CI) is a pre-existing srv2 host difference, reproduced on unmodified code before this branch existed. It is why the process exits 1; it is not this change.

— sent from fierce-ram-721