docs: remove what this repository published about a consumer's corpus

Operator decision 2026-09-21: nothing from that consumer's collection goes out
on the public remote. The NAME stays where it is already published -- it is a
consumer of this library, named as such, and removing it would mean rewriting
published history, which this repository does not do. What goes is everything
that describes their CONTENT.

Removed across README, CLAUDE.md, CHANGELOG, four dated reports, the
consumption contract, three source modules and three test modules: their
corpus's document and page counts, the concept count of a bundle built from
it, the byte figures of a payload built from it, the question and fasit counts
and recorded score of their evaluation set, a bundle id with two content refs,
an order id naming them, and a path into their repository.

Kept, because the argument survives without the corpus: RATIOS and
percentages. A ratio is the finding -- a withheld list that is 65.5 % of a
payload is a defect at any corpus size -- and it discloses nothing about how
large anyone's collection is. Where a claim lost its denominator it now SAYS
so rather than quietly reading as unmeasured: the gate-refusal limitation in
the README states that the corpus and its counts are deliberately withheld and
points the reader at their own build, which is the number that binds them
anyway.

One integrity pin is kept and named here rather than left to be found: the
retrieval gate still pins that set by sha256, because the pin is what refuses
a self-written file in the right shape, and a checksum discloses nothing about
what it checksums. Its recorded SCORE is gone -- that was their figure about
their own corpus, and the row now says so instead of restating it.

The known-positive constants move with the contract document, as they must.
Suite green, 2372 passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -55,16 +55,19 @@ Read this before pointing the tool at documents you depend on. Every number
 here was measured; none of it is a plan.
 
 - **The default gate refuses whole documents, and they are documents you may
-  want.** Measured 2026-09-20 on an official documentation corpus of 594
-  sources: `guard-trusted-source`, the shipped default, refused **17 of 594
-  sources outright** — `fail_secure` 3, `quarantine_review` 14 — and **16 of
-  those were 197 official documentation pages** (8.1 %), among them the pages
-  on hooks, skills, permissions, errors, env-vars and authentication. Not one
-  element of a refused document reaches the bundle. Rebuilt with `--gate none`,
-  all 17 went through untouched, so the refusal is the gate and not the
-  readers: a page of official documentation naturally carries commands and
-  instruction-shaped text, and the guard reads that as something to hold for
-  review. The build says so now — it names the count, the files, the codes and
+  want.** Measured 2026-09-20 against a real corpus of official documentation:
+  `guard-trusted-source`, the shipped default, refused a minority of sources
+  outright, under `fail_secure` and `quarantine_review`, and most of those were
+  ordinary reference pages. Not one element of a refused document reaches the
+  bundle. Rebuilt with `--gate none`, every one of them went through
+  untouched, so the refusal is the gate and not the readers: a page of
+  official documentation naturally carries commands and instruction-shaped
+  text, and the guard reads that as something to hold for review. **The
+  corpus, its size and the per-page counts are deliberately not published
+  here** — it belongs to a consumer whose material this repository does not
+  republish — so this bullet carries no denominator. Run your own: the build
+  names the count, the files and the codes on every run, which is the number
+  that actually binds you. The build says so now — it names the count, the files, the codes and
   that command — and exits 0, because the bundle is a true record of what the
   gate allowed. **If you vouch for the source yourself, build with `--gate
   none`;** the bundle then records that nothing was screened. The default was
@@ -982,9 +985,10 @@ reader who sees a near miss can ask for it — and `complete`, which says whethe
 those names ARE the whole set. `--withheld-nearest N` sets how many are named
 (default 20) and `--withheld-full` names every one, which is what an instrument
 classifying every miss should ask for. The default moved on a measurement: on a
-2313-concept bundle the flat list came to 186 440 bytes, **65.5 % of the written
-payload**, none of it counted against the budget the same payload reported, and
-none of it anything a reader could act on. `--withheld-titles` is retired by
+large real bundle the flat list came to **65.5 % of the written payload**, none
+of it counted against the budget the same payload reported, and none of it
+anything a reader could act on. The same question after the change costs
+**18.4 %** of what it did before. `--withheld-titles` is retired by
 that change — it existed to buy the one field the near misses now carry.
 
 Every excerpt carries the concept's `title`, and — when the producer wrote them