test(fixtures): replace sector-specific example material with generic, fictitious examples — green

Every fixture, test document, tool example and document now uses an invented
kitchen-and-baking handbook series, written in this repository. The package's
behaviour is unchanged; src/ changes are comments and help text only.

- Generated fixtures are regenerated from their generators. Their structural
  counts are identical before and after: elements, images, rows, cells,
  headings, bookmarks and the witness inventory's per-document totals. The
  image-inbox and accounting documents are renamed kapittel-84-*.
- tools/okf_accounting_gate.py: the two options that named one real corpus
  each are replaced by a generic, repeatable --corpus PATH with no default.
  Row 5 compares the PDF pair alone. Gate verdict unchanged: RED rows 2, 3, 6.
- tools/okf_witness.py: the STS JSON reader for one publisher's delivery is
  removed, along with its three twins and five tests. The mutation harness
  loses W09.
- docs/: 13 dated reports that documented runs on a retired reference corpus
  are removed, and 40 are neutralized. Dead links are removed, and no new
  dangling path is introduced.
- The synthetic MCP-gate corpus and the residual probe words are neutral.

Valgt: keep the `okf quality --fasit` bar value (the measured fraction, one corpus) and
rewrite only its provenance, because the verdict stays unchanged and the
number names nothing.

Term check with the local list: 0 of 411 tracked files, 0 file names, 0 of
27 binary fixtures. Suite after git add: 2457 passed, 1 skipped. The base
tree had 2460 passed and 2 skipped; five tests went with the JSON reader and
four were added by the term check. ruff, ruff format and mypy --strict src/
are clean.

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

docs/plan/structure-derivation.md

@@ -63,7 +63,7 @@ nothing derived can still use everything declared.
 | | same number + ordered `version` | **derived** |
 | `version`, `status`, `date` | producer only | declared |
 
-The number grammar is alpha-prefixed (`N500`, `V720`, `R610.4`) or dotted
+The number grammar is alpha-prefixed (`Q500`, `W720`, `P610.4`) or dotted
 numeric (`4.2.1`). A **bare integer is deliberately not a number**: admitting
 `12-things.md` or `2026-notes.md` would stamp a document number on most of a
 second brain that never had one.
@@ -239,8 +239,8 @@ change — rather than as "not possible".
    and supersession.
 
 2. **A reference to a parent-level number does not resolve to a child.** In the
-   synthetic corpus, `N130` in the body of one document does not resolve to a
-   document numbered `N130.2`; it is reported unresolved (`N130?`). This is
+   synthetic corpus, `Q130` in the body of one document does not resolve to a
+   document numbered `Q130.2`; it is reported unresolved (`Q130?`). This is
    honest but incomplete — the fix is a prefix-resolution rule
    (`subject` resolves to the unique document whose number starts with it), and
    it was left out because "unique" has to be defined against a real corpus
@@ -270,7 +270,7 @@ change — rather than as "not possible".
 
 # Door C: the index carries the sender's facts, and only theirs
 
-Ordered by vegnormal-okf (`20260826T224500Z-873805419`) on a measurement, not a
+Ordered by a downstream consumer (`20260826T224500Z-873805419`) on a measurement, not a
 preference. A pre-registered reasoning bake-off on 2026-08-27 ran the same
 bundle through two index shapes:
 
@@ -320,7 +320,7 @@ reads a value only to check the policy can render it.
 
 Operator directive 2026-08-27, verbatim: *"alt vi lager rundt OKF publiseres på
 Forgejo og skal virke for alt av innhold"* — so a design that only works for
-numbered norms is wrong even when it scores well on N100/N200/N500. Nothing in
+numbered norms is wrong even when it scores well on three numbered reference bundles. Nothing in
 `_project_facets` can key off a numbering scheme, and the suite says so with an
 unnumbered Norwegian meeting note (`status` + `date`, no number, no parent, no
 version) and with a document declaring none of the policy's keys, which renders
@@ -414,14 +414,14 @@ own `import_prefix` now states it directly, and M10 is killed.
 1. **`title` is not in `STRUCTURED_V1`'s facet set.** Widening it would move
    Door B's index bytes, so it stays a caller's key to name. For a sender whose
    concept paths are UUIDs this is the difference between a title in the index
-   and none — flagged to vegnormal-okf rather than decided here.
+   and none — flagged to that consumer rather than decided here.
 2. **Door C's index is an append plus a per-target refresh, not a projection of
    the whole bundle** (contrast D-S4). A concept removed from the bundle by hand
    leaves its entry behind. Reprojection would mean enumerating the directory,
    which no profile has asked this door to do.
 3. **Parent-prefix resolution is still deferred**, unchanged and for the
    unchanged reason: "unique prefix match" must be defined against a real
-   corpus. `vegnormal-okf` has that corpus; the count is theirs to take.
+   corpus. The consumer has that corpus; the count is theirs to take.
 4. **The before/after number is not ours to produce.** Whether the faceted index
    is worth its cost on a real corpus is answered by re-running the same arm
    with the same scoring, on their data.