open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Releases Activity

feat(okf): enforce §3 okf_version shape, bump convention 0.1 -> 0.2

Browse source 
The 2026-07-23 reservation said enforcement waits until "the emitters have
migrated". Measured rather than assumed, and the emitter set turned out to be
TWO, not three:

  okr @0059da7       okf_version: 0.1 + okf_layout: kb-layout-2026-06. Migrated.
  linkedin-studio    scaffold.ts:38 -> okf_version: 0.1. Never carried a layout
                     string; has no okf_layout and needs none.
  ms-ai-architect    NOT an emitter. Zero index.md in the repo; okf_version
                     appears in one planning doc. The status table already said
                     "designed, not built" -- only the word "emitters" implied it.

Swept the whole marketplace plus the sibling consumer repos: every live
okf_version value is 0.1. The flip is a no-op today and locks the invariant.

The gate checks SHAPE (/^\d+(\.\d+)*$/), never membership: the upstream value
set is Google's (spec §12), so a bundle targeting a newer version passes. A
membership check would be the convention claiming a set it says it does not own
-- the over-reach class this round has corrected three times. Presence stays
unenforced (reported, not failed) as a separate §3 MUST.

Convention bumped 0.1 -> 0.2 by this log's own criterion: the set of conforming
bundles changed (the spec explicitly said a layout string "conforms today", and
rollout rule 6 defines conformance as gate output). The §12 per-plugin re-check
is pre-measured as finding zero violations.

Also closes a parity blind spot found while landing this: check-okf-parity
compared the okf_version VALUE, which is identical exactly when two impls
disagree about whether it is acceptable -- a false "agree" on the axis the gate
exists to watch. The signature now carries a boolean shape verdict, with
red-marker-layout as the committed red proof. Its "diverge" expectation encodes
okr's lag (they still pure-echo) and flips to "agree" when they mirror it.

And a correction the round earned: portfolio-optimiser enumerated their own
bundle surface and it is four, not three. The dormant fourth
(reference_domain.py:49 -> package data at :70) has no flag form at all, so our
published claim that the re-measurement surfaced "one" unreported entry was
itself one-of-two. Sharpens the standing rule: a search shaped like one entry
type cannot see another; install-vs-fixture is one instance, not the class.

Suite 73 -> 78. coord: PO replied, okr + llm-ingestion-okf notified (the latter
under the standing promise to flag any okf-check.mjs change).
This commit is contained in:
Kjell Tore Guttormsen 2026-07-25 20:32:30 +02:00
commit 6a72b26985
9 changed files with 227 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

25
scripts/check-okf-parity.test.mjs
View file

@ -93,6 +93,31 @@ test('red-proof: BOM+CRLF typed concept diverges; the same file as UTF-8/LF agre
}
});
// --- marker axis: §3 okf_version shape enforcement (catalog enforces, okr echoes) ---
// This axis was invisible to the gate until the signature carried the shape verdict: the
// signature compared the okf_version VALUE, which is identical across impls precisely when
// they disagree about whether it is acceptable. A false "agree" on the one axis the gate
// exists to watch.
test('marker axis: a layout string in okf_version diverges; a version-shaped one agrees', async () => {
const impls = [CATALOG, OKR];
const layout = tmpRoot();
const versioned = tmpRoot();
try {
writeFileSync(join(layout, 'index.md'), 'okf_version: kb-layout-2026-06\n\n# Bundle\n');
writeFileSync(join(layout, 'c.md'), TYPED);
const evLayout = await evaluateBundle(layout, impls);
assert.equal(evLayout.diverges, true, 'catalog enforces the shape, okr still pure-echoes -> diverge');
writeFileSync(join(versioned, 'index.md'), ROOTINDEX);
writeFileSync(join(versioned, 'c.md'), TYPED);
const evVersioned = await evaluateBundle(versioned, impls);
assert.equal(evVersioned.diverges, false, 'a version-shaped value is accepted by both -> agree');
} finally {
rmSync(layout, { recursive: true, force: true });
rmSync(versioned, { recursive: true, force: true });
}
});
// --- Layer 2b: symlink axis (runtime-materialized; must not hang/crash) ---
test('symlink axis: symlinked file + dir + loop are skipped by both, no hang, agree', async () => {
const dir = tmpRoot();