@jstn-sdk/ma 0.1.13 → 0.14.0

package/docs/onboarding.md

@@ -1,81 +0,0 @@
-# Onboarding
-
-This is the shortest entrypoint for the real first-run Meta-Architect path.
-
-## Read first
-
-1. `README.md`
-2. `docs/getting-started.md`
-3. `example/usage-workflow.md`
-4. `docs/release-spec.md`
-5. `docs/skills-publishing.md`
-
-## Canonical install and start
-
-Recommended CLI install for macOS, Linux, WSL, and Git-Bash:
-
-```bash
-# One-line install (POSIX shells only; use WSL/Git-Bash on Windows)
-curl -fsSL https://cdn.jsdelivr.net/gh/JustineDevs/meta-architect@main/scripts/install.sh | sh
-```
-
-The installer uses jsDelivr to fetch this repo's POSIX install script and runs the canonical npm install path.
-
-```bash
-# Install
-npm i -g @openai/codex@latest @jstn-sdk/ma@latest
-
-# Start Codex context if needed
-ma --madmax --high
-
-# Remove Meta-Architect only
-npm uninstall -g @jstn-sdk/ma
-
-# Remove Meta-Architect and Codex
-npm uninstall -g @jstn-sdk/ma @openai/codex
-```
-
-## First runtime action
-
-Start with `$maestro` when you want MA to choose and drive the next safe lane:
-
-```text
-$maestro
-```
-
-Use the structured `$arch` prompt from [example/usage-workflow.md](../example/usage-workflow.md) when you already know the project brief and want to begin directly with architecture:
-
-```text
-$arch I want to build: [PROJECT IDEA]
-```
-
-Then continue through:
-- `$sage`
-- `$flow`
-- `$vet`
-- `$vibe`
-- `$build`
-
-## Secondary helper path
-
-Only use this when you need local repo scaffolding or scripted validation:
-
-```bash
-ma setup
-ma
-ma idea "Prepare Meta-Architect v0.1.13 for a production package release with real install docs, Obsidian brain-context support, learning-loop reliability, and package proof artifacts."
-ma run '$maestro'
-ma run '$arch'
-ma run '$sage'
-ma run '$flow'
-ma run '$vet'
-ma run '$vibe'
-ma run '$build'
-```
-
-## First safety rules
-
-- Do not commit runtime `.ma` state.
-- Do not bypass gates by editing status files manually.
-- Do not assume a release channel succeeded without evidence.
-- Do not treat fallback MCP docs mode as normal verified evidence.

package/docs/prompt-guidance-contract.md

@@ -1,17 +0,0 @@
-# Prompt Guidance Contract
-
-Meta-Architect prompt surfaces must preserve the Active Autonomy Core contract.
-
-## Required Patterns
-
-1. `AUTO-CONTINUE` and `ASK` must be named explicitly.
-2. The `ASK` list is closed: destructive, irreversible, credential-gated, external-production, materially scope-changing, or missing authority.
-3. Permission-handoff phrasing is banned on AUTO-CONTINUE branches.
-4. Skills and role prompts must describe completion as a loop with explicit stop conditions.
-5. Workflow terminal replies must name an outcome: `finished`, `blocked`, `failed`, `cancelled`, or `askuserQuestion`.
-6. Completion claims require fresh verification evidence or an explicit validation gap.
-7. Runtime hook policy must include stall-pattern coverage for passive permission handoffs.
-
-## Contributor Rule
-
-Do not weaken the anti-passive contract when editing prompts, skills, hooks, or exported host payloads. If a prompt surface cannot execute safely, it must name the exact closed-list ASK reason instead of asking a vague permission question.

package/docs/prompt-guidance-fragments/active-autonomy-core.md

@@ -1,7 +0,0 @@
-<!-- ACTIVE AUTONOMY CORE - DO NOT REMOVE -->
-- AUTO-CONTINUE: clear, already-requested, local/workspace-scoped, low-risk, reversible, non-destructive work with an available verification path. Continue executing, inspecting, editing, testing, and verifying without permission handoff.
-- ASK only for destructive, irreversible, credential-gated, external-production, materially scope-changing actions, or when missing authority blocks progress.
-- On AUTO-CONTINUE branches, do not say "Should I proceed?", "Would you like me to continue?", "If you want, I can ...", or equivalent permission-handoff phrasing. State the next action or evidence-backed result.
-- Do not instruct humans to perform ordinary safe reversible workspace actions; execute them through MA/runtime tools and report evidence.
-- Completion requires a terminal outcome (`finished`, `blocked`, `failed`, `cancelled`, or `askuserQuestion`) plus fresh verification evidence or an explicit validation gap.
-<!-- END ACTIVE AUTONOMY CORE -->

package/docs/skills-publishing.md

@@ -1,255 +0,0 @@
-# Skills Publishing
-
-Meta-Architect ships skills through a deliberate source-to-package pipeline. This repository treats publishable skills as product artifacts, not as raw markdown files.
-
-## Two skill surfaces
-
-### 1. Internal runtime surface
-
-Location:
-- `.ma/skills/`
-
-Purpose:
-- local runtime behavior
-- internal command contracts
-- generated or seeded operator surfaces
-
-### 2. Publishable skill surface
-
-Location:
-- `skills/`
-
-Purpose:
-- installable Codex skill folders
-- UI metadata via `agents/openai.yaml`
-- versionable public skill contract
-
-Do not confuse these two layers. The repo publishes `skills/`, not `.ma/`.
-
-## Published surface types
-
-The publishable `skills/` surface contains:
-- one umbrella autonomous manager: `$maestro`
-- fixed gated lanes: `$arch`, `$sage`, `$flow`, `$vet`, `$vibe`, `$build`
-- non-gating helper skills: `$align`, `$diagnose`, `$tdd`, `$cleanup`
-
-Only `$maestro` is the umbrella surface. Helper skills are intentionally publishable but non-gating.
-The `ma` terminal helper command is part of the npm package surface, not the publishable skill contract.
-
-## Canonical packaging flow
-
-### Generate manifest
-
-```bash
-npm run skills:manifest
-```
-
-Expected effect:
-- writes `skills/index.json`
-- manifest entries should match the actual skill directories
-
-### Validate skills
-
-```bash
-npm run skills:validate
-```
-
-Expected effect:
-- every skill folder passes the validator
-- missing or invalid frontmatter should fail the command
-- missing or structurally incomplete `agents/openai.yaml` should fail the command
-
-### Sync plugin mirror
-
-```bash
-npm run plugin:sync
-npm run plugin:verify
-```
-
-Expected effect:
-- `plugins/meta-architect/skills/` mirrors the canonical `skills/` surface
-- the local marketplace and plugin bundle remain aligned with the package skill contract
-- plugin drift fails verification instead of surviving into release artifacts
-
-### Create bundle
-
-```bash
-npm run skills:pack
-```
-
-Expected effect:
-- creates `dist/meta-architect-skills.tgz`
-- bundle should be non-empty
-
-### Smoke-test install
-
-```bash
-npm run skills:install -- --path ./dist/installed-skills
-```
-
-Expected effect:
-- all publishable skill folders are copied to the target install path
-- install target should contain:
-  - `align`
-  - `maestro`
-  - `arch`
-  - `sage`
-  - `flow`
-  - `diagnose`
-  - `tdd`
-  - `cleanup`
-  - `vet`
-  - `vibe`
-  - `build`
-- install target should not contain:
-  - `meta-architect`
-
-## Expected outputs
-
-### `skills/index.json`
-
-Should contain:
-- schema version
-- skill names
-- repo-local path mapping
-- descriptions
-- only native Meta-Architect skill identities
-- a `maestro` description that matches the bounded autonomous-manager contract
-
-### `dist/meta-architect-skills.tgz`
-
-Should contain:
-- `skills/`
-- each skill folder
-- each `SKILL.md`
-- each `agents/openai.yaml`
-- any intended references/assets
-
-It should **not** rely on hidden runtime state.
-
-Important:
-- `npm run skills:pack` creates the **skills bundle tarball only**
-- it is not the same thing as the broader npm package tarball from `npm pack`
-- the npm package surface is controlled separately by `package.json > files`
-
-## Source vs package contents
-
-The npm package and tarball should stay explicit.
-
-Current package intent:
-- package name: `@jstn-sdk/ma`
-- public publish config
-- explicit `files` list in `package.json`
-
-The publishable package should include:
-- `bin/`
-- `skills/`
-- `docs/`
-- `scripts/`
-- `index.js`
-- `README.md`
-- `LICENSE`
-
-It should not include:
-- runtime `.ma` state
-- local logs
-- temp install targets
-- generated local caches
-
-The `skills:pack` tarball is narrower than the npm package:
-- `skills:pack` => `skills/` distribution bundle
-- `npm pack` => public npm package with the explicit `files` list
-
-## Release and dist-tag discipline
-
-Meta-Architect release behavior is lane-aware:
-- stable versions publish to npm `latest`
-- prerelease versions publish to explicit lanes such as `next`, `beta`, or `canary`
-- prereleases must use `npm publish --tag <lane>`
-- stable releases keep the default `latest` behavior and public scoped access
-
-Before publish:
-1. bump version with `npm version <version> --no-git-tag-version`
-2. update changelog and release docs
-3. run `npm run release:verify`
-4. run `npm run release:check`
-5. create and push tag `v<version>`
-6. publish the package with the correct lane behavior
-   - preferred: run `.github/workflows/npm-publish.yml` on a supported cloud runner so provenance can be generated
-   - local fallback: omit `--provenance` and publish with `npm publish --access public` or `npm publish --access public --tag <lane>`
-7. verify the resulting dist-tags with `npm view @jstn-sdk/ma version dist-tags time --json`
-
-## Plugin relation
-
-The plugin bundle in:
-- `plugins/meta-architect/`
-
-is related but not identical to the npm/package skill bundle.
-
-Relationship:
-- `skills/` is the canonical publishable skill source
-- `plugins/meta-architect/` is the plugin-installable consumer-facing bundle
-- both should remain aligned in behavior and version intent
-- `.agents/plugins/marketplace.json` advertises the local plugin source for discovery
-- `plugins/meta-architect/.codex-plugin/plugin.json` is the plugin contract entrypoint
-- the umbrella in-session entry point is `$maestro`; there is no separately shipped `$meta-architect` skill
-- `$maestro` is the bounded autonomous manager, not a second terminal runtime
-- helper skills remain publishable mirrors, but they do not add release gates or alternate umbrella entry points
-
-If a skill contract changes:
-1. update `skills/`
-2. regenerate manifest
-3. sync the plugin mirror
-4. validate skills
-5. ensure plugin-facing bundle still reflects the same product contract
-
-## Real commands for a release-minded flow
-
-```bash
-npm run skills:manifest
-npm run plugin:sync
-npm run skills:validate
-npm run plugin:verify
-npm run skills:pack
-npm run skills:install -- --path ./dist/installed-skills
-npm run pack:inspect
-```
-
-## Expected failure modes
-
-- manifest drift:
-  - `skills/index.json` does not match actual skill directories
-- invalid skill:
-  - malformed frontmatter
-  - missing `SKILL.md`
-  - invalid `agents/openai.yaml`
-- package drift:
-  - tarball includes files not intended for public distribution
-- plugin drift:
-  - plugin bundle no longer matches the published skill contract
-
-## Release artifact expectations
-
-Before a release is considered real:
-- `skills/index.json` must be current
-- `dist/meta-architect-skills.tgz` must exist
-- `dist/meta-architect_<version>_all.deb` must exist for the Debian-family release lane
-- `dist/meta-architect-<version>-1-any.pkg.tar.xz` must exist for the Arch-family release lane
-- `dist/meta-architect-<version>-1.noarch.rpm` must exist for the Fedora/openSUSE-style release lane
-- install smoke test must pass
-- package inspection must be sane
-- docs must match the published behavior
-
-## Related surfaces
-
-- [README.md](../README.md)
-- [docs/skills.md](./skills.md)
-- [plugins/meta-architect/README.md](../plugins/meta-architect/README.md)
-- [plugins/meta-architect/.codex-plugin/plugin.json](../plugins/meta-architect/.codex-plugin/plugin.json)
-- [../.agents/plugins/marketplace.json](../.agents/plugins/marketplace.json)
-- [package.json](../package.json)
-- [scripts/skills-manifest.js](../scripts/skills-manifest.js)
-- [scripts/plugin-sync.js](../scripts/plugin-sync.js)
-- [scripts/skills-validate.js](../scripts/skills-validate.js)
-- [scripts/skills-pack.js](../scripts/skills-pack.js)
-- [scripts/skills-install.js](../scripts/skills-install.js)