@deeeed/metamask-harness 0.92.37 → 0.92.39

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 ## Unreleased
 
+## 0.92.39 - 2026-10-20
+
+### Added
+
+- `mm-harness recipe-validate <recipe.json> [--artifact-manifest <file>] [--artifact-dir <dir>] [--action-manifest <file>] [--json]` validates a recipe and its retained Recipe v1 run package with the shared validator, the same checks publication runs. It exits 1 when the result is invalid. Skills that package PR evidence can validate a run through the task's own harness.
+
+## 0.92.38 - 2026-10-20
+
+### Changed
+
+- Pin `@farmslot/handoff` 0.4.1. The learning package that `mm-harness checklist mark` closeout stages is refused as a recovery phrase only when it holds a BIP-39 phrase whose checksum is valid. Before, any run of 12 wordlist words blocked it, including recipe intent prose, JSON keys and node ids. A real phrase still blocks, in JSON, Markdown, YAML, CSV or logs, apart from the misses handoff's README lists (for example, a phrase split across separate multi-word JSON values).
+
 ## 0.92.37 - 2026-10-20
 
 ### Changed

package/dist/command-contract.js

@@ -1003,6 +1003,36 @@ Example:
       positionals: [{ label: "action", choices: ["build", "plan", "advise", "advisor-status"] }]
     }
   },
+  {
+    name: "recipe-validate",
+    summary: "Validate a recipe and its retained Recipe v1 artifact package.",
+    example: "mm-harness recipe-validate artifacts/recipe-run/recipe.json --artifact-dir artifacts/recipe-run --json",
+    helpText: `mm-harness recipe-validate <recipe.json> [flags]
+
+  Validates the recipe graph and, with --artifact-dir, the run package beside it:
+  required files, manifest paths and digests, recorded parameters and resolved
+  dependencies. The checks are the shared Recipe v1 validator's. Exits 1 when the
+  result is invalid.
+
+  --artifact-manifest <file>  artifact-manifest.json to validate
+  --artifact-dir <dir>        Artifact package directory (required files, manifest paths)
+  --action-manifest <file>    Runner action manifest for action checks
+  --json                      Machine-readable result: { status, findings, summary }
+
+Example:
+  mm-harness recipe-validate artifacts/recipe-run/recipe.json \\
+    --artifact-manifest artifacts/recipe-run/artifact-manifest.json \\
+    --artifact-dir artifacts/recipe-run --json`,
+    contract: {
+      options: options(HELP, JSON, {
+        "--artifact-manifest": value(),
+        "--artifact-dir": value(),
+        "--action-manifest": value()
+      }),
+      positionals: [{ label: "recipe" }],
+      minimumPositionals: 1
+    }
+  },
   {
     name: "provision",
     summary: "Install the cached Runway iOS dev client on a prepared mobile slot (no deps, no Metro).",

package/dist/commands/recipe-validate.js

@@ -0,0 +1,30 @@
+import { optionFlag, optionString, parseArgs, usageError } from "@farmslot/recipe-cli/harness";
+import { validateRecipeCliInput } from "@farmslot/recipe-runner/cli/support";
+const USAGE = "Usage: mm-harness recipe-validate <recipe.json> [--artifact-manifest <file>] [--artifact-dir <dir>] [--action-manifest <file>] [--json]";
+async function handleRecipeValidate(argv) {
+  const parsed = parseArgs(argv);
+  const [recipePath, ...extra] = parsed.positional;
+  if (!recipePath || extra.length > 0) throw usageError(USAGE);
+  const result = await validateRecipeCliInput({
+    recipePath,
+    actionManifestPath: optionString(parsed.options, "actionManifest"),
+    artifactManifestPath: optionString(parsed.options, "artifactManifest"),
+    artifactDir: optionString(parsed.options, "artifactDir")
+  });
+  if (optionFlag(parsed.options, "json")) {
+    process.stdout.write(`${JSON.stringify(result, null, 2)}
+`);
+  } else {
+    const { errors, warnings } = result.summary;
+    process.stdout.write(`recipe validation: ${result.status} (${errors} errors, ${warnings} warnings)
+`);
+    for (const finding of result.findings) {
+      process.stdout.write(`- ${finding.severity} ${finding.code} ${finding.path}: ${finding.message}
+`);
+    }
+  }
+  return result.status === "invalid" ? 1 : 0;
+}
+export {
+  handleRecipeValidate
+};

package/dist/mm-harness-cli.js

@@ -58,6 +58,7 @@ import { handleHelp } from "./commands/help.js";
 import { overlayCommandOptions } from "./commands/overlay.js";
 import { handlePin } from "./commands/pin.js";
 import { handlePrBody } from "./commands/pr-body.js";
+import { handleRecipeValidate } from "./commands/recipe-validate.js";
 import { handleProvision } from "./commands/provision.js";
 import { handleResolveExtension } from "./commands/resolve-extension.js";
 import { handleRuntimeDecision } from "./commands/runtime-decision.js";
@@ -183,6 +184,7 @@ const PUBLIC_RUN = {
   },
   check: { run: handleCheck },
   "recipe-quality": { run: (args) => handleRecipeQuality(args, cliRecipeQualityOptions) },
+  "recipe-validate": { run: handleRecipeValidate },
   provision: { run: (args) => handleProvision(parseArgs(args)) },
   install: { run: overlay("install") },
   verify: { run: overlay("verify") },
@@ -228,7 +230,7 @@ const HELP_GROUPS = [
   {
     title: "PROVE",
     blurb: "run recipes and inspect readiness",
-    commands: ["run", "last", "doctor", "check", "checklist", "review", "pr-body", "recipe-quality"]
+    commands: ["run", "last", "doctor", "check", "checklist", "review", "pr-body", "recipe-quality", "recipe-validate"]
   },
   {
     title: "RUNTIME OVERLAY",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.92.37",
+  "version": "0.92.39",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"
@@ -26,7 +26,7 @@
     "@farmslot/adapter-sdk": "0.25.0",
     "@farmslot/adapter-web": "0.17.0",
     "@farmslot/agent-runtime": "0.36.0",
-    "@farmslot/handoff": "0.3.2",
+    "@farmslot/handoff": "0.4.1",
     "@farmslot/protocol": "0.60.0",
     "@farmslot/recipe-cli": "0.30.0",
     "@farmslot/recipe-runner": "0.46.0",