MQ: re-state two silently-red v2.test claims against landed shapes (structured body signature, wall root)

[gunbai-bot]

Second PR of the MQ lane (parent gentle-koi-724). It re-states two of the #12860 v2.test. silent reds against the shapes that landed, deletes those two identities from gunbc.rung_drop_amendment v2_test_family_reds_measured_outside_the_gate (and from its docs/design-rung-drops.md projection). The three service rows and the qualified-site field cell were landed by #12894; the call-position cells belong to bold-crane-252's walker retirement.

claim	turned red at	class	fix
manual.structured_body_dispatch structured_body_produce_subsumes_add_table	not bisected	C, old shape	the fixture fix (dag_add_arrow_signature_node built through declared_signature) landed independently on main in #12770; this PR now carries only its amendment-row deletion
name_resolve.test_code_reference_wall supplied_root_is_what_normalize_emits_holds	the root diverged in two places (not bisected; the first is probably #12785)	C, old shape	the supplied NORMALIZED root carried resolve's bound bool_node_symbol in type positions, but normalize emits the spelling Bool, so it now supplies ^Bool. It also supplied peer_leaf's body shared_fixture() as a bare atom. Normalize lowers that to a zero-argument call, so it is now built by wall_call, which calls normalize's own constructor v2.compiler.body_lowering_fold body_lower_transform_call

Also deleted (red on main since #12876, in the same file): name_resolve.test_code_reference_wall a_parameter_default_is_refused_at_parse_holds asserted that a parameter default fails at parse. #12876 gave defaults a production, so the source now parses, and lowering refuses it with one typed reason. That fact is owned by #12876's v2.test.claim.parse.default_value a_parameter_default_refuses_at_the_default_holds. A re-statement here would have been that control a second time, and as a new witness it measured 114,161 eval steps against the 72,300 budget, so the floor refused it. The row is deleted and the wall's comment cites the owning control.

Discrimination: for each claim, the fixture before this PR is the mutation, and it is red. The remaining 15 claims of the wall file stay green with the new fixture, so they do not depend on the old bound-symbol shape.

Not in this PR: emit.rust_variant_construct_emit x2. Two-point check: PASS at 9ce0394, FAIL at #12397. The arm body is the pattern binder v, and before #12397 it was minted as a literal that happened to print v. The emitter projects arm bodies under arrow-parameter scope only. That is a producer gap, so the fix is a separate PR3 (approved by gentle-koi-724) in which target_model consumes resolve's binder scope. Its two rows stay in the amendment until then.

Evidence: remote claim_batch at the final head, file by file: test_code_reference_wall 15/15, structured_body_dispatch 4/4, service_declaration_lowering 14/14, qualified_site_enumerator_differential 2/2 (35 PASS, 0 FAIL; the deleted row is the 36th).

🤖 Generated with Claude Code