STAGE 0.6.6

Released: 2026-07-24

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

Release Decision

This patch makes the explicit external project-mapping route operational from the installed plugin alone. A consumer can now snapshot a target repository, author against exact schema-compatible references, and validate the resulting manifest without reading STAGE repository implementation source.

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

What Changed

• Packaged the immutable 0.1 and 0.3 project-map schemas.
• Added an exact empty 0.3 manifest template and a complete schema-valid populated example.
• Added a schema-synchronized reference containing every enumerated authoring value accepted by the 0.3 schema.
• Packaged the read-only repository snapshot helper and generic project-map validator used by external audits.
• Directed consumers to invoke packaged commands rather than inspect their implementation unless an actual operation fails.
• Required one project inventory for an unchanged source snapshot instead of repeated rg, find, ls-files, or ls-tree reassurance passes.
• Added package tests that compare templates, examples, schemas, commands, and value vocabulary against their repository-owned canonical sources.

Compatibility

• Existing adopted maps, external audits, and historical studies remain valid.
• Project-map schemas remain at 0.1 and 0.3; no migration is required.
• stage_version: "0.3" and SPEC.md remain unchanged.
• The plugin still packages only stage-deliver-change and stage-map-project.
• Exact skill prose and helper implementation remain unstable internal detail; their documented command interfaces and artifact compatibility are retained.

Evidence

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

A fixed-revision synthetic game fixture was audited repeatedly from isolated installed-plugin candidates. Before the complete reference package, the consumer read validator and schema implementation source, repeated source inventory work, and repaired guessed enum values after an invalid first draft. The final candidate used one target inventory, did not inspect validator or schema implementation source, passed project-map validation on the first attempt, and left the target repository unchanged according to independent before-and-after snapshots.

In that bounded comparison, observed action calls fell from 77 to 48 and aggregate input fell from approximately 1.26 million to 0.83 million tokens. These are diagnostic observations from one synthetic fixture under one host configuration. They are not release gates, causal treatment evidence, or a general efficiency claim.

Limitations

• Machine-valid structure does not establish that a map is semantically correct, complete, useful, or accepted by its owner.
• The dogfood fixture is synthetic and does not establish independent adoption or transferability.
• A single inventory is sufficient only while the recorded source snapshot is unchanged; new source state requires a new snapshot and inspection.
• Packaged commands reduce setup and archaeology but do not remove the need to inspect project-owned evidence.
• External audits still require accountable human review before adoption.
• STAGE remains optimized first for the owner's personal workflow and does not claim empirical proof or universal fit.