Skip to main content

STAGE 0.6.8

Released: 2026-07-24

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

Release Decision​

This patch hardens the installed project-map operations and the repository-backed external-audit refresher. It removes false preservation and publication claims without adding another practitioner workflow or artifact family.

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

What Changed​

  • Restore both external draft artifacts if either publication write fails, so a failed refresh cannot leave a mixed generation.
  • Reject external-audit publication when the inspected branch, revision, Git status, adopted map, or adopted manifest changes after generation.
  • Permit safe generated, external-generated, and runtime ownership families to describe outputs that do not exist yet, while source-bearing families still require resolved repository paths and every declaration rejects absolute paths, parent traversal, and backslash paths.
  • State the repository snapshot's actual Git source-state scope and exclusions instead of implying that ignored caches or the whole filesystem are covered.
  • Require two consecutive source-state observations to match before publishing a snapshot, rejecting repositories that change during capture.
  • Track source changes inside initialized submodules recursively, including nested dirty submodules that parent Git summaries cannot distinguish.
  • Track source changes inside untracked embedded Git repositories rather than treating the collapsed directory record as complete content evidence.
  • Record a clean-environment installed-0.6.7 mapping-command probe that validated the adopted map, confirmed unchanged source, and rejected a nested target.

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. Generated and runtime ownership declarations gain support for absent output families; source-bearing declarations remain strict.
  • Repository snapshot JSON shape is an explicitly incidental interface. Use the same helper release for the before and after receipts of one comparison; cross-version receipt comparison is not a supported compatibility promise.

Evidence​

The release candidate passed 303 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.

Focused subprocess tests exercise canonical and installed-package copies of the project-map validator and snapshot helper. Snapshot tests use real Git repositories to cover ignored caches, mid-capture mutation, direct and nested dirty submodules, untracked embedded repositories, worktrees, rename counts, and repository-boundary rejection. A clean STAGE repository dogfood capture recorded git_source_state, then produced a matching post-inspection receipt at the same branch and revision.

Limitations​

  • A source snapshot covers only the fields declared in its receipt. Ignored files and directories, Git internals other than origins, filesystem metadata, and external tool state remain outside its claim.
  • Two matching consecutive observations reject detected races but do not lock a repository or prove that no transient mutation occurred between system calls.
  • Uninitialized submodules have no available worktree source to inspect; their declared Git status remains recorded, but their absent content is not invented as evidence.
  • Machine-valid paths and provenance do not establish that a project map is semantically complete, useful, or accepted by its owner.
  • The external-audit refresher remains repository-owned maintainer tooling, not a general installed consumer command.
  • STAGE remains optimized first for the owner's personal workflow and does not claim independent adoption, empirical proof, or universal fit.
Last updated on