STAGE 0.6.7

Released: 2026-07-24

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

Release Decision

This patch hardens installed project mapping and repository-only external audit refreshes. It closes false-green validation cases around source state, declared paths, result evidence, dirty-path accounting, and equivalent Git remote syntax.

No Safety Kernel obligation, project-map schema, normative method version, game runtime architecture, or visual-review route changes in this release.

What Changed

• Require installed project-map validation and source snapshots to target a Git work-tree root rather than an arbitrary nested directory.
• Validate every declared project-map path or glob, including bare directory paths and wildcard-only ownership patterns.
• Require wildcard declarations to match files present in the checked-out tree instead of accepting tracked files deleted from disk.
• Define committed_head, live_tree, and live_tree_plus_head review source semantics, and reject committed_head claims against dirty targets.
• Require operation result states such as passed, failed, and inconclusive to have a matching recorded evidence outcome.
• Normalize common HTTPS, SCP-style SSH, and ssh:// forms before comparing recorded and actual Git remotes.
• Count a rename or copy as one dirty status record in project maps and source snapshots.
• Require the repository-only external-audit refresher to inspect a repository root and to write its trial outside the inspected repository.
• Clarify the project-map authoring procedure field, packaged command dependencies, and the proposed 1.0 mapping-operation boundary.
• Record a bounded installed-0.6.6 ordinary-delivery probe without turning it into a general productivity claim.

Compatibility

• Project-map schemas remain at 0.1 and 0.3; no migration is required.
• stage_version and SPEC.md remain unchanged.
• The plugin still packages only stage-deliver-change and stage-map-project.
• Existing truthful maps remain compatible. A map that relied on a deleted wildcard match, dirty committed_head source, unsupported result state, or mismatched remote may now fail validation because the previous success was incorrect.

Evidence

The release candidate passed 292 tests across 27 modules, every supported map and study, frozen compatibility fingerprints, the Solo Unity profile, repository links, structured-file validation, and diff hygiene. Direct skill and plugin validation passed independently.

The tests exercise both canonical and installed-package copies of the mapping commands through real subprocesses. They cover nested-target rejection, read-only source snapshots, renamed paths, deleted wildcard matches, source basis, result evidence, and equivalent remote forms.

Limitations

• Machine-valid structure does not establish that a map is complete, useful, or accepted by its owner.
• Dirty-state metadata is not a content fingerprint. Use the packaged source snapshot helper and an independent before/after comparison when a read-only claim matters.
• The external-audit refresher is repository-owned maintainer tooling, not a general installed consumer command.
• Exported screenshots, videos, and contact sheets are evidence outputs only. Visual judgment belongs in the running game or native engine; a durable gallery should exist only when it is independently useful to the product or its developers.
• STAGE remains optimized first for the owner's personal workflow and does not claim independent adoption, empirical proof, or universal fit.