docs(consume,build): both parent defaults stay off, and the reason is now a measurement

K3-21 B. `cli.DEFAULT_SHELL_PARENT`'s comment said it was off because `okf
consume` reads no `parent` key; after A that sentence was false and the
default was unmeasured in both directions. Re-measured on the one standard
with heading-only sections: hit@1, hit@8 and hit@50 stay 6/6 at both k with
the known-positive at rank 1, but the link's bundle-absolute path repeats
the document's directory in 675 bodies, and the delivered set moved on 2 of
8 questions at the default k and 3 of 8 at k 50, newly delivered shells
matching the question only through that path on 1 of 3, 4 of 7 and 6 of 23
-- the saturation K3-20 took out of the id signal, back through the body.
Off.

`consume.DEFAULT_FOLLOW_PARENT`: the same delivered set as the pointer (16
of 16 payloads), 6 of 6 correct either way on questions whose answers are
never shells, at +2 488 / +2 746 B on the 2 of 8 default-k payloads holding a
linked shell and up to +20 817 B at k 50. Off.

A test holds both defaults and that the false sentence is gone.

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

tests/test_parent_text.py

@@ -157,3 +157,12 @@ def test_the_cli_takes_the_flag_and_its_opt_out(tmp_path: Path) -> None:
     assert consume.parse_args([str(bundle), "--question", SHELL]).follow_parent is (
         consume.DEFAULT_FOLLOW_PARENT
     )
+
+
+def test_both_defaults_are_off_and_the_reason_is_a_measurement() -> None:
+    """K3-21 B re-measured both once `okf consume` read `parent`. A default is
+    a published promise, so it gets a test that goes red when it moves; the
+    numbers behind each are in the comment above the constant."""
+    assert consume.DEFAULT_FOLLOW_PARENT is False
+    assert cli.DEFAULT_SHELL_PARENT is False
+    assert "reads no `parent` key" not in Path(cli.__file__).read_text(encoding="utf-8")