@jstn-sdk/ma 0.1.8 → 0.1.9

package/README.md

@@ -18,9 +18,9 @@
 </div>
 
 > [!IMPORTANT]
-> Meta-Architect `v0.1.8` is a production-grade skills line.
+> Meta-Architect `v0.1.9` is a production-grade skills line.
 > It is not a lightweight demo branch.
-> From `v0.1.8` 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.9` onward, the package is expected to ship with stable skill contracts, deterministic packaging, explicit release gates, and honest install and publish surfaces.
 
 ## Overview
 
@@ -57,7 +57,7 @@ It adds:
   </tr>
   <tr>
     <td><strong>Release line</strong></td>
-    <td><code>v0.1.8</code></td>
+    <td><code>v0.1.9</code></td>
   </tr>
   <tr>
     <td><strong>License</strong></td>
@@ -230,7 +230,7 @@ Required output:
 5. Data model and storage choices
 6. Auth/security considerations
 7. DX/UX considerations
-8. Delivery plan for v0.1.8
+8. Delivery plan for v0.1.9
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -257,6 +257,7 @@ If you are working from a repository directly and need scaffolded local support
 
 ```bash
 ma bootstrap
+ma bootstrap --init-mcp
 ma doctor
 ma setup
 ma
@@ -264,6 +265,7 @@ ma
 
 Recommended lazy-user path:
 - run `ma bootstrap` first to repair packaged assets, scaffold local runtime files, and verify the environment
+- add `--init-mcp` if you want starter GitMCP source files written into the local `mcp/` folder when it is empty or invalid
 - use `ma doctor` later when you want a check-only readiness report without changing files
 
 Expected output for `ma setup`:
@@ -418,6 +420,7 @@ What `ma bootstrap` does:
 - checks whether `codex` is callable
 - repairs installed skills and support-bundle assets when possible
 - runs local scaffold setup
+- can seed starter MCP files with `--init-mcp` when the local MCP config is empty or invalid
 - reports `READY`, `READY_WITH_WARNINGS`, or `BLOCKED`
 
 What `ma doctor` does:
@@ -605,7 +608,7 @@ Release automation:
 | [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.8.md) | QA evidence for the `v0.1.8` line |
+| [Release Readiness](./docs/qa/release-readiness-0.1.9.md) | QA evidence for the `v0.1.9` line |
 
 ## Release Hygiene
 

package/bin/ma.js

@@ -37,7 +37,7 @@ import { syncStatusUpdates } from "../src/state-sync.js";
 function printUsage() {
   console.error("Secondary helper commands:");
   console.error("  ma");
-  console.error("  ma bootstrap");
+  console.error("  ma bootstrap [--init-mcp]");
   console.error("  ma doctor");
   console.error("  ma setup");
   console.error("  ma init");
@@ -224,7 +224,7 @@ async function main() {
   }
 
   if (command === "bootstrap") {
-    const outcome = await runBootstrap();
+    const outcome = await runBootstrap({ initMcp: rest.includes("--init-mcp") });
     process.exitCode = outcome.result === "BLOCKED" ? 1 : 0;
     return;
   }

package/docs/README.md

@@ -17,7 +17,7 @@ Meta-Architect documentation is organized by operator task.
 
 ## QA and readiness
 
-- [Release Readiness 0.1.8](./qa/release-readiness-0.1.8.md)
+- [Release Readiness 0.1.9](./qa/release-readiness-0.1.9.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.8
+8. Delivery plan for v0.1.9
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -185,6 +185,7 @@ Easy rule:
 - it checks whether `codex` is callable
 - it repairs installed skills and support-bundle assets when possible
 - it runs local scaffold setup
+- it can seed starter MCP files with `--init-mcp` when the local MCP config is empty or invalid
 - it reports `READY`, `READY_WITH_WARNINGS`, or `BLOCKED`
 
 `ma doctor` is the check-only path:

package/docs/qa/{release-readiness-0.1.8.md → release-readiness-0.1.9.md}

@@ -1,25 +1,25 @@
-# Release Readiness 0.1.8
+# Release Readiness 0.1.9
 
 ## Production bar
 
-`v0.1.8` is treated as production only when:
+`v0.1.9` 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.8`
+- release docs, package metadata, and workflows all agree on `0.1.9`
 
 Target release state:
-- npm package: `@jstn-sdk/ma@0.1.8`
+- npm package: `@jstn-sdk/ma@0.1.9`
 - npm registry state: pending publish
-- publishability note: `0.1.7` is already published, so `0.1.8` is the next publishable package line
-- git tag: `v0.1.8`
-- GitHub release: pending publish for `v0.1.8`
+- publishability note: `0.1.8` is already published, so `0.1.9` is the next publishable package line
+- git tag: `v0.1.9`
+- GitHub release: pending publish for `v0.1.9`
 
 ## Production checklist
 
 - skills-first product identity: PASS
 - package/plugin identity aligned to `@jstn-sdk/ma`: PASS
-- version/tag alignment `0.1.8` / `v0.1.8`: PASS
+- version/tag alignment `0.1.9` / `v0.1.9`: 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.8 Requirements & Rules
+# v0.1.9 Requirements & Rules
 
 ## Production definition
 
-Meta-Architect `v0.1.8` is production only when:
+Meta-Architect `v0.1.9` 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.8` must have
+## What `v0.1.9` must have
 
 ### 1. Canonical package/runtime path
 
@@ -49,11 +49,11 @@ Canonical state files:
 
 ### 4. Required release evidence
 
-- `package.json` version `0.1.8`
-- git tag `v0.1.8`
+- `package.json` version `0.1.9`
+- git tag `v0.1.9`
 - `RELEASE.md`
 - `CHANGELOG.md`
-- `docs/qa/release-readiness-0.1.8.md`
+- `docs/qa/release-readiness-0.1.9.md`
 - green `npm run release:check`
 
 ### 5. Dist-tag discipline

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Codex-native skills system for architecture, evidence, review, and gated build guidance.",
   "license": "MIT",
   "author": "JustineDevs",

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

@@ -1,7 +1,7 @@
 {
   "name": "meta-architect",
   "displayName": "Meta-Architect",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "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.8",
+  "version": "0.1.9",
   "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.8",
+  "version": "0.1.9",
   "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.8`
+- plugin scope is aligned to Meta-Architect `v0.1.9`
 - any breaking contract change should be versioned intentionally
 
 The plugin is one distribution surface of the same product, not a separate product line.

package/src/bootstrap.js

@@ -3,7 +3,7 @@ import fs from "node:fs/promises";
 import os from "node:os";
 import path from "node:path";
 import { loadMcpServers } from "./mcp-config.js";
-import { getRepoRoot, getRuntimeWritePath } from "./paths.js";
+import { getRepoRoot, getRuntimeWritePath, packageRoot } from "./paths.js";
 import {
   areSkillsInstalled,
   ensureSkillsInstalled,
@@ -155,14 +155,33 @@ async function inspectLocalScaffold() {
   return true;
 }
 
-async function inspectMcpState() {
+async function seedStarterMcpConfig() {
+  const files = ["servers.json", "collections.json", "fallback.json"];
+  for (const file of files) {
+    await fs.copyFile(path.join(packageRoot, "mcp", file), path.join(getRepoRoot(), "mcp", file));
+  }
+}
+
+async function inspectMcpState({ fix, initMcp }) {
   try {
     const servers = await loadMcpServers();
     if (servers.servers.length === 0) {
+      if (fix && initMcp) {
+        await seedStarterMcpConfig();
+        const seededServers = await loadMcpServers();
+        return makeStatus(
+          "FIXED",
+          "starter MCP sources were seeded into mcp/servers.json",
+          `${seededServers.servers.length} configured source(s)`,
+        );
+      }
+
       return makeStatus(
         "WARN",
         "mcp/servers.json exists but contains no approved repo-backed sources",
-        "Add exact upstream GitMCP repo endpoints before claiming VERIFIED evidence.",
+        initMcp
+          ? "Run `ma bootstrap --init-mcp` to seed starter sources, or add exact upstream GitMCP repo endpoints manually."
+          : "Add exact upstream GitMCP repo endpoints before claiming VERIFIED evidence.",
       );
     }
 
@@ -172,11 +191,21 @@ async function inspectMcpState() {
       `${servers.servers.length} configured source(s)`,
     );
   } catch (error) {
+    if (fix && initMcp) {
+      await seedStarterMcpConfig();
+      const seededServers = await loadMcpServers();
+      return makeStatus(
+        "FIXED",
+        "starter MCP sources replaced an invalid MCP configuration",
+        `${seededServers.servers.length} configured source(s)`,
+      );
+    }
+
     return makeStatus("WARN", "mcp/servers.json is not ready for evidence binding", error.message);
   }
 }
 
-async function runEnvironmentFlow({ fix }) {
+async function runEnvironmentFlow({ fix, initMcp }) {
   const statuses = [];
 
   const codexResolution = await inspectCodexResolution({ fix });
@@ -256,7 +285,7 @@ async function runEnvironmentFlow({ fix }) {
     );
   }
 
-  statuses.push(await inspectMcpState());
+  statuses.push(await inspectMcpState({ fix, initMcp }));
   return statuses;
 }
 
@@ -297,15 +326,15 @@ function printStatuses(title, statuses) {
 }
 
 export async function runDoctor() {
-  const statuses = await runEnvironmentFlow({ fix: false });
+  const statuses = await runEnvironmentFlow({ fix: false, initMcp: false });
   return {
     statuses,
     result: printStatuses("Meta-Architect Doctor", statuses),
   };
 }
 
-export async function runBootstrap() {
-  const statuses = await runEnvironmentFlow({ fix: true });
+export async function runBootstrap({ initMcp = false } = {}) {
+  const statuses = await runEnvironmentFlow({ fix: true, initMcp });
   return {
     statuses,
     result: printStatuses("Meta-Architect Bootstrap", statuses),

package/src/mcp-live-client.js

@@ -38,7 +38,7 @@ export class McpSseClient {
       capabilities: {},
       clientInfo: {
         name: "meta-architect",
-        version: "0.1.8",
+        version: "0.1.9",
       },
     });
 

package/src/skills.js

@@ -508,8 +508,8 @@ export async function runInit() {
       path.join(getRepoRoot(), "docs", "release-spec.md"),
     ],
     [
-      path.join(packageRoot, "docs", "qa", "release-readiness-0.1.8.md"),
-      path.join(getRepoRoot(), "docs", "qa", "release-readiness-0.1.8.md"),
+      path.join(packageRoot, "docs", "qa", "release-readiness-0.1.9.md"),
+      path.join(getRepoRoot(), "docs", "qa", "release-readiness-0.1.9.md"),
     ],
   ];