mason-context 0.12.0 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 0.14.0 — 2026-09-07
+
+Install Mason without installing Node or npm. Standalone downloads bundle the runtime for macOS, Linux, and Windows.
+
+- Add self-contained release archives with a pinned Node runtime and locked production dependencies for macOS, Linux (glibc), and Windows on x64/arm64. Shell and PowerShell installers verify downloads and retain unrelated launchers.
+- Add `mason setup`, `status`, `check`, `audit`, `review`, `drift`, and `mcp`, plus standalone `upgrade` and `uninstall`. Existing dedicated binaries and npm installation remain supported.
+- Run standalone project MCP and hooks from copied, pinned runtimes without system Node/npm. Global upgrades leave project versions unchanged; explicit setup preserves repair evidence and resets changed activation. Fresh clones install their own runtime.
+- Gate standalone publication on native installer/MCP/hook/upgrade/uninstall smoke tests for all six targets. Protocol validation is separate from native host trust and agent-performance evidence.
+
+See the [installation guide](docs/distribution.md). Existing npm users can continue with `npx --package mason-context@0.14.0 mason setup --host codex` (or `--host claude`), or install the standalone CLI and run `mason setup` for each host to switch its project runtime. Decision records and retained repair baselines need no migration.
+
+## 0.13.0 — 2026-09-06
+
+Mason now has one project setup operation for Codex and Claude Code. It preserves the original audit, installs a private pinned runtime, and configures MCP, lifecycle hooks, and assistant instructions without adding an npm manifest to the application. Status distinguishes configured integration from observed use.
+
+- Add unified `mason-auto setup --host codex|claude` and explicit MCP `mason_init(mode: "setup", host)` onboarding. Preserve audit evidence before documentation edits; install a pinned private runtime without changing application manifests; merge MCP, lifecycle hooks, instructions, and ignore rules with repeatable/resumable setup.
+- Add human-readable interactive setup status with structured JSON support. Distinguish configured, pending, active, and attention states using actual MCP context calls and complete hook lifecycles for the current installation and worktree/branch. Preserve native host trust and explicit disabled settings; configuration alone does not establish activation.
+- Scope automation cache keys to the inputs each audit check observes. Generated build churn no longer reruns unrelated checks; documented generated paths, workspace membership, manifest contents, and decision evidence remain dependencies. Read independent instruction-file metadata concurrently.
+- Classify automation failures in CLI JSON and MCP responses, preserve bounded execution receipts and durations, and keep unfinished or failed executions distinct from verified evidence. Report when storage exhaustion also prevents saving a failure receipt; clean up locks whose owner metadata could not be written.
+- Omit dependency advisories for conservatively recognized Android release-version-only changes. Unknown or mixed manifest edits remain advisory, and original retained advisories still require review.
+
+Install or upgrade from the target repository with `npx --package mason-context@0.13.0 mason-auto setup --host codex` (or `--host claude`). Review native MCP/hook trust and start a new session, then use `npx --package mason-context@0.13.0 mason-auto status` after an ordinary task. Setup never grants host trust. Existing manual installations remain supported; decision records and retained repair baselines require no migration.
+
+Validation covers both hosts' setup, original evidence retention, resumable installs, native Claude guidance imports, configuration preservation, and uncertain activation states. Packaged npm installation, real MCP connections, deterministic hook replay, and fresh-clone recovery passed. Replay establishes mechanism behavior; broader agent usefulness and large-repository performance remain separate evidence gaps.
+
 ## 0.12.0 — 2026-09-06
 
 Mason can now run documentation checks automatically through Claude Code and Codex hooks. It preserves findings before edits can hide them, resumes retained evidence across sessions, and verifies repairs against the final commit. Hook installation is opt-in.
@@ -53,4 +78,4 @@ Mason now provides useful project checks and decision capture without building a
 4. Replace workflows that re-verify a decision by saving identical content. An unchanged `save_decision` is now a no-op; use `review_decision` with `action: "reaffirm"` for accepted records. Content or attribution changes create a new proposed revision. A proposal cannot supersede an accepted record; review the replacement and retire the original separately.
 5. Audit, drift, and review JSON contracts remain additive. Review evidence is optional and advisory for default exit codes. With `--require-evidence`, current failures exit 1; incomplete, missing, skipped, stale, or unknown evidence exits 2. A current failure takes precedence over incomplete evidence. The existing missing-partner check still drives exit 1.
 
-Imported commands are never executed. Check provenance applies to its recorded commit and clean checkout, not local edits or complete test coverage. File associations identify relevant knowledge without claiming that a decision was violated. See [CI evidence usage](README.md#combine-ci-evidence-with-project-knowledge) for manifests and supported formats.
+Imported commands are never executed. Check provenance applies to its recorded commit and clean checkout, not local edits or complete test coverage. File associations identify relevant knowledge without claiming that a decision was violated. See [CI evidence usage](docs/checks.md#combine-ci-evidence-with-project-knowledge) for manifests and supported formats.