release: t27c 0.5.1 -- device DNA is named on every die, not only on die A #7762

Goal

Cut t27c 0.5.1 so that R3-3 (#7669) can name its dies. t27c 0.5.0 refuses the DNA of every die whose FUSE_DNA tail is not die A's 0x4F (#7758): on die B, t27c silicon passed but wrote device_dna: null. Every R3-3 operator builds from the tag, so the fix only reaches their receipts through a new tag.

Boundary

• bootstrap/Cargo.toml version, .zenodo.json version, and the t27c entry in Cargo.lock. These are the files that release.yml's VERSION TRUTH gate reads for a t27c-v* tag.
• No code change in this issue's PR. The fix is verified: the FUSE_DNA tail is per-die data, so a second die is named (Closes #7758) #7761 (Closes device_dna.t27: FUSE_DNA tail is per-die, so a second die is refused as DNA_BAD_TAIL #7758).
• The tag t27c-v0.5.1 is pushed only after verified: the FUSE_DNA tail is per-die data, so a second die is named (Closes #7758) #7761 and this PR are on master.
• After the tag: specs/fpga/ternary_link.t27's seal is re-saved by the tag build, as verified: ternary_link sealed by the t27c 0.5.0 tag build; R3-2 receipts move to their own run directory (Refs #7669) #7681 did for 0.5.0, so that run-record matches receipt toolchains against the seal's built_by.
• ZENODO_DEPOSITION_T27C stays unset, so no DOI is minted, as in 0.4.0 and 0.5.0.

User Scenarios & Testing

• Given the tag t27c-v0.5.1 on a master commit carrying this change and verified: the FUSE_DNA tail is per-die data, so a second die is named (Closes #7758) #7761, release.yml's preflight finds both manifests at 0.5.1, cargo publish --dry-run passes, and crates.io has no t27c 0.5.1 yet.
• Given die B and the tag build, t27c silicon specs/fpga/ternary_link.t27 … --pnr-seed 7 prints DNA 0389c0c2d85e85c (FUSE_DNA and XSC_DNA agree, before and after the run), and the receipt's device_dna is that text.

Requirements

• FR-1: patch, not minor. A rule relaxation in the verified specs; no new subcommand, and the backends are untouched.
• FR-2: both manifests are bumped in one commit.

Success Criteria

• grep -m1 '^version' bootstrap/Cargo.toml prints version = "0.5.1".
• .zenodo.json version is 0.5.1.
• crates.io lists t27c 0.5.1.

Refs #7669, #6655

Requirements

FR-001: The release MUST be a patch version (0.5.1), not a minor version, reflecting a rule relaxation in verified specs with no new subcommand and no backend changes.
FR-002: Both manifests (bootstrap/Cargo.toml and .zenodo.json) MUST be version-bumped to 0.5.1 in a single commit.