ledger: t27b row for specs/claw/token_shape.t27, master ratchet UNLISTED 1 -> 0 #10633

Boundary

docs/reports/t27b_expectations.json on master only: one new row, {"path": "specs/claw/token_shape.t27", "t27b": "pass"}. No spec, cap or gate file changes.

User Scenarios

• A contributor opens any PR against master. t27b-native-ratchet is red with UNLISTED 1: specs/claw/token_shape.t27: the reference passes it and the ledger does not name it (t27b pass). The spec landed in claw: claw-t27f/suggest/refresh pass with a note when the App token cannot be minted; claw-refresh can read the queue (#10576) #10585 (claw: token_shape.t27 -- every App-token job passes with a note when the token cannot be minted (#10576) #10577) without a ledger row; ledger: t27b rows for sar_cdac and spice_convert, UNLISTED 12 -> 0 (Closes #10615) #10616 added the other 12 missing rows.
• After the fix, the ratchet on a fresh master merge reports UNLISTED 0.

Requirements

• Add the row, in sorted position (after specs/claw/text.t27).
• Do not raise the ledger's cap; a pass row does not count against it.

Success Criteria

• t27b-native-ratchet on the fix PR reports UNEXPECTED FAILURE 0, UNEXPECTED PASS 0, UNLISTED 0.
• Measured on PR t27f: R4d -- mode 5 overlays live inside one scene, none on a beat crossfade #10627's run 919c636: UNLISTED 13, of which 12 are on master's ledger now; this row is the 13th.

Requirements

FR-001: The ledger file docs/reports/t27b_expectations.json MUST contain a new row {"path": "specs/claw/token_shape.t27", "t27b": "pass"} inserted in sorted order after the row for specs/claw/text.t27.

FR-002: The ledger's cap MUST NOT be raised; a pass row does not count against it.