Rung-drop amendment: count three silent v2.test emit round-trip reds (separate measurement)

dag/gunbc/rung_drop_amendment/v2_test_family_reds_measured_outside_the_gate.dag

@@ -13,5 +13,5 @@ data v2_test_family_reds_measured_outside_the_gate: RungDropAmendment = RungDrop
 
   later_event: "the srv1 probe of the withdrawn v2.test. family (neat-boar-16, scratch commit eff2d73b14 = main c95f906 plus the family, artifacts on branch artifact/v2-gate-probe) measured what this row's population holds for that family: 841 v2.test.* modules declaring 5,030 test fns at c29acd041e1 have no required route; with the family restored, 4,265 were planned, 4,192 passed, 17 reached no verdict (route gaps already rostered by v2.workflow.floor_route_gap), and 44 were red on main with no lane observing them. Preparation dominated, about 3,569 modules resolved and 3,096 s wall against about 101 s of claim evaluation, the shape of this row's 2026-09-19 nominal-roster cut, so the family stays out until the trigger below. One module, v2.test.claim.cargo_build_run_argv_witness, did not typecheck on main and refused the whole floor in strict preparation when the family was restored; gunbc#12860 repaired it" as NonEmptyStr,
 
-  bearing: "of the 44 measured red identities, those still red are named here with their owners, and each leaves this amendment's list when its fix lands, so restoring the family does not inherit them as silent reds. Owner deep-ferret-305 (floor lane), fixed by work item adhoc-e6c8990b-ccf: v2.test.claim.declaring_identity_spelling.production_ingest.matched_imported_kernel_type_position_is_absent_from_the_census_today (returned false); v2.test.claim.reference_derived_residency_reading.a_type_declaration_does_not_resolve_from_a_live_module_root_pending_11574 (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_holds_accepts (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_wrong_value_discriminates (returned false); v2.test.manual.program_assembly_multi_file.program_assembly_cross_file_import_assembles_holds (returned false); v2.test.manual.structured_body_dispatch.structured_body_produce_subsumes_add_table (returned false); v2.test.name_resolve.test_code_reference_wall.supplied_root_is_what_normalize_emits_holds (returned false); v2.test.parse.d5_expression_grammar_parse.cause_p_keyword_field_init_red_tokens_remain_holds (returned false); v2.test.parse.type_decl_modifier_g0_parse_probe.generic_param_publishes_the_generic_ident_class_holds (returned false). Owner calm-hawk-793 (typing/identity lane), measured red on main on 2026-10-01 while fixing the rows above and missing from the srv1 list: v2.test.manual.ingest_bridge.ingest_identity_coercion_accepts_source_present_in_authored_roster (returned false); v2.test.execution.infer_product_introduction.product_introduction_derives_fully_evidenced_products_holds (returned false). None is an expected-red row: that roster asserts the identity executes, and these do not while the family is outside the gate" as NonEmptyStr,
+  bearing: "of the 44 measured red identities, those still red are named here with their owners, and each leaves this amendment's list when its fix lands, so restoring the family does not inherit them as silent reds. Owner deep-ferret-305 (floor lane), fixed by work item adhoc-e6c8990b-ccf: v2.test.claim.declaring_identity_spelling.production_ingest.matched_imported_kernel_type_position_is_absent_from_the_census_today (returned false); v2.test.claim.reference_derived_residency_reading.a_type_declaration_does_not_resolve_from_a_live_module_root_pending_11574 (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_holds_accepts (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_wrong_value_discriminates (returned false); v2.test.manual.program_assembly_multi_file.program_assembly_cross_file_import_assembles_holds (returned false); v2.test.manual.structured_body_dispatch.structured_body_produce_subsumes_add_table (returned false); v2.test.name_resolve.test_code_reference_wall.supplied_root_is_what_normalize_emits_holds (returned false); v2.test.parse.d5_expression_grammar_parse.cause_p_keyword_field_init_red_tokens_remain_holds (returned false); v2.test.parse.type_decl_modifier_g0_parse_probe.generic_param_publishes_the_generic_ident_class_holds (returned false). Owner calm-hawk-793 (typing/identity lane), measured red on main on 2026-10-01 while fixing the rows above and missing from the srv1 list: v2.test.manual.ingest_bridge.ingest_identity_coercion_accepts_source_present_in_authored_roster (returned false); v2.test.execution.infer_product_introduction.product_introduction_derives_fully_evidenced_products_holds (returned false). Owner calm-fox-43 (grammar lane), measured red in a SEPARATE measurement from the srv1 probe: gunbc run --claim-run on main eb60ee176d0 on 2026-10-01 (remote 48GB runner), identical on main's grammar and on gunbc#12920, so not caused by that change; cause not yet derived: v2.test.execution.emit_ingest_grammar_relation_round_trip.same_grammar_parse_ingest_bridge_holds (returned false); v2.test.execution.dag_add_emit_round_trip.dag_add_domain_coerce_accepts_holds (returned false); v2.test.execution.dag_add_emit_round_trip.dag_add_domain_translate_accepts_holds (returned false). None is an expected-red row: that roster asserts the identity executes, and these do not while the family is outside the gate" as NonEmptyStr,
 }

docs/design-rung-drops.md

@@ -106,7 +106,7 @@ Producer: `tools.emission_entry_instrument::measure_entry_emission`
 
 **RUNG DROP, DECLARED (2026-08-29, the CI bankruptcy, operator ruling in session neat-tern-658).** PREVIOUS RUNG: mechanically preventable for every class the required run carried -- eight phases over two lanes, the floor folding every discovered witness (11,996 on the last green run) through a whole-corpus strict preparation, plus v2-emission, emit-compile, partition-crates and generated-artifact drift. TEMPORARY RUNG: mechanically preventable ONLY for what the static gate names -- parse, namespace-wave-admission, regen, generated-artifact drift, and a floor over `v2.workflow.required_floor` `required_gate_prefixes` prepared as that roster's import closure -- and MITIGATABLE for everything else: those witnesses and phases are still runnable (the floor with the gate widened, `claim_executor --required-v2-emission`, `--required-emit-compile`; and -- CORRECTED 2026-08-31, re-verified against main AFTER the generated-artifact partial climb below, because a drop whose stated mitigation cannot be executed is not mitigated but a rung-honesty defect in the drop row itself, and one cited as coverage -- NOT `--required-partition-crates`, which is ABSENT from claim_executor's argument parser: that build is projected by `gunbc.repo.repo_self_build` `repo_self_build_partition_crates_command`. `--required-generated-artifact` is absent from that parser too, and the climb below restores the CHECK without restoring that spelling, so the generated-artifact projection is regenerated through the .dag entry point `tools.generated_artifact_gate` `main_wet_one`, invoked per artifact path via `gunbc run` on a gunbc BUILT FROM SOURCE -- the installed binary predates the section 4c annotation channel and cannot parse the corpus. Both flag spellings went with this cut's deleted phases and the prose naming them was not updated, so this sentence recited two remedies nobody could run) and their receipts are produced only when someone runs them, so a regression there is caught at the next manual run, not at merge. REASON: the last green run was 87 wall minutes (`gh run view 33140387402`), strict preparation alone 27 of them on one core, against ~50 squash-merges a day; main sat red for fifteen consecutive runs on two integration collisions no PR could have seen (#9662), and the CI-cost lane's change-denominated selection did not land in time to prevent it. A gate no merge can wait for validates nothing, which is a lower rung than a small gate that runs. POPULATION: every witness outside the roster (reported per run as `declined_outside_required_gate` in the disposition TSV), the three deleted required phases v2-emission, emit-compile, and partition-crates, and the v1-compiler lib tests that carry the `live-corpus` ignore reason -- enumerated by `cargo test -p v1-compiler --lib -- --ignored --list` -- each of which prepares or builds over the live tree and is run only by the receipts lane; AND -- POPULATION AMENDED 2026-09-02, because this row was cited as coverage for a member it did not name -- every module OUTSIDE THE REQUIRED FLOOR GATE CLOSURE, which no required phase compiles at all: the floor prepares the import closure of `required_gate_prefixes`, not the corpus, so a module that no rostered prefix transitively imports is never checked by any required run, and a green required run has therefore never entailed that the corpus holds the floor. That member is a FOURTH thing the original population sentence did not name -- not a witness outside the roster, not a deleted phase, not an ignored lib test -- while the RESTORATION TRIGGER below already covers it verbatim (the whole corpus as its universe). The omission was a rung-honesty defect in THIS ROW rather than a missing class, so it is amended here instead of filed as a second row: two rows behind one trigger is the same single-authority fork this project rejects in every other subject, and the more dangerous form when the row is quoted as evidence of what CI checks. the first-ever CI run of `cargo test -p v1-compiler --lib` (run 33238828500) was cancelled by its own 60-minute timeout with 204 of 682 tests finished, which is how that class was measured into existence. The workflow's two-lane shape, the aggregate context, and the per-claim cost receipt are unchanged, and the drop is countable from that receipt every run. RESTORATION TRIGGER: the CAPABILITY of a required run whose population is DERIVED from the change -- the roadmap's 'decide what matters before paying to prepare everything' -- executing on the required path with the whole corpus as its universe; a widening of the static roster does not retire this row, it only moves the population. Widening the roster is a wall-clock decision priced by the cost receipt and recorded on the roster's own header. GENERATED-ARTIFACT PARTIAL CLIMB (2026-08-31): restoring generated-artifact drift widens the static required roster by one exact class and does NOT retire this drop; the population-derived restoration trigger has not fired. INCIDENT RECEIPT (2026-08-31), recorded because a drop whose population has demonstrably fired ranks differently for restoration than one that never has: the generated-artifact drift member produced a real stale artifact on main -- two correct regens composed a `docs/design-ledgers.md` missing the frontier-receipts projection of `gunbc.self_host_compile_phase_frontier`, with no conflict and no author error -- detected only sideways by an adjacent-diff review question, and bounded to exactly one file by a dispatched whole-population `main_wet` regen on pristine main (repair and measurement: PR #9804). The window between drift landing and detection is the cost this row's REASON accepted, now materialized once. INCIDENT RECEIPT (2026-09-02), recorded on the same principle as the one above -- a population that has demonstrably fired ranks differently for restoration than one that never has: a whole-corpus compile over dag plus src/v2 found 11 NON-EXHAUSTIVE MATCH SITES STANDING ON GREEN MAIN, closed variants that do not eliminate exhaustively, which is the ordinary compiler floor this document names first; every one of them sits in a module the gate closure never compiles, so no required run has ever been able to see them. Measured as the BASELINE arm of the nested-pattern exhaustiveness checker in gunbc#10028 (whose own change additionally exposes a larger population of ordinary floor defects that the OLD checker could not see -- that population is counted by that PR and its repair program, deliberately NOT transcribed here, because a number copied into this row rots the moment the instrument that produced it is re-run; it is not evidence about this gate in any case, since those sites were invisible to the CHECKER rather than to CI, and only the 11 that main already carries under today's checker measure what the gate does not compile). Those 11 are the first number anyone has put on the gap between main is green and the corpus holds the floor, and they are exactly the population this amendment names.
 
-AMENDED 2026-10-01: the srv1 probe of the withdrawn v2.test. family (neat-boar-16, scratch commit eff2d73b14 = main c95f906 plus the family, artifacts on branch artifact/v2-gate-probe) measured what this row's population holds for that family: 841 v2.test.* modules declaring 5,030 test fns at c29acd041e1 have no required route; with the family restored, 4,265 were planned, 4,192 passed, 17 reached no verdict (route gaps already rostered by v2.workflow.floor_route_gap), and 44 were red on main with no lane observing them. Preparation dominated, about 3,569 modules resolved and 3,096 s wall against about 101 s of claim evaluation, the shape of this row's 2026-09-19 nominal-roster cut, so the family stays out until the trigger below. One module, v2.test.claim.cargo_build_run_argv_witness, did not typecheck on main and refused the whole floor in strict preparation when the family was restored; gunbc#12860 repaired it; of the 44 measured red identities, those still red are named here with their owners, and each leaves this amendment's list when its fix lands, so restoring the family does not inherit them as silent reds. Owner deep-ferret-305 (floor lane), fixed by work item adhoc-e6c8990b-ccf: v2.test.claim.declaring_identity_spelling.production_ingest.matched_imported_kernel_type_position_is_absent_from_the_census_today (returned false); v2.test.claim.reference_derived_residency_reading.a_type_declaration_does_not_resolve_from_a_live_module_root_pending_11574 (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_holds_accepts (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_wrong_value_discriminates (returned false); v2.test.manual.program_assembly_multi_file.program_assembly_cross_file_import_assembles_holds (returned false); v2.test.manual.structured_body_dispatch.structured_body_produce_subsumes_add_table (returned false); v2.test.name_resolve.test_code_reference_wall.supplied_root_is_what_normalize_emits_holds (returned false); v2.test.parse.d5_expression_grammar_parse.cause_p_keyword_field_init_red_tokens_remain_holds (returned false); v2.test.parse.type_decl_modifier_g0_parse_probe.generic_param_publishes_the_generic_ident_class_holds (returned false). Owner calm-hawk-793 (typing/identity lane), measured red on main on 2026-10-01 while fixing the rows above and missing from the srv1 list: v2.test.manual.ingest_bridge.ingest_identity_coercion_accepts_source_present_in_authored_roster (returned false); v2.test.execution.infer_product_introduction.product_introduction_derives_fully_evidenced_products_holds (returned false). None is an expected-red row: that roster asserts the identity executes, and these do not while the family is outside the gate. The restoration trigger above stands whole.
+AMENDED 2026-10-01: the srv1 probe of the withdrawn v2.test. family (neat-boar-16, scratch commit eff2d73b14 = main c95f906 plus the family, artifacts on branch artifact/v2-gate-probe) measured what this row's population holds for that family: 841 v2.test.* modules declaring 5,030 test fns at c29acd041e1 have no required route; with the family restored, 4,265 were planned, 4,192 passed, 17 reached no verdict (route gaps already rostered by v2.workflow.floor_route_gap), and 44 were red on main with no lane observing them. Preparation dominated, about 3,569 modules resolved and 3,096 s wall against about 101 s of claim evaluation, the shape of this row's 2026-09-19 nominal-roster cut, so the family stays out until the trigger below. One module, v2.test.claim.cargo_build_run_argv_witness, did not typecheck on main and refused the whole floor in strict preparation when the family was restored; gunbc#12860 repaired it; of the 44 measured red identities, those still red are named here with their owners, and each leaves this amendment's list when its fix lands, so restoring the family does not inherit them as silent reds. Owner deep-ferret-305 (floor lane), fixed by work item adhoc-e6c8990b-ccf: v2.test.claim.declaring_identity_spelling.production_ingest.matched_imported_kernel_type_position_is_absent_from_the_census_today (returned false); v2.test.claim.reference_derived_residency_reading.a_type_declaration_does_not_resolve_from_a_live_module_root_pending_11574 (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_holds_accepts (returned false); v2.test.emit.rust_variant_construct_emit.rust_variant_construct_emit_wrong_value_discriminates (returned false); v2.test.manual.program_assembly_multi_file.program_assembly_cross_file_import_assembles_holds (returned false); v2.test.manual.structured_body_dispatch.structured_body_produce_subsumes_add_table (returned false); v2.test.name_resolve.test_code_reference_wall.supplied_root_is_what_normalize_emits_holds (returned false); v2.test.parse.d5_expression_grammar_parse.cause_p_keyword_field_init_red_tokens_remain_holds (returned false); v2.test.parse.type_decl_modifier_g0_parse_probe.generic_param_publishes_the_generic_ident_class_holds (returned false). Owner calm-hawk-793 (typing/identity lane), measured red on main on 2026-10-01 while fixing the rows above and missing from the srv1 list: v2.test.manual.ingest_bridge.ingest_identity_coercion_accepts_source_present_in_authored_roster (returned false); v2.test.execution.infer_product_introduction.product_introduction_derives_fully_evidenced_products_holds (returned false). Owner calm-fox-43 (grammar lane), measured red in a SEPARATE measurement from the srv1 probe: gunbc run --claim-run on main eb60ee176d0 on 2026-10-01 (remote 48GB runner), identical on main's grammar and on gunbc#12920, so not caused by that change; cause not yet derived: v2.test.execution.emit_ingest_grammar_relation_round_trip.same_grammar_parse_ingest_bridge_holds (returned false); v2.test.execution.dag_add_emit_round_trip.dag_add_domain_coerce_accepts_holds (returned false); v2.test.execution.dag_add_emit_round_trip.dag_add_domain_translate_accepts_holds (returned false). None is an expected-red row: that roster asserts the identity executes, and these do not while the family is outside the gate. The restoration trigger above stands whole.
 
 ### Non-literal kernel-String refusal at the structural text boundary — declared 2026-08-30