@squadrules/mcp 5.13.8 → 5.14.1

package/dist/embed-docs/mem/adapter-migration.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: adapter-migration
 title: Adapter Migration Workflow
 ---

package/dist/embed-docs/mem/author-adapter.md

@@ -1,6 +1,6 @@
 ---
 slug: author-adapter
-version: "5.13.8"
+version: "5.14.1"
 title: Author Adapter (Create / Review / Refactor)
 ---
 
@@ -167,9 +167,22 @@ The server never names a path on your machine; you do.
   the title.
 - Keep the contract one line: `interpreter: "bash"`, `cmd: python3
   "$SQUADRULES_LOCAL_ARTIFACT_DIR/artifacts/<name>.py" --gate <name>`.
-- Verify before shipping: `activate` the adapter and confirm
-  `linked_artifacts[].relative_path` is exactly the path `cmd` invokes. Run each
-  row's `materialize` command before the contract that needs it.
+- Verify before shipping — **two** checks, both required:
+  1. `activate` the adapter and confirm `linked_artifacts[].relative_path` is
+     exactly the path `cmd` invokes. Follow each row's `materialize` instruction before
+     the contract that needs it.
+  2. **Export check:** call MCP **`export`** with
+     `uri: "squadrules://adapter/<slug>"` and `format: skill_tree` (or
+     `skill_zip` for the bundle) and confirm the script is present under
+     `artifacts/` at the path the contract invokes. Read the returned
+     `diagnostics[]`: `artifact_stored_sha_mismatch` or
+     `artifact_relative_path_invalid` means the stored artifact is broken —
+     re-train it instead of shipping it.
+- A `cmd` that names a script the export does not contain is a broken adapter:
+  it fails at run time with a missing-file error and burns the user's step.
+  Fix it before shipping. The only exception is a repository-owned gate that
+  the adapter names explicitly and that lives in the user's repository — say so
+  in the adapter text, and state how the agent finds it.
 
 ### Drafting rules (all operations)
 
@@ -191,6 +204,14 @@ Dependencies, middle H2s one per stage with JSON contract block, last H2 Reward
 Signal. Frontmatter: `slug` (required), `version` (optional), `chain_root`
 (required for mid-chain adapters).
 
+**Scripts are obtained, not assumed:** when a step's `cmd` invokes a script, the
+adapter must state in its own text how the agent obtains that file before
+running the command — follow the `activate` artifact row's `materialize`
+instruction, or `export` the adapter. A step that says only "run `python3
+…/artifacts/x.py`" leaves the agent guessing where the file is; a
+missing-file gate failure is the most common
+result of that omission.
+
 **Contracts:** One per adapter is the default; a second is justified only at a
 boundary that is hard to roll back. Load `challenge-type-guide` for decision
 rules and JSON formats (`forward` with

package/dist/embed-docs/mem/bulk-insert-adapters-via-cli.md

@@ -1,6 +1,6 @@
 ---
 slug: bulk-insert-adapters-via-cli
-version: "5.13.8"
+version: "5.14.1"
 title: Bulk Insert Adapters via SQUADRULES CLI
 ---
 

package/dist/embed-docs/mem/challenge-type-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: challenge-type-guide
 title: Challenge Type Selection Guide
 ---
@@ -268,15 +268,26 @@ exists:
    `adapter_uri`. Add `relative_path` only when the default
    `artifacts/<artifact_name>` is not the path you want; the identity header and
    slug rules are in the `train` description.
-4. Verify before you run it: `activate` the adapter and check that
-   `linked_artifacts[].relative_path` equals the path the contract invokes. A
-   mismatch surfaces only when the gate runs.
-
-**At execution time:** run the `materialize` command carried by that
-`linked_artifacts[]` row — it writes the payload under
-`$SQUADRULES_LOCAL_ARTIFACT_DIR`, verifies the digest, and marks the file
-executable. `forward` responses do not repeat the list, so materialize during the
-run's first step.
+4. Verify before you run it — **two** checks:
+   - `activate` the adapter and check that `linked_artifacts[].relative_path`
+     equals the path the contract invokes.
+   - **Export check:** `export` the adapter (`format: skill_tree`, or
+     `skill_zip` for the bundle) and confirm the script is in the bundle at
+     that path, with no `artifact_stored_sha_mismatch` or
+     `artifact_relative_path_invalid` in `diagnostics[]`.
+
+   A mismatch surfaces only when the gate runs — by then it is the user's
+   failed step, not your typo.
+
+**At execution time:** follow the `materialize` instruction carried by that
+`linked_artifacts[]` row — call the MCP `export` tool with the specified
+arguments, write the returned content to the `out` path under
+`$SQUADRULES_LOCAL_ARTIFACT_DIR`, verify the digest, and set permissions.
+`forward` responses do not repeat the list, so materialize during the
+run's first step. When the choice carries no artifact row, the agent obtains the
+script with **`export`** (`format: skill_tree` or `format: skill_zip`) and takes
+it from `artifacts/`. State which route applies in the adapter text — a step that
+does not say how to get the file leaves the agent guessing.
 
 **One script, many gates:** `--gate <name>` on a single dispatcher replaces one
 inlined program per step. Change the gate once, not seven times.

package/dist/embed-docs/mem/critic-loop-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: critic-loop-guide
 title: Critic Loop Integration and Mutation Gate Guide
 ---

package/dist/embed-docs/mem/critic-loop.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: critic-loop
 title: Critic Loop
 ---

package/dist/embed-docs/mem/protocol-linking-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: protocol-linking-guide
 title: Adapter Linking Guide
 ---

package/dist/embed-docs/mem/refine-search.md

@@ -1,5 +1,5 @@
 ---
-version: "5.13.8"
+version: "5.14.1"
 slug: refine-search
 title: Get help refining your search
 ---