§12 says "When Google bumps OKF, each plugin re-checks conformance." Google
bumped 2026-07-25; commons ruled the trigger catalog's to pull and the plugin
owners' to perform. This is the pull.
Held: upstream has NOT moved (git ls-remote answers 3fcbb9f, identical to the
mirror the 0.3 round read; SPEC last touched 2026-07-24 in 780fe9d). All seven
upstream anchors resolve exactly, quotes verbatim. The §3 floor is conformant
with upstream §11. No floor change -> the convention stays at 0.3.
Corrected:
1. §14 said "OKF SPEC v0.1" while linking blob/main/okf/SPEC.md, which has
served v0.2 since 2026-07-24 — a reader following our own reference got
v0.2 under a v0.1 label.
2. §3 attributed to upstream a rule upstream does not state: "upstream binds
the index.md requirement to the bundle root alone", cited to commons'
method-spec.md. Google requires index.md NOWHERE (SPEC :117 "Optional",
:504 "MAY appear in any directory", :759 consumers MUST NOT reject for
missing index files). Three rungs, not two; ours is highest either way, so
only the attribution was wrong.
3. §4 now names v0.2's second breaking change (# Citations -> sources).
Measured 2026-08-03: no marketplace emitter writes # Citations; the one
live exposure is a plan, not code — ms-ai-architect's brief still names an
upstream v0.1 example as the template to copy.
Suites 120/120, 0 fail. check-versions 12/12 OK.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01THEvHPWM11RupX24wBGKLu
Kjell Tore Guttormsen
552784e262