corpus ratchet red on master: suite_expectations still pins specs/nn/hslm.t27 after #10055 fixed it #10071

Summary

Master fails the corpus ratchet, and every open pull request inherits the red check. PR #10055 made specs/nn/hslm.t27 parse with no discarded tokens, but the expected-failure ledger docs/reports/suite_expectations.json still pins that spec as parse-no-discard with discard_tokens 153 (issue 1959).

CI run 39055607561 (job 117462918639) on master 35879c0 reports:

ledger:              82 / 82 cap
observed (primary):  81
UNEXPECTED PASSES  : 1
  - specs/nn/hslm.t27 [parse-no-discard] (fixed -- remove from the ledger)
DISCARD WORSENED   : 1
  > specs/nn/hslm.t27 [parse-no-discard] pinned at 153 but this run took NO reading
RATCHET: FAIL

Both lines are one fact: the spec improved and the ledger did not follow. The fix is a data change: drop the entry and lower max_entries from 82 to 81, written by t27c suite --repo-root . --bless-expectations (the command the workflow's own "Explain a failure" step names), not by hand.

The two other checks that were red on master at the same time are out of scope here:

• duplicate-bodies: fixed on master by t27b: emit_kit -- one home for the writers' shared helpers (Refs #9994) #10065 (the shared t27b writer helpers moved to one spec).
• cli-tri: tracked by cli-tri: retire deleted-workflow test and refresh measured census pins #9634 (a unit test in the tri CLI still reads the deleted brain-seal-refresh workflow). The fix is a deletion in existing Rust, which needs the owner's owner-approved-foreign label; it is left for the owner there.

Boundary

• docs/reports/suite_expectations.json

User Scenarios

• Given master with the hslm entry removed from the ledger, when the corpus ratchet runs, then it reports 0 unexpected passes, 0 worsened discards and RATCHET: OK.
• Given a later change that makes hslm discard tokens again, when the ratchet runs, then it fails as an unexpected failure, because the amnesty is gone.

Requirements

• FR-001: The ledger MUST NOT contain an entry for the hslm spec.
• FR-002: max_entries MUST equal the new number of entries (81), lowered, never raised.
• FR-003: The ledger MUST be written by t27c suite --bless-expectations; every other entry MUST stay byte-identical.
• FR-004: The change MUST touch no file outside the Boundary, and no hand-written code.

Success Criteria

• t27c suite --repo-root . --ratchet --corpus-only exits 0 on the Railway lab with 0 unexpected passes and 0 worsened discards.
• The diff of the ledger is 1 entry removed and 1 cap line changed, 0 other lines.
• The corpus-ratchet check on the pull request passes.