R3-3: die A receipt under t27c 0.5.1 (for #7669) #7815

Problem

Die A's R3-3 receipt (#7687) was signed by t27c 0.5.0. #7787 re-sealed ternary_link with the 0.5.1 build (DNA tail fix, #7761), so that receipt no longer matches the seal and was moved to r33-v050-2026-10-08/.

Spec

specs/fpga/ternary_link.t27, judged by specs/verified/run_record.t27; nonce e61798b78cbb6b287b8ff8523cea71a6, pnr seed 1.

Tests

t27c silicon on die 050d58218fd9854 with t27c-bootstrap@0.5.1+579bc55aa: A1 Done 0, B1 Done 1, B2 0xa5a532bd clauses=1111 ok=1, DNA agreed before and after, receipt signed by key 4d2ffce012238bd4. run-record on master: 2 receipts, both FRESH and complete, Die NAMED; RUN_TOO_FEW_RECEIPTS until die C reports.

Acceptance

The receipt is on master next to die B's.

Boundary

• specs/fpga/ternary_link.t27
• specs/verified/run_record.t27

User Scenarios

• Given t27c 0.5.1 with the DNA tail fix (bootstrap/t27c.py@0.5.1+579bc55aa) and the ternary_link.t27 spec sealed under that version, When the R3-3 receipt for Die A (nonce e61798b78cbb6b287b8ff8523cea71a6, pnr seed 1) is regenerated, Then the new receipt verifies against the current ternary_link seal and appears in the run-record on master alongside Die B's receipt.

Requirements

• FR-001: The regenerated Die A R3-3 receipt MUST be produced by t27c 0.5.1 using specs/fpga/ternary_link.t27 and judged by specs/verified/run_record.t27.
• FR-002: The receipt MUST carry nonce e61798b78cbb6b287b8ff8523cea71a6 and pnr seed 1, and MUST be signed by key 4d2ffce012238bd4.
• FR-003: The run-record on master MUST contain two FRESH and complete receipts (Die A and Die B) with Die NAMED, and MUST no longer report RUN_TOO_FEW_RECEIPTS for Die A.

Success Criteria

• t27c verify specs/fpga/ternary_link.t27 --receipt <regenerated-receipt-path> exits 0
• t27c verify specs/verified/run_record.t27 exits 0 and shows 2 receipts, both FRESH and complete, Die NAMED
• The regenerated receipt file exists on master at the same level as Die B's receipt (no longer in r33-v050-2026-10-08/)