@jstn-sdk/ma 0.1.0 → 0.1.2

package/.codex/prompts/enforcement.md

@@ -19,7 +19,7 @@ Your purpose is to turn project ideas into evidence-backed architecture, validat
 Treat Meta-Architect as two layers:
 
 - **Kernel**
-  - CLI runtime
+  - helper runtime
   - gate enforcement
   - decision and release state
   - MCP evidence binding

package/.codex/prompts/onboarding.md

@@ -1,10 +1,10 @@
 # Onboarding
 
-Meta-Architect is a skills-first orchestration layer with a strict kernel.
+Meta-Architect is a skills-first system for Codex with a strict kernel.
 
 ## What is implemented
 
-The primary runtime surface is `ma --madmax --high` plus:
+The primary product surface is the in-session skill flow:
 - `$arch`
 - `$sage`
 - `$flow`
@@ -12,7 +12,7 @@ The primary runtime surface is `ma --madmax --high` plus:
 - `$vibe`
 - `$build`
 
-Repo-local helper commands remain available through:
+Secondary helper commands remain available through:
 - `ma init`
 - `ma idea`
 - `ma skills`
@@ -32,10 +32,10 @@ Repo-local helper commands remain available through:
 2. Read `docs/getting-started.md`
 3. Read `docs/release-spec.md`
 4. Read `docs/skills.md`
-5. Start with `ma --madmax --high` and use `$arch` before assuming the workflow is ready
+5. Start Codex context if needed, then use `$arch` before assuming the workflow is ready
 
 ## What not to do
 
 - Do not edit `.ma/release.json` or `.ma/decisions.json` manually to bypass the gate model.
-- Do not treat `.ma/logs/` or `.ma/state/` as source.
+- Do not treat `.ma` support files as public source.
 - Do not claim release channels succeeded without proof.

package/README.md

@@ -1,8 +1,8 @@
 <div align="center">
   <img src="./docs/assets/meta-architect-logo.svg" alt="Meta-Architect logo" width="1024" height="240">
-  <p>Production-grade skills package and CLI for programmatic architecture, evidence-backed OSS selection, gate-driven review, and release-minded build unlocking.</p>
+  <p>Production-grade Codex skills and plugin package for architecture, evidence-backed OSS selection, gate-driven review, and release-minded build guidance.</p>
   <p>
-    <img src="https://img.shields.io/npm/v/%40jstn-sdk%2Fmeta-architect" alt="npm version">
+    <img src="https://img.shields.io/npm/v/%40jstn-sdk%2Fma" alt="npm version">
     <img src="https://img.shields.io/badge/node-%3E%3D20-339933" alt="Node.js 20+">
     <img src="https://img.shields.io/github/v/release/JustineDevs/meta-architect" alt="GitHub release">
     <img src="https://img.shields.io/badge/license-MIT-16A34A" alt="MIT License">
@@ -10,9 +10,9 @@
 </div>
 
 > [!IMPORTANT]
-> Meta-Architect `v0.1.0` is a production-grade skills line.
+> Meta-Architect `v0.1.2` is a production-grade skills line.
 > It is not a lightweight demo branch.
-> From `v0.1.0` 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.2` onward, the package is expected to ship with stable skill contracts, deterministic packaging, explicit release gates, and honest install and publish surfaces.
 
 ## Overview
 
@@ -35,8 +35,8 @@ It adds:
     <td><code>@jstn-sdk/ma</code></td>
   </tr>
   <tr>
-    <td><strong>CLI commands</strong></td>
-    <td><code>ma</code>, <code>meta-architect</code></td>
+    <td><strong>Helper command</strong></td>
+    <td><code>ma</code> (secondary support surface)</td>
   </tr>
   <tr>
     <td><strong>Runtime</strong></td>
@@ -44,7 +44,7 @@ It adds:
   </tr>
   <tr>
     <td><strong>Release line</strong></td>
-    <td><code>v0.1.0</code></td>
+    <td><code>v0.1.2</code></td>
   </tr>
   <tr>
     <td><strong>License</strong></td>
@@ -58,7 +58,7 @@ It adds:
 - npm `>=10`
 - Git
 - an MCP-capable coding runtime
-- OpenAI Codex CLI for the recommended package-first path
+- Codex for the recommended package-first path
 - macOS, Linux, or WSL2 recommended
 
 > [!TIP]
@@ -68,13 +68,13 @@ It adds:
 
 Meta-Architect is intended to be consumed as an installed package, not primarily as a git clone.
 
-Default operator path:
+Primary product path:
 
 ```bash
 # Install
 npm i -g @openai/codex@latest @jstn-sdk/ma@latest
 
-# Launch
+# Start Codex context if needed
 ma --madmax --high
 
 # Remove Meta-Architect only
@@ -86,11 +86,10 @@ npm uninstall -g @jstn-sdk/ma @openai/codex
 
 What this assumes:
 
-- Codex CLI is installed globally
-- Meta-Architect is installed globally as a package
+- Codex is installed globally
+- Meta-Architect is installed globally as the skills/plugin package
 - Meta-Architect installs its published skill surface into the active Codex home
-- `ma` launches Codex with the Meta-Architect workflow posture already attached
-- you will operate through the skill-driven workflow inside the Codex session
+- the product experience happens through the skill workflow inside Codex
 
 > [!IMPORTANT]
 > The recommended default flow is package-first.
@@ -133,10 +132,9 @@ npm uninstall -g @jstn-sdk/ma @openai/codex
 
 This gives you:
 
-- `ma`
-- `meta-architect`
 - the installed Meta-Architect skill surface
-- the canonical Meta-Architect runtime entrypoints inside a Codex session
+- the canonical Meta-Architect skill entrypoints inside a Codex session
+- the optional `ma` helper command when a guided start is useful
 
 ### Contributor setup: source checkout
 
@@ -153,7 +151,7 @@ npm link
 
 ## Quick Start
 
-### 1. Launch the runtime
+### 1. Start Codex context if needed
 
 ```bash
 ma --madmax --high
@@ -195,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.0
+8. Delivery plan for v0.1.2
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -215,7 +213,7 @@ $build
 
 See [example/usage-workflow.md](./example/usage-workflow.md) for the full prompt templates for each step.
 
-### 4. Secondary maintenance path
+### 4. Secondary helper path
 
 If you are working from a repository directly and need scaffolded local support files, use:
 
@@ -311,10 +309,10 @@ git worktree add ../api feature/api
 
 ### 7. Simple command guide
 
-There are two different ways to use Meta-Architect.
+Meta-Architect has two surfaces.
 
-1. Terminal commands
-2. In-session skills
+- terminal helper commands
+- in-session skills
 
 Terminal commands are normal shell commands you run in the terminal:
 
@@ -338,8 +336,8 @@ $build
 ```
 
 Plain-language difference:
-- `ma ...` = terminal helper commands
-- `$...` = in-session skill prompts
+- `ma ...` = helper commands in the terminal
+- `$...` = the product experience inside Codex
 
 What `ma setup` and `ma init` do:
 - both currently do the same thing
@@ -348,9 +346,10 @@ What `ma setup` and `ma init` do:
 - they do not run the skill workflow by themselves
 
 What to use when:
-- use `ma --madmax --high` or `ma` to enter Codex
+- 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
 
@@ -405,7 +404,7 @@ Meta-Architect has two related but different distribution surfaces.
 
 | Surface | Purpose | Produced by |
 | --- | --- | --- |
-| npm package | public package containing CLI, docs, scripts, and canonical skills | `npm publish` or `npm pack` |
+| npm package | public package containing the installable Meta-Architect skills/plugin system, docs, scripts, and canonical skills | `npm publish` or `npm pack` |
 | skills bundle | narrower tarball containing `skills/` only | `npm run skills:pack` |
 
 Required packaging commands:
@@ -424,7 +423,7 @@ Pre-publish rules:
 - `npm run skills:validate` must pass
 - `dist/meta-architect-skills.tgz` must exist
 - `npm pack --dry-run` must show only intended public files
-- docs must match real CLI and release behavior
+- docs must match the real skills/plugin and release behavior
 
 Release lane discipline:
 - stable versions publish to npm `latest`
@@ -512,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.0.md) | QA evidence for the `v0.1.0` line |
+| [Release Readiness](./docs/qa/release-readiness-0.1.2.md) | QA evidence for the `v0.1.2` 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,
@@ -28,12 +33,13 @@ import {
 import { syncStatusUpdates } from "../src/state-sync.js";
 
 function printUsage() {
-  console.error("Usage:");
+  console.error("Secondary helper commands:");
   console.error("  ma");
   console.error("  ma setup");
   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.0](./qa/release-readiness-0.1.0.md)
+- [Release Readiness 0.1.2](./qa/release-readiness-0.1.2.md)
 
 ## Repo structure references
 

package/docs/getting-started.md

@@ -1,11 +1,11 @@
 # Getting Started
 
-This guide takes a new user from clone to a green-gated Meta-Architect workflow on a real project.
+This guide takes Meta-Architect from install to a green-gated skill workflow on a real project.
 
 ## Goal
 
 By the end of this guide you should be able to:
-- install Meta-Architect locally
+- install Meta-Architect
 - configure MCP/GitMCP sources
 - run the full architecture-to-build sequence
 - understand how each gate moves
@@ -38,7 +38,7 @@ npm uninstall -g @jstn-sdk/ma
 npm uninstall -g @jstn-sdk/ma @openai/codex
 ```
 
-That is the default operator posture. `ma` is the Meta-Architect launcher for a Codex session, and the rest of this guide should match the in-session workflow shape in [example/usage-workflow.md](../example/usage-workflow.md).
+That is the default product path. The product experience is the in-session skill workflow in [example/usage-workflow.md](../example/usage-workflow.md). The `ma` command is only a helper for starting or supporting that flow.
 
 ## 2. Real usage workflow
 
@@ -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.0
+8. Delivery plan for v0.1.2
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -102,8 +102,7 @@ npm link
 ```
 
 Why `npm link` matters:
-- the docs use the `ma` command directly
-- `npm link` makes the local CLI available without requiring a global publish step
+- it makes the local helper command available without requiring a global publish step
 
 ## 4. Secondary repository setup flow
 
@@ -122,7 +121,7 @@ Expected effects:
 - `.codex/prompts/` exists
 - local `.ma/skills/`, `.ma/evidence/`, `.ma/context/`, `.ma/specs/`, `.ma/plans/`, and `.ma/runbook.md` are seeded
 - `mcp/`, `docs/`, and `sprint/` surfaces exist
-- `ma` launches the local Codex CLI when run with no arguments
+- `ma` opens Codex with the Meta-Architect helper posture when run with no arguments
 
 Expected output:
 
@@ -142,7 +141,7 @@ ready: docs/qa
 ready: sprint
 ```
 
-This setup path is secondary to the canonical `ma --madmax --high` runtime launch. Use it when you need local repo scaffolding.
+This setup path is secondary to the canonical in-session skill workflow. Use it when you need local repo scaffolding.
 
 ## 4.1 Understand the two surfaces
 
@@ -156,6 +155,7 @@ Terminal commands are normal shell commands:
 ```bash
 ma setup
 ma init
+ma sdk-path
 ma status
 ma run '$arch'
 ```
@@ -180,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/onboarding.md

@@ -1,6 +1,6 @@
 # Onboarding
 
-This is the shortest operator entrypoint for someone who just opened Meta-Architect and needs the real first-run path.
+This is the shortest entrypoint for the real first-run Meta-Architect path.
 
 ## Read first
 
@@ -10,13 +10,13 @@ This is the shortest operator entrypoint for someone who just opened Meta-Archit
 4. `docs/release-spec.md`
 5. `docs/skills-publishing.md`
 
-## Canonical install and launch
+## Canonical install and start
 
 ```bash
 # Install
 npm i -g @openai/codex@latest @jstn-sdk/ma@latest
 
-# Launch
+# Start Codex context if needed
 ma --madmax --high
 
 # Remove Meta-Architect only

package/docs/qa/{release-readiness-0.1.0.md → release-readiness-0.1.2.md}

@@ -1,19 +1,36 @@
-# Release Readiness 0.1.0
+# Release Readiness 0.1.2
 
 ## Production bar
 
-`v0.1.0` is treated as production only when:
+`v0.1.2` 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.0`
+- release docs, package metadata, and workflows all agree on `0.1.2`
 
 Target release state:
-- npm package: `@jstn-sdk/ma@0.1.0`
-- npm registry state: pending manual publish
-- publishability note: this renamed package line is intended to publish as `0.1.0`
-- git tag: `v0.1.0`
-- GitHub release: published at `2026-05-02T10:59:33Z`
+- npm package: `@jstn-sdk/ma@0.1.2`
+- npm registry state: pending publish
+- publishability note: `0.1.1` is already published, so `0.1.2` is the next publishable package line
+- git tag: `v0.1.2`
+- GitHub release: pending publish for `v0.1.2`
+
+## Production checklist
+
+- skills-first product identity: PASS
+- package/plugin identity aligned to `@jstn-sdk/ma`: PASS
+- version/tag alignment `0.1.2` / `v0.1.2`: PASS
+- install/uninstall docs aligned: PASS
+- onboarding is concise and sequential: PASS
+- helper command documented as secondary: PASS
+- skills/prompts/manifests aligned: PASS
+- packaging includes required assets: PASS
+- tests pass: PASS
+- package dry-run passes: PASS
+- installed-package behavior passes: PASS
+- workflow/release/provenance docs aligned: PASS
+- no stale package names remain in tracked repo surfaces: PASS
+- no conflicting CLI-first product story remains in tracked product docs: PASS
 
 ## Automated checks run
 

package/docs/release-spec.md

@@ -1,18 +1,18 @@
-# v0.1.0 Requirements & Rules
+# v0.1.2 Requirements & Rules
 
 ## Production definition
 
-Meta-Architect `v0.1.0` is production only when:
+Meta-Architect `v0.1.2` is production only when:
 1. the package/install surface works
-2. the runtime workflow from `$arch` through `$build` 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.0` must have
+## What `v0.1.2` must have
 
 ### 1. Canonical package/runtime path
 
 - install: `npm i -g @openai/codex@latest @jstn-sdk/ma@latest`
-- launch: `ma --madmax --high`
+- optional helper launch: `ma --madmax --high`
 - uninstall Meta-Architect only: `npm uninstall -g @jstn-sdk/ma`
 - uninstall Meta-Architect and Codex: `npm uninstall -g @jstn-sdk/ma @openai/codex`
 - runtime trigger surface:
@@ -49,16 +49,16 @@ Canonical state files:
 
 ### 4. Required release evidence
 
-- `package.json` version `0.1.0`
-- git tag `v0.1.0`
+- `package.json` version `0.1.2`
+- git tag `v0.1.2`
 - `RELEASE.md`
 - `CHANGELOG.md`
-- `docs/qa/release-readiness-0.1.0.md`
+- `docs/qa/release-readiness-0.1.2.md`
 - green `npm run release:check`
 
 ### 5. Dist-tag discipline
 
-- stable versions such as `0.1.0` 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

@@ -10,13 +10,13 @@ Meta-Architect’s canonical Codex runtime surface is:
 
 ## Real usage path
 
-Install the package once, launch through `ma`, and use the skills directly in-session.
+Install the package once, start Codex context if needed, and use the skills directly in-session.
 
 ```bash
 # Install
 npm i -g @openai/codex@latest @jstn-sdk/ma@latest
 
-# Launch
+# Start Codex context if needed
 ma --madmax --high
 
 # Remove Meta-Architect only
@@ -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:
@@ -88,4 +116,4 @@ Every skill result must include:
 
 ## Operator note
 
-The runtime trigger surface is primary. The `ma` helper commands exist to launch Codex with Meta-Architect attached and to provide repo-local state automation when scripted verification is needed.
+The in-session skill surface is primary. The `ma` helper commands only exist to start Codex context and to provide repo-local state automation when scripted verification is needed.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.0",
-  "description": "Codex-native runtime layer for architecture, evidence, review, and gated build workflows.",
+  "version": "0.1.2",
+  "description": "Codex-native skills system for architecture, evidence, review, and gated build guidance.",
   "license": "MIT",
   "author": "JustineDevs",
   "homepage": "https://github.com/JustineDevs/meta-architect#readme",
@@ -21,8 +21,8 @@
     "ai",
     "agent",
     "orchestration",
-    "cli",
-    "developer-tools"
+    "plugin",
+    "workflow-system"
   ],
   "type": "module",
   "main": "index.js",
@@ -37,6 +37,7 @@
     ".agents/plugins/",
     "mcp/",
     "plugins/",
+    "templates/",
     "sprint/",
     "skills/",
     "docs/",

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

@@ -1,7 +1,7 @@
 {
   "name": "meta-architect",
   "displayName": "Meta-Architect",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "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.0",
+  "version": "0.1.2",
   "description": "Skills-first workflow layer for Codex with architecture, evidence, review, and gated build guidance.",
   "author": {
     "name": "JustineDevs",
@@ -16,7 +16,7 @@
   "interface": {
     "displayName": "Meta-Architect",
     "shortDescription": "Architecture-first skill bundle for Codex workflows.",
-    "longDescription": "Plugin = Meta-Architect skill discovery plus plugin-scoped MCP and app metadata. Runtime = the ma launcher plus .ma state, release gates, and scripted helper commands when a repository needs local workflow state.",
+    "longDescription": "Meta-Architect packages reusable Codex skills plus plugin-scoped MCP and app metadata. The in-session skill workflow is primary. The ma helper command and .ma state only support setup, release gates, and optional local helper automation.",
     "developerName": "JustineDevs",
     "category": "Developer Tools"
   }

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

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