Skip to content

Second v2 re-mint after the hubs: every spec whose tests now pass gets a v2 seal (#8095) #8371

Closed

Description

@gHashTag

Since #8177 (types.t27) and #8209 (constants.t27) landed, specs that imported them compile again. On master, frontier reports 424 of 1743 reused, with 1203 specs missing a valid v2 seal.

The loop (#8314) ran t27c seal --save on all 1203:

That leaves 727 specs, and every twin seal file of a kept spec carries the same v2 record.

Acceptance criteria

  • t27c frontier on the branch reports more than 1000 of 1743 reused
  • no kept seal records a blocked, failing or zero-test verdict

Boundary

.trinity/seals/

User Scenarios

  • Given the hubs (types.t27 and constants.t27) are landed and specs compile again, when the re-mint loop runs t27c seal --save on all 1203 unsealed specs, then only specs with v2 identity, zero failed tests, and at least one test receive a kept v2 seal.
  • Given a spec's tests fail or the spec does not compile, when the re-mint loop processes it, then no seal is kept for that spec.
  • Given a spec has zero tests, when the re-mint loop processes it, then its seal is reverted (zero-test hole closed).

Requirements

  • FR-001: The re-mint process MUST run t27c seal --save on every spec lacking a valid v2 seal.
  • FR-002: A seal MUST be kept only if the spec compiles, has v2 identity, has at least one test, and has zero failed tests.
  • FR-003: Seals for blocked (non-compiling) specs MUST be reverted.
  • FR-004: Seals for specs with zero tests MUST be reverted.
  • FR-005: Every twin seal file of a kept spec MUST carry the same v2 record.
  • FR-006: The final kept seal count MUST be 727 specs.

Success Criteria

  • t27c frontier reports more than 1000 of 1743 reused (exit 0)
  • Zero kept seals in .trinity/seals/ record a blocked verdict
  • Zero kept seals in .trinity/seals/ record a failing verdict
  • Zero kept seals in .trinity/seals/ record a zero-test verdict
  • Exactly 727 seal files exist in .trinity/seals/ with valid v2 records

Activity

  1. added a commit that references this issue on Oct 9, 2026
    19a2327
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions