docs(privacy): no private path and no coordination id in what this span added

A public repository should not carry the layout of the machine it was written
on, and it should not carry the identifiers of a queue nobody outside can see.
Six places in material this span added or changed did.

Neutral text, same facts: a private queue path in the EOL report, a private
note path in two docstrings and one report header, and four order identifiers
opening four reports. Where a sentence lost its source it says `internal
measurement note` -- the measurement is still named, the path is not.

One of them was output, not prose: row 9 of the retrieval gate printed a
`~/corpora/...` path to stdout on every run. It says the bundles exist on the
machine the row was written against; the row already takes `--k2 SET SHA
BUNDLE` from anyone who holds them.

Measured with the patterns as given, and both validated against a
known-positive on `df5a118` first -- an unvalidated pattern reporting zero is
not a measurement:

* `~/\.claude|/Users/|coord/.*/orders` over the 74 files the span touches:
  **9 -> 6**. The six left are deliberate: two README lines telling a reader to
  install a skill into their OWN `~/.claude/skills`, one prose line arguing
  that `/Users/...` is not more portable than a relative path, and three lines
  of `tests/test_retrieval_gate.py`'s own known-positive for this exact check,
  which removing would disarm it.
* `[0-9]{8}T[0-9]{6}Z-[0-9]+` over the 38 files the span ADDED: **4 -> 0**.

A note on the method, because the first run of the first grep reported 0 and
was wrong: zsh does not word-split an unquoted parameter, so
`git grep -- $FILES` passed 74 names as one argument and matched no file at
all. Both numbers above come from `$(git diff --name-only ...)`, which zsh does
split, and the known-positive is what made the false zero visible.

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

docs/2026-09-17-bildestien-0-10-1.md

@@ -1,8 +1,7 @@
 # Two findings in the image path, closed before push (0.10.1)
 
-Order `20260917T135034Z-4840022792`, from an independent review of `v0.10.0`
-(`~/.claude/docs/2026-09-17-review-okf-0.10.0.local.md`, LOCAL-ONLY). The
-review's verdict was "safe to push, with reservations": no blocker, and
+From an independent review of `v0.10.0` (an internal measurement note, not
+committed here). The review's verdict was "safe to push, with reservations": no blocker, and
 byte-identity, determinism and `--no-assets` parity all hold. Both findings
 land with the shipped defaults (`--assets` on, `--gate guard-trusted-source`),
 and both are new in 0.10.0, because before it no reader read an `<img>`

docs/2026-09-18-regnskapsgaten-herdet.md

@@ -1,7 +1,7 @@
 # The content-accounting gate, hardened: the judge opens the bundle itself
 
-2026-09-18. Order `20260917T142837Z-445369650`, from an independent adversarial
-review of `0b00de4` commissioned after the accounting was built. The review's
+2026-09-18. Raised by an independent adversarial review of `0b00de4`,
+commissioned after the accounting was built. The review's
 verdict was that the gate is "an honest RED today, but cannot be trusted as a
 judge once it turns green": it was a calculator over a report the judged party
 writes. This is what changed, measured.

docs/2026-09-19-eol-stroemmen-som-ikke-maler.md

@@ -136,9 +136,8 @@ the flag, so no row moves.
 
 ## 5. The count in a closing message
 
-The previous closing message said "the five other pending orders" where there
-were six. Measured here with `find ~/.claude/coord/llm-ingestion-okf/orders
--maxdepth 1 -name '*.md' | wc -l` at closing time, not from memory.
+The previous closing message miscounted the outstanding work items. The count
+here was measured at closing time against the queue itself, not from memory.
 
 ## 6. The bytes, and every gate
 

docs/2026-09-19-hvert-baaret-bilde-kan-vises.md

@@ -1,7 +1,7 @@
 # Every carried image is one a model can be shown
 
-`llm-ingestion-okf`, 2026-09-19. Order `20260919T033624Z-4535320370`, raised
-from PM's measurement of the frozen R761 package's `assets/` directory.
+`llm-ingestion-okf`, 2026-09-19. Raised from an internal measurement of the
+frozen R761 package's `assets/` directory.
 
 Nothing is tagged, pushed or released here. No new version: the entries go
 under the untagged `[0.10.1]`.

docs/2026-09-19-regnskapsgaten-rest-og-normaliseringsdoren.md

@@ -1,7 +1,7 @@
 # The accounting gate's remainder, and one normalisation door
 
-`llm-ingestion-okf`, 2026-09-19. Order `20260918T110211Z-9941518407`, raised
-from PM's re-measurement of `ed8d9d7`
+`llm-ingestion-okf`, 2026-09-19. Raised
+from a re-measurement of `ed8d9d7`
 (verdict: PARTIAL). Six holes, each with a red test written in its own commit,
 plus the operator's decision of 2026-09-18 about U+00AD.
 

tools/okf_retrieval_gate.py

@@ -93,8 +93,8 @@ CLASSES: tuple[tuple[str, str], ...] = (
 #: this gate must fell.
 MUTANT_BAR = 0.90
 
-#: K2's denominator, from `~/.claude/docs/okf-utfallsgrunnlag.md`. The bundles
-#: are on this machine; the gold set is nowhere, by design.
+#: K2's denominator, from an internal measurement note. The bundles exist on
+#: the machine this row was written against; the gold set is nowhere, by design.
 K2_QUESTIONS = 6
 
 
@@ -2187,8 +2187,8 @@ def row_nine(k2: tuple[QuestionSet, Mapping[str, Path]] | None = None) -> Row:
             RED,
             f"not measured: 0 of {K2_QUESTIONS} questions have a gold set anywhere",
             [
-                "    the bundles exist (~/corpora/okf-telling-20260829/K2-bundle-*), the "
-                "answer key does not",
+                "    the bundles exist on the machine this row was written "
+                "against; the answer key does not, anywhere",
                 "    a set that cannot be measured is a red number, never an absent row",
                 "    who can write it: whoever holds the K2 corpus -- it names documents "
                 "that may not be committed here, so it arrives as a path plus a sha256",