Skip to content

Seals are stale on master: 126 gen-drift and 9 stale make coverage and spec-guards red #12972

Open

Description

@gHashTag

Boundary

Files: .trinity/seals/*.json only (the 135 seals listed by the failing coverage step of the Seal Coverage run on master 4cfd2f2, run 41172959376: 126 gen-drift, 9 stale). No spec, no compiler source, no workflow, no baseline file is edited. Out of scope: the cli-tri census, duplicate-bodies, "Documented t27c subcommands exist", emit-bitexact, Corpus ratchet.

User Scenarios

  • A contributor opens any PR against master and sees coverage ("Every seal still describes its spec") and spec-guards red for a reason the PR did not cause. They cannot tell their own breakage from the inherited one.
  • A reviewer wants to merge a docs-only PR; the required check is red because master's seals are behind the emitter (afea7d49d4, gen-rust slice-field capture) and behind five specs edited without a re-seal.
  • A maintainer reads docs/BRANCH-PROTECTION.md and expects the gate to be a signal, not noise.

Requirements

  1. Re-save each listed seal with t27c seal <spec> --save, using a t27c whose compiler sources equal master. Re-sealing a gen-drift seal is a statement that the new output is the wanted one, so each gen-drift seal must change only gen_hash_rust (and sealed_at), which is what the emitter commit explains.
  2. Run tri seals sync-twins so twin seals carry the newest claims.
  3. A seal whose spec does not generate (the emit-bitexact specs) is not written with gen_hash=none; it is reported and left out of the commit.
  4. No absolute home-directory path appears in any committed file.
  5. One commit, Closes this issue, one PR against master.

Success Criteria

  • python3 tools/check_seal_coverage.py exits 0 on the PR head (the coverage check is green).
  • spec-guards is no longer red because of seals.
  • The diff touches only .trinity/seals/*.json.
  • A list of any seal left out, with the reason, is in the PR body.

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Covered by specs/verified/seal_management.t27.

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.

  3. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec exists and passes typecheck + tests. M2 milestone complete.

  4. gHashTag commented on Nov 18, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions