Skip to content

specs(golden): reach 100% coverage — fix [str]->[N]str types, add negative-control tests - #13314

Merged
gHashTag merged 1 commit into
masterfrom
fix/golden-coverage-100pct
Nov 7, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/golden-coverage-100pct

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 7, 2026

Copy link
Copy Markdown
Collaborator

All 7 golden specs now pass coverage: tests 7/7, vacuous 7/7, negative-control 7/7, seal 7/7, issue 7/7, gaps 0, coverage 35/35.

Fixes:

  • [str] arrays → [N]str fixed-size arrays (Zig codegen doesn't support [][]const u8 array initialization)
  • Removed ;} after test blocks (current parser rejects it)
  • Added negative_control_refutes_* tests to each spec
  • Re-sealed all 7 golden specs

Closes #12913

…;} syntax, add negative-control tests

All 7 golden specs now pass coverage: tests 7/7, vacuous 7/7,
negative-control 7/7, seal 7/7, issue 7/7, gaps 0, coverage 35/35.

Fixes:
- [str] arrays → [N]str fixed-size arrays (Zig codegen doesn't support
  [][]const u8 array initialization)
- Removed ;} after test blocks (current parser rejects it)
- Added negative_control_refutes_* tests to each spec
- Re-sealed all 7 golden specs

Closes #12913
@gHashTag
gHashTag merged commit b93cee0 into master Nov 7, 2026
32 of 36 checks passed
@gHashTag
gHashTag deleted the fix/golden-coverage-100pct branch November 7, 2026 20:51
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-07 20:54:10 UTC

Summary

Status Count
Total Open PRs 44
PRs with Failing Checks 42
PRs with All Checks Green 2
READY 2
FAILING 42
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b882be1e4933 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

gHashTag added a commit that referenced this pull request Nov 7, 2026
…13303)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag added a commit that referenced this pull request Nov 8, 2026
…27b compiles it (Refs #13303)

#13314 left `pub const MECHANISM_DESCRIPTION : str = [` (three strings
typed as one str). t27b refuses it: the native ratchet reports
`golden_oracle.t27: ledger pass, now blocked: ExprArrayLiteral` on
master 4dfdd26 and on #13305 head 37c0665. The 4cfd2f2 text,
which the ledger records as a pass, had `[3]str`. Only that token
changes; every test of master's text stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag added a commit that referenced this pull request Nov 8, 2026
 (Closes #13303) (#13305)

* specs: restore golden and shootout syntax undone by #12996/#12997 (Closes #13303)

The #12997 and #12996 merges took the old side of an add/add conflict
and brought back text of 11 specs that no longer parses (`};` after
test blocks, `[...];` after const arrays, `str = [` for string arrays).

This restores the text each spec held at 28fd63d, which equals
4cfd2f2 for specs/golden and 53cb6e6 for specs/tri/shootout.
The set of test, invariant and assert lines is identical to master's.
improve.t27 no longer uses tri::t27b::zig_like_optimization_plan,
which 6b8b6ca moved to docs.

The restored golden specs hash to the spec_hash already recorded in
golden_GoldenSeries.json and golden_GoldenSpiral.json.

Closes #13303

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* specs: restore codegen_audit.t27 typed LOSSES undone by #12997 (Closes #13303)

The merge turned `LOSSES : [5]Loss` back into an untyped array and dropped
the bench `use` and the branch-bound model section. The t27b native ratchet
reports the file as "ledger pass, now blocked: ExprArrayLiteral" (run
42406646026). Restore the 73f626b text the ledger records as a pass;
every test and name of master's version is kept, 5 tests come back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* specs/golden: take master's #13314 text whole after the merge (Refs #13303)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* specs/golden: type golden_oracle MECHANISM_DESCRIPTION as [3]str so t27b compiles it (Refs #13303)

#13314 left `pub const MECHANISM_DESCRIPTION : str = [` (three strings
typed as one str). t27b refuses it: the native ratchet reports
`golden_oracle.t27: ledger pass, now blocked: ExprArrayLiteral` on
master 4dfdd26 and on #13305 head 37c0665. The 4cfd2f2 text,
which the ledger records as a pass, had `[3]str`. Only that token
changes; every test of master's text stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* seals: re-save golden_GoldenOracle for the [3]str fix (Refs #13303)

Re-saved from a T27 OS shell-cell pane with ~/t27/target/release/t27c
(built from cb1c1d6, an ancestor of master), on the owner's word
for this one seal on #13305. spec_hash ca92a02a5e matches the fixed
specs/golden/golden_oracle.t27; tests 5/5, vacuous 0. Not blessed, not
added to tools/seal_baseline.txt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

Epic: GOLDEN CHAIN — One .t27 Spec to Bit-Exact Software and Silicon

1 participant