fix(okf-v0.2): generated.by is process:okf-ingest — the id commons decided

v0.5.0a1 shipped the one actor value the spec owner had already excluded.
Caught before any pilot was notified, so it costs a tag, not a migration.

Commons decided <fast id> = process:okf-ingest on 2026-07-31, on this repo's
own proposal, superseding option (d) (process:llm-ingestion-okf) chosen here on
07-27. The exclusion is ingest-spec.md:7-8, frozen on the spec being
framework-neutral: normalising OUR repo name into the normative id would force
every other conformant implementation to write it into its own output. Verified
against three independent sources before touching anything — commons' coord
message 20260731T154140Z, their plan :215-216/:244, and their STATE :37.

Why this had to land before the pilot notifications rather than after:

  actor is both the stamp written and the value owned back (OwnershipPolicy),
  and recognition is one-way. A pilot that had run Test A against the excluded
  id would hold bundles this library stops recognising the moment the id is
  corrected — collision_unstamped on their OWN files. That is the A-E5 failure
  mode, and we would have inflicted it.

Worse, it would not have shown up as a failure: the plan's A-E3 expectation
(:854) named the same excluded value as the code, so Test A would have PASSED
and confirmed the error. Expectation and implementation agreeing is not
evidence when both predate the decision.

Nothing in the wild carried the old value: OKF_V0_2 did not exist at v0.4.0, so
the profile has never been released. v0.5.0a1 is abandoned, not moved — a tag
already on a public remote does not get force-pushed, and the history should
say plainly that a1 was wrong.

A-E3 now records both corrections with dates. The V1 paragraph at :1169 is
superseded in place rather than rewritten: its reasoning still holds, only its
outcome moved.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CVTup4v7tW9QiVyBENk2LV

tests/test_okf_v0_2_profile.py

@@ -18,11 +18,13 @@ Three things, in the order the risk runs:
    type: `root`, `connection_ref`, `base_url`. `credential_ref` is never a
    locator and never reaches frontmatter.
 
-`generated.by` is `process:llm-ingestion-okf` — option (d) from the plan's V1,
-chosen by the operator 2026-07-27 over the `<producer>/<version>` form A-E3 was
-written against. The value carries no version, which is what keeps a byte-
-compared fixture stable across releases. **A-E3 is now stale in the pilot
-specification and owes po-claude a correction.**
+`generated.by` is `process:okf-ingest` — decided by commons 2026-07-31 on this
+repo's own proposal, superseding option (d) (`process:llm-ingestion-okf`), which
+was chosen here 2026-07-27 and is now explicitly excluded. The exclusion is
+`ingest-spec.md:7-8`, frozen on the spec being framework-neutral: normalising
+*our* repo name would force every other conformant implementation to write it
+into its own output. The value carries no version either way, which is what
+keeps a byte-compared fixture stable across releases.
 """
 
 from __future__ import annotations
@@ -46,7 +48,7 @@ from llm_ingestion_okf.profiles import DEFAULT, OKF_LATEST, OKF_V0_2, STRICT_V1,
 
 INGESTED_AT = "2026-07-25T12:00:00Z"
 STAMP = "manifest@0123456789abcdef"
-V0_2_STAMP = f"{{ by: process:llm-ingestion-okf, at: {INGESTED_AT} }}"
+V0_2_STAMP = f"{{ by: process:okf-ingest, at: {INGESTED_AT} }}"
 
 
 def _manifest(source: Source) -> Manifest:

tests/test_profile_threading.py

@@ -88,7 +88,7 @@ def test_v0_2_profile_reaches_the_emitted_frontmatter(file_setup: tuple[Path, Pa
     manifest_path, bundle = file_setup
     materialize_bundle(manifest_path, bundle, INGESTED_AT, profile=OKF_V0_2)
     text = (bundle / "ingest-orders.md").read_text(encoding="utf-8")
-    assert f"generated: {{ by: process:llm-ingestion-okf, at: {INGESTED_AT} }}" in text
+    assert f"generated: {{ by: process:okf-ingest, at: {INGESTED_AT} }}" in text
     assert "sources: [{ id: catalogue-1, resource: data }]" in text
     assert "generated: true" not in text