Migrate all variants to OKF v0.2#8
Merged
Merged
Conversation
Spec bumped upstream 2026-07-24 (knowledge-catalog PR #227). Core conformance rules are unchanged; this migration tracks the rest: - OKF_VERSION 0.1 -> 0.2 (model.py, index stamping, tests) - sources adopts the v0.2 mapping shape (SPEC 5.1): the frontmatter parser accepts one-level mapping entries in block lists, Page.path_list extracts resource values for path/edge fields, and new check_sources errors on entries missing resource, warns on legacy string entries and on non-bundle-absolute paths - resolve_link resolves bundle-absolute (leading-slash) path-field values; external URLs in path fields are skipped as provenance - CLAUDE.md templates show the mapping shape in all four variants - README conformance section updated for v0.2 (generated.at mapping, bundle-absolute now the spec-recommended link form) - ADR 0001 addendum: v0.2 6.1 adopted bundle-absolute as recommended - type-vocabulary position doc predictions scored against the outcome - migration assessment doc added (docs/research/2026-07-26)
The per-variant caps (110-145) were set at redesign-time size plus a few lines of slack, which made routine spec-driven edits into line golf. 200 keeps the cap as a bloat tripwire while leaving real headroom.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OKF bumped to v0.2 upstream on 2026-07-24 (GoogleCloudPlatform/knowledge-catalog#227). The core conformance rules are unchanged, so existing bundles stay conformant; this PR tracks everything else:
OKF_VERSION0.1 → 0.2 (version constant, index stamping, README).sourcesadopts the v0.2 mapping shape (SPEC §5.1): the frontmatter parser now accepts one-level mapping entries in block lists (- resource: /sources/foo.mdplus continuation lines),path_listextractsresourcevalues for path/edge fields, and a newcheck_sourceserrors on entries missingresourceand warns on legacy string entries and non-bundle-absolute paths.docs/research/2026-07-26-okf-v0.2-migration.md.Notes
index.mdokf_versionfrontmatter (§12), which resolves the one spec tension the v0.1 conformance work documented.timestamp→generated.at, body# Citations→sources) do not affect these templates; the README deviations text was updated to referencegenerated.at.