Skip to content

spec automation/seal-stands-in: a seal answers for its tests - #8335

Merged
gHashTag merged 1 commit into
masterfrom
claude/seal-stands-in
Oct 10, 2026
Merged

gHashTag merged 1 commit into
masterfrom
claude/seal-stands-in

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Closes #8334

Host: gHashTag/999-multibots-telegraf scripts/check-t27-specs.mjs --run. Owner: speed development up with t27 seal. Measured 2026-10-09: 48 vendored specs compiled in 25 s; 35 carry a seal for their exact bytes with passing tests.

  • stands_in(hash_same, sealed_total, sealed_failed, forced)
  • compiles(no_seal, seal_stands_in)

Test report: 3 tests, 3 pass. Negative controls: 6/6 caught (each clause of stands_in dropped, each side of compiles dropped).

phi^2 + 1/phi^2 = 3 | TRINITY

🤖 Generated with Claude Code

https://claude.ai/code/session_01FJktaYxNrfAUdxSwdQw3gV


Generated by Claude Code

The 999 host compiles every vendored spec to run its tests; 35 of 48
already carry a seal in t27 for their exact bytes with passing tests.
A seal now stands in for that run when it sealed these bytes, its tests
ran, none failed, and it was not forced; --no-seal always compiles.

Closes #8334

phi^2 + 1/phi^2 = 3 | TRINITY

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FJktaYxNrfAUdxSwdQw3gV

gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner Author

t27b-native-ratchet is red here. It is not this PR's: it is a non-required check that is red on master too, and this PR only changes one spec under specs/automation/ (plus its seal and NOW entry), which the native ratchet does not read. No fix is ported. The four required checks (validate, check-linked-issue, parse-ratchet, own-language) gate the merge.


Generated by Claude Code

gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner Author

Corpus ratchet (expected-failure ledger) is red here too, and it is not this PR's: its only finding is specs/math/constants.t27 [parse-no-discard] discards 349 tokens, pinned at 386 (-37) -- re-bless to pin it (DISCARD IMPROVED, channel top-level-resync 37->0) — a spec this PR does not touch, moved by the math/constants work on master. This PR adds one file under specs/automation/ (plus its seal and NOW entry); UNEXPECTED FAILURES 0, GATE FAILURES 0. No fix is ported: the re-bless belongs with the change that improved constants.t27. The four required checks gate the merge.


Generated by Claude Code

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-09 20:37:29 UTC

Summary

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

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=557cd271f4e3 != 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 pushed a commit that referenced this pull request Oct 9, 2026
… blog-share with t27c 0.5.2

Corpus ratchet was red on this PR, and on every PR built on master after
#8209 (#8316 and #8335 too): #8209 made specs/math/constants.t27 compile
again, its 37 top-level-resync tokens are gone, and the ratchet asks for
the pin to follow ("DISCARD IMPROVED ... re-bless to pin it"). The pin is
lowered by hand, only that row: 349 tokens, all bdd-block-fallback.
Local `t27c suite --ratchet --corpus-only`: RATCHET: CLEAN (it was FAIL
with the same constants.t27 line before).

The blog-share seal is rewritten by t27c 0.5.2 (seal_schema 2, toolchain
recorded), as master's seals are; the first one was written by a 0.5.1
build. Gen hashes are unchanged; 20/20 tests.

Refs #8318

phi^2 + 1/phi^2 = 3 | TRINITY

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ScHVrGSr6zZUdwkdC8DR9k
This was referenced Oct 9, 2026
This was referenced Oct 10, 2026
@gHashTag
gHashTag merged commit 4e764b4 into master Oct 10, 2026
27 of 29 checks passed
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.

spec automation/seal-stands-in: a spec's seal answers for its tests, so nothing compiles them again

2 participants