mason-context 0.13.0 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # 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.
@@ -67,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.