Repository navigation
Repair the two main reds the Wave A restore surfaced (#8503 fallout) - #8571
Merged
Merged
Conversation
Both failures are latent defects the quarantine was hiding, not defects in #8503: the two witnesses sat under long/ while main moved out from under their assertions, and un-quarantining them made the divergence executable. 1. test.claim.live_deploy.emit.witness_scripts_stay_within_ci_runner_grants pinned the tree-sync ExecStart with the two-prefix exclude list. #8522 widened deployed_tree_excluded_prefixes to six prefixes and updated the two witnesses that were visible at the time (candidate_checkout_witness, live_deploy_unit_emission_oracle_witness); this one was in long/ and was not. The pin now transcribes the current six-prefix ExecStart, matching its two siblings. 2. v2.test.lens_inert_carrier.inert_carrier_test.inert_carrier_no_unrostered_or_stale #8413 landed the compute-fabric carriers; two of them — Attempt (product.fabric.execution) and Offer (product.fabric.supply) — are referenced only from fabric_terminal_contract_witness_test, so the live inert set went to 14 against a 12-row roster. Both get a roster row naming the consumer they await, under the existing row dissolution. Measured, not inferred: an independent reimplementation of compute_inert_carrier_data over the same corpus reproduces the 12 rostered names exactly and adds precisely Attempt and Offer. Verified by execution (claim_batch, both entries, this tree): src/v2/lens/inert_carrier_test.dag 4 PASS, 0 FAIL dag/test/claim/live_deploy/emit_test.dag 47 PASS, 0 FAIL The RED control for both is main itself: run 32290602208 fails exactly these two identities and nothing else (planned=9683 executed=9683 failed=2). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 task
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Aug 19, 2026
…tities from long-home prefixes Rebased Wave B derivation onto post-Wave-A/#8556/#8413/#8503/#8571 main and re-derived the candidate population from scratch (not reused): 101-file superset of long_home_prefixes() modules, minus four exclusion terms (falsifier_substrate_long_lane_rows narrowed to its correct 20-row block, explicit_witness_admissions 17, witness_deferral_freeze 129, and a newly discovered falsifier_rehomed_bin_wet_rows function-grain exclusion covering 2 files), minus standing exclusions (rust_test_fixtures_import_closure_witness_test.dag, extdeps_scope_placement_gate_seed_runner_loudness_witness_test.dag), yielding 13 modules / 131 identities. Reconciled 336 -> 131 by category against the prior baseline with no "anything else" bucket (202 Wave A restorations + 3 standing exclusions + 131 = 336), confirming no over-exclusion. Of the 13 candidates, transport_script_wall_compile_red_test.dag is held back per royal-hawk-392's direction: it is a measured specimen of the compile_dag_rust_emit_check floor-run first-toucher attribution class (1394ms -> 48963ms, 35x, same content, different execution order) now dispatched as its own lane rather than restored here — restoring it risks tripping the CPU safety deadline on this run (a hard interrupted_before_verdict failure, not telemetry) and would perturb first-touch cost attribution for every other row in the same required_floor run. It is not excluded for being slow. where_refinement_enforcement_witness_test.dag IS included: its two BUDGET-REFUSED measurements are non-blocking over_cost_line_diagnostic telemetry under current admission-bar policy, not exclusion grounds, distinct from completed_over_cost_requirement (which stays at 0 in the bar). Renamed the 12 surviving modules out of their long-home path/name prefixes and updated the load-bearing entry:/backing_entry: path citations in their consumers (commit_workflow.dag, self_host emit-coverage/wet-receipt/routing carriers, witness_admission_test.dag) plus prose_row_frontier.dag and the remaining long-lane cross-references among wave1_gate1_d fixtures. Note for future derivations: prior-restoration history (Wave A's own reverts of transport_script and where_refinement for measured cost) is invisible to every roster this algorithm reads — it exists only in git commit history (43693a8), never in a current-tree authority. Checking it before renaming avoided burning the one sanctioned required_floor run rediscovering it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T14grdwVcA5HutxDKrm5qF
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both failures are latent defects the quarantine was hiding, not defects in
#8503: the two witnesses sat under long/ while main moved out from under
their assertions, and un-quarantining them made the divergence executable.
test.claim.live_deploy.emit.witness_scripts_stay_within_ci_runner_grants
pinned the tree-sync ExecStart with the two-prefix exclude list. Widen the deployed-tree exclusions to the host-state prefixes rsync was shipping #8522
widened deployed_tree_excluded_prefixes to six prefixes and updated the
two witnesses that were visible at the time (candidate_checkout_witness,
live_deploy_unit_emission_oracle_witness); this one was in long/ and was
not. The pin now transcribes the current six-prefix ExecStart, matching
its two siblings.
v2.test.lens_inert_carrier.inert_carrier_test.inert_carrier_no_unrostered_or_stale
Compute fabric wave 1: terminal contract and budget as a lease over money #8413 landed the compute-fabric carriers; two of them — Attempt
(product.fabric.execution) and Offer (product.fabric.supply) — are
referenced only from fabric_terminal_contract_witness_test, so the live
inert set went to 14 against a 12-row roster. Both get a roster row
naming the consumer they await, under the existing row dissolution.
Measured, not inferred: an independent reimplementation of
compute_inert_carrier_data over the same corpus reproduces the 12 rostered
names exactly and adds precisely Attempt and Offer.
Verified by execution (claim_batch, both entries, this tree):
src/v2/lens/inert_carrier_test.dag 4 PASS, 0 FAIL
dag/test/claim/live_deploy/emit_test.dag 47 PASS, 0 FAIL
The RED control for both is main itself: run 32290602208 fails exactly
these two identities and nothing else (planned=9683 executed=9683 failed=2).
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com