ci: restore the Zig drift leg -- gen/zig committed again, 68/68 zig-ast-check clean - #322
Merged
Conversation
…st-check clean The gen-zig validity campaign (t27#1910, closed by #1911/#1915/#1917/#1918 plus tri-net's spec legalizations #310/#321) took the backend from 66/68 invalid to 0/68. gen/zig/ returns with all 68 files (each validated with zig ast-check 0.15.2), and spec-drift-guard's Zig leg is back: byte-exact diff against 't27c gen' built from upstream master (no formatter in the Zig path, so no fmt-vs-drift contradiction). Two backends now under the required drift gate. gen/ additions are t27c generations (L2 bypassed per the guard's fix path). Co-Authored-By: Claude Fable 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
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.
Finale of the gen-zig validity campaign (t27#1910, now closed): four upstream PRs (t27#1911/#1915/#1917/#1918) plus tri-net's spec legalizations (#310/#321) took the Zig backend from 66/68 invalid to 0/68. This PR commits gen/zig/ back (all 68 files, each
zig ast-check-clean under 0.15.2) and restores spec-drift-guard's Zig leg: byte-exact diff againstt27c genbuilt from upstream master -- the Zig path has no formatter, so the fmt-vs-drift contradiction that killed the old Rust leg does not apply here.The repo's SSOT discipline now covers TWO generated backends under the required drift gate; the C leg remains out pending its own validity sweep.
🤖 Generated with Claude Code