@jstn-sdk/ma 0.1.13 → 0.14.1

package/docs/README.md

@@ -6,11 +6,16 @@ Meta-Architect documentation is organized by operator task.
 
 - [Getting Started](./getting-started.md)
 - [Production Demo Guide](../DEMO.md)
+- [Real Demo Runbook](./demo/REAL_DEMO_RUNBOOK.md)
+- [Demo Story](./demo/DEMO_STORY.md)
+- [Prospect Checklist](./demo/PROSPECT_CHECKLIST.md)
 - [Coverage Matrix](../COVERAGE.md)
 - [Release Spec](./release-spec.md)
 - [Skills Reference](./skills.md)
 - umbrella, gated lanes, and helper skill distinctions live in the Skills Reference
 - [Installed Support Bundle](./installed-sdk.md)
+- [Runtime retention](./runtime-retention.md)
+- [External architect review](./architect-review.md)
 
 ## Packaging and installation
 
@@ -18,12 +23,13 @@ Meta-Architect documentation is organized by operator task.
 - published helper-skill and plugin-mirror expectations live in Skills Publishing
 - Linux-native distro package expectations live in the Release Spec and release-readiness docs
 - [MCP Setup](./mcp-setup.md)
+- [Continuity Graph](./continuity-graph.md)
 - [Plugin Bundle](../plugins/meta-architect/README.md)
 
 ## QA and readiness
 
-- [Release Readiness 0.1.13](./qa/release-readiness-0.1.13.md)
-- [Release Issue Gates 0.1.13](./qa/release-issue-gates-0.1.13.json)
+- [Release Readiness 0.14.1](./qa/release-readiness-0.14.1.md)
+- [Release Issue Gates 0.14.1](./qa/release-issue-gates-0.14.1.json)
 
 ## Repo structure references
 

package/docs/autonomous-tasks.md

@@ -0,0 +1,46 @@
+# Autonomous tasks
+
+Meta-Architect persists autonomous work in `.ma/tasks/autonomous-queue.json`.
+The queue is separate from the team-run registry and is driven by the existing
+Maestro manager.
+
+## Intake
+
+```bash
+ma task add "Implement the parser" --priority high --label backend
+ma task bulk tasks.json
+cat tasks.yaml | ma task bulk - --format yaml
+ma task list --json
+```
+
+Each task receives a durable contract, status, retry budget, dependencies,
+labels, optional deadline, selected environment capabilities, and evidence.
+Duplicate IDs, malformed contracts, unknown dependencies, and dependency
+cycles are rejected before persistence.
+
+## Execution
+
+```bash
+ma task run --concurrency 3
+ma task run --max-tasks 20 --json
+ma task cancel task-123 "No longer needed"
+```
+
+Independent queued tasks run up to the configured concurrency. Dependencies
+run first; failed, blocked, cancelled, expired, or unsafe tasks do not run
+their downstream work. A failed task is retried up to `maxAttempts`, and the
+queue remains resumable after interruption.
+
+Environment discovery records installed project and user capabilities before
+execution. Existing skills are observed rather than claimed or modified, and
+vendor invocation metadata uses the environment's native `$`, `/`, or plain
+command convention when a vendor is selected.
+
+Every state transition emits a Maestro event under `.ma/events/` and persists
+the latest queue atomically. Safe local work proceeds automatically; goals
+that imply credentials, destructive changes, publication, production, or
+other external mutations are blocked with an actionable reason.
+
+The default runner delegates to the existing Maestro manager. Tests and host
+integrations can inject `execute(task)` into `runAutonomousTasks` without
+changing the queue contract.

package/docs/codex-integration.md

@@ -0,0 +1,16 @@
+# Codex integration
+
+Meta-Architect drives the installed Codex binary; it does not reproduce Codex's TUI or runtime.
+
+`CodexAppServerClient` uses the real stdio JSON-RPC app-server lifecycle: initialize, thread start/resume/fork/list/archive, turn start/interrupt, configuration read/write, and streamed notifications. `runCodexExec()` uses `codex exec --json` for bounded automation, and `generateCodexBindings()` delegates type/schema generation to the running Codex binary.
+
+All child processes use argument arrays with `shell: false`, time out, and surface non-zero exits. Goal support remains Codex-owned: prompts may request the installed `create_goal`, `get_goal`, and `update_goal` tools, while Meta-Architect only consumes the resulting notifications.
+
+```js
+import { CodexAppServerClient } from "@jstn-sdk/ma";
+
+const codex = new CodexAppServerClient();
+await codex.initialize();
+const thread = await codex.startThread({ ephemeral: true });
+await codex.startTurn({ threadId: thread.id, input: [{ type: "text", text: "Run the quality gate" }] });
+```

package/docs/getting-started.md

@@ -26,10 +26,15 @@ Recommended CLI install for macOS, Linux, WSL, and Git-Bash:
 
 ```bash
 # One-line install (POSIX shells only; use WSL/Git-Bash on Windows)
-curl -fsSL https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@main/scripts/install.sh | sh
+curl -fsSLo install.sh https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@latest/scripts/install.sh && curl -fsSLo install.sh.sha256 https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@latest/scripts/install.sh.sha256 && sed 's#scripts/install.sh#install.sh#' install.sh.sha256 | sha256sum -c - && sh install.sh
 ```
 
 The jsDelivr installer runs `npm i -g @openai/codex@latest @jstn-sdk/ma@latest`, then `ma setup`.
+Use `sh install.sh --dry-run` to inspect the plan, `--no-setup` to skip local
+runtime writes, or `--no-skills` to skip skill/support-bundle writes. The
+installer prints Node/npm/Codex versions and an uninstall command after a real
+install. npm installation is side-effect free; host selection and skill
+installation happen explicitly during the first interactive `ma` launch.
 
 Debian-family install:
 
@@ -51,6 +56,11 @@ sudo dnf install ./meta-architect-<version>-1.noarch.rpm
 
 Default supported npm fallback:
 
+On the first interactive `ma` launch, Meta-Architect detects supported CLI and
+IDE host markers and asks once for the installation scope and targets. The
+selection is recorded in `.ma/prelaunch.json`; CI and piped/non-interactive
+launches skip the prompt and preserve the default Codex bootstrap behavior.
+
 ```bash
 # Install
 npm i -g @openai/codex@latest @jstn-sdk/ma@latest
@@ -101,7 +111,7 @@ Required output:
 5. Data model and storage choices
 6. Auth/security considerations
 7. DX/UX considerations
-8. Delivery plan for v0.1.13
+8. Delivery plan for v0.14.1
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -161,6 +171,10 @@ Expected effects:
 - `mcp/`, `docs/`, and `sprint/` surfaces exist
 - `ma` opens Codex with the Meta-Architect helper posture when run with no arguments
 
+`.ma/` is the canonical Meta-Architect project namespace. A legacy `.omx/` directory may
+exist for oh-my-codex orchestration history, but new MA setup and generated guidance never
+use it as runtime state.
+
 Expected output:
 
 ```text
@@ -242,6 +256,11 @@ Contract split:
 - it runs the same environment checks without changing files
 - it prints the current readiness state and exact next step
 
+Maintainers use `npm run package:doctor` (also available as
+`npm run release:doctor`) for release and package artifact completeness. It
+does not inspect the installed user environment; both commands use the same
+status vocabulary so their scopes remain explicit.
+
 `ma sdk-path` prints the installed packaged support-bundle root for relevant files such as prompts, MCP files, sprint files, scripts, plugin metadata, and templates.
 
 ## 5. Configure MCP / GitMCP
@@ -291,7 +310,7 @@ See [docs/mcp-setup.md](./mcp-setup.md) for endpoint policy and evidence semanti
 ## 6. Secondary helper flow
 
 ```bash
-ma idea "Prepare Meta-Architect v0.1.13 for a production package release with real install docs, Obsidian brain-context support, learning-loop reliability, and package proof artifacts."
+ma idea "Prepare Meta-Architect v0.14.1 for a production package release with real install docs, Obsidian brain-context support, learning-loop reliability, and package proof artifacts."
 ```
 
 Expected effects:
@@ -476,7 +495,7 @@ If `$build` fails:
 
 ```bash
 ma setup
-ma idea "Prepare Meta-Architect v0.1.13 for a production package release with real install docs, Obsidian brain-context support, learning-loop reliability, and package proof artifacts."
+ma idea "Prepare Meta-Architect v0.14.1 for a production package release with real install docs, Obsidian brain-context support, learning-loop reliability, and package proof artifacts."
 ma run '$arch'
 ma run '$sage'
 ma run '$flow'
@@ -504,13 +523,18 @@ Canonical demo reference:
 After implementation work is complete:
 
 ```bash
-ma merge feature/ui development
-ma release development prod
+ma merge feature/ui dev
+ma release dev main
 ```
 
+These commands record approval by default; they do not execute Git. Use
+`--dry-run` to run preflight and print the exact merge command without changing
+state, or `--execute` to run the checked, explicit merge on the target branch.
+Both modes require a clean worktree and a valid source branch.
+
 Expected effects:
-- merge only succeeds for `feature/* -> development`
-- release only succeeds for `development|release/* -> prod`
+- merge only succeeds for `feature/* -> dev`
+- release only succeeds for `dev|release/* -> main`
 - final statuses advance to:
   - `build_status = DONE`
   - `merge_status = MERGED_TO_DEVELOPMENT`

package/docs/mcp-setup.md

@@ -1,5 +1,9 @@
 # MCP / GitMCP Setup
 
+The MCP client advertises the installed Meta-Architect version read from the
+package metadata. `ma doctor` reports the same value, while `0.0.0-dev` is used
+only when development metadata is unavailable.
+
 1. Use approved discovery accelerators when you need to find OSS candidates faster than browsing GitHub directly.
 2. Add repo-specific GitMCP endpoints in `mcp/servers.json` for any project you want to treat as approved evidence.
 3. Confirm categories in `mcp/collections.json`.
@@ -15,6 +19,7 @@
 - `team_run`
 - `code_intel`
 - `playbooks`
+- `context`
 
 `playbooks` is a read-only packaged capability. It does not point at external MCP servers and it does not repurpose `mcp/collections.json`.
 
@@ -77,9 +82,16 @@ To enable bridge-backed live verification, configure a trusted local bridge comm
 
 ```bash
 export MA_MCP_REMOTE_BRIDGE_CMD="mcp-remote {url}"
+export MA_MCP_REMOTE_BRIDGE_ALLOWLIST="mcp-remote"
 ```
 
-The `{url}` placeholder is replaced with the exact repo endpoint from `mcp/servers.json`. Use a preinstalled, trusted bridge binary or wrapper; do not depend on automatic package downloads in production verification.
+The `{url}` placeholder is replaced with the exact repo endpoint from `mcp/servers.json`. The command must be explicitly allowlisted by basename or exact path in `MA_MCP_REMOTE_BRIDGE_ALLOWLIST`, or by a project-local `mcp/bridge.json` file such as `{ "allowedCommands": ["mcp-remote"] }`. Use a preinstalled, trusted bridge binary or wrapper; do not depend on automatic package downloads in production verification.
+
+Bridge startup, exit, failure, and bounded stderr diagnostics are recorded as
+redacted receipts under `.ma/evidence/mcp-bridge-receipts/`. The bridge receives
+only a minimal environment allowlist, and request timeouts are bounded by
+`MA_MCP_REQUEST_TIMEOUT_MS` (15 seconds by default). `ma doctor` should be used
+to verify the command policy before live evidence collection.
 
 When no bridge is configured:
 - direct-SSE-compatible MCP servers can still verify normally
@@ -110,3 +122,20 @@ The current release intentionally includes both broad discovery lists and core-s
 
 Obsidian-derived notes remain `vault_context`.
 They do not count as `build_evidence` unless `$sage`, `$vet`, or another owning lane promotes a specific claim with source-backed proof.
+## Local context capability
+
+The setup-owned local MCP registry exposes read-only context evidence through
+the `context` capability. Its resources are:
+
+- `context://project-index` — source-truth project fingerprint and file metadata.
+- `context://freshness` — incremental refresh status and changed-file evidence.
+- `context://learning` — validated learning-loop state.
+- `context://obsidian` — validated vault index and operation receipts when configured.
+- `context://hooks` — hook configuration and audit evidence.
+- `context://commands` — source-derived command map.
+- `context://agent-brief` — bounded first-read generated context.
+- `context://architecture` — bounded generated architecture map.
+
+Every response includes `record_type`, `authority`, `source`, and `available`
+metadata. Missing optional artifacts return an unavailable result; writes are
+not exposed by this capability.

package/docs/qa/{release-issue-gates-0.1.13.json → release-issue-gates-0.14.1.json}

@@ -1,7 +1,7 @@
 {
   "schemaVersion": "1.0.0",
-  "releaseVersion": "0.1.13",
-  "releaseTag": "v0.1.13",
+  "releaseVersion": "0.14.1",
+  "releaseTag": "v0.14.1",
   "previousVersion": "0.1.12",
   "passContract": {
     "allIssuesMustPassProduction": true,
@@ -13,9 +13,9 @@
       "number": 13,
       "title": "[feature] Meta tracking: next-release core gated lanes and runtime maturity program",
       "url": "https://github.com/JustineDevs/meta-architect/issues/13",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "All child next-release issues are individually passed with evidence.",
@@ -26,11 +26,11 @@
       "proof": {
         "implementationEvidence": [
           "Child issues #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #28, #29 are individually marked passed in this gate with implementation, verification, and production evidence.",
-          "docs/qa/release-readiness-0.1.13.md links this gate as the canonical v0.1.13 issue proof artifact.",
+          "docs/qa/release-readiness-0.14.1.md links this gate as the canonical v0.14.1 issue proof artifact.",
           "src/release-issue-gates.js validates all tracked issue statuses, labels, proof arrays, milestone, release version, and release tag."
         ],
         "verificationEvidence": [
-          "node-based validateReleaseIssueGates(document, { version: 0.1.13 }) returns valid true after this evidence update.",
+          "node-based validateReleaseIssueGates(document, { version: 0.14.1 }) returns valid true after this evidence update.",
           "test/release-issue-gates.test.js covers failing pending gates and passing proof gates.",
           "npm run check passed after core implementation changes (Biome checked 117 files).",
           "npm test passed after core implementation changes (30/30 tests).",
@@ -45,15 +45,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 14,
       "title": "[feature] Reconcile core gated lane contracts and harden the `$build` state loop",
       "url": "https://github.com/JustineDevs/meta-architect/issues/14",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Core gated lane contracts are implemented in repo code and prompts.",
@@ -83,15 +83,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 15,
       "title": "[feature] Add the operational scratchpad layer and `maestro-state.json` control-plane ledger",
       "url": "https://github.com/JustineDevs/meta-architect/issues/15",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Scratchpad and maestro-state ledger are implemented with safe ownership boundaries.",
@@ -119,15 +119,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 16,
       "title": "[feature] Add read-only supply-chain exposure intake and build circuit-breaker orchestration",
       "url": "https://github.com/JustineDevs/meta-architect/issues/16",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Supply-chain intake is read-only and cannot mutate release state directly.",
@@ -157,15 +157,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 17,
       "title": "[feature] Add the Redaction Gateway for provider-bound context sanitization",
       "url": "https://github.com/JustineDevs/meta-architect/issues/17",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Provider-bound context sanitization is implemented.",
@@ -192,15 +192,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 18,
       "title": "[feature] Add the Alignment Sentinel for runtime drift detection and bounded worker reboot",
       "url": "https://github.com/JustineDevs/meta-architect/issues/18",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Runtime drift detection is implemented.",
@@ -227,15 +227,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 19,
       "title": "[feature] Add the Synthetic Workspace Virtualizer for low-overhead bounded verification",
       "url": "https://github.com/JustineDevs/meta-architect/issues/19",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Synthetic workspace virtualization is implemented without replacing real release checks.",
@@ -262,15 +262,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 20,
       "title": "[feature] Add the Quorum Review Engine as an optional high-assurance `$build` substep",
       "url": "https://github.com/JustineDevs/meta-architect/issues/20",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Quorum review is available as an optional high-assurance substep.",
@@ -297,15 +297,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 21,
       "title": "[feature] Add an incremental code graph and bounded `$rehearse` trajectory mode",
       "url": "https://github.com/JustineDevs/meta-architect/issues/21",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Incremental code graph support is implemented.",
@@ -332,15 +332,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 22,
       "title": "[feature] Add the multi-agent skills registry and exported compatibility payload contract",
       "url": "https://github.com/JustineDevs/meta-architect/issues/22",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Universal and non-universal agent registry is implemented.",
@@ -367,15 +367,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 23,
       "title": "[feature] Harden Linux packaging and cross-agent install verification against the real release contract",
       "url": "https://github.com/JustineDevs/meta-architect/issues/23",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Linux package artifacts build for Debian, Arch, and RPM lanes.",
@@ -390,32 +390,32 @@
           "test/package-install-smoke.test.js and test/package-exports.test.js cover install and package export behavior."
         ],
         "verificationEvidence": [
-          "npm run linux:packages:build passed and produced dist/meta-architect_0.1.13_all.deb, dist/meta-architect-0.1.13-1-any.pkg.tar.xz, and dist/meta-architect-0.1.13-1.noarch.rpm.",
+          "npm run linux:packages:build passed and produced dist/meta-architect_0.14.1_all.deb, dist/meta-architect-0.14.1-1-any.pkg.tar.xz, and dist/meta-architect-0.14.1-1.noarch.rpm.",
           "npm run linux:packages:smoke passed against extracted package payloads.",
-          "npm run release:assets passed and validated all v0.1.13 release artifacts plus dist/linux-package-manifest.json.",
+          "npm run release:assets passed and validated all v0.14.1 release artifacts plus dist/linux-package-manifest.json.",
           "npm run check passed after core implementation changes (Biome checked 117 files).",
           "npm test passed after core implementation changes (30/30 tests).",
           "node bin/ma.js doctor returned READY after runtime artifact validation.",
           "node bin/ma.js status reported Evidence VERIFIED, Logic GREEN, Security GREEN, Experience GREEN, and Build DONE."
         ],
         "productionEvidence": [
-          "dist/meta-architect_0.1.13_all.deb validated by release:assets at 1889688 bytes.",
-          "dist/meta-architect-0.1.13-1-any.pkg.tar.xz validated by release:assets at 1892412 bytes.",
-          "dist/meta-architect-0.1.13-1.noarch.rpm validated by release:assets at 1990404 bytes.",
+          "dist/meta-architect_0.14.1_all.deb validated by release:assets at 1889688 bytes.",
+          "dist/meta-architect-0.14.1-1-any.pkg.tar.xz validated by release:assets at 1892412 bytes.",
+          "dist/meta-architect-0.14.1-1.noarch.rpm validated by release:assets at 1990404 bytes.",
           "node bin/ma.js status exercised the shipped CLI runtime and reported all release lanes green.",
           "node bin/ma.js doctor exercised install/runtime readiness checks and returned READY.",
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 24,
       "title": "[feature] Add Obsidian Integration Core as default vault/plugin capability",
       "url": "https://github.com/JustineDevs/meta-architect/issues/24",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Obsidian integration is default core, not optional.",
@@ -447,15 +447,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 25,
       "title": "[feature] Add Context Economy Core as default compression capability",
       "url": "https://github.com/JustineDevs/meta-architect/issues/25",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Context economy is default core across applicable capabilities.",
@@ -486,15 +486,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 26,
       "title": "[feature] Add Ralph Execution Core as default maestro execution engine",
       "url": "https://github.com/JustineDevs/meta-architect/issues/26",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Ralph execution core is default where autonomous execution applies.",
@@ -522,15 +522,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 27,
       "title": "[feature] Add Workspace Intelligence Runtime Core semantic composition contracts",
       "url": "https://github.com/JustineDevs/meta-architect/issues/27",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Workspace intelligence runtime contracts are implemented.",
@@ -559,15 +559,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 28,
       "title": "[feature] Add Prompt Strategy Core as default MA prompt-policy capability",
       "url": "https://github.com/JustineDevs/meta-architect/issues/28",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Prompt strategy is default core across applicable roles and skills.",
@@ -598,15 +598,15 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     },
     {
       "number": 29,
       "title": "[feature] Add Active Autonomy Contract Core to prevent passive chatbot behavior",
       "url": "https://github.com/JustineDevs/meta-architect/issues/29",
-      "releaseVersion": "0.1.13",
-      "releaseTag": "v0.1.13",
-      "milestone": "v0.1.13",
+      "releaseVersion": "0.14.1",
+      "releaseTag": "v0.14.1",
+      "milestone": "v0.14.1",
       "status": "passed",
       "requiredProof": [
         "Active autonomy contract is default core across applicable agents and roles.",
@@ -638,7 +638,7 @@
           "npm run release:check is the required final production release gate for this issue set."
         ]
       },
-      "labels": ["feature", "next-release", "v0.1.13"]
+      "labels": ["feature", "next-release", "v0.14.1"]
     }
   ]
 }