@jstn-sdk/ma 0.1.1 → 0.1.3

package/README.md

@@ -10,9 +10,9 @@
 </div>
 
 > [!IMPORTANT]
-> Meta-Architect `v0.1.1` is a production-grade skills line.
+> Meta-Architect `v0.1.3` is a production-grade skills line.
 > It is not a lightweight demo branch.
-> From `v0.1.1` onward, the package is expected to ship with stable skill contracts, deterministic packaging, explicit release gates, and honest install and publish surfaces.
+> From `v0.1.3` onward, the package is expected to ship with stable skill contracts, deterministic packaging, explicit release gates, and honest install and publish surfaces.
 
 ## Overview
 
@@ -44,7 +44,7 @@ It adds:
   </tr>
   <tr>
     <td><strong>Release line</strong></td>
-    <td><code>v0.1.1</code></td>
+    <td><code>v0.1.3</code></td>
   </tr>
   <tr>
     <td><strong>License</strong></td>
@@ -193,7 +193,7 @@ Required output:
 5. Data model and storage choices
 6. Auth/security considerations
 7. DX/UX considerations
-8. Delivery plan for v0.1.1
+8. Delivery plan for v0.1.3
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -349,6 +349,7 @@ What to use when:
 - use Codex and run the skills in-session
 - use `$arch -> $sage -> $flow -> $vet -> $vibe -> $build` inside the Codex session
 - use `ma setup` or `ma init` only when you want local scaffolding or scripted helper automation from the terminal
+- use `ma sdk-path` when you need the exact installed support-bundle path for packaged prompts, MCP files, sprint files, scripts, plugin metadata, or templates
 
 ## Core Maintainers
 
@@ -510,12 +511,13 @@ Provenance note:
 | --- | --- |
 | [Getting Started](./docs/getting-started.md) | end-to-end local onboarding |
 | [Skills Reference](./docs/skills.md) | trigger-by-trigger contract guide |
+| [Installed Support Bundle](./docs/installed-sdk.md) | standard packaged asset path for skills and helper flows |
 | [Skills Publishing](./docs/skills-publishing.md) | source-to-package pipeline |
 | [MCP Setup](./docs/mcp-setup.md) | evidence endpoint policy |
 | [Plugin README](./plugins/meta-architect/README.md) | plugin distribution surface |
 | [Collaborative Whiteboard Mission](./missions/collaborative-whiteboard/mission.md) | concrete scenario walkthrough |
 | [Release Spec](./docs/release-spec.md) | release and gate policy |
-| [Release Readiness](./docs/qa/release-readiness-0.1.1.md) | QA evidence for the `v0.1.1` line |
+| [Release Readiness](./docs/qa/release-readiness-0.1.3.md) | QA evidence for the `v0.1.3` line |
 
 ## Release Hygiene
 

package/bin/ma.js

@@ -15,6 +15,11 @@ import {
 } from "../src/policy.js";
 import { loadReleaseState } from "../src/release-state.js";
 import { writeBuildPlanArtifact } from "../src/runtime-artifacts.js";
+import {
+  ensureSkillsInstalled,
+  ensureSupportBundleInstalled,
+  getSupportBundleRoot,
+} from "../src/skill-installer.js";
 import {
   listSkills,
   runArch,
@@ -34,6 +39,7 @@ function printUsage() {
   console.error("  ma init");
   console.error('  ma idea "..."');
   console.error("  ma skills");
+  console.error("  ma sdk-path");
   console.error("  ma status");
   console.error("  ma run $arch|$sage|$flow|$vet|$vibe|$build");
   console.error("  ma merge <source-branch> <target-branch>");
@@ -198,6 +204,7 @@ async function main() {
   const arg = rest[0];
 
   if (shouldDelegateToCodex(args)) {
+    await Promise.all([ensureSkillsInstalled(), ensureSupportBundleInstalled()]);
     process.exitCode = runCodex(args);
     return;
   }
@@ -236,6 +243,11 @@ async function main() {
     return;
   }
 
+  if (command === "sdk-path") {
+    process.stdout.write(`${getSupportBundleRoot()}\n`);
+    return;
+  }
+
   if (command === "status") {
     const releaseState = await loadReleaseState();
     printStatus(releaseState);

package/docs/README.md

@@ -7,6 +7,7 @@ Meta-Architect documentation is organized by operator task.
 - [Getting Started](./getting-started.md)
 - [Release Spec](./release-spec.md)
 - [Skills Reference](./skills.md)
+- [Installed Support Bundle](./installed-sdk.md)
 
 ## Packaging and installation
 
@@ -16,7 +17,7 @@ Meta-Architect documentation is organized by operator task.
 
 ## QA and readiness
 
-- [Release Readiness 0.1.1](./qa/release-readiness-0.1.1.md)
+- [Release Readiness 0.1.3](./qa/release-readiness-0.1.3.md)
 
 ## Repo structure references
 

package/docs/getting-started.md

@@ -74,7 +74,7 @@ Required output:
 5. Data model and storage choices
 6. Auth/security considerations
 7. DX/UX considerations
-8. Delivery plan for v0.1.1
+8. Delivery plan for v0.1.3
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -155,6 +155,7 @@ Terminal commands are normal shell commands:
 ```bash
 ma setup
 ma init
+ma sdk-path
 ma status
 ma run '$arch'
 ```
@@ -179,6 +180,8 @@ Easy rule:
 - they prepare context, specs, plans, evidence, and runbook files
 - they do not automatically run the skill workflow
 
+`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
 
 Edit:

package/docs/installed-sdk.md

@@ -0,0 +1,60 @@
+# Installed Support Bundle
+
+Meta-Architect installs two things into the active Codex home:
+
+1. skills under `CODEX_HOME/skills/`
+2. a support bundle under `CODEX_HOME/meta-architect-sdk/`
+
+The support bundle exists so skills and helper paths can use relevant packaged files without guessing where they live.
+
+## Canonical support bundle path
+
+Default:
+
+```text
+~/.codex/meta-architect-sdk/
+```
+
+If `CODEX_HOME` is set, use:
+
+```text
+$CODEX_HOME/meta-architect-sdk/
+```
+
+You can print the exact active path with:
+
+```bash
+ma sdk-path
+```
+
+## What is installed there
+
+- `mcp/`
+- `sprint/`
+- `prompts/`
+- `scripts/`
+- `plugins/meta-architect/`
+- `templates/`
+- `docs/README.md`
+- `asset-manifest.json`
+
+## Why this exists
+
+- skills can rely on a standard installed asset root
+- helper paths can repair missing support assets automatically
+- packaged references do not depend on a source checkout
+- the product can use relevant packaged files without path guessing
+
+## Contract
+
+When Meta-Architect needs packaged support files, prefer the installed support bundle first.
+
+Examples:
+- MCP starter files -> `meta-architect-sdk/mcp/`
+- sprint references -> `meta-architect-sdk/sprint/`
+- Codex prompt assets -> `meta-architect-sdk/prompts/`
+- helper scripts -> `meta-architect-sdk/scripts/`
+- plugin metadata -> `meta-architect-sdk/plugins/meta-architect/`
+- templates -> `meta-architect-sdk/templates/`
+
+The in-session skill flow is still primary. This bundle only standardizes packaged asset access.

package/docs/qa/{release-readiness-0.1.1.md → release-readiness-0.1.3.md}

@@ -1,25 +1,25 @@
-# Release Readiness 0.1.1
+# Release Readiness 0.1.3
 
 ## Production bar
 
-`v0.1.1` is treated as production only when:
+`v0.1.3` is treated as production only when:
 - the package installs cleanly from the canonical public install command
 - the Codex-hosted runtime path works end to end
 - the helper flow remains valid for scripted verification
-- release docs, package metadata, and workflows all agree on `0.1.1`
+- release docs, package metadata, and workflows all agree on `0.1.3`
 
 Target release state:
-- npm package: `@jstn-sdk/ma@0.1.1`
+- npm package: `@jstn-sdk/ma@0.1.3`
 - npm registry state: pending publish
-- publishability note: `0.1.0` is already published, so `0.1.1` is the next publishable package line
-- git tag: `v0.1.1`
-- GitHub release: pending publish for `v0.1.1`
+- publishability note: `0.1.2` is already published, so `0.1.3` is the next publishable package line
+- git tag: `v0.1.3`
+- GitHub release: pending publish for `v0.1.3`
 
 ## Production checklist
 
 - skills-first product identity: PASS
 - package/plugin identity aligned to `@jstn-sdk/ma`: PASS
-- version/tag alignment `0.1.1` / `v0.1.1`: PASS
+- version/tag alignment `0.1.3` / `v0.1.3`: PASS
 - install/uninstall docs aligned: PASS
 - onboarding is concise and sequential: PASS
 - helper command documented as secondary: PASS

package/docs/release-spec.md

@@ -1,13 +1,13 @@
-# v0.1.1 Requirements & Rules
+# v0.1.3 Requirements & Rules
 
 ## Production definition
 
-Meta-Architect `v0.1.1` is production only when:
+Meta-Architect `v0.1.3` is production only when:
 1. the package/install surface works
 2. the in-session skill workflow from `$arch` through `$build` works
 3. the release evidence matches the actual package and git tag
 
-## What `v0.1.1` must have
+## What `v0.1.3` must have
 
 ### 1. Canonical package/runtime path
 
@@ -49,16 +49,16 @@ Canonical state files:
 
 ### 4. Required release evidence
 
-- `package.json` version `0.1.1`
-- git tag `v0.1.1`
+- `package.json` version `0.1.3`
+- git tag `v0.1.3`
 - `RELEASE.md`
 - `CHANGELOG.md`
-- `docs/qa/release-readiness-0.1.1.md`
+- `docs/qa/release-readiness-0.1.3.md`
 - green `npm run release:check`
 
 ### 5. Dist-tag discipline
 
-- stable versions such as `0.1.1` publish to npm `latest`
+- stable versions such as `0.1.2` publish to npm `latest`
 - prerelease versions such as `0.2.0-beta.1` must publish with explicit tags such as `beta`
 - recommended alternate lanes are `next`, `beta`, and `canary`
 - prerelease publication must use `npm publish --tag <lane>`

package/docs/skills.md

@@ -67,6 +67,34 @@ Important:
 - they only create local support files
 - they do not replace the in-session skill flow
 
+## Installed support bundle
+
+Meta-Architect also installs a standard packaged support bundle for relevant files.
+
+Default path:
+
+```text
+~/.codex/meta-architect-sdk/
+```
+
+Use:
+
+```bash
+ma sdk-path
+```
+
+when you want the exact active path.
+
+Relevant packaged assets there include:
+- `mcp/`
+- `sprint/`
+- `prompts/`
+- `scripts/`
+- `plugins/meta-architect/`
+- `templates/`
+
+This exists so Meta-Architect can use relevant packaged files without guessing paths.
+
 ## Shared output contract
 
 Every skill result must include:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Codex-native skills system for architecture, evidence, review, and gated build guidance.",
   "license": "MIT",
   "author": "JustineDevs",
@@ -37,6 +37,7 @@
     ".agents/plugins/",
     "mcp/",
     "plugins/",
+    "templates/",
     "sprint/",
     "skills/",
     "docs/",
@@ -59,6 +60,7 @@
     "status": "node ./bin/ma.js status",
     "build:gate": "node ./bin/ma.js run '$build'",
     "release:meta": "node ./scripts/release-metadata.js",
+    "release:sync": "node ./scripts/release-sync.js",
     "release:verify": "node ./scripts/release-verify.js",
     "release:check": "npm run release:verify && npm run skills:manifest && npm run plugin:sync && npm run skills:validate && npm run plugin:verify && npm run skills:pack && npm run check && npm test && npm run pack:inspect",
     "skills:manifest": "node ./scripts/skills-manifest.js",

package/plugins/meta-architect/.app.json

@@ -1,7 +1,7 @@
 {
   "name": "meta-architect",
   "displayName": "Meta-Architect",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Programmatic architecture and verified engineering skills for Codex-native workflows.",
   "entry": "./README.md",
   "skillsDir": "./skills"

package/plugins/meta-architect/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "meta-architect",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Skills-first workflow layer for Codex with architecture, evidence, review, and gated build guidance.",
   "author": {
     "name": "JustineDevs",

package/plugins/meta-architect/.mcp.json

@@ -1,6 +1,6 @@
 {
   "name": "meta-architect",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "collections": [
     "sindresorhus/awesome",
     "dzharii/awesome-typescript",

package/plugins/meta-architect/README.md

@@ -105,7 +105,7 @@ When consuming the plugin:
 The plugin version should track the release scope of the core repo.
 
 For this repository:
-- plugin scope is aligned to Meta-Architect `v0.1.1`
+- plugin scope is aligned to Meta-Architect `v0.1.3`
 - any breaking contract change should be versioned intentionally
 
 The plugin is one distribution surface of the same product, not a separate product line.

package/plugins/meta-architect/skills/arch/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Architect"
-  short_description: "Architecture and stack design for MA flows"
+  display_name: "$arch"
+  short_description: "Architecture-first product and system design"
   default_prompt: "Use $arch to produce architecture, stack rationale, subsystem boundaries, tradeoffs, and a phased delivery plan."

package/plugins/meta-architect/skills/build/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Build"
-  short_description: "Gated build planning and branch/worktree prep"
+  display_name: "$build"
+  short_description: "Build-readiness decision and next implementation step"
   default_prompt: "Use $build to decide whether implementation is ready, what remains blocked, and what the next build slice should be."

package/plugins/meta-architect/skills/flow/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Flow"
-  short_description: "Business logic and state validation for MA"
+  display_name: "$flow"
+  short_description: "Logic, states, transitions, and blockers"
   default_prompt: "Use $flow to map business logic, state transitions, invariants, and blockers in the current design."

package/plugins/meta-architect/skills/meta-architect/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "Meta-Architect"
-  short_description: "Core orchestration and gated build workflows"
+  display_name: "$meta-architect"
+  short_description: "Full Meta-Architect skill workflow"
   default_prompt: "Use $meta-architect to run the full Meta-Architect workflow inside Codex, then route through $arch, $sage, $flow, $vet, $vibe, and $build as needed."

package/plugins/meta-architect/skills/sage/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Sage"
-  short_description: "GitMCP-backed OSS evidence selection"
+  display_name: "$sage"
+  short_description: "Evidence-backed stack and OSS validation"
   default_prompt: "Use $sage to validate stack choices with official docs, upstream repos, and approved GitMCP-backed sources."

package/plugins/meta-architect/skills/vet/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Vet"
-  short_description: "Security, CVE, and risk review for MA"
+  display_name: "$vet"
+  short_description: "Security and trust-boundary review"
   default_prompt: "Use $vet to review trust boundaries, security risks, abuse cases, and safer alternatives in the current design."

package/plugins/meta-architect/skills/vibe/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "MA Vibe"
-  short_description: "DX and UX review before Meta-Architect build"
+  display_name: "$vibe"
+  short_description: "DX and UX review before implementation"
   default_prompt: "Use $vibe to review developer and user experience risks before the build lane proceeds."

package/scripts/postinstall.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 import process from "node:process";
-import { installSkills } from "../src/skill-installer.js";
+import { installSkills, installSupportBundle } from "../src/skill-installer.js";
 
 async function main() {
   if (process.env.MA_SKIP_AUTO_INSTALL === "1") {
@@ -9,8 +9,12 @@ async function main() {
     return;
   }
 
-  const { targetRoot, installed } = await installSkills();
-  console.log(`meta-architect: installed ${installed.length} Codex skills into ${targetRoot}`);
+  const [
+    { targetRoot: skillRoot, installed: skills },
+    { targetRoot: bundleRoot, installed: assets },
+  ] = await Promise.all([installSkills(), installSupportBundle()]);
+  console.log(`meta-architect: installed ${skills.length} Codex skills into ${skillRoot}`);
+  console.log(`meta-architect: installed ${assets.length} support assets into ${bundleRoot}`);
 }
 
 main().catch((error) => {