docs: the reach clause was true of U+00AD alone, and the CHANGELOG says so
"0 across `tests/fixtures`, `examples`, `skills`, `docs`, `src`, README and
CHANGELOG" was published for all SIX characters and is false. Counted here
over `git ls-files` in those seven places, with a planted known-positive
proving the scanner can find one:
TRACKED in the seven places: 257 | readable: 230 | binary: 27
files carrying ANY of the six: 2
tests/fixtures/accounting/rejected-inventory.json {'200B': 1}
tests/fixtures/accounting/rejected/avvist.html {'200B': 1}
files carrying U+00AD: 0 []
KNOWN-POSITIVE planted file: {'00AD': 1, '2060': 1}
The two are this repo's own known-negative fixture for a carrier the door
refuses to remove. For U+00AD -- the character the door actually removes, and
the one the reach argument needs -- the figure is 0 of 230. (PM measured 229
on `43331fc`; the tree has gained one readable tracked file since.)
CHANGELOG under the untagged [0.10.1]: the three now-held sentences, the log's
stated provenance, and both corrected numbers.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
7509b6b6bc
commit
28f879849c
3 changed files with 44 additions and 5 deletions
|
|
@ -74,9 +74,17 @@ LOG: * **Normalisation**: 71 soft hyphen(s) (U+00AD) removed from 1 of 1
|
|||
**Reach, measured rather than argued.** 0 of the **78** readable documents of
|
||||
the K2 reference corpus carry U+00AD or any of the five other characters (the 8
|
||||
unreadable ones raise before extraction, so the denominator is 78 of 86); 0 in
|
||||
the pinned K2 bundle's concept bodies; 0 across `tests/fixtures`, `examples`,
|
||||
`skills`, `docs`, `src`, README and CHANGELOG. The door cannot have moved a byte
|
||||
anyone here has measured.
|
||||
the pinned K2 bundle's concept bodies; U+00AD is 0 of the **230** readable
|
||||
tracked files across `tests/fixtures`, `examples`, `skills`, `docs`, `src`,
|
||||
README and CHANGELOG. The door cannot have moved a byte anyone here has
|
||||
measured.
|
||||
|
||||
**Corrected 2026-09-19.** That last clause first read "0 across" for all SIX
|
||||
characters, and that is false: **2 of the 230** carry U+200B --
|
||||
`tests/fixtures/accounting/rejected/avvist.html` and its inventory twin, this
|
||||
repo's own known-negative for a carrier the door refuses to remove. For
|
||||
U+00AD, the character the door actually removes, the figure is 0, and that is
|
||||
the one the reach argument needs.
|
||||
|
||||
**Known-negative, in the suite.** A source carrying U+200B is still
|
||||
`fail_secure`, still exits 1, and the character is still in the extracted text.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue