Re-seal specs/t27f/frontend.t27: its seal went stale on master in 2e561c612, Seal Coverage red on every PR #10811

tools/check_seal_coverage.py ("Every seal still describes its spec", workflow Seal Coverage) fails on every PR, because one seal on master no longer holds: t27f_T27fFrontend.json. On master 2e561c6 (#10782 M4) changed specs/t27f/frontend.t27 but did not re-seal it. t27c seal --verify specs/t27f/frontend.t27 on master gives VERIFICATION FAILED, and the gen hashes differ. Seen on #10799, among others.

Boundary

• .trinity/seals/t27f_T27fFrontend.json
• docs/now/2026-10-19-reseal-t27f-frontend.md

Done when

t27c seal --verify specs/t27f/frontend.t27 prints all hashes MATCH, and check_seal_coverage.py reports no seal that newly does not hold.

Generated by Claude Code

User Scenarios

• Given the seal file .trinity/seals/t27f_T27fFrontend.json no longer matches specs/t27f/frontend.t27 after changes in commit 2e561c6, when running t27c seal --verify specs/t27f/frontend.t27, then the command prints VERIFICATION FAILED and the gen hashes differ.
• Given the seal has been re-generated for the current spec, when running t27c seal --verify specs/t27f/frontend.t27, then the command prints all hashes MATCH.
• Given all seals are current, when running tools/check_seal_coverage.py, then the script reports no seal that newly does not hold.

Requirements

• FR-001: The seal file .trinity/seals/t27f_T27fFrontend.json MUST be regenerated to match the current specs/t27f/frontend.t27.
• FR-002: Command t27c seal --verify specs/t27f/frontend.t27 MUST print all hashes MATCH and exit 0.
• FR-003: Command tools/check_seal_coverage.py MUST report no seal that newly does not hold and exit 0.
• FR-004: The regeneration MUST be documented in docs/now/2026-10-19-reseal-t27f-frontend.md.