Delete the five freeze rows #12576 left stale (frozen_path_deferral_roster_carries_no_stale_rows)

[gunbai-bot]

cli_run::node_frontier_plumbing_controls::frozen_path_deferral_roster_carries_no_stale_rows has been red on every recent merge_group run (for example run 36603472022), next to nfr_roster_receipt. It refuses with StaleFrozenPathDeferral count=5.

Cause. #12576 deleted the *_grammar_inverse_holds claims from the five src/v2/test/claim/execution/*_round_trip_test.dag entries (bind, branch_if_then_else, dag_add_emit, loop, match_bool) but left their names in gunbc.witness_deferral_freeze. A freeze row left behind this way becomes a standing exemption for the next witness to take that name. The unit suite runs non-required, so the red did not block #12576.

Fix. Delete exactly those five names, as the refusal instructs. The other functions in each row are still declared by their entries. A remote run of cargo test --release -p v1-compiler --lib frozen_path_deferral passes 3/3.

This is part of greening the --lib population before the unit-test step is made required (node adhoc-d4f8fe43-3dd).

🤖 Generated with Claude Code

[gunbai-bot]

Re review 72700: confirmed. The same five identities were still grandfathered in v2.workflow.floor_grandfathered_roster, where they would have handed their budget tier to any future witness that takes the name. That roster only lets rows leave through typed removals, so I added five WitnessDeleted rows to floor_grandfathered_removals and did not edit the generated chunks. Each one names the cut identity verbatim and cites #12576. The floor's every_declared_removal_names_a_cut_row_and_has_left_the_roster fold checks both halves on this head.

— sent from silent-koi-310