STAGE 0.6.10

Released: 2026-07-24

The plugin package version is 0.6.10. SPEC.md is method version 0.6.

Release Decision

This patch hardens the optional project-map contract and its installed validator after a source-level public-contract audit. It closes false-green paths in operation evidence, preflight, ownership, path resolution, and external-audit provenance without changing the Safety Kernel or either supported project-map schema.

STAGE 1.0.0 remains an owner decision. This release does not infer acceptance of the proposed 1.x compatibility contract.

What Changed

• Require every 0.3 operation to declare material purpose, readiness, effects, and at least one supported nonblank evidence claim.
• Require exact operation results to use one coherent scoped outcome claim and a same-claim classified verification route; split or outcome-free records no longer compose into a false result.
• Make operation preflight validate the complete semantic map contract before evaluating capabilities, authority, or safety, and fail closed when a capability declaration is omitted.
• Reject blank ownership coordinates and require unresolved authority to name an accountable decision owner plus a material prohibited mutation.
• Reject blank recorded or caller-supplied external-audit repository identities so empty provenance cannot match itself.
• Constrain map paths to project-owned, case-sensitive, segment-aware resolution; reject ignored host state, escaping symlinks, artifact-root traversal, and unresolved generated ownership sources.
• Require repository-backed 0.1 to 0.3 migration to validate both the immutable source and the completed candidate before atomic publication.
• Clarify read-only inspection, operation completion, human/wire vocabulary, and production audio evidence boundaries in installed guidance.
• Turn the 1.0 readiness document into an explicit owner decision surface while leaving its acceptance state pending.

Compatibility

• SPEC.md remains method version 0.6.
• Project-map schemas remain exactly 0.1 and 0.3; no migration is required.
• The plugin still packages only stage-deliver-change and the explicit-only stage-map-project route.
• Valid existing maps and command invocations remain compatible. Inputs that relied on empty evidence, unresolved authority, unsafe paths, or blank provenance now fail instead of receiving an unsupported success result.
• The installed validator and snapshot helper retain their documented read-only and 0-only success boundaries.

Evidence

The release candidate passed 347 tests across 27 modules, every supported map and study, frozen schema fingerprints, the Solo Unity profile, repository links, structured-file validation, and diff hygiene. The current Codex plugin validator and both skill validators passed independently.

Focused regressions cover malformed operation contracts, exact-result claim linkage, preflight semantics, unresolved ownership, whitespace-only evidence, blank external provenance, generated ownership, project-owned path resolution, schema migration, and canonical/installed package parity. Installed-0.6.9 dogfood also exercised validation and scoped repository snapshots from a disposable release clone without changing deliberately stale Git index bytes.

Limitations

• Schema-valid paths, provenance, and evidence coordinates do not establish that a project map is complete, useful, current, or accepted by its owner.
• A live-tree review records Git coordinates but does not fingerprint dirty file content. Use matching snapshot receipts for the narrower read-only source-state preservation claim they define.
• Preflight validates declared capability, authority, safety, and semantics; it does not execute an operation or prove its project preconditions.
• The package supplies scripts and dependency declarations, not a Python runtime or environment.
• STAGE remains optimized for the owner's personal workflow and does not claim independent adoption, productivity improvement, or universal fit.