@jstn-sdk/ma 0.1.9 → 0.1.11

package/README.md

@@ -18,9 +18,9 @@
 </div>
 
 > [!IMPORTANT]
-> Meta-Architect `v0.1.9` is a production-grade skills line.
+> Meta-Architect `v0.1.11` is a production-grade skills line.
 > It is not a lightweight demo branch.
-> 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.
+> From `v0.1.11` 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.9</code></td>
+    <td><code>v0.1.11</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.9
+8. Delivery plan for v0.1.11
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -608,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.9.md) | QA evidence for the `v0.1.9` line |
+| [Release Readiness](./docs/qa/release-readiness-0.1.11.md) | QA evidence for the `v0.1.11` line |
 
 ## Release Hygiene
 

package/docs/README.md

@@ -17,7 +17,7 @@ Meta-Architect documentation is organized by operator task.
 
 ## QA and readiness
 
-- [Release Readiness 0.1.9](./qa/release-readiness-0.1.9.md)
+- [Release Readiness 0.1.11](./qa/release-readiness-0.1.11.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.9
+8. Delivery plan for v0.1.11
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this

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

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "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.9",
+  "version": "0.1.11",
   "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.9",
+  "version": "0.1.11",
   "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.9",
+  "version": "0.1.11",
   "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.9`
+- plugin scope is aligned to Meta-Architect `v0.1.11`
 - any breaking contract change should be versioned intentionally
 
 The plugin is one distribution surface of the same product, not a separate product line.

package/scripts/biome-staged.js

@@ -0,0 +1,66 @@
+#!/usr/bin/env node
+
+import { spawnSync } from "node:child_process";
+import fs from "node:fs";
+import path from "node:path";
+
+const supportedExtensions = new Set([
+  ".js",
+  ".mjs",
+  ".cjs",
+  ".jsx",
+  ".ts",
+  ".tsx",
+  ".json",
+  ".jsonc",
+  ".css",
+]);
+
+function run(command, args) {
+  const result = spawnSync(command, args, {
+    stdio: "inherit",
+    encoding: "utf8",
+  });
+
+  if (result.error) {
+    throw result.error;
+  }
+
+  if (typeof result.status === "number" && result.status !== 0) {
+    process.exit(result.status);
+  }
+}
+
+function getStagedFiles() {
+  const result = spawnSync("git", ["diff", "--cached", "--name-only", "--diff-filter=ACMR"], {
+    encoding: "utf8",
+  });
+
+  if (result.error) {
+    throw result.error;
+  }
+
+  if (typeof result.status === "number" && result.status !== 0) {
+    process.exit(result.status);
+  }
+
+  return result.stdout
+    .split("\n")
+    .map((line) => line.trim())
+    .filter(Boolean)
+    .filter((file) => supportedExtensions.has(path.extname(file)))
+    .filter((file) => fs.existsSync(file));
+}
+
+function main() {
+  const files = getStagedFiles();
+  if (files.length === 0) {
+    return;
+  }
+
+  run("npx", ["@biomejs/biome", "format", "--write", ...files]);
+  run("git", ["update-index", "--again"]);
+  run("npx", ["@biomejs/biome", "lint", ...files]);
+}
+
+main();

package/scripts/release-sync.js

@@ -75,6 +75,15 @@ function writeJson(file, value) {
   fs.writeFileSync(file, `${JSON.stringify(value, null, 2)}\n`);
 }
 
+function writePluginManifestJson(file, value) {
+  let content = `${JSON.stringify(value, null, 2)}\n`;
+  if (Array.isArray(value.keywords)) {
+    const inlineKeywords = `[${value.keywords.map((entry) => JSON.stringify(entry)).join(", ")}]`;
+    content = content.replace(/"keywords": \[[\s\S]*?\],/, `"keywords": ${inlineKeywords},`);
+  }
+  fs.writeFileSync(file, content);
+}
+
 function readText(file) {
   return fs.readFileSync(file, "utf8");
 }
@@ -191,12 +200,16 @@ function syncPluginVersions(nextVersion) {
   for (const file of [
     path.join("plugins", "meta-architect", ".app.json"),
     path.join("plugins", "meta-architect", ".mcp.json"),
-    path.join("plugins", "meta-architect", ".codex-plugin", "plugin.json"),
   ]) {
     const value = readJson(file);
     value.version = nextVersion;
     writeJson(file, value);
   }
+
+  const pluginManifestFile = path.join("plugins", "meta-architect", ".codex-plugin", "plugin.json");
+  const pluginManifest = readJson(pluginManifestFile);
+  pluginManifest.version = nextVersion;
+  writePluginManifestJson(pluginManifestFile, pluginManifest);
 }
 
 function syncCurrentReleaseFiles(oldVersion, nextVersion) {

package/src/mcp-live-client.js

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

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.9.md"),
-      path.join(getRepoRoot(), "docs", "qa", "release-readiness-0.1.9.md"),
+      path.join(packageRoot, "docs", "qa", "release-readiness-0.1.11.md"),
+      path.join(getRepoRoot(), "docs", "qa", "release-readiness-0.1.11.md"),
     ],
   ];