Skip to content

fix(seals): baseline the four html/xml seals #5580 unsealed (Refs #5577) - #5612

Merged
gHashTag merged 1 commit into
masterfrom
fix/reseal-html-xml
Oct 2, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/reseal-html-xml

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Refs #5577

Seal Coverage (coverage) has failed on master since #5605 merged, and on every PR
opened since (#5605 itself, #5610), always with the same four seals:

TriHtml.json  encoding_TriHtml.json  [stale]  specs/tri/encoding/html.t27
TriXml.json   encoding_TriXml.json   [stale]  specs/tri/encoding/xml.t27

#5580 restored 30 seals on the 15 specs whose own tests fail, on purpose. #5605 wrote
baseline lines for 26 of the 30 and missed these four. Both specs still fail their
own tests (t27c test-report: html 1/3, xml 0/1), so re-sealing is the wrong repair
and seal --save refuses it since #5605. This adds the four lines in the same
wording as the other 26.

Measured locally with the compiler present:
OK: 1415 seals, 1291 hold, 124 known-broken (89 dangling, 5 no-spec-path, 30 stale)
-- 30 stale is the #5580 set exactly.

🤖 Generated with Claude Code

#5580 deliberately restored 30 seals on specs whose own tests fail; #5605
baselined 26 of them and missed TriHtml, TriXml, encoding_TriHtml and
encoding_TriXml. Seal Coverage has failed on master and every PR since,
with exactly those four. Their specs still fail their tests, so the repair
is the baseline line, not a re-seal.

Local gate: OK, 1415 seals, 30 stale = the #5580 set.

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

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-02 16:51:32 UTC

Summary

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

Seal Status

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

Copy link
Copy Markdown
Collaborator Author

Reviewer bee (triage 2026-10-03): evidence for head b9119dd0f5b148286fc1c4e4b1f276d49628f388. Merging.

  • Diff: 2 files, +23/-0. Four ledger lines in tools/seal_baseline.txt (TriHtml, TriXml, encoding_TriHtml, encoding_TriXml), same wording as the 26 lines fix(seal): seal --save runs the spec's tests and refuses on FAIL (refs #5577) #5605 added, plus a docs/now entry. No .t27 spec and no seal JSON is changed, so no reseal is owed.
  • Master is red on exactly this: coverage on master 9be91c7a fails with FAIL: 4 seal(s) newly do not hold naming these four seals. Not yet on master (grep -c 'TriHtml|TriXml' tools/seal_baseline.txt on master = 0).
  • Checks at this head: coverage pass, required validate / check-linked-issue / parse-ratchet pass. The only red is untrusted-input, which is red on master for every PR.
  • mergeable=MERGEABLE, 1 commit, 8 behind master with no overlap in these files.
  • No credentials in the diff.

@tri-claw tri-claw Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bee review: see evidence comment

@gHashTag
gHashTag merged commit 6fc8b57 into master Oct 2, 2026
35 of 36 checks passed
@gHashTag
gHashTag deleted the fix/reseal-html-xml branch October 26, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bee-reviewed A reviewer bee reviewed and verified this PR at its current head; the only merge signal (#5525)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant