feat(propose,cli): the sheet's rows, the wrapped sentence, and a default that moved

K3 round 3, order 20260908T170037Z-3622420612-from-.claude, plus the PM
injection of 17:55Z carrying the operator's D3 answer.

TWO NEW RULES, both OFF by default.

`--sheet-section-rows` cuts an open table block at the rows that label its
sections: a RUN of at least three rows whose first cell is a bare numeric
label. It is the first rule here that opens a span INSIDE a table, and the
opposite direction from Arm E -- that arm decides how far a block extends,
this decides where it is cut inside. The spreadsheet is the one file type no
arm had ever moved: 1 concept -> 12 on the priced sheet, of which 11 are the
reference's 11 cost groups. The run guard buys exactly three candidates on the
corpus (the rows stating a computation basis), and each section carries its
own `source_sheet` + `source_rows`, verified on the artifact.

`--drop-wrapped-outline` declines an outline candidate whose line continues
onto the next one. Round 2 falsified the LENGTH axis on this case; this one is
not about size. Over the 12-document sample it separates 8 of 34 candidates --
the quoted regulation paragraphs and the risk-table rows -- and none of the 26
the operator kept. Position 4: 4 concepts -> 1, the reference. The cell is
`treffer` by count and lossy by bytes, and the report says so.

Whole corpus, one cached extraction: 1 of 39 documents changes under the first
rule (0 of 32 pdf, 0 of 5 docx), 5 of 39 under the second (all pdf). Arm B and
F2 are byte-identical against a frozen c3b645b, both halves by `diff -r`.

THE `okf build` DEFAULT MOVED, and this is the operator's decision executed,
not a side effect: no flag now means `--outline-run 3 --unit-fold`. Each arm
keeps an explicit opt-out (`--outline-run 0`, `--no-unit-fold`) and the pair
reproduces the pre-move bytes exactly. The proposer's own defaults do NOT
move: they are what the goldens and every published reproduction block are
pinned to, so the two layers now disagree on purpose and `cli.py` says where.
Two shipped expectations moved with it and both are stated in place. MEASURED
AND REPORTED BACK: the configuration made default scores 2 of 12 on the unit
worksheet, `docx` 0 of 3 -- Arm F's published 5 of 12 was measured with
`--table-grid` ON, and without it the fold has no joined table to fold.

Position 1 is declined for the second round on the axis the order named: 3 of
3 recovered chapters have body under them, so "heading-on-heading" separates 0
of 3.

The K2 ranking control round 2 could not measure: two bundles from frozen
c3b645b differing only in `--keep-table-heading`, 2 of 1108 files apart. The
priced concept ranks 96 of 629 in BOTH and is delivered at rank 10 in both, so
the flag buys 35 payload bytes and zero rank positions. Round 2's prediction
is falsified: the concept's NAME was already restored by the orphan-name
inheritance; the flag adds the heading LINE.

The stale S7 literal is restated where it stood (`c759a657...`, 171 614 B,
re-measured on this HEAD), so the next order cannot inherit the superseded one.

1397 -> 1414 tests. Report: docs/2026-09-08-k3-runde3-per-filtype.md.

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

CLAUDE.md

@@ -259,18 +259,28 @@ and fixtures, never code.
   collide); `--ingested-at` and `--proposed-at` default to one shared epoch
   constant rather than the clock, because a wall-clock default takes
   rebuild-equals-incremental away from anyone who omits them.
-  **Four segmentation rules are REACHABLE here and all four are OFF by
+  **Six segmentation rules are REACHABLE here and all six are OFF by
   default** (2026-09-08): `--outline-run N` (Arm D), `--table-grid` (Arm E),
-  `--unit-fold` (Arm F) and `--keep-table-heading` (D1), each passed to the
-  proposer unchanged. Until that day the build path called the proposer with no
+  `--unit-fold` (Arm F), `--keep-table-heading` (D1), `--sheet-section-rows`
+  and `--drop-wrapped-outline` (both D3), each passed to the proposer
+  unchanged. Until that day the build path called the proposer with no
   arm flag at all, so a tender PDF that Arm D splits into nine concepts landed
   as one -- a build path a full arm behind the proposer. Exposing them is not
   the same decision as moving one: **which arm should ship as the default is
   the operator's, and a no-flag build stays byte-identical** (measured by
   digest before and after, and by Arm E over all 43 corpus documents). Arm C
   (`--max-segment-chars`) stays unexposed: no reference has ever been measured
-  for its cap. Reports: `docs/2026-09-08-k3-arm-f-mot-enhetsarket.md` and
-  `docs/2026-09-08-k3-runde2-per-filtype.md`.
+  for its cap. The two D3 rules read grammars nothing else here reads: a table
+  row's FIRST CELL (a run of bare numeric labels cuts the block that holds
+  them, which is the only way to reach a sheet whose units are rows and the
+  opposite direction from Arm E), and whether a RECOVERED heading's line is a
+  wrapped sentence (a heading is a complete line; quoted regulation and a
+  recovered table row are not). Both remove or add nothing anywhere else: over
+  the 43-document corpus they change 1 and 5 of 39 readable documents, and
+  **0 of 5 `docx` either way**. Reports:
+  `docs/2026-09-08-k3-arm-f-mot-enhetsarket.md`,
+  `docs/2026-09-08-k3-runde2-per-filtype.md` and
+  `docs/2026-09-08-k3-runde3-per-filtype.md`.
 - Consume a bundle: `python3 tools/okf_consume.py <bundle> --question "<q>"
   [--k N] [--limit N] [--out PATH] [--ref IDENTITY]` — the **pre-pass**
   `docs/consumption-contract.md` § 1 defines, and the only reading direction