duplicate-bodies red on master: ledger the claw helper copies from #10283/#10286/#10287/#10288 #10311

Goal

The duplicate-bodies check is red on master (238b6a9) and therefore on every open pull request, including the #10024 epic PR #10275. python3 tools/dupe_scan.py reports six bodies that are copied but in no ledger, plus one group that grew:

• buf_has, digit_byte, put_count, put_str: specs/claw/gates.t27 and specs/claw/sarif.t27 (spec(claw): sarif.t27 -- t27c findings as SARIF 2.1.0 for code scanning #10288).
• str_eq: specs/claw/gates.t27 and specs/claw/suggest.t27 (spec(claw): suggest.t27 -- one-click formatter suggestions, COMMENT only (Closes #10285) #10286).
• has_prefix: specs/claw/service.t27 (feat(claw): claw/t27f -- the seal-gated T27F check on every .t27 pull request through the TRI CLAW App (Closes #10268) #10283) and starts_with in specs/claw/preview.t27 (spec(claw): preview -- the T27F preview deployment of a PR as law (Closes #10282) #10287).
• bytes_eq 2 -> 3: same in specs/claw/sarif_pins.t27 (spec(claw): sarif.t27 -- t27c findings as SARIF 2.1.0 for code scanning #10288).

Boundary

• tools/duplicate_bodies_baseline.txt only, written by python3 tools/dupe_scan.py --bless.
• Not in scope: sharing the claw helpers into one module (a follow-up: sarif.t27 states it must lower alone under gen-c), any other check on master.

Scenarios

• Given master at 238b6a9, When python3 tools/dupe_scan.py runs, Then it exits 1 with the seven errors above.
• Given the branch, When it runs, Then it exits 0.

Requirements

• FR-001: The ledger MUST be --bless output on master's tree, not hand-edited.
• FR-002: The commit message MUST name each group, the PR that added the copy, and why the copy is deliberate or deferred.

Success Criteria

• duplicate-bodies passes on the PR.

Close criteria

• The PR merges and duplicate-bodies passes on master.