required_floor: admit test.claim.seed_growth_admission_witness to the required gate

[gunbai-bot]

Operator ruling (escalation msg_341a9785, approved 2026-10-03): admit test.claim.seed_growth_admission_witness to v2.workflow.required_floor required_gate_authored_modules so the seed-growth roster's duplicate-key and well-formed checks (and the addition/staleness join) execute at merge. Admitted at exact module grain, not a family prefix.

Derived artifacts: regenerated by the CI generated lane's drift repair if any shift; the floor's per-identity dispositions on this head are the evidence that the witness is planned and green. Enrolment margin to be read from this PR's floor run.

🤖 Generated with Claude Code

[gunbai-bot]

Floor on 42e19c7 showed what admission is for: three claims red on main (the duplicate-key check: eval_match/match_pattern rostered by both the kernel-grounding and interpreter-eval-correctness rows) and the staleness claim over budget (74,485 steps). Fixed in the next commit: one row per declaration; the staleness claim supplies its roster via the new seed_growth_stale_over, with the real-roster path still executed by a_live_roster_declaration_is_not_reported_stale. No debt row added.

[briansrls]

Blocking control gap: the split preserves the generic staleness relation, but it no longer discriminates that the production wrapper seed_growth_stale_justifications is bound to the complete real roster. The new bounded claim calls seed_growth_stale_over directly with a synthetic two-row roster. The surviving real-roster claim passes live_items = seed_growth_roster_all_declarations() and expects zero stale; that would also pass if seed_growth_stale_justifications accidentally used [] or any strict subset of the real roster. The old over-budget negative case was the only control that made an empty/subset wrapper red.

Please add a bounded real-roster negative control, split/chunked if necessary, or change the construction so an incomplete roster binding is unwritable. It should exercise seed_growth_stale_justifications (or structurally establish its exact complete-roster binding), not only the parameterized helper. Do not restore the over-budget monolithic claim; no debt row is needed for a bounded split.

The exact authored-module admission, the post-#13100 single homes for eval_match/match_pattern, and the rest of the change look sound.

[briansrls]

APPROVE at exact head d4f0cdb. The prior completeness gap is closed. seed_growth_stale_declarations is now the production binding to seed_growth_roster_all_declarations, while seed_growth_stale_justifications only renders those declaration refs to keys. The new required-floor claim drives a rogue live population through that production binding and requires one stale declaration per real roster row, so an empty or strict partial binding reds; the existing all-live claim covers the zero-stale arm. The exact-head floor planned and passed the claim within budget with FloorClean and zero over-cost, and all four checks are green. Queue through the merge queue.