@jstn-sdk/ma 0.1.11 → 0.1.12

package/mcp/native-playbooks.json

@@ -0,0 +1,117 @@
+{
+  "schemaVersion": "0.1.0",
+  "packs": [
+    {
+      "id": "native-ingest-core",
+      "title": "Native Ingest Core",
+      "summary": "Read-only Meta-Architect playbook pack for support-bundle-aware runtime wiring and native packaging discipline.",
+      "readOnly": true,
+      "applicableSkills": ["maestro", "sage", "vet", "align", "diagnose", "tdd", "cleanup"],
+      "runtimeSurfaces": [
+        "mcp/native-playbooks.json",
+        "mcp/local/playbooks.js",
+        "mcp/local-capabilities.json",
+        "docs/installed-sdk.md",
+        "docs/mcp-setup.md"
+      ],
+      "patterns": [
+        {
+          "id": "single-umbrella-routing",
+          "title": "Keep maestro singular",
+          "guidance": "Route native helper families through maestro while keeping the gated release sequence unchanged.",
+          "appliesTo": ["maestro"]
+        },
+        {
+          "id": "read-only-local-capability",
+          "title": "Expose playbooks read-only",
+          "guidance": "Treat playbooks as a packaged local capability with allowlisted resource reads and no mutating local tools.",
+          "appliesTo": ["maestro", "align", "diagnose", "tdd", "cleanup"]
+        },
+        {
+          "id": "bundle-first-support-assets",
+          "title": "Prefer packaged assets",
+          "guidance": "Use support-bundle-installed docs and packaged MCP assets instead of source-checkout-relative guessing.",
+          "appliesTo": ["maestro", "sage", "vet"]
+        }
+      ],
+      "references": [
+        {
+          "id": "installed-support-bundle",
+          "title": "Installed support bundle contract",
+          "path": "docs/installed-sdk.md",
+          "role": "support-bundle"
+        },
+        {
+          "id": "mcp-setup",
+          "title": "MCP setup and GitMCP verification",
+          "path": "docs/mcp-setup.md",
+          "role": "mcp-setup"
+        },
+        {
+          "id": "native-engineering-patterns",
+          "title": "Native engineering patterns",
+          "path": "docs/reference/native-engineering-patterns.md",
+          "role": "reference"
+        },
+        {
+          "id": "native-style-and-deslop",
+          "title": "Native style and deslop",
+          "path": "docs/reference/native-style-and-deslop.md",
+          "role": "reference"
+        },
+        {
+          "id": "native-security-playbooks",
+          "title": "Native security playbooks",
+          "path": "docs/reference/native-security-playbooks.md",
+          "role": "reference"
+        },
+        {
+          "id": "native-source-selection",
+          "title": "Native source selection",
+          "path": "docs/reference/native-source-selection.md",
+          "role": "reference"
+        },
+        {
+          "id": "maestro-native-ingest-map",
+          "title": "Maestro native ingest map",
+          "path": "skills/maestro/references/native-ingest-map.md",
+          "role": "skill-reference"
+        },
+        {
+          "id": "sage-source-selection-pack",
+          "title": "Sage source selection pack",
+          "path": "skills/sage/references/source-selection.md",
+          "role": "skill-reference"
+        },
+        {
+          "id": "vet-security-playbooks-pack",
+          "title": "Vet security playbooks pack",
+          "path": "skills/vet/references/security-playbooks.md",
+          "role": "skill-reference"
+        },
+        {
+          "id": "align-shared-language-pack",
+          "title": "Align shared language pack",
+          "path": "skills/align/references/shared-language.md",
+          "role": "skill-reference"
+        },
+        {
+          "id": "cleanup-style-and-deslop-pack",
+          "title": "Cleanup style and deslop pack",
+          "path": "skills/cleanup/references/style-and-deslop.md",
+          "role": "skill-reference"
+        }
+      ],
+      "provenance": [
+        {
+          "kind": "product-rule",
+          "note": "Repo-owned native curation only; do not expose upstream-branded catalogs as first-class product surfaces."
+        },
+        {
+          "kind": "release-scope",
+          "note": "Playbooks stay read-only in this release and extend the existing first-party local capability registry."
+        }
+      ]
+    }
+  ]
+}

package/mcp/servers.json

@@ -2,51 +2,61 @@
   "schemaVersion": "0.1.0",
   "servers": [
     {
+      "kind": "gitmcp-evidence",
       "category": "meta-list",
       "repo": "sindresorhus/awesome",
       "endpoint": "https://gitmcp.io/sindresorhus/awesome"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "typescript",
       "repo": "dzharii/awesome-typescript",
       "endpoint": "https://gitmcp.io/dzharii/awesome-typescript"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "rust",
       "repo": "rust-unofficial/awesome-rust",
       "endpoint": "https://gitmcp.io/rust-unofficial/awesome-rust"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "go",
       "repo": "avelino/awesome-go",
       "endpoint": "https://gitmcp.io/avelino/awesome-go"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "python",
       "repo": "vinta/awesome-python",
       "endpoint": "https://gitmcp.io/vinta/awesome-python"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "java",
       "repo": "akullpp/awesome-java",
       "endpoint": "https://gitmcp.io/akullpp/awesome-java"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "dotnet",
       "repo": "quozd/awesome-dotnet",
       "endpoint": "https://gitmcp.io/quozd/awesome-dotnet"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "security",
       "repo": "sbilly/awesome-security",
       "endpoint": "https://gitmcp.io/sbilly/awesome-security"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "self-hosted",
       "repo": "awesome-selfhosted/awesome-selfhosted",
       "endpoint": "https://gitmcp.io/awesome-selfhosted/awesome-selfhosted"
     },
     {
+      "kind": "gitmcp-evidence",
       "category": "system-design",
       "repo": "checkcheckzz/system-design-interview",
       "endpoint": "https://gitmcp.io/checkcheckzz/system-design-interview"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jstn-sdk/ma",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "Codex-native skills system for architecture, evidence, review, and gated build guidance.",
   "license": "MIT",
   "author": "JustineDevs",
@@ -58,11 +58,14 @@
     "postinstall": "node ./scripts/postinstall.js",
     "test": "node --test",
     "status": "node ./bin/ma.js status",
+    "linux:packages:build": "node ./scripts/build-linux-packages.mjs",
+    "linux:packages:smoke": "node ./scripts/linux-package-smoke.mjs",
     "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:assets": "node ./.github/scripts/validate-release-assets.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",
     "skills:validate": "node ./scripts/skills-validate.js",

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

@@ -1,7 +1,7 @@
 {
   "name": "meta-architect",
   "displayName": "Meta-Architect",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "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,7 +1,7 @@
 {
   "name": "meta-architect",
-  "version": "0.1.11",
-  "description": "Skills-first workflow layer for Codex with architecture, evidence, review, and gated build guidance.",
+  "version": "0.1.12",
+  "description": "Skills-first workflow layer for Codex with a bounded autonomous manager, architecture, evidence, review, and gated build guidance.",
   "author": {
     "name": "JustineDevs",
     "url": "https://github.com/JustineDevs"
@@ -15,8 +15,8 @@
   "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.",
+    "shortDescription": "Architecture-first skill bundle with a bounded in-session autonomous manager.",
+    "longDescription": "Meta-Architect packages reusable Codex skills plus plugin-scoped MCP and app metadata. The in-session skill workflow is primary, with `$maestro` as the single bounded autonomous manager over the fixed gated sequence and the publishable non-gating helper skills. 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/.mcp.json

@@ -1,6 +1,6 @@
 {
   "name": "meta-architect",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "collections": [
     "sindresorhus/awesome",
     "dzharii/awesome-typescript",

package/plugins/meta-architect/README.md

@@ -9,6 +9,10 @@ This plugin bundle packages the Meta-Architect skill surfaces for consumers that
   - `.app.json`
   - `.mcp.json`
 - bundled Meta-Architect skill surfaces under `skills/`
+- one umbrella autonomous manager: `$maestro`
+- fixed gated lanes: `$arch`, `$sage`, `$flow`, `$vet`, `$vibe`, `$build`
+- non-gating helper skills: `$align`, `$diagnose`, `$tdd`, `$cleanup`
+- packaged native reference files mirrored under the relevant skill folders
 - a release-scoped version line aligned to the repo
 
 ## What the plugin does not contain
@@ -46,6 +50,26 @@ The plugin-facing bundle should be consumed alongside the repository’s documen
 
 Canonical package/runtime path:
 
+Debian-family install:
+
+```bash
+sudo apt install ./meta-architect_<version>_all.deb
+```
+
+Arch-family install:
+
+```bash
+sudo pacman -U ./meta-architect-<version>-1-any.pkg.tar.xz
+```
+
+Fedora/openSUSE install:
+
+```bash
+sudo dnf install ./meta-architect-<version>-1.noarch.rpm
+```
+
+npm fallback/default supported path:
+
 ```bash
 # Install
 npm i -g @openai/codex@latest @jstn-sdk/ma@latest
@@ -79,6 +103,8 @@ npm run skills:install -- --path ./dist/installed-skills
 
 Consumer expectation:
 - the plugin ships the same public skill contracts as the canonical `skills/` directory
+- `$maestro` remains the only umbrella surface in the plugin bundle and acts as the bounded autonomous manager for the in-session workflow
+- helper skills are installable mirrors, but they remain non-gating and do not create new release gates
 - it does not define a looser or simplified product contract
 
 ## MCP wiring expectations
@@ -105,7 +131,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.11`
+- plugin scope is aligned to Meta-Architect `v0.1.12`
 - any breaking contract change should be versioned intentionally
 
 The plugin is one distribution surface of the same product, not a separate product line.

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

@@ -0,0 +1,24 @@
+---
+name: align
+description: "Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes."
+---
+
+# Align
+
+Use this skill inside Codex when the problem is ambiguity, drift, or mismatched language rather than missing implementation. `align` is a non-gating helper skill.
+
+## Output
+
+Produce:
+- current ambiguity or mismatch
+- normalized terminology
+- scope boundary and exclusions
+- acceptance checks or rewritten prompts
+- exact next trigger, usually `$maestro` or the lane that owns the next decision
+
+## Rules
+
+- Align language and scope without creating a new release gate.
+- Prefer tightening existing artifacts over inventing parallel docs.
+- Keep terminology Meta-Architect-native for user-facing surfaces.
+- Use `references/shared-language.md` for naming, taxonomy, and docs-clarity patterns.

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

@@ -0,0 +1,4 @@
+interface:
+  display_name: "$align"
+  short_description: "Scope alignment and shared language helper"
+  default_prompt: "Use $align to resolve scope drift, normalize terminology, and tighten prompts or docs before handing work back to the owning gated lane."

package/plugins/meta-architect/skills/align/references/shared-language.md

@@ -0,0 +1,24 @@
+# Shared Language
+
+Use this reference pack with `align` when terminology, scope, or docs are drifting.
+
+## Naming rules
+
+- `$maestro` is the only umbrella surface.
+- `$arch -> $sage -> $flow -> $vet -> $vibe -> $build` remains the fixed gated sequence.
+- `align`, `diagnose`, `tdd`, and `cleanup` are helper skills only.
+- User-facing guidance stays Meta-Architect-native; external source names may appear as evidence, not as product surfaces.
+
+## Alignment checklist
+
+- Name the current artifact, lane, and decision owner.
+- Replace vague nouns with one stable term.
+- Separate what is in scope, out of scope, and not yet decided.
+- Rewrite prompts or docs so the next trigger is obvious.
+
+## Docs-clarity patterns
+
+- Put the next trigger in one line.
+- Distinguish terminal helper commands from in-session skills.
+- Distinguish gated lanes from helper skills.
+- Prefer concise, high-signal wording over long catalogs or branding-heavy lists.

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

@@ -0,0 +1,23 @@
+---
+name: cleanup
+description: "Use when the user wants contract-preserving simplification, anti-slop cleanup, or a final-pass polish after the main decision is made."
+---
+
+# Cleanup
+
+Use this skill inside Codex when the core behavior is understood but the artifact still needs simplification, deslop work, or clearer prose. `cleanup` is a non-gating helper skill.
+
+## Output
+
+Produce:
+- removable complexity or noisy wording
+- behavior-preserving simplifications
+- residual risks after cleanup
+- exact next trigger, usually the owning lane or release verification
+
+## Rules
+
+- Prefer deletion over addition.
+- Preserve behavior and decision ownership while cleaning up.
+- Keep user-facing wording concise and product-native.
+- Use `references/style-and-deslop.md` for simplification and prose cleanup patterns.

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

@@ -0,0 +1,4 @@
+interface:
+  display_name: "$cleanup"
+  short_description: "Anti-slop cleanup and final-pass polish"
+  default_prompt: "Use $cleanup to simplify noisy code or docs, remove avoidable slop, and polish wording without changing the owning lane."

package/plugins/meta-architect/skills/cleanup/references/style-and-deslop.md

@@ -0,0 +1,18 @@
+# Style And Deslop
+
+Use this reference pack with `cleanup` when an artifact works but still feels bloated, generic, or hard to trust.
+
+## Cleanup priorities
+
+- remove repeated framing
+- cut placeholder language and empty intensifiers
+- collapse duplicate concepts into one stable term
+- prefer shorter, sharper instructions when they preserve meaning
+- delete unused or non-essential surface area before adding more structure
+
+## Safe cleanup checks
+
+- behavior or contract is unchanged
+- the next trigger is still explicit
+- helper-vs-gated distinctions remain intact
+- no upstream brand names are introduced as product surfaces

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

@@ -0,0 +1,24 @@
+---
+name: diagnose
+description: "Use when the user needs failure triage, blocked-lane diagnosis, or root-cause decomposition before the next gate can move."
+---
+
+# Diagnose
+
+Use this skill inside Codex when a lane is blocked, a symptom is vague, or the next useful move is to decompose the failure before editing code. `diagnose` is a non-gating helper skill.
+
+## Output
+
+Produce:
+- observed symptom
+- likely failure slices
+- missing evidence or missing reproduction steps
+- smallest next probe
+- exact next trigger, usually the owning lane or `$maestro`
+
+## Rules
+
+- Decompose the problem before proposing broad fixes.
+- Prefer the smallest reproducible boundary that can confirm or kill a hypothesis.
+- Keep release-state ownership with the gated lane that is blocked.
+- Escalate assumptions clearly when evidence is still incomplete.

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

@@ -0,0 +1,4 @@
+interface:
+  display_name: "$diagnose"
+  short_description: "Blocked-lane diagnosis and failure triage"
+  default_prompt: "Use $diagnose to break a vague failure into concrete hypotheses, probes, and the smallest next debugging step without changing gate ownership."

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

@@ -1,11 +1,34 @@
 ---
 name: maestro
-description: "Use when the user wants Meta-Architect to choose the best next workflow step, explain why, and recommend the right lane or assignment."
+description: "Use when the user wants the singular Meta-Architect in-session autonomous manager: choose the best next workflow step, manage the fixed gated workflow, and route bounded helper handoffs inside Codex."
 ---
 
 # Maestro
 
-Use this skill inside Codex when you want Meta-Architect to act like a workflow manager.
+## Overview
+
+Use this skill inside Codex as the singular Meta-Architect umbrella surface and bounded autonomous manager. It inspects workflow state, chooses the smallest safe next step, manages the fixed gated design-and-review sequence one lane at a time, and routes helper handoffs when they are enough. There is no separate shipped `$meta-architect` skill.
+
+## Workflow
+
+1. Inspect the current gate state, active evidence, and current blockers.
+2. Choose the smallest safe next step and decide whether the next move is:
+   - a direct advisory result
+   - a helper-skill handoff
+   - a gated-lane handoff
+3. When the issue is alignment, diagnosis, regression-first execution, or final-pass cleanup, hand work to the publishable but non-gating helper skills:
+   - `$align`
+   - `$diagnose`
+   - `$tdd`
+   - `$cleanup`
+4. When the user wants the full Meta-Architect workflow, manage the fixed gated sequence without inventing new gates or skipping lane ownership:
+   - `$arch`
+   - `$sage`
+   - `$flow`
+   - `$vet`
+   - `$vibe`
+   - `$build`
+5. End with a clear result shape: decision, evidence, blockers, the lane assignment if any, and the exact next trigger.
 
 ## Output
 
@@ -22,4 +45,14 @@ Produce:
 - Prefer the smallest next step that moves the workflow forward safely.
 - Respect current gate state before recommending implementation or release work.
 - Be explicit when more evidence, planning, or validation is still needed.
-- Route to the in-session skill flow first; use helper commands only when they are the clearest support path.
+- Treat the in-session skill flow as primary. Use `ma ...` terminal helpers only when repo-local setup, inspection, or scripted state automation is explicitly the better support path.
+- Keep `$maestro` as the only umbrella surface. It owns next-step management and bounded handoff decisions, but it does not replace the outputs owned by the gated lanes.
+- Helper skills are publishable mirrors, but they are non-gating. They support a lane and then hand control back to `$maestro` or the fixed gated sequence.
+- Do not expand the release-gated sequence for this release. Gate ownership stays with `$arch -> $sage -> $flow -> $vet -> $vibe -> $build`.
+- Stay inside Codex unless the user explicitly asks for repo-local helper commands.
+- Keep the workflow architecture-first. Do not jump into code before the architecture and review lanes are grounded.
+- Use approved discovery accelerators such as Ossium, Trendshift, Dev Hunt, Libraries.io, Open Hub, and Open-source Projects when you need faster OSS candidate discovery, then validate any promising project through upstream repos and official docs.
+- Keep the `$sage` order explicit: known upstream sources first, discovery accelerators second, exact repo mapping third, approval only after upstream verification.
+- Prefer official docs, upstream repos, and repo-configured GitMCP sources when validating tooling choices.
+- For release gates and branch policy, read `references/core-release-rules.md`.
+- For the native helper-family contract and pattern classification, read `references/native-ingest-map.md`.

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

@@ -1,4 +1,4 @@
 interface:
   display_name: "$maestro"
-  short_description: "Best next step and lane orchestration"
-  default_prompt: "Use $maestro to inspect the current Meta-Architect workflow state, choose the best next step, explain why it is next, and recommend the right lane or assignment."
+  short_description: "Bounded autonomous manager for the gated workflow and helper handoffs"
+  default_prompt: "Use $maestro as the singular Meta-Architect in-session autonomous manager: inspect workflow state, choose the smallest safe next step, hand work to $align, $diagnose, $tdd, or $cleanup when a publishable non-gating helper is enough, and manage the fixed gated sequence at $arch, $sage, $flow, $vet, $vibe, and $build without inventing new gates."

package/plugins/meta-architect/skills/maestro/references/native-ingest-map.md

@@ -0,0 +1,44 @@
+# Native Ingest Map
+
+Meta-Architect absorbs new pattern families as native product guidance without turning them into new umbrella brands or new release gates.
+
+## Publishable helper skills
+
+- `align`
+  - purpose: scope alignment, shared language, and docs clarity
+  - gate effect: none
+- `diagnose`
+  - purpose: failure decomposition, blocked-lane triage, and root-cause framing
+  - gate effect: none
+- `tdd`
+  - purpose: regression-first and test-first execution scaffolds
+  - gate effect: none
+- `cleanup`
+  - purpose: anti-slop cleanup, prose humanization, and final-pass polish
+  - gate effect: none
+
+## Existing-lane absorption
+
+- `$sage`
+  - owns source selection, upstream validation order, and evidence quality
+  - uses curated native reference packs instead of raw catalog browsing as the product surface
+- `$vet`
+  - owns security/trust-boundary review and security playbook application
+  - absorbs security playbook patterns without creating a second security umbrella
+- `$maestro`
+  - remains the only umbrella surface and bounded autonomous manager
+  - owns next-step recommendation, helper handoff decisions, and fixed-sequence management
+  - does not create new gate states and does not replace the outputs owned by gated lanes
+
+## Fixed gated sequence
+
+The release-owned sequence does not change in this ingest:
+
+1. `$arch`
+2. `$sage`
+3. `$flow`
+4. `$vet`
+5. `$vibe`
+6. `$build`
+
+Helper skills remain publishable but non-gating. They can prepare, unblock, or clean up work around those lanes, but they do not create new gate states and they do not own release-state transitions.

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

@@ -5,7 +5,7 @@ description: "Use when the user wants evidence-backed technology choices, OSS ev
 
 # Sage
 
-Use this skill inside Codex to verify or challenge stack choices with real sources.
+Use this skill inside Codex to verify or challenge stack choices with real sources. `$sage` remains the evidence gate even as Meta-Architect absorbs more native curation and reference packs.
 
 ## Output
 
@@ -24,6 +24,7 @@ Produce:
   - use discovery accelerators to find or narrow candidates
   - map the selected candidate back to an exact upstream repo
   - verify against upstream repos and official docs before approving it
+- Use `references/source-selection.md` when you need the native source-selection contract, evidence ladder, or packaged discovery rules.
 - Use approved discovery accelerators when you need faster OSS candidate discovery:
   - Ossium (`https://ossium.live/home`) for trending, curated, YC-backed, and GSoC-linked OSS discovery
   - Trendshift (`https://trendshift.io/`) for rising GitHub engagement and topic momentum
@@ -31,6 +32,7 @@ Produce:
   - Libraries.io (`https://libraries.io/`) for package/dependency metadata, with caution because its public data is scraped and not validated/curated for accuracy
   - Open Hub (`https://openhub.net/`) for project activity, contributor, and comparison signals
   - Open-source Projects (`https://www.opensourceprojects.dev/`) for curated OSS discovery and detailed project writeups
+- Discovery accelerators are candidate-finding tools, not approval surfaces. The user-facing Meta-Architect product stays native even when evidence sources are external.
 - Do not invent package capabilities or maturity claims.
 - Prefer primary sources over summaries when validating technical details.
 - Do not treat discovery listings alone as VERIFIED evidence; promote candidates to upstream repos and official docs before approving them.

package/plugins/meta-architect/skills/sage/references/source-selection.md

@@ -0,0 +1,28 @@
+# Source Selection
+
+Use this reference pack inside `$sage` when the repo needs evidence-backed selection without turning raw catalogs into the product surface.
+
+## Evidence order
+
+1. Known upstream repo and official docs
+2. Discovery accelerator to find or narrow candidates
+3. Exact upstream repo mapping for the shortlisted candidate
+4. Upstream repo plus official-doc verification before approval
+
+## Discovery accelerator rules
+
+- Use accelerators to reduce search time, not to replace validation.
+- Treat listings, rankings, and trend signals as hints.
+- Promote any serious candidate to an exact upstream repo before calling it VERIFIED.
+- Keep user-facing guidance in Meta-Architect language rather than echoing catalog branding as if it were a first-class product surface.
+
+## Minimum approval bar
+
+- Exact upstream repo identified
+- Official docs available when relevant
+- Claimed capability verified from a primary source
+- Maturity caveats called out when evidence is weak
+
+## Native posture
+
+Meta-Architect ships curated guidance and playbooks. It does not ship a raw mirror of external catalogs. External sources remain evidence inputs, not user-facing skill identities.

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

@@ -0,0 +1,24 @@
+---
+name: tdd
+description: "Use when the user wants regression-first or test-first scaffolding before implementation work expands."
+---
+
+# TDD
+
+Use this skill inside Codex when implementation should start by locking behavior with tests. `tdd` is a non-gating helper skill that supports execution once the relevant lane is ready.
+
+## Output
+
+Produce:
+- behavior to lock
+- minimal regression or failing test shape
+- implementation boundary
+- proof that the test belongs to the requested change
+- exact next trigger, usually the implementation lane or `$cleanup`
+
+## Rules
+
+- Prefer the smallest failing test that proves the requested behavior.
+- Lock current behavior before cleanup or refactor work when behavior is not already protected.
+- Do not treat `tdd` as a replacement for the build gate.
+- Keep test intent explicit so the next implementation step stays narrow.

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

@@ -0,0 +1,4 @@
+interface:
+  display_name: "$tdd"
+  short_description: "Regression-first and test-first helper"
+  default_prompt: "Use $tdd to define the smallest test that locks the requested behavior before implementation expands."