fix(docs): the narration undercounted the tests, and the checker did not look

"Nearly two hundred tests" was written when there were 196. There are 205 now,
which is over two hundred, not nearly it, so a judge would have heard the
project undersell itself in its own video.

check-claims.mjs read digits in the README and PROGRESS and never looked at the
narration, where the count is spelled in words. It does now: it parses
"(nearly|about|over|around|more than) N hundred tests" out of demo-script.json
and checks it against the real suite. "Over three hundred" fails against 205,
so the guard has teeth.

Also: the builders-group announcement said "70+ teams", written when the
registry had 63. It has 152 now, so 70+ was both stale and an undersell; it says
130+, which is true and stays true.

Verified this pass, no change needed: the amount and fee math is correct across
twelve edge cases including the 0.1+0.2 float trap, and rejects every malformed
input; the watcher's accounting is correct across nine, including the exact
deadline boundary and a one-unit shortfall; the React binding runs under a fake
React and tears down without throwing; the dashboard QR dialog is a native modal
that traps focus and returns it on close; no mojibake, BOM or invalid UTF-8 in
any shipped file; the arcade makes no network call at all.