docs(okf-check): correct the body-text fallback rationale — 1 emitter, not 2
linkedin-studio migrated its bundle-root okf_version from body text into the root index.md frontmatter block (their bc47c18, which is their HEAD). The comment justifying the body-text fallback still claimed two live emitters. Verified against ground truth rather than taken from the notice: - linkedin-studio scaffold.ts now emits okf_version 0.1 inside the frontmatter block (measured 2026-08-02 at bc47c18). - okr scripts/okf-index.mjs:204 still pushes it as body text, after the `# heading` line with no `---` delimiters (measured 2026-08-02 at d634385). So the fallback stays — it is still load-bearing for okr, and check-okf-parity still compares this value against okr's live checker. Only the count and the removal condition change. Comment-only; 106/106 tests green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RDSiMcgLMpEETwtkc86Nym
This commit is contained in:
parent
a3e7254a00
commit
029ffb878d
1 changed files with 6 additions and 4 deletions
|
|
@ -81,11 +81,13 @@ function unquote(value) {
|
||||||
// §12:773-775, read at 3fcbb9f). This convention previously said the opposite.
|
// §12:773-775, read at 3fcbb9f). This convention previously said the opposite.
|
||||||
//
|
//
|
||||||
// The pre-0.3 body-text form is still READ and still passes. That is deliberate, not leftover:
|
// The pre-0.3 body-text form is still READ and still passes. That is deliberate, not leftover:
|
||||||
// two marketplace emitters write it today (okr scripts/okf-index.mjs:204 and linkedin-studio
|
// ONE marketplace emitter still writes it (okr scripts/okf-index.mjs:204 — body text, emitted
|
||||||
// scaffold.ts:38, both measured 2026-07-31), and check-okf-parity compares this very value
|
// after the `# heading` line with no `---` delimiters; measured 2026-08-02 at okr d634385), and
|
||||||
// against okr's LIVE checker. Reading frontmatter alone would report null here and 0.1 there,
|
// check-okf-parity compares this very value against okr's LIVE checker. Reading frontmatter alone
|
||||||
// splitting the parity signature on every body-text bundle before a single emitter had migrated.
|
// would report null here and 0.1 there, splitting the parity signature on every body-text bundle.
|
||||||
// So placement is DECLARED, not enforced: the gate reports which form it found and moves on.
|
// So placement is DECLARED, not enforced: the gate reports which form it found and moves on.
|
||||||
|
// linkedin-studio was the second emitter; it migrated to root frontmatter at its bc47c18
|
||||||
|
// (scaffold.ts, measured 2026-08-02). The fallback becomes removable only once okr migrates too.
|
||||||
//
|
//
|
||||||
// okf_layout is deliberately NOT read here. §12 (v0.3) keeps it in body text, because upstream's
|
// okf_layout is deliberately NOT read here. §12 (v0.3) keeps it in body text, because upstream's
|
||||||
// exception is enumerated to ONE key ("an okf_version key"); this convention's own extension
|
// exception is enumerated to ONE key ("an okf_version key"); this convention's own extension
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue