@squadrules/mcp 5.14.7 → 5.15.1

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

@@ -1,5 +1,5 @@
 ---
-version: "5.14.7"
+version: "5.15.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.14.7"
+version: "5.15.1"
 title: Author Adapter (Create / Review / Refactor)
 ---
 
@@ -169,7 +169,7 @@ The server never names a path on your machine; you do.
   "$SQUADRULES_LOCAL_ARTIFACT_DIR/artifacts/<name>.py" --gate <name>`.
 - 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
+     exactly the path `cmd` invokes. Run each row's `materialize.cmd` before
      the contract that needs it.
   2. **Export check:** call MCP **`export`** with
      `uri: "squadrules://adapter/<slug>"` and `format: skill_tree` (or
@@ -206,8 +206,8 @@ Signal. Frontmatter: `slug` (required), `version` (optional), `chain_root`
 
 **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
+running the command — run the `activate` artifact row's `materialize.cmd`,
+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.

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

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

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

@@ -1,5 +1,5 @@
 ---
-version: "5.14.7"
+version: "5.15.1"
 slug: challenge-type-guide
 title: Challenge Type Selection Guide
 ---
@@ -279,10 +279,13 @@ exists:
    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.
+**At execution time:** run the `materialize.cmd` carried by that
+`linked_artifacts[]` row verbatim — it creates the parent directory, writes the
+file under `$SQUADRULES_LOCAL_ARTIFACT_DIR`, verifies the digest, and sets
+permissions. On the stdio transport, call the MCP `export` tool with the row's
+`arguments` first and set `B64` to the returned `content`; on HTTP, `cmd`
+downloads the artifact itself. Do not retype artifact bytes through an editor or
+a heredoc — an exact-byte write is not an agent task.
 `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

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

@@ -1,5 +1,5 @@
 ---
-version: "5.14.7"
+version: "5.15.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.14.7"
+version: "5.15.1"
 slug: critic-loop
 title: Critic Loop
 ---

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

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

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

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