Skip to content

ratchet: re-pin igla race backend/rtl discard counts moved by #10689 (Closes #10695) #10699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gHashTag merged 2 commits into from
Oct 18, 2026
Merged

ratchet: re-pin igla race backend/rtl discard counts moved by #10689 (Closes #10695) #10699

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5dca840
ratchet: re-pin igla race backend/rtl discard counts moved by #10689 …
gHashTag Oct 18, 2026
fc48efd
t27f skill: run the corpus ratchet when moving text between specs (Re…
gHashTag Oct 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .claude/skills/t27f/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,13 @@ Traps from this tick (ffmpeg on the lab):
import, and nothing was copied. Then compare `test-report` against **master**, not against
"passes". The igla race specs are BLOCKED at a zig error on master, so the right claim is
"the same verdict as before", not "the tests pass".
Then run the corpus ratchet on the lab (`t27c suite --repo-root . --ratchet --corpus-only`).
`test-report` cannot see text moving between two specs that the ledger pins. #10689 moved an
invariant the parser discards, so 15 tokens moved from `rtl` to `backend`. The ratchet went
red (`DISCARD WORSENED` +15 on one spec, `IMPROVED` -15 on the other), and the gate merged it
red anyway (#10695, fixed in #10699). To re-pin, run `--bless-expectations` to measure, then
copy only the moved numbers into master's file: the bless also deletes the
`_why_entries_fell` history field.
7. Before you open a PR that adds a spec, run `python3 tools/dupe_scan.py` on the lab. The
issue gate auto-merges non-draft PRs even when a check is red: #10681 merged with a copy of
`lit_len` that was red on `duplicate-bodies` until #10688. Reuse the existing body through
Expand Down
8 changes: 4 additions & 4 deletions docs/reports/suite_expectations.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,9 @@
"reason": "top-level drop-recovery discards tokens; parser reaches EOF so `parse` reports success (T42)",
"issue": 1959,
"expires": "2026-11-30",
"discard_tokens": 481,
"discard_tokens": 496,
"discard_by_channel": {
"bdd-block-fallback": 463,
"bdd-block-fallback": 478,
"stray-brace": 1,
"top-level-resync": 17
}
Expand Down Expand Up @@ -254,9 +254,9 @@
"reason": "top-level drop-recovery discards tokens; parser reaches EOF so `parse` reports success (T42)",
"issue": 1959,
"expires": "2026-11-30",
"discard_tokens": 628,
"discard_tokens": 613,
"discard_by_channel": {
"bdd-block-fallback": 594,
"bdd-block-fallback": 579,
"brace-body/in-fallback": 33,
"stray-brace": 1
}
Expand Down
Loading