Repository navigation
fix(ci): master green again -- stale corpus-ledger rows, census re-pin, t27mcp duplicate helpers (Closes #10171) - #10172
Merged
Merged
Conversation
…pin after pr-budget.yml (Closes #10171) Corpus ratchet: #10101 (seven igla/coder specs) and #10095 (nn/attention) now pass every phase; their rows are dropped and the cap follows 81 -> 73. Re-pinned: bench_proxy 738 -> 696, prm 521 -> 520, benchmark 315 -> 319 (bdd-block-fallback only: #10101 lengthened then-conditions in BDD blocks the parser already skips). Census: #10087 added pr-budget.yml. workflow files 66 -> 67, jobs 87 -> 88, run steps 313 -> 314, bash steps 292 -> 293, path-not-quiet 198 -> 200. Re-pinned with tri census pin --bless. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 18, 2026 02:44
…cond copy (Refs #10171) #10157 landed examples.t27 with byte-identical find(), has() and NO_POS from check_hints.t27, so duplicate-bodies on master reports two new groups. examples.t27 now imports t27mcp::check_hints. gen-c still emits both definitions in the one C file the wasm build compiles; 8/8 tests, 0 vacuous. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
changed the title
This was referenced Oct 18, 2026
Closed
This was referenced Oct 18, 2026
Contributor
This was referenced Oct 18, 2026
…check_hints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-10-18 03:47:25 UTC
Summary
Seal Status
|
gHashTag
added a commit
that referenced
this pull request
Oct 18, 2026
…and refuses (Closes #10204) specs/ci/suite_ledger_steward.t27 decides, per corpus-ledger row and per master run, what a steward may write to docs/reports/suite_expectations.json: DROP a row whose spec passes, REPIN a discard pin that fell, lower the gate-failure pin and the cap to the count. It refuses a new failure, a moved or expired row, any rise, a missing reading, an unpinned or self-inconsistent row, a cap rise and a drop flood. A refused row stays as master has it and the rest is applied (#10192's rule). Tests pinned on #10172, #8345, #7804, #6437, #9281, #8823 and #5497. specs/jobs/suite_ledger_steward.t27 is the job card. Seals written by t27c on the Railway lab. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 18, 2026
…and refuses (Closes #10204) (#10208) specs/ci/suite_ledger_steward.t27 decides, per corpus-ledger row and per master run, what a steward may write to docs/reports/suite_expectations.json: DROP a row whose spec passes, REPIN a discard pin that fell, lower the gate-failure pin and the cap to the count. It refuses a new failure, a moved or expired row, any rise, a missing reading, an unpinned or self-inconsistent row, a cap rise and a drop flood. A refused row stays as master has it and the rest is applied (#10192's rule). Tests pinned on #10172, #8345, #7804, #6437, #9281, #8823 and #5497. specs/jobs/suite_ledger_steward.t27 is the job card. Seals written by t27c on the Railway lab. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 18, 2026
…loses #10303) Master's cli-tri step "No census moved without saying so" has been red since 834f258, because #10283 moved two pinned censuses without re-blessing them. That was my miss. Re-blessed with `tri census pin --bless` on the Railway lab, from master dc4ea95. What moved, and why: - gates shell, jobs 88 -> 89: #10283 added the claw-t27f job to gate-topology.yml. - gates shell, run steps 314 -> 316 (runner-named 293 -> 295): the claw-t27f job's steps, as of #10299, which made the check-run POST plus one PATCH per further annotation batch. - gates quiet, quiet-shape steps 32 -> 33, file-existence guards 9 -> 10, variable-in-path 6 -> 7, named-but-not-quiet 200 -> 204: the same job.s steps. No other workflow changed since the last bless, so every moved line comes from gate-topology.yml No other workflow changed between the last bless (290ff17, #10172) and dc4ea95. `tri census pin --gate` exits 0 after the re-bless. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 18, 2026
…loses #10303) Master's cli-tri step "No census moved without saying so" has been red since 834f258, because #10283 moved two pinned censuses without re-blessing them. That was my miss. Re-blessed with `tri census pin --bless` on the Railway lab, from master dc4ea95. What moved, and why: - gates shell, jobs 88 -> 89: #10283 added the claw-t27f job to gate-topology.yml. - gates shell, run steps 314 -> 316 (runner-named 293 -> 295): the claw-t27f job's steps, as of #10299, which made the check-run POST plus one PATCH per further annotation batch. - gates quiet, quiet-shape steps 32 -> 33, file-existence guards 9 -> 10, variable-in-path 6 -> 7, named-but-not-quiet 200 -> 204: the same job's steps. No other workflow changed since the last bless, so every moved line comes from gate-topology.yml. No other workflow changed between the last bless (290ff17, #10172) and dc4ea95. `tri census pin --gate` exits 0 after the re-bless. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 18, 2026
…loses #10303) (#10304) Master's cli-tri step "No census moved without saying so" has been red since 834f258, because #10283 moved two pinned censuses without re-blessing them. That was my miss. Re-blessed with `tri census pin --bless` on the Railway lab, from master dc4ea95. What moved, and why: - gates shell, jobs 88 -> 89: #10283 added the claw-t27f job to gate-topology.yml. - gates shell, run steps 314 -> 316 (runner-named 293 -> 295): the claw-t27f job's steps, as of #10299, which made the check-run POST plus one PATCH per further annotation batch. - gates quiet, quiet-shape steps 32 -> 33, file-existence guards 9 -> 10, variable-in-path 6 -> 7, named-but-not-quiet 200 -> 204: the same job's steps. No other workflow changed since the last bless, so every moved line comes from gate-topology.yml. No other workflow changed between the last bless (290ff17, #10172) and dc4ea95. `tri census pin --gate` exits 0 after the re-bless. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #10171
#10160 fixed the two master reds it targeted, but by the time it merged two more had landed. As a result, every open PR still inherits
Corpus ratchet,cli-triandduplicate-bodiesred.What changes
docs/reports/suite_expectations.json:specs/igla/coder/*from spec(igla): make the nine IGLA CODER specs compile and pass with 0 vacuous (Closes #10075) #10101 andspecs/nn/attention.t27from spec(nn): make attention.t27 compile and pass with 0 vacuous tests (Closes #10094) #10095.bdd-block-fallbackchannel. spec(igla): make the nine IGLA CODER specs compile and pass with 0 vacuous (Closes #10075) #10101 lengthenedthenconditions inside given/when/then blocks, and the parser already skips those blocks wholesale. Both moves are recorded in_why_entries_fell/_why_entries_rose, and the existing history is kept. This is a hand edit, because--bless-expectationsrewrites those notes away.tools/census/quiet.txt,shell.txt: re-pinned withtri census pin --bless. gate(policy): wire pr_budget.t27 into a pull_request_target gate -- draft the 21st open PR, promote held drafts, exempt queen-* (Closes #10074) #10087 addedpr-budget.yml(1 job, 1 run step). The moved numbers:specs/t27mcp/examples.t27: specs/t27mcp: land examples.t27 and spec_brief.t27 on master #10157 landed it with byte-identical copies offind(),has()andNO_POSfromcheck_hints.t27, soduplicate-bodiesreports two new groups on master. It now doesuse t27mcp::check_hints;instead.t27c gen-cstill emits both definitions in the single C file the wasm build compiles, andzig cc -csucceeds.dupe_scan: no new duplicate body.Evidence (Railway lab)
t27c suite --ratchet --corpus-only:specs/tri/t27b/conformance/verilog_odd_cast.t27 [parse]. It comes from the lab's binary, which predates t27c: accept uN casts, 1 <= N <= 64, decided in int_type_names.t27 (Closes #10072) #10084 (the uN casts that spec exercises). CI builds master's t27c and reported 0 unexpected failures on fix(ci): master green -- rust_convert CSE hoist, mesh crypto mismatch, stale type row (Closes #10158) #10160.tri census pin --gate: passes after the bless.🤖 Generated with Claude Code