@jstn-sdk/ma 0.1.3 → 0.1.5

package/docs/installed-sdk.md

@@ -1,60 +0,0 @@
-# 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.3.md

@@ -1,79 +0,0 @@
-# Release Readiness 0.1.3
-
-## Production bar
-
-`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.3`
-
-Target release state:
-- npm package: `@jstn-sdk/ma@0.1.3`
-- 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`
-
-## 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
-- 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
-
-```bash
-npm run release:check
-```
-
-That must cover:
-- skills manifest generation
-- skill validation
-- skill bundle packaging
-- repo checks
-- automated tests
-- npm package dry-run inspection
-
-## Manual/behavioral checks run
-
-Canonical launch:
-
-```bash
-ma --madmax --high
-```
-
-Helper-path validation:
-
-```bash
-ma setup
-ma idea "Build a demo app"
-ma run '$arch'
-ma run '$sage'
-ma run '$flow'
-ma run '$vet'
-ma run '$vibe'
-ma status
-ma run '$build'
-```
-
-Expected evidence:
-- `.ma/release.json` remains the source of truth
-- `.ma/decisions.json` records the helper-path activity
-- `$build` stays blocked until upstream gates are green, then becomes ready
-
-## Known limitations
-
-- interactive Codex conversation quality depends on the installed Codex host
-- release publication still depends on npm ownership/authorization for the target package name

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

@@ -1,23 +0,0 @@
-{
-  "name": "meta-architect",
-  "version": "0.1.3",
-  "description": "Skills-first workflow layer for Codex with architecture, evidence, review, and gated build guidance.",
-  "author": {
-    "name": "JustineDevs",
-    "url": "https://github.com/JustineDevs"
-  },
-  "homepage": "https://github.com/JustineDevs/meta-architect",
-  "repository": "https://github.com/JustineDevs/meta-architect.git",
-  "license": "MIT",
-  "keywords": ["codex", "skills", "architecture", "workflow", "review"],
-  "skills": "./skills/",
-  "mcpServers": "./.mcp.json",
-  "apps": "./.app.json",
-  "interface": {
-    "displayName": "Meta-Architect",
-    "shortDescription": "Architecture-first skill bundle for Codex workflows.",
-    "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/skills/arch/SKILL.md

@@ -1,27 +0,0 @@
----
-name: arch
-description: "Use when the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning."
----
-
-# Arch
-
-Use this skill inside Codex to turn a product idea into a concrete architecture brief.
-
-## Output
-
-Produce:
-- problem framing
-- user and workload assumptions
-- system architecture and subsystem boundaries
-- stack recommendation with tradeoffs
-- data model and storage choices
-- auth, security, and operational concerns
-- phased delivery plan
-- top risks and open questions
-- exact next trigger, usually `$sage`
-
-## Rules
-
-- Ask only for constraints that materially change the architecture.
-- Keep the design biased toward the simplest system that can satisfy the stated requirements.
-- Be explicit about tradeoffs, failure modes, and what should stay out of the first version.

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

@@ -1,4 +0,0 @@
-interface:
-  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/SKILL.md

@@ -1,24 +0,0 @@
----
-name: build
-description: "Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be."
----
-
-# Build
-
-Use this skill inside Codex to convert the earlier review lanes into an implementation-ready decision.
-
-## Output
-
-Produce:
-- current readiness verdict
-- blockers that still prevent implementation
-- the narrowest viable build slice
-- branch or worktree suggestions when relevant
-- test and verification expectations
-- the exact next implementation step
-
-## Rules
-
-- Do not claim readiness if architecture, evidence, logic, security, or DX/UX gaps remain unresolved.
-- Keep the recommended build slice small, testable, and reversible.
-- If the user wants code immediately and the path is clear, end with a concrete implementation plan rather than more review prose.

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

@@ -1,4 +0,0 @@
-interface:
-  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/SKILL.md

@@ -1,24 +0,0 @@
----
-name: flow
-description: "Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation."
----
-
-# Flow
-
-Use this skill inside Codex to pressure-test how the system behaves, not just how it is structured.
-
-## Output
-
-Produce:
-- key actors and system states
-- main flows and failure flows
-- invariants and state transitions
-- race conditions, dead ends, and consistency risks
-- missing requirements or ambiguous behavior
-- exact next trigger, usually `$vet`
-
-## Rules
-
-- Focus on behavior, not UI polish or low-level code details.
-- Surface ambiguity aggressively when it affects correctness.
-- Prefer simple state models over sprawling branching logic.

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

@@ -1,4 +0,0 @@
-interface:
-  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 +0,0 @@
-interface:
-  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/meta-architect/references/core-release-rules.md

@@ -1,13 +0,0 @@
-# Core Release Rules
-
-- Required status fields live in `.ma/decisions.json` and `.ma/release.json`.
-- `$build` is blocked unless:
-  - `idea_status = CLEAR`
-  - `architecture_status = APPROVED`
-  - `evidence_status = VERIFIED`
-  - `logic_status = GREEN`
-  - `security_status = GREEN`
-  - `experience_status = GREEN` or `WAIVED`
-- Feature work merges into `development`, never directly into `prod`.
-- Release promotion is allowed only from `development` or approved `release/*`.
-- Use the helper command path only when repo-local state automation is explicitly needed; otherwise stay inside Codex and carry the gate decisions in the session.

package/plugins/meta-architect/skills/sage/SKILL.md

@@ -1,24 +0,0 @@
----
-name: sage
-description: "Use when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`."
----
-
-# Sage
-
-Use this skill inside Codex to verify or challenge stack choices with real sources.
-
-## Output
-
-Produce:
-- candidate tools, libraries, or services
-- why each option fits or fails the architecture
-- source-backed evidence from official docs, upstream repos, or approved GitMCP sources
-- recommendation with tradeoffs
-- unresolved gaps or missing evidence
-- exact next trigger, usually `$flow`
-
-## Rules
-
-- Do not invent package capabilities or maturity claims.
-- Prefer primary sources over summaries when validating technical details.
-- If the evidence is weak or contradictory, say so clearly and keep the recommendation conditional.

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

@@ -1,4 +0,0 @@
-interface:
-  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/SKILL.md

@@ -1,25 +0,0 @@
----
-name: vet
-description: "Use when the user wants a security and trust-boundary review of the current design before implementation or release."
----
-
-# Vet
-
-Use this skill inside Codex to review security posture before the build lane.
-
-## Output
-
-Produce:
-- trust boundaries
-- authn/authz expectations
-- sensitive data paths
-- abuse cases and likely failure modes
-- concrete mitigations
-- release blockers vs acceptable risks
-- exact next trigger, usually `$vibe`
-
-## Rules
-
-- Prioritize material risks over exhaustive but low-value checklists.
-- Call out missing assumptions that affect security posture.
-- Distinguish between must-fix blockers and documented accepted risk.

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

@@ -1,4 +0,0 @@
-interface:
-  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/SKILL.md

@@ -1,24 +0,0 @@
----
-name: vibe
-description: "Use when the user wants a DX and UX review of the planned workflow before implementation proceeds."
----
-
-# Vibe
-
-Use this skill inside Codex to review whether the system will feel coherent for both operators and end users.
-
-## Output
-
-Produce:
-- developer workflow risks
-- user workflow risks
-- complexity hotspots
-- onboarding or operability friction
-- simplifications that improve clarity
-- exact next trigger, usually `$build`
-
-## Rules
-
-- Focus on concrete friction, not aesthetics-only feedback.
-- Prefer fewer surfaces, fewer steps, and clearer operator outcomes.
-- Preserve the architecture and security constraints established earlier in the flow.

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

@@ -1,4 +0,0 @@
-interface:
-  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/plugin-sync.js

@@ -1,92 +0,0 @@
-#!/usr/bin/env node
-
-import fs from "node:fs/promises";
-import path from "node:path";
-import process from "node:process";
-
-const repoRoot = process.cwd();
-const skillsRoot = path.join(repoRoot, "skills");
-const pluginRoot = path.join(repoRoot, "plugins", "meta-architect");
-const pluginSkillsRoot = path.join(pluginRoot, "skills");
-
-function parseArgs(argv) {
-  return {
-    check: argv.includes("--check"),
-  };
-}
-
-async function copyDir(src, dest) {
-  await fs.mkdir(dest, { recursive: true });
-  const entries = await fs.readdir(src, { withFileTypes: true });
-  for (const entry of entries) {
-    const srcPath = path.join(src, entry.name);
-    const destPath = path.join(dest, entry.name);
-    if (entry.isDirectory()) {
-      await copyDir(srcPath, destPath);
-    } else {
-      await fs.copyFile(srcPath, destPath);
-    }
-  }
-}
-
-async function listSkillDirs(root) {
-  const entries = await fs.readdir(root, { withFileTypes: true }).catch(() => []);
-  return entries
-    .filter((entry) => entry.isDirectory())
-    .map((entry) => entry.name)
-    .sort();
-}
-
-async function syncPluginSkills() {
-  const skillDirs = await listSkillDirs(skillsRoot);
-  await fs.mkdir(pluginSkillsRoot, { recursive: true });
-
-  const existingPluginDirs = await listSkillDirs(pluginSkillsRoot);
-  for (const name of existingPluginDirs) {
-    if (!skillDirs.includes(name)) {
-      await fs.rm(path.join(pluginSkillsRoot, name), { recursive: true, force: true });
-    }
-  }
-
-  for (const name of skillDirs) {
-    const src = path.join(skillsRoot, name);
-    const dest = path.join(pluginSkillsRoot, name);
-    await fs.rm(dest, { recursive: true, force: true });
-    await copyDir(src, dest);
-  }
-
-  return skillDirs;
-}
-
-async function verifyPluginSkills() {
-  const skillDirs = await listSkillDirs(skillsRoot);
-  const pluginDirs = await listSkillDirs(pluginSkillsRoot);
-  if (skillDirs.length !== pluginDirs.length) {
-    throw new Error("Plugin skill mirror drift: directory count mismatch");
-  }
-
-  for (let index = 0; index < skillDirs.length; index += 1) {
-    if (skillDirs[index] !== pluginDirs[index]) {
-      throw new Error(
-        `Plugin skill mirror drift: expected ${skillDirs[index]}, found ${pluginDirs[index]}`,
-      );
-    }
-  }
-}
-
-async function main() {
-  const args = parseArgs(process.argv.slice(2));
-  if (args.check) {
-    await verifyPluginSkills();
-    console.log(pluginSkillsRoot);
-    return;
-  }
-
-  await syncPluginSkills();
-  console.log(pluginSkillsRoot);
-}
-
-main().catch((error) => {
-  console.error(error.message);
-  process.exitCode = 1;
-});

package/scripts/postinstall.js

@@ -1,23 +0,0 @@
-#!/usr/bin/env node
-
-import process from "node:process";
-import { installSkills, installSupportBundle } from "../src/skill-installer.js";
-
-async function main() {
-  if (process.env.MA_SKIP_AUTO_INSTALL === "1") {
-    console.log("meta-architect: skipped Codex skill auto-install");
-    return;
-  }
-
-  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) => {
-  console.error(`meta-architect: failed to install Codex skills: ${error.message}`);
-  process.exitCode = 1;
-});

package/scripts/release-metadata.js

@@ -1,94 +0,0 @@
-#!/usr/bin/env node
-
-import fs from "node:fs";
-import process from "node:process";
-
-function loadPackageJson() {
-  return JSON.parse(fs.readFileSync("package.json", "utf8"));
-}
-
-function parseVersion(version) {
-  const match = version.match(
-    /^(?<major>\d+)\.(?<minor>\d+)\.(?<patch>\d+)(?:-(?<prerelease>[0-9A-Za-z.-]+))?$/,
-  );
-  if (!match?.groups) {
-    throw new Error(`Invalid package.json version: ${version}`);
-  }
-  return match.groups;
-}
-
-function computeMetadata(version) {
-  const parsed = parseVersion(version);
-  const prerelease = parsed.prerelease ?? "";
-  const prereleaseIdentifiers = prerelease ? prerelease.split(".") : [];
-  const isPrerelease = prereleaseIdentifiers.length > 0;
-  const distTag = isPrerelease ? prereleaseIdentifiers[0] : "latest";
-
-  return {
-    version,
-    gitTag: `v${version}`,
-    isPrerelease,
-    distTag,
-    prerelease,
-  };
-}
-
-function parseArgs(argv) {
-  const args = {
-    field: "",
-    githubOutput: "",
-  };
-
-  for (let index = 0; index < argv.length; index += 1) {
-    const token = argv[index];
-    if (token === "--field") {
-      args.field = argv[index + 1] ?? "";
-      index += 1;
-      continue;
-    }
-    if (token === "--github-output") {
-      args.githubOutput = argv[index + 1] ?? "";
-      index += 1;
-    }
-  }
-
-  return args;
-}
-
-function writeGithubOutput(outputPath, metadata) {
-  const lines = [
-    `version=${metadata.version}`,
-    `git_tag=${metadata.gitTag}`,
-    `dist_tag=${metadata.distTag}`,
-    `is_prerelease=${metadata.isPrerelease}`,
-  ];
-  fs.appendFileSync(outputPath, `${lines.join("\n")}\n`);
-}
-
-function main() {
-  const args = parseArgs(process.argv.slice(2));
-  const pkg = loadPackageJson();
-  const metadata = computeMetadata(pkg.version);
-
-  if (args.githubOutput) {
-    writeGithubOutput(args.githubOutput, metadata);
-  }
-
-  if (args.field) {
-    const value = metadata[args.field];
-    if (value === undefined) {
-      throw new Error(`Unknown metadata field: ${args.field}`);
-    }
-    console.log(value);
-    return;
-  }
-
-  console.log(JSON.stringify(metadata, null, 2));
-}
-
-try {
-  main();
-} catch (error) {
-  console.error(error.message);
-  process.exitCode = 1;
-}