OKF v0.2.0 — transactional parser-backed mutations

OKF v0.2.0

v0.2.0 is the existing annotated tag for the transactional parser-backed mutation release. The tag was verified and was not moved or recreated.

Implementation commits

• 43f7214 — immutable snapshots, revisions, staged changes, CAS/idempotency, journaled filesystem commits, recovery, and graph correctness.
• bb9c169 — Goldmark/yaml.v3-backed lossless mutation spans, fail-closed presentation errors, overlay/source improvements, and verification corpus.

Public API and compatibility

• immutable store.Snapshot and algorithm-qualified revisions;
• versioned store.ChangeSet, operations, and preconditions;
• Preview and optimistic Commit with inspectable conflicts;
• bounded idempotency receipts;
• durable journaled store/fs commit and recovery;
• lossless EnsureRelation, MoveConcept, and RenameFragment planning.

Existing bundle parsing, validation, graph, CLI, and MCP wire contracts remain source compatible. No methodology profiles, workflow states, or business-specific domain types were added.

Platform and isolation scope

The tagged durable store/fs implementation targets Darwin and Linux. Leases are advisory: raw editors do not coordinate, and raw readers can observe a multi-file rename during publication. Recovery completes a recorded transaction; it is not distributed isolation.

The post-tag v0.2.x hardening in 74ca10e makes unsupported targets compile-safe and gives Open/OpenContext a typed runtime error. That follow-up does not alter the existing tag contents.

Verification and traceability

• Transactional mutation issue #1
• Release-engineering issue #2
• Reviewable PR #3
• Green PR CI run
• Green protected-main CI run
• Final review cleanup PR #4 and its green PR CI run
• Semantic test-suite cleanup PR #5 and its green PR CI run
• Version-tag integrity PR #6 and its green PR CI run
• Final green protected-main CI run
• Green disposable v* tag-trigger run, proving the zero-base tag path; the probe tag was deleted after verification
• Requirement-to-evidence table
• Tagged-source mutation evidence

The hosted CI runs above verify the post-tag release-engineering hardening. Tagged-source verification is recorded separately; the runs are not represented as tag-native checks.

This is a Go-module/source release. No prebuilt binaries are published.