docs(okf-v0.2): the pilot baseline was ambiguous and we asserted it was shared

Two corrections to claims this repo made, both measured rather than argued.

1. `examples/ingest-golden-file/` names TWO different fixtures. Ours holds
   ingest-orders.md + ingest-products.md; po-claude's holds ingest-costs.md +
   ingest-edge.md; the manifests differ at line 3 char 41; content-file overlap
   is zero and the only shared filename, index.md, is byte-different. We agreed
   a pilot baseline by name, and the name pointed at two files. A-E1 is the stop
   condition, so a mismatched baseline would have surfaced as a profile defect.
   The pilot runs THEIR fixture -- A-E1 asserts byte-identity with what their
   pinned version produces, which is a claim about their baseline, not ours --
   and the report must state repo and path.

2. "The shared fixture, ratified by two independent implementations" was false.
   We took it from an incoming message and passed it on the same day without
   measuring, while holding a standing rule that incoming messages are premises,
   not facts, and applying that rule only to spec readings. Commons caught it.

The :29 argument in V1 survives in commons' stronger form: the clause requires
reproducing "the shared golden extractions", the definite article presumes one
set where there are two, so it has no referent today. (b) therefore does not
break a shared fixture we have -- it cements that one can never arise, since a
producer-bearing field inside the byte-compared prefix makes convergence
impossible by construction. The :280 half stays observable and fires on our next
release regardless.

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

docs/plan/okf-v0.2-alignment.md

@@ -388,11 +388,26 @@ than showing up as a failed run afterwards.
   their byte-frozen golden: they have no `timestamp` field at all (they have
   `ingested_at`, a different field with a different mandate), and no `# Citations`
   heading in any body they produce or read. Their current form is literally
-  `generated: true`, so A-E3 is calibrated correctly against them. Baseline:
-  `examples/ingest-golden-file/manifest.json`, chosen because it is byte-frozen
-  alongside its `expected-bundle/` and `ingested-at.txt` **and** is the shared
-  fixture against the sibling implementation — so A-E1 is an exact byte
-  comparison against a baseline two independent implementations already ratified.
+  `generated: true`, so A-E3 is calibrated correctly against them.
+
+  **Baseline: `examples/ingest-golden-file/` — and the name is ambiguous.**
+  Measured 2026-07-26 after commons checked the claim: *both* repos have a path by
+  that name holding *different* fixtures. Ours is `ingest-orders.md` +
+  `ingest-products.md`; theirs is `ingest-costs.md` + `ingest-edge.md`; the
+  manifests differ (`cmp`: line 3, char 41); content-file overlap is **zero**. The
+  only shared filename is `index.md`, and those are byte-different.
+
+  So the reason we gave for choosing it — "the shared fixture against the sibling
+  implementation, ratified by two independent implementations" — is **false**. We
+  took it from their message and passed it on the same day without measuring,
+  having a standing rule that an incoming message is a premise rather than fact
+  and applying it only to spec readings. Commons caught it.
+
+  The fixture remains the right choice, for a different reason: A-E1 asserts
+  byte-identity with what *their pinned version* produces, which is a claim about
+  *their* baseline, not ours. The pilot runs **their** fixture, and the report
+  states repo and path explicitly. Corrected to them before the run — A-E1 is the
+  stop condition, so a mismatched baseline would have surfaced as a profile defect.
 - **`catalog` — yes.** Accepted the provisional terms explicitly. Runs after
   2026-07-30. Pre-measured their own gate on a synthetic proxy (6 runs,
   `okf-check.mjs` unmodified at `6a72b26`) because we asked them not to trust a
@@ -712,9 +727,21 @@ They measured the blast radius as normative-only for them —
 `examples/ingest-golden-*` does not exist in commons. **It is observable here
 today.** Four fixtures carry `generated:` on line 8 inside the byte-compared
 prefix (`ingest-golden-file/…/ingest-orders.md`, `…/ingest-products.md`,
-`ingest-golden-sql/…/ingest-metrics.md`, `ingest-golden-http/…/ingest-status.md`),
-and `ingest-golden-file` is the shared fixture against the sibling implementation
-— the same one po-claude runs the pilot against.
+`ingest-golden-sql/…/ingest-metrics.md`, `ingest-golden-http/…/ingest-status.md`).
+
+**The `:29` argument survives, but not in the form we sent it.** We wrote that
+`ingest-golden-file` is the fixture *shared* with the sibling implementation.
+Commons checked, and it is not: our set and po-claude's are disjoint, and commons
+has none — `git log --all` confirms they never did. `:29` requires reproducing
+"**the shared** golden extractions byte for byte", and the definite article
+presumes one set where there are two, so the clause has no referent today and each
+implementation reproduces its own by construction.
+
+Their reformulation is stronger than our original: (b) does not break a shared
+fixture we have — **(b) cements that a shared fixture can never arise**, because a
+producer-bearing field inside the byte-compared prefix makes convergence
+impossible by construction, later as much as now. The `:280` half stays observable
+here and fires on our next release either way.
 
 So we now back **(d)**, commons' fourth option: `generated: { by:
 "process:<fixed id>", at: <ingested_at> }`, using v0.2 §7's explicit