Skip to content

fix(seals): repository-relative spec_path for the three #6789 isa seals (Closes #6849) - #6852

Closed
gHashTag wants to merge 2 commits into
masterfrom
fix/seal-paths-t27a
Closed

gHashTag wants to merge 2 commits into
masterfrom
fix/seal-paths-t27a

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Three seals minted in #6789's agent worktree commit spec_path with an absolute /Users/playra/.../agent-worktree/... path. That fails the devhome scan on master and classifies the seals as phantom in seal coverage (root / spec_path with an absolute path names nothing on a runner).

Rewritten to repository-relative. Verified before committing: each relative spec exists on master and its sha256 equals the seal's recorded spec_hash -- only the location field was machine-specific, every other claim is unchanged.

Closes #6849

🤖 Generated with Claude Code

…ls (Closes #6849)

isa_T27a, isa_Tri27Encoding and theory_CompilerTheoryIsaRoundTrip were
minted in an agent worktree and committed spec_path as an absolute
/Users/playra/t27/.claude/worktrees/agent-a008408b9580a5586/... path,
which fails the devhome gate on master and reads as phantom to
tools/check_seal_coverage.py (root / absolute never exists on a runner).
Each relative path exists on master and sha256-matches the seal's
spec_hash, so no other claim in the seal changes.

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

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 13:58:49 UTC

Summary

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

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

Seal Status

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

gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner Author

Note: #6861 carries the identical three seal spec_path changes plus the orbitofrontal_value.t27 parse fix (the #6755 corpus-ratchet / emit-bitexact red). Either can land first; the seal hunks are byte-identical, so the second one merges clean.

This was referenced Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 14:32:59 UTC

Summary

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

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

Seal Status

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

gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner Author

Superseded: master's #6862 resealed the same three t27a seals with repo-relative spec_path, so this diff is already on master.

@gHashTag gHashTag closed this Oct 6, 2026
@gHashTag gHashTag added the owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR label Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Three seals from #6789 carry absolute agent-worktree spec_path -- devhome scan + seal coverage red on master

1 participant