ledger: t27b row for specs/analog/sar_comparator.t27, UNLISTED 1 -> 0 on master #10649

Boundary

docs/reports/t27b_expectations.json on master only: one new row, {"path": "specs/analog/sar_comparator.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, which reads: specs/analog/sar_comparator.t27: the reference passes it and the ledger does not name it (t27b pass). The spec landed in analog: sar_comparator.t27 -- the SAR ADC dynamic comparator, multi-node Newton, square law against ngspice LEVEL=1 (Closes #10583) #10604 without a ledger row. Measured on t27f: R4f -- mode 5 holds the address for REEL_CTA_MIN_MS, cut 1 capped at BEAT_CUT1_LAST_MS (Closes #10629) #10632's run (0ce6fae vs ledger 90f6248); ledger: t27b row for specs/claw/token_shape.t27, UNLISTED 1 -> 0 (Closes #10633) #10634, t27f: frontend.t27 -- T27F is t27's frontend, every visual surface in one law, served by TRI CLAW (Closes #10537) #10551 and claw: visual_output.t27 -- a T27F visual in every output that did work (Closes #10508) #10510 show the same red.
• After the fix, the ratchet on a fresh master merge reports UNLISTED 0.

Requirements

• Add the row in sorted position, after specs/analog/sar_cdac.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.
• The same row on claw: reel_still.t27 -- the TRI CLAW /mcp tool that renders one particle still #10548 (a35cf27) is consistent with this one, so the two merge cleanly.

Requirements

• FR-001: The ledger file docs/reports/t27b_expectations.json MUST contain a new row for specs/analog/sar_comparator.t27 with "t27b": "pass" inserted in sorted order immediately after the row for specs/analog/sar_cdac.t27.
• FR-002: The change MUST NOT raise the ledger's cap; a pass row does not count against it.