@jstn-sdk/ma 0.1.3 → 0.1.4

package/README.md

@@ -10,9 +10,9 @@
 </div>
 
 > [!IMPORTANT]
-> Meta-Architect `v0.1.3` is a production-grade skills line.
+> Meta-Architect `v0.1.4` is a production-grade skills line.
 > It is not a lightweight demo branch.
-> 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.
+> From `v0.1.4` 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.3</code></td>
+    <td><code>v0.1.4</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.3
+8. Delivery plan for v0.1.4
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this
@@ -447,6 +447,12 @@ Provenance note:
 - a local shell publish will fail with `Automatic provenance generation not supported for provider: null`
 - use the repository publish workflow when provenance is required
 
+Release automation:
+- `npm run release:sync` bumps and synchronizes the active release line only when watched release-relevant files changed
+- `npm run release:advance` force-bumps the next patch line and rewrites the same version-bearing files
+- `.github/workflows/release-sync.yml` runs the sync path on `main` pushes that touch watched release-relevant paths
+- `.github/workflows/release-advance.yml` runs after a published GitHub release and advances the repo to the next patch line automatically
+
 > [!CAUTION]
 > Do not claim npm, GitHub release, or any other publish channel until that channel has actually succeeded.
 > Release documentation must match reality, not intent.
@@ -517,7 +523,7 @@ Provenance note:
 | [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.3.md) | QA evidence for the `v0.1.3` line |
+| [Release Readiness](./docs/qa/release-readiness-0.1.4.md) | QA evidence for the `v0.1.4` 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.3](./qa/release-readiness-0.1.3.md)
+- [Release Readiness 0.1.4](./qa/release-readiness-0.1.4.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.3
+8. Delivery plan for v0.1.4
 9. Risks and trade-offs
 10. Decision log
 11. Exact next trigger to run after this

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

@@ -1,25 +1,25 @@
-# Release Readiness 0.1.3
+# Release Readiness 0.1.4
 
 ## Production bar
 
-`v0.1.3` is treated as production only when:
+`v0.1.4` 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.3`
+- release docs, package metadata, and workflows all agree on `0.1.4`
 
 Target release state:
-- npm package: `@jstn-sdk/ma@0.1.3`
+- npm package: `@jstn-sdk/ma@0.1.4`
 - npm registry state: pending publish
-- 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`
+- publishability note: `0.1.3` is already published, so `0.1.4` is the next publishable package line
+- git tag: `v0.1.4`
+- GitHub release: pending publish for `v0.1.4`
 
 ## Production checklist
 
 - skills-first product identity: PASS
 - package/plugin identity aligned to `@jstn-sdk/ma`: PASS
-- version/tag alignment `0.1.3` / `v0.1.3`: PASS
+- version/tag alignment `0.1.4` / `v0.1.4`: 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.3 Requirements & Rules
+# v0.1.4 Requirements & Rules
 
 ## Production definition
 
-Meta-Architect `v0.1.3` is production only when:
+Meta-Architect `v0.1.4` 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.3` must have
+## What `v0.1.4` must have
 
 ### 1. Canonical package/runtime path
 
@@ -49,11 +49,11 @@ Canonical state files:
 
 ### 4. Required release evidence
 
-- `package.json` version `0.1.3`
-- git tag `v0.1.3`
+- `package.json` version `0.1.4`
+- git tag `v0.1.4`
 - `RELEASE.md`
 - `CHANGELOG.md`
-- `docs/qa/release-readiness-0.1.3.md`
+- `docs/qa/release-readiness-0.1.4.md`
 - green `npm run release:check`
 
 ### 5. Dist-tag discipline
@@ -79,6 +79,13 @@ Canonical state files:
    - Prerelease publish: `npm publish --access public --tag <lane>`
 10. Verify dist-tags with `npm view @jstn-sdk/ma version dist-tags time --json`
 
+### 6.1 Release automation
+
+- `npm run release:sync` updates the active release line when watched release-relevant files changed
+- `npm run release:advance` force-bumps the next patch line after a completed release
+- `.github/workflows/release-sync.yml` automates the sync path on `main`
+- `.github/workflows/release-advance.yml` advances the repo to the next patch line after a published release
+
 ### 7. Provenance rule
 
 - `npm publish --provenance` is valid only from a supported cloud CI/CD provider

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Codex-native skills system for architecture, evidence, review, and gated build guidance.",
   "license": "MIT",
   "author": "JustineDevs",
@@ -61,6 +61,7 @@
     "build:gate": "node ./bin/ma.js run '$build'",
     "release:meta": "node ./scripts/release-metadata.js",
     "release:sync": "node ./scripts/release-sync.js",
+    "release:advance": "node ./scripts/release-sync.js --force --bump patch",
     "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.3",
+  "version": "0.1.4",
   "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.3",
+  "version": "0.1.4",
   "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.3",
+  "version": "0.1.4",
   "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.3`
+- plugin scope is aligned to Meta-Architect `v0.1.4`
 - 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/release-sync.js

@@ -34,6 +34,7 @@ function parseArgs(argv) {
     fromRef: "",
     toRef: "",
     githubOutput: "",
+    force: false,
   };
 
   for (let index = 0; index < argv.length; index += 1) {
@@ -56,6 +57,10 @@ function parseArgs(argv) {
     if (token === "--github-output") {
       args.githubOutput = argv[index + 1] ?? "";
       index += 1;
+      continue;
+    }
+    if (token === "--force") {
+      args.force = true;
     }
   }
 
@@ -112,13 +117,17 @@ function git(args) {
   return execFileSync("git", args, { encoding: "utf8" }).trim();
 }
 
-function getChangedFiles({ fromRef, toRef }) {
+function getChangedFiles({ fromRef, toRef, force }) {
   if (process.env.RELEASE_SYNC_CHANGED_FILES) {
     return process.env.RELEASE_SYNC_CHANGED_FILES.split("\n")
       .map((line) => line.trim())
       .filter(Boolean);
   }
 
+  if (force) {
+    return [];
+  }
+
   if (fromRef && toRef && !/^0+$/.test(fromRef)) {
     return git(["diff", "--name-only", fromRef, toRef])
       .split("\n")
@@ -291,9 +300,9 @@ function main() {
   const pkg = readJson("package.json");
   const currentVersion = pkg.version;
   const changedFiles = getChangedFiles(args);
-  const relevantChanges = changedFiles.filter(isWatchedPath);
+  const relevantChanges = args.force ? ["<forced>"] : changedFiles.filter(isWatchedPath);
 
-  if (relevantChanges.length === 0) {
+  if (relevantChanges.length === 0 && !args.force) {
     if (args.githubOutput) {
       writeGithubOutput(args.githubOutput, { updated: "false", version: currentVersion });
     }
@@ -301,6 +310,7 @@ function main() {
       JSON.stringify(
         {
           updated: false,
+          forced: false,
           version: currentVersion,
           changedFiles,
         },
@@ -329,6 +339,7 @@ function main() {
     JSON.stringify(
       {
         updated: true,
+        forced: args.force,
         bump: bumpKind,
         previousVersion: currentVersion,
         version: nextVersion,

package/src/mcp-live-client.js

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

package/src/skills.js

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