docs: correct a coverage overstatement in the D34 footnote, and repair the D34 row

[Gavin-Borges]

Three defects, all shipped by PR #291 and all found by an adversarial re-read of that PR's own output against the row it cites. Nothing here is a new claim - each change either removes an assertion or supplies a field the table already required.

1. README.md's competitor-table footnote overstated the pass's coverage

It claimed "Every PredIG/PRIME/NetMHCpan/pVACtools cell above ... is bound to a primary source read in full", and that D34 "lists every source and every cell's citation". It then named ONE exception.

D34 describes TWO. The second is pVACtools's "Pan-allele training" cell, which D34 records as excluded from the verification pass entirely - one research pass had transcribed SESTRAV's own column text into that row - and states plainly is "unchanged and unverified by this pass".

The footnote now says 34 of 36 are source-bound, names both exceptions, and the pVACtools cell is flagged inline in the table the way the NetMHCpan one already was. D34's citations are also per tool, not per cell, so that phrase is dropped.

Note the direction: the overstatement claimed more verification coverage than the pass achieved. That is the flattering direction this repository's defects keep taking, and it is the reason .claude/rules/third-party-claims.md exists.

2. D34's own disposition arithmetic was the root cause, so it is fixed rather than patched around

The row read "seven cells were corrected" plus "Twenty-nine cells were checked and confirmed accurate", which sums to exactly the 36 cells in scope - leaving no slot for the one unresolved cell and the one excluded cell the same row goes on to describe. The arithmetic asserted full coverage while the prose disclosed two gaps, and the README sentence was written from the arithmetic.

Corrected to 7 corrected + 27 confirmed + 1 unresolved + 1 excluded = 36, with a dated note recording the double-booking and its propagation.

3. The D34 table row was malformed: 8 cells against the table's 9 columns

Every field from "Scope boundary" onward rendered one column to the left - the 2026-08-25 date displayed under "Limitation / corrective language", and the file list under "Last verified".

• Counted escape-aware; the row contains escaped pipes, so a naive pipe count misreads it.
• Confirmed present on origin/main at fce43b5 before this change rather than introduced by it.

The missing "Scope boundary" cell is supplied, stating only what the row already evidences: the 36 competitor cells across nine capability rows, with SESTRAV's own column and the Tier A metric row explicitly out of scope.

Verification

• Integrity harness after these edits: 150 PASS / 0 WARN / 2 FAIL / 7 SKIP - unchanged from the pre-edit baseline. The two FAILs are the standing owner-owned C1/D20 and C2/D21 rulings and are untouched here.
• Table column counts re-checked escape-aware: D34 now 9 cells, matching D31/D32/D33 and the header.
• No banned non-ASCII introduced in either file.
• Full local pre-push test gate passed.

Still owner-owned, deliberately not changed here

The NetMHCpan "Multi-virus support" (Pan-pathogen) cell remains unresolved pending your ruling. Per rule 3 of third-party-claims.md, the right replacement could not be sourced either, so it stays flagged rather than rewritten to a synthesized claim.