Skip to content

[ci] Re-seal petal_menu.t27 and bench.t27: stale gen-hashes fail Spec Guards and Seal Coverage #11641

Closed

Description

@gHashTag

Context

specs/t27f/petal_menu.t27 and specs/t27os/bench.t27 were edited after their .trinity/seals were last written (petal_menu in 431fdd3c7, bench in f72f9e4f2, both on 2026-10-20), and the seals were not regenerated. Two master CI gates therefore fail on every push since 2026-10-21: Spec Guards (gen-hash drift, check_seal_currency.py) and Seal Coverage (check_seal_coverage.py). This issue is the L1 anchor for the re-seal repair.

User Scenarios

  • Given the two specs edited on 2026-10-20, when t27c seal <spec> --save runs with the master compiler, then the seal records the four gen_hash_* values the compiler now emits and the current spec_hash.
  • Given the re-sealed specs, when python3 tools/check_seal_currency.py runs in the Spec Guards workflow, then it reports STALE generated-code hash: 0.
  • Given the re-sealed specs, when python3 tools/check_seal_coverage.py runs in the Seal Coverage workflow, then both seals hold and the gate reports OK.

Requirements

  • FR-001: .trinity/seals/t27f_T27fPetalMenu.json MUST be regenerated with the master t27c so its gen_hash_{c,rust,verilog,zig} and spec_hash match what the compiler now emits for specs/t27f/petal_menu.t27.
  • FR-002: .trinity/seals/t27os_T27osBench.json MUST be regenerated with the master t27c so its gen_hash_{c,rust,verilog,zig} and spec_hash match what the compiler now emits for specs/t27os/bench.t27.
  • FR-003: the repair MUST record current output rather than baselining the drift, so the two seals stop counting as newly-broken in seal_baseline.txt.

Success Criteria

  • python3 tools/check_seal_currency.py exits 0 and prints STALE generated-code hash : 0
  • python3 tools/check_seal_coverage.py exits 0 and prints OK: with both seals among the 2888 that hold
  • git diff touches only the two seal JSON files (18 lines each: hashes, sealed_at, spec_hash, test counts)
  • both seals record failed: 0 against the re-run tests

Boundary

  • .trinity/seals/t27f_T27fPetalMenu.json
  • .trinity/seals/t27os_T27osBench.json

Activity

  1. added a commit that references this issue on Oct 22, 2026
    b68358b
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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions