Historical record. This page describes the results and requirements recorded in revision 61e75e9. It is not a report of checks on the current revision.

OKF v0.2.2

v0.2.2 was tagged on 2026-09-17. This page records that release, not later changes in the current working tree. Existing tags must not be moved or recreated.

Included work

The release implements the task09–21 program:

• the pinned OKF v0.2 contract, conformance corpus, typed bundle model, version-aware validation, and graph projection profile;
• lossless structural YAML mutation, closed semantic v0.2 operations, and proof-bound transactional migration from v0.1;
• store compatibility guardrails, durable store/fs recovery, and bounded journal payload decoding;
• version-aware CLI commands, nine schema-validated MCP tools, synchronized EN/RU guidance, fixtures, examples, and plugin packaging.

The historical regression suites were reorganized by behavior without reducing their 401 top-level Test*/Fuzz* inventory. The tracked development evidence records the original hashes and old-to-new test mapping.

Migration hardening

• A failed production store open no longer leaves a typed-nil interface for deferred cleanup, so okf migrate --write returns an operational error instead of panicking.
• Darwin treats the fixed system aliases /var and /tmp as their /private/var and /private/tmp targets before the descriptor capability walk. Arbitrary symlink path components remain rejected.
• MCP live target-noop, CLI dry-run, and CLI --write have distinct durable adapter contracts documented across the English and Russian surfaces.

Compatibility and limitations

• The document format remains okf_version: "0.2"; the repository release, plugin package, and document-spec versions remain independent.
• Public Go APIs, ChangeSet v1, and CommitReceipt v1 stay compatible.
• Execution and attestation runtime, attester ABI, sandboxing, network dereference, and invented trust scoring remain out of scope.
• The annotated v0.2.2 tag points to commit 8e5ef56.