Skip to content

ci: restore the Zig drift leg -- gen/zig committed again, 68/68 zig-ast-check clean - #322

Merged
gHashTag merged 1 commit into
mainfrom
ci/restore-zig-drift-leg
Aug 8, 2026
Merged

ci: restore the Zig drift leg -- gen/zig committed again, 68/68 zig-ast-check clean#322
gHashTag merged 1 commit into
mainfrom
ci/restore-zig-drift-leg

Conversation

@gHashTag

@gHashTag gHashTag commented Aug 8, 2026

Copy link
Copy Markdown
Owner

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 against t27c gen built 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

…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>
@gHashTag
gHashTag merged commit 8ac9abc into main Aug 8, 2026
4 checks passed
@gHashTag
gHashTag deleted the ci/restore-zig-drift-leg branch August 8, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant