feat(check): the contract and the checker state the payload's v1.1 forms

C6. `docs/consumption-contract.md` now says what the pre-pass emits:

- SS 2.5 point 2: sub-questions are written in the bundle's terms and given to
  the pre-pass in ONE run where it takes several;
- SS 8's example is `okf-consumption/2` as shipped: `withheld` is the
  `{total, by_rule, nearest, complete}` mapping, `coverage` carries
  `absent_terms` and `weak`, an excerpt carries `text`, `text_sha256`,
  `passage` and `own_title`; point 1 closes the identity on `withheld.total`;
- point 7 keeps the falsified verdicts on record and states the one reading
  carried since v1.1, `weak`, with its rule: a word held in no form, or
  nothing delivered -- whether a word exists at all, which does not move with
  question style or corpus size the way the two shares did;
- point 8 the passage (`{start, end, of}`, `text_sha256` over the passage,
  `sha256` still the file's), point 9 several sub-questions in one run (one
  cut, `questions`, `subquestions`, per-sub-question coverage), point 10 a
  title inherited from the heading above, with `own_title`;
- SS 10 names this library's default ranking (BM25) and `--ranking fusion`.

`okf check` holds the two new forms a reader acts on: `passage_malformed`
(not whole numbers with 0 <= start < end <= of) and `subquestions_unindexed`
(not distinct indices into `questions`, or indices in a payload listing none).
17 -> 19 rules; the two tests that pin the published count move with it.
Each rule is held against a real payload (0 findings) and against that
payload broken six ways.

Editing the contract moved the SS 7.4 known-positive, measured once after the
edit: 19 837 -> 23 672 encoded, 19 358 -> 23 092 raw, delta 479 -> 580. The
example payload and `skills/okf-consume` are regenerated by the published
recipe and `okf check` reports 19 rules, 0 findings on them.

Suite on a clean tree after `git add`: 2443 passed, 2 skipped, 4 xfailed.
ruff, ruff format, mypy --strict clean.

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

skills/okf-consume/SKILL.md

@@ -290,7 +290,7 @@ carries its denominator.
 | Limit | `120000` |
 | Unit | `utf-8 bytes of emitted JSON` |
 | Instrument | `okf_consume.measure (len of the ensure_ascii=False JSON encoding, utf-8)` |
-| Known-positive | `docs/consumption-contract.md, encoded as a JSON string` at `19837` |
+| Known-positive | `docs/consumption-contract.md, encoded as a JSON string` at `23672` |
 
 The instrument reproduces the known-positive figure before any of its own
 numbers are believed. Report what the run actually spent.

skills/okf-consume/references/README.md

@@ -37,7 +37,7 @@ Why each part is there:
   checkout on one machine. The line strips that checkout's prefix and nothing
   else, and a test holds the shipped `SKILL.md` to the generator's output with
   exactly that prefix removed.
-- **`okf check`** should report `conformant: 17 rules over 3 excerpts and 0
+- **`okf check`** should report `conformant: 19 rules over 3 excerpts and 0
   withheld entries, 0 findings` and exit 0.
 
 The generated `name` is `b-golden-segmented-okf-v0-2-consume` while this

skills/okf-consume/references/example-payload.json

@@ -11,10 +11,10 @@
     "spent": 2289,
     "known_positive": {
       "case": "docs/consumption-contract.md, encoded as a JSON string",
-      "expected": 19837,
-      "measured": 19837,
-      "raw_bytes": 19358,
-      "encoding_delta": 479
+      "expected": 23672,
+      "measured": 23672,
+      "raw_bytes": 23092,
+      "encoding_delta": 580
     }
   },
   "denominators": {