Skip to content

specs: one distinct real test for a/b_c and a_b_c, replacing the #8488 twins (Closes #8508) - #8496

Merged
gHashTag merged 2 commits into
masterfrom
queen-8472-a
Oct 10, 2026
Merged

gHashTag merged 2 commits into
masterfrom
queen-8472-a

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

Closes #8508. Replaces what #8488 landed in specs/a/b_c.t27 and specs/a_b/c.t27: byte-equal twin test_module_exists bodies plus assert-true blocks in both files (the assertionless shape the corpus ratchet gates against — latent red while master's corpus-ratchet runs sat cancelled).

One distinct, real test per spec now:

  • specs/a/b_c.t27 — test b_c_dummy_returns_true asserts dummy() == true (the module's only declared value)
  • specs/a_b/c.t27 — test c_dummy_value binds the dummy() result to a local first and asserts it — no byte-equal twin of the sibling

Both verified on the t27c lab: one test, one pass, zero FAIL, one runtime assert executed, zero vacuous passes.

🤖 Generated with Claude Code

Each of the two acceptance-criteria stubs declares exactly one function,
dummy(), and nothing else; each now carries one test block asserting what
that function returns. specs/agents/{v,w,x,y,z}.t27 from the same issue
were already checked by #6620, so this PR covers the two specs that were
still pass_vacuous at lab run 285512a.

Closes #8472

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@gHashTag

Copy link
Copy Markdown
Owner Author

Superseded mid-flight: PR #8488 (branch queen-8472, commit 50fbc78, author "Trinity Bee") merged as 1f4863e at 2026-10-10 09:53Z and closed #8472 while this branch was being verified on the t27c lab. Both branches edit the tail of the same two files, so this PR now conflicts.

What differs from what landed: this branch adds ONE test per file with distinct bodies (no byte-equal twin, per the issue's own sibling rule) and no assert true block -- the shape tools/check_assertionless_spec_tests.py (corpus-ratchet, "No new assertionless spec test") exists to catch, and which #8488 adds to both files. Lab verification at 0c5aa6c: t27c test-report = 1 test / 1 pass / 0 FAIL / 1 runtime assert executed / 0 vacuous passes per spec.

Auto-merge disabled; left open for the coordinator to decide whether to adopt these tests over the landed twins or close as superseded. Separately, the t27b-native-ratchet ledger is pinned at 606611c and stale against master: this run showed 8 UNEXPECTED PASS rows (6 of them from #6620/#6623 already on master, not from this branch) and 6 UNLISTED -- the steward ledger needs a re-bless independent of this PR.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-10 10:20:27 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=bd3352ccb90e != 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).

…rue (#8508)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-10 10:46:01 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 49
PRs with All Checks Green 1
READY 0
FAILING 49
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 49 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=bd3352ccb90e != 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).

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.

specs: a/b_c and a_b_c test bodies are byte-equal twins carrying assert true (from #8488)

1 participant