paper_claims.t27 states the withdrawn 323 MHz GF16 clock in a claim text #10418

specs/numeric/paper_claims.t27 (merged in #10401) quotes the GoldenFloat abstract's claim "35 of 35 testbench vectors at 323 MHz on an XC7A35T" in its claim text CL_TEXT[9]. docs/nona-03-manifest/RESEARCH_CLAIMS.md, Retraction 2026-08-18, withdrew the 323 MHz figure: it is the toggle rate of a ring oscillator, not a GF16 path. A withdrawn number must not be stated in a live first-party spec, and the withdrawn-live gate fails on that line after the merge.

Boundary

• specs/numeric/paper_claims.t27: the one claim text CL_TEXT[9].

Out of scope: the counts and verdicts, the other claims, tools/withdrawn_live_baseline.txt.

Scenarios

• python3 tools/check_withdrawn_live.py on master reports no withdrawn number in specs/numeric/paper_claims.t27.
• tri papers and t27_paper_claims show row 10 as "35 of 35 testbench vectors pass" plus a pointer to the retraction, still not checkable.

Requirements

• The claim text no longer states the withdrawn frequency and names the retraction instead.
• The verdict stays V_UNCHECKED, and the totals stay 34 fit / 8 do not / 3 not checkable. The testbench pass is still unrecomputable here, and RESEARCH_CLAIMS.md says the testbench passing is what the build does establish.

Criteria

• t27c test-report: 10 of 10 pass, 0 vacuous.
• t27c fmt leaves the file unchanged.
• The withdrawn-live check is green on the PR.

Success Criteria

• t27c test-report specs/numeric/paper_claims.t27 passes with "10 of 10 pass, 0 vacuous" exit 0
• t27c fmt specs/numeric/paper_claims.t27 leaves file unchanged exit 0
• python3 tools/check_withdrawn_live.py reports no withdrawn number in specs/numeric/paper_claims.t27 exit 0