docs(okf-v0.2): the pilot answered before the tag existed, and it changed the tag

All three pilots accepted. Their measurements land in the plan now rather than
as failed runs later, which is the entire return on asking before building.

Six corrections, each measured by the consumer rather than reasoned by us:

- A-E6 specified `okf_version: "0.2"` quoted. Catalog measured the quoted form
  failing their shape regex with exit 1, and a UTF-8 BOM making the marker
  invisible while still exiting 0. Both now stated as raw-byte expectations.
- A-E2 said the diff lies only *inside* the frontmatter block. No bundle whose
  root index has no frontmatter block can satisfy that together with A-E6.
- B-E3 covers one of catalog's three gates; the other two cannot see our
  fixture. Recorded so the report is not read as broader than it is.
- Our claim that no gate keys on the version value was wrong as formulated:
  check-okf-parity.mjs puts the raw value in its signature. It compares without
  judging -- verdict-invariant, not value-blind.
- C-E1's ground truth is 524 non-reserved documents, not 522; 522 was correct
  at d2c12d2.
- `materialize_bundle` gains keyword-only `profile=DEFAULT` on po-claude's
  request. The signature already has a `*`, so their three-positional call path
  stays source-compatible and additivity becomes a property of the signature
  instead of something a consumer measures.

Also recorded: po-claude closed their index-parser defect themselves (f41264f),
so do not design around it; the assumption under it -- "a generated index has no
frontmatter" -- is not peculiar to them. Dropping the superseded `timestamp`
draws one catalog warning per concept file, decided after the pilot, not before.

The estimate's open caveat is discharged by reading profiles.py:197: emit is one
formatting path, the validator already admits list values, so only the emitter
side is missing and the sizing stands.

CLAUDE.md gains a standing constraint: consumer content stays at form level in
public files. The wiki's bundle is private pending an Anthropic ToS assessment,
their report goes back through coord, and a push is not reversible.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A2aKJxLejT9S8jYwoZ9fut

CLAUDE.md

@@ -152,6 +152,14 @@ and fixtures, never code.
   and `docs/oppstartsprompt.md` are LOCAL-ONLY (gitignored) — never commit
   session state or internal briefs. No secrets, sober English prose, no
   marketing language.
+- **Consumer content stays at form level in public files.** Some consumers we
+  read are private (`claude-code-llm-wiki` is, pending an Anthropic ToS
+  assessment). Key names, counts, gate names, profile fields and contract shapes
+  are publishable; page bodies, full title or path lists from a consumer's
+  bundle, and Anthropic-derived prose are not. Findings about a private
+  consumer's data go back to them through coord, never as a file here. This
+  costs nothing — every question this library asks of a consumer is about shapes
+  and key sets — and it is not reversible once pushed.
 - After `git commit`: push to Forgejo (`git push origin`) immediately.
   Never GitHub.