P11 (order 20260910T225652Z), NOK 0, no push. PATH okf is 0.8.1 (uv tool list,
__version__, --help flags). src/ untouched.
(ix) on 0.8.1 shipped: 629/623/6 and 629/620/9 - PM's predicted denominators,
now measured. --no-source-quota alone gives back 629/621/8 and 629/617/12 in
both arms; the exact numbers are an interaction with tie-shared-rank (both
arms) and stem-prefix (open arm). --title-covered never fires here (byte-
identical payload). 0.8.1 with the three new rules off reproduces the 0.7.0
payloads' delivered lists and budgets.
P10 section 6 diagnosed: a bisect over okf's own history (known-positive at
both ends) puts the price schedule's loss at okf 38104b7, whose only consume
code change is DOCUMENT_PRIOR_EXPONENT 1.0 -> 0.5; putting that one constant
back in a copy returns the old payload byte for byte. tie-shared-rank is ruled
out; known_positive 10349 -> 12563 is a version marker, not the mechanism. On
0.8.1 the schedule is over_budget_after_knapsack, not below_k.
okf check on 0.8.1 has 15 rules, not 16: rule 16 (bundle_mismatch) is on okf
main 7cca9e0, in no tag. Run from an export of 7cca9e0 the K3-15 pair is rc 1
and the right pair rc 0 - a real cross-corpus mismatch, not an okf defect.
Offer rows on four corpora: identifiers unchanged (65/50, 435, 982, 272).
The P10 doc gets dated additions in sections 4 and 6; the old sentences stand.
Test docstring: +2 lines naming the 0.8.1 rule count, no behaviour change.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
RED. P9 measured `okf check` (0.7.0, 15 rules) rc 1 on both K2 payloads with 20
findings, every one of them `excerpt_unnamed`. On po's side the same absence is
SILENT: `_excerpt_header` appends `title:` only `if excerpt.title is not None`.
F1 (reporting) over F2 (refusing), and F2's price is a NUMBER: of the 20 payload
files in this repository 10 carry a `title` on every excerpt and 10 on none, and
among the ten F2 would refuse is the ONE git-tracked payload fixture
(tests/fixtures/prepass/bygg-energi-mikro-fixture.payload.json, 4 excerpts,
0 titled). F2 would need a tracked fixture rewritten to make its own rule green,
and would reverse PrepassExcerpt's written "a required field would refuse every
payload written before today".
6 failed, 1 passed. The one green is `test_no_existing_payload_is_refused` --
F1's promise, true before the rule and required to stay true through it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>