@deeeed/metamask-harness 0.92.19 → 0.92.20

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 ## Unreleased
 
+## 0.92.20 - 2026-10-17
+
+### Removed
+
+- Retire the unused `runtime-health` hidden command and the `health` and `home` aliases of `status`. Extension health checks keep running inside `ensure-ready`, `runtime-decision` and launch verification.
+
+### Changed
+
+- Document that hosted tasks resolve the Recipe Cook and Perps checklist roots from each node's pool `env`.
+
 ## 0.92.19 - 2026-10-17
 
 ### Fixed

package/README.md

@@ -473,6 +473,8 @@ Farmslot selects that same package through `recipe.provider.root.env`, configure
 
 Explicitly invoke `mms-recipe-dev`, `mms-recipe-fix-bug`, `mms-recipe-qa` or the team's static review skill. `mms-recipe-cook` selects or resumes their shared Markdown checklist. Matching descriptions or changed paths never activates these workflows.
 
+Hosted tasks select that checklist on the execution node, not the gateway. The Core, Mobile and Extension packs root their Recipe Cook checklists at `CONSENSYS_RECIPE_COOK_ROOT` and their Perps checklists at `PERPS_RECIPE_LIBRARY_ROOT`. Set them in every node's pool `env`, not only the gateway's. A node missing the root for the selected checklist refuses the task as source unavailable.
+
 Static Perps review uses a generated source checklist without installing or launching the app harness. `recipe-qa` freezes a PR, range or daily change window and requires runtime smoke plus selected recipe proof. Official release validation uses its named release profile and proof lane.
 
 TASK.md holds the request; CHECKLIST.md is the sole step list. The frozen terminal contract and task-local mark validate completion. Publication, retained sessions and workspace cleanup belong to the caller. Farmslot handles them through its control plane; direct invocation returns the outcome to the engineer. See the [task-directory guide](site/task-dir.html) and [QA tutorial](site/tutorials/v5.html).

package/dist/cli-commands.js

@@ -14,7 +14,7 @@ const SPEC = {
     { name: "config", desc: "Per-engineer locations and optional advisor settings", args: ["list", "path", "get", "set", "unset"], flags: ["--json"] },
     { name: "tutorial", desc: "Open the visual recipe tutorial", flags: ["--json", "--no-open"] },
     { name: "setup-base", desc: "Bootstrap numbered product checkouts", flags: ["--dir", "--counts", "--only", "--dry-run", "--force", "--json", "--show-config", "--reset-config", "--skip-harness-update"] },
-    { name: "status", aliases: ["health", "home"], desc: "Home status + next commands", flags: ["--json", "--fast", "--watch", "--task"] },
+    { name: "status", desc: "Home status + next commands", flags: ["--json", "--fast", "--watch", "--task"] },
     { name: "ports", desc: "Slot ports and runtime paths", flags: ["--json"] },
     { name: "up", desc: "Decide + run minimum work to reach ready", flags: ["--json", "--dry-run"] },
     { name: "sync", desc: "Refresh harness + canonicalize wallet fixture", flags: ["--json"] },

package/dist/command-contract.js

@@ -258,13 +258,12 @@ Example:
   },
   {
     name: "status",
-    aliases: ["health", "home"],
     summary: "Home dashboard for a checkout: detected adapter, next command, and (mobile) connected devices with the selected target.",
     example: "mm-harness status",
     helpText: `mm-harness status [flags]
 
   Home dashboard for the current checkout \u2014 the detected adapter, the next command
-  to run, and (mobile only) the connected devices with live app state. Aliases: health, home.
+  to run, and (mobile only) the connected devices with live app state.
 
   --adapter <{adapters}>  Target adapter (auto-detected inside a checkout)
   --target <path>                    Checkout path (default: cwd)
@@ -1409,7 +1408,6 @@ Example:
 ];
 const HIDDEN_COMMANDS = [
   "completion-candidates",
-  "runtime-health",
   "runtime-decision",
   "resolve-extension",
   "ensure-ready",

package/dist/mm-harness-cli.js

@@ -54,7 +54,6 @@ import { handleRecipeQuality } from "./commands/recipe-quality.js";
 import { handleResolveExtension } from "./commands/resolve-extension.js";
 import { handleReview } from "./commands/review.js";
 import { handleRuntimeDecision } from "./commands/runtime-decision.js";
-import { handleRuntimeHealth } from "./commands/runtime-health.js";
 import { handleRuntimeLaunch } from "./commands/runtime-launch.js";
 import { handleSelfTest } from "./commands/self-test.js";
 import { handleSetupBase } from "./commands/setup-base.js";
@@ -173,7 +172,6 @@ const PUBLIC_RUN = {
 const HIDDEN_RUN = {
   // Shell completion answers for the checkout's adapter, so it resolves one.
   "completion-candidates": { run: handleCompletionCandidates, nudge: false, context: "adapter" },
-  "runtime-health": { run: (args) => handleRuntimeHealth(parseArgs(args)) },
   "runtime-decision": { run: (args) => handleRuntimeDecision(parseArgs(args, { recordIsFlag: true })) },
   "resolve-extension": { run: (args) => handleResolveExtension(parseArgs(args)) },
   "ensure-ready": { run: (args) => handleEnsureReady(parseArgs(args)) },

package/docs/CONTRIBUTING.md

@@ -92,7 +92,7 @@ command-local platform ladders for surface-owned behavior:
   `prepare`, `debug`, `reload` and `runtime-decision` read their own members.
 
 A few comparisons remain where a command exists for one platform
-(`runtime-health`, `resolve-extension`, `ensure-ready`, `runtime-launch`) or
+(`resolve-extension`, `ensure-ready`, `runtime-launch`) or
 code compares a platform's own data (`review/knowledge.ts`, the Core jest
 grouping in `check.ts`, the Mobile release-artifact state file).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.92.19",
+  "version": "0.92.20",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"

package/dist/commands/runtime-health.js

@@ -1,19 +0,0 @@
-import { adapterOption, optionFlag, optionString, parsePort, targetPath } from "@farmslot/recipe-cli/harness";
-async function handleRuntimeHealth({ options }) {
-  const adapter = adapterOption(options);
-  if (adapter !== "extension") throw new Error("runtime-health currently applies to the extension adapter.");
-  const target = targetPath(options);
-  const cdpPort = parsePort(
-    optionString(options, "cdpPort") ?? process.env.CDP_PORT ?? process.env.RECIPE_CDP_PORT,
-    "runtime-health requires --cdp-port <port>."
-  );
-  const { checkExtensionRuntimeHealth, formatHealthFailure } = await import("../adapters/extension/runtime.js");
-  const report = await checkExtensionRuntimeHealth(target, cdpPort);
-  if (optionFlag(options, "json")) console.log(JSON.stringify(report, null, 2));
-  else if (report.status === "PASS") console.log(`PASS extension runtime cdp=${cdpPort} target=${report.targetUrl}`);
-  else console.error(formatHealthFailure(report, target));
-  return report.status === "PASS" ? 0 : 1;
-}
-export {
-  handleRuntimeHealth
-};