@jstn-sdk/ma 0.1.5 → 0.1.7

package/.agents/plugins/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "meta-architect-local",
+  "interface": {
+    "displayName": "Meta-Architect Local Plugins"
+  },
+  "plugins": [
+    {
+      "name": "meta-architect",
+      "source": {
+        "source": "local",
+        "path": "./plugins/meta-architect"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Developer Tools"
+    }
+  ]
+}

package/.codex/hooks.json

@@ -4,7 +4,7 @@
     {
       "event": "prebuild",
       "action": "deny-unless-gates-green",
-      "source": ".omx/decisions.json"
+      "source": ".ma/decisions.json"
     },
     {
       "event": "prerelease",

package/.codex/prompts/enforcement.md

@@ -19,7 +19,7 @@ Your purpose is to turn project ideas into evidence-backed architecture, validat
 Treat Meta-Architect as two layers:
 
 - **Kernel**
-  - CLI runtime
+  - helper runtime
   - gate enforcement
   - decision and release state
   - MCP evidence binding
@@ -42,18 +42,28 @@ The kernel may be minimal, but it must be strict. Extensions may vary, but they
 6. Do not allow direct release from a task branch or linked worktree.
 7. All completed task branches must merge into `development` before release promotion.
 8. Only release from `development` or an approved `release/*` branch to `prod`.
-9. Every write-capable implemented entrypoint must append a decision record to `.omx/decisions.json`.
+9. Every write-capable implemented entrypoint must append a decision record to `.ma/decisions.json`.
 10. Every security finding with unresolved High or Critical severity must force `security_status = RED`.
 11. Every unresolved critical business-logic blocker must force `logic_status = RED`.
 12. No silent status upgrades are allowed.
 13. No hallucinated packages, repositories, or MCP endpoints are allowed.
-14. Runtime `.omx` residue such as logs/state/tmp/cache must not be treated as public source.
+14. Runtime `.ma` residue such as logs/state/tmp/cache must not be treated as public source.
 15. When a gate is blocked, explain the blocker and list the next allowed triggers.
 
 ## Evidence rule
 
 `https://gitmcp.io/docs` is fallback policy only. It is not a normal approved evidence source for unlocking `$build`.
 
+Approved discovery accelerators include `https://ossium.live/home`, `https://trendshift.io/`, `https://devhunt.org/`, `https://libraries.io/`, `https://openhub.net/`, and `https://www.opensourceprojects.dev/`.
+
+These discovery accelerators help find OSS candidates faster, but they are not by themselves VERIFIED evidence sources for unlocking `$build`.
+
+Canonical evidence order:
+1. If the upstream repo or official docs are already known, start there.
+2. Otherwise use approved discovery accelerators to generate or narrow candidates.
+3. Map the chosen candidate to an exact upstream repository.
+4. Verify against upstream repos and official docs before upgrading evidence status.
+
 ## Release truth rule
 
 Do not claim a channel is published unless the corresponding push, release creation, asset upload, or package publish actually succeeded.

package/.codex/prompts/onboarding.md

@@ -1,26 +1,41 @@
 # Onboarding
 
-Meta-Architect is a Codex-native runtime layer.
+Meta-Architect is a skills-first system for Codex with a strict kernel.
 
-## Canonical start
+## What is implemented
 
-1. Install `@openai/codex` and `meta-architect`
-2. Launch `ma --madmax --high`
-3. Operate through `$arch`, `$sage`, `$flow`, `$vet`, `$vibe`, `$build`
+The primary product surface is the in-session skill flow:
+- `$arch`
+- `$sage`
+- `$flow`
+- `$vet`
+- `$vibe`
+- `$build`
 
-## Secondary helpers
-
-Use only when needed:
-- `ma status`
+Secondary helper commands remain available through:
+- `ma init`
 - `ma idea`
-- `ma run ...`
+- `ma skills`
+- `ma status`
+- `ma run '$arch'`
+- `ma run '$sage'`
+- `ma run '$flow'`
+- `ma run '$vet'`
+- `ma run '$vibe'`
+- `ma run '$build'`
 - `ma merge`
 - `ma release`
-- `ma doctor`
-- `ma setup`
+
+## What to learn first
+
+1. Read `README.md`
+2. Read `docs/getting-started.md`
+3. Read `docs/release-spec.md`
+4. Read `docs/skills.md`
+5. Start Codex context if needed, then use `$arch` before assuming the workflow is ready
 
 ## What not to do
 
-- Do not edit `.omx/release.json` or `.omx/decisions.json` manually to bypass the gate model.
-- Do not treat `.omx/logs/`, `.omx/state/`, or `.omx/metrics.json` as source.
+- Do not edit `.ma/release.json` or `.ma/decisions.json` manually to bypass the gate model.
+- Do not treat `.ma` support files as public source.
 - Do not claim release channels succeeded without proof.