test(mutants,assets): a mutant is judged by the suite that owns it, 45 of 45

The runner could only run one test file, which is why PM's three
survivors from `43331fc` could not be added: two are held by the gate's
row 3 and one by the soft-hyphen door's suite. A mutant now names its
suite; the catalogue goes 39 to 45.

X3 and X4 rewritten against the code as it now stands -- a mutant table
is a copy of the code it mutates, and this round moved the lines both of
them quoted. X6 is the defeated state exactly, X7 cuts the ledger off at
its source, X8 removes the cursor rule, P6/P11/P12 are PM's three.

Two survivors on the first run, both findings, both closed:
- X4 survived because every forgery arm now fails on the ledger check
  before the binding is reached. An arm was added where the run DID book
  the pair and the block stating it points at another picture.
- X5 survived the WHOLE suite -- 2134 passed with the disarming removed
  -- because a document-supplied field can no longer reach the gate. The
  property is about the BUNDLE and not about one judge, so it is kept and
  measured in `tests/test_assets.py`, with a known-positive counting the
  run's own two fields on the same expression.

killed 45 of 45, exit 0. Report, CHANGELOG and CLAUDE.md written.

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

CLAUDE.md

@@ -1081,6 +1081,35 @@ and fixtures, never code.
   and not FIDELITY, which its docstring now states: a converter writing a
   blank PNG is accepted, the suite fells that mutant and the judge cannot.
   Report: `docs/2026-09-19-bmp-resten-terminator-og-pekerblokk.md`.
+  **AND THAT ROUND NARROWED BOTH DEFECTS WITHOUT CLOSING EITHER.** A POINTER
+  BLOCK IS A FORM AND A FORM IS NOT A SIGNATURE: measured through the real
+  `okf build`, one ordinary HTML file with **two `<p>` elements** writes the
+  two lines `_POINTER` matches, and the same refused BMP read as held again --
+  also with `<p>`+`<br>`, and with a markdown note beside the HTML carrier,
+  **3 of 3**. So the pair is read from the RUN's own ledger (`--accounting`
+  now books `conversions: [{from, to}]` per document, off `assets.conversion`)
+  and the bundle text only CONFIRMS it: the confirmation can be forged and the
+  ledger cannot. **Chosen over neutralising pointer-shaped text at
+  extraction**, which would change what every document SAYS to defend a tool
+  outside the build. A build with no accounting door reports a converted image
+  claimed-and-not-found rather than believing it. Measured: 3 of 3 forged ->
+  refused with the known-positive True in all three, the text-level regression
+  guard 3 arms -> 13, R761 rebuilt `diff -r`-identical, 50 assets, **19 of 19**
+  conversions confirmed against 19 declared, SHY 71, u = 0, d = 0. And the
+  TERMINATOR asks only that a stream say it is finished, which it may do
+  anywhere: a stream whose FIRST two bytes are the EOB escape was carried with
+  **32 of 32** pixels never decoded while Pillow refuses the same file. The
+  cursor must now also stand at or past the end of the last row. **The line is
+  the CURSOR and not the pixels** -- a delta and an end-of-line escape state
+  their skip, so every decoder agrees on the index-0 pixels they pass over,
+  and a pixel-coverage count would refuse both constructions the format
+  defines. The corpus cannot choose (over the **25** RLE8 BMPs the delivery
+  ships, 25 of 25 paint every pixel, 25 of 25 reach the end, **0 of 25** use a
+  delta) and an independent decoder can: Pillow reads **5 of 8** streams and
+  refuses the same **3**, one short by a single pixel. The earlier `19 of 19`
+  figures above are the BUNDLE's carried assets; 25 is what the delivery
+  ships. Report:
+  `docs/2026-09-19-pekerblokken-bindes-til-kjoringen.md`.
 - **Account for content: `okf build --accounting PATH` and its judge
   `python3 tools/okf_accounting_gate.py` (2026-09-17).**
   - The gate was written RED at `0b00de4` and turned GREEN on all six rows by