@deeeed/metamask-harness 0.50.6 → 0.51.0

package/dist/mm-harness-cli.js

@@ -123,7 +123,9 @@ Example:
   mark delegates checklist state to @farmslot/agent-runtime. Successful complete
   and no-change marks stage a learning package through @farmslot/handoff.
   closeout exposes that same Handoff boundary directly; --share remains explicit.
-  The task directory must contain CHECKLIST.md and checklist-target.json.
+  The task directory is the one mm-harness task init wrote. Without a
+  checklist-target.json it marks CHECKLIST.md and writes SIGNAL.json; only a
+  role switch writes that manifest, to point at its own checklist.
 
   Steps: start | 1 | 2 | ... | complete | no-change | blocked
 
@@ -133,6 +135,84 @@ Example:
   mm-harness checklist mark temp/tasks/recipe-cook/<task> complete --mark-last
   mm-harness checklist closeout temp/tasks/recipe-cook/<task> --share`
   },
+  {
+    name: "prepare",
+    summary: "Bring this checkout to a proven-ready state and write the readiness record.",
+    example: "mm-harness prepare --platform extension",
+    helpText: `mm-harness prepare [flags]
+
+  Run the readiness chain for this checkout and record what it did as one
+  protocol readiness record (sandbox.json). Steps run in order and stop at the
+  first failure; later steps are recorded as skipped.
+
+    doctor --fix   status   launch --verify   fixtures set   verify
+
+  Core skips launch and fixtures (headless; verify is its readiness gate).
+  Mobile infers ios|android from the connected devices reported by status and
+  refuses with the numbered choice when that is ambiguous.
+
+  --target <path>                    Checkout path (default: cwd)
+  --platform <mobile|extension|core> Force the platform (auto-detected inside a checkout)
+  --mobile-platform <ios|android>    Mobile target when status cannot decide it
+  --artifacts-dir <dir>              Where sandbox.json and the per-step reports land
+                                     (default: <target>/temp/recipe/runtime)
+  --json                             Print the readiness record
+
+  Exit 0 when the record is ready, 1 otherwise.
+
+Example:
+  mm-harness prepare
+  mm-harness prepare --platform mobile --mobile-platform ios --json
+  mm-harness prepare --artifacts-dir temp/tasks/fix/TAT-1/artifacts --json`
+  },
+  {
+    name: "task",
+    summary: "Create the task directory an agent works from, out of a shared execution template.",
+    example: 'mm-harness task init temp/tasks/fix/TAT-1 --flow fix-bug --run-mode autonomous --template fix-bug/autonomous.mobile --title "Wrong total"',
+    helpText: `mm-harness task init <task-dir> [options]
+
+  Write the task directory from a selected execution template: TASK.md, the
+  CHECKLIST.md whose boxes are the steps, a mark shim routed through
+  mm-harness checklist mark, and inputs/ (handoff.json, worker-terminal-contract.json).
+  checklist-target.json is NOT written \u2014 absent means CHECKLIST.md + SIGNAL.json.
+
+  Applied when you do not pass them: --surface skill, --mark-command for this
+  executable, and --platform from the detected checkout.
+
+Task:
+  --title <t>                        Task title (required)
+  --task-text <s> | --task-file <p>  Task description, inline or from a file
+  --ticket <key>                     Ticket key
+  --source-ref <url>                 Where the task came from
+
+Selection (same catalog as execution-template):
+  --flow <flow>                      Exact flow (required)
+  --run-mode <mode>                  autonomous|interactive|validation (required)
+  --platform <platform>              Exact platform
+  --template <id>                    Exact template id (required)
+  --domain <domain>                  Exact domain
+  --dir <path>                       Custom flow-tree source (repeatable)
+  --domain-dir <domain=path>         Domain-scoped team source (repeatable)
+  --package-templates <path>         Canonical package flow-tree root
+  --package-id <id>                  Source label for the package root
+  --project-worker <path>            Project template directory
+  --project-name <name>              Source label for project templates
+
+Identity and rendering:
+  --surface <s>                      Handoff surface (default: skill)
+  --project <name>  --repo <owner/name>  --attempt-id <id>
+  --var KEY=VALUE                    Template placeholder value (repeatable)
+  --task-dir-label <label>           Task directory as written into the documents
+  --mode-preamble <text>             Run-mode preamble for TASK.md
+  --addendum-file <path>             Extra task-document section
+  --mark-command <cmd>               Override the recorded mark command
+  --json                             Machine-readable output
+
+Example:
+  mm-harness task init temp/tasks/fix/TAT-1 --flow fix-bug --run-mode autonomous \\
+    --template fix-bug/autonomous.mobile --package-templates <path> \\
+    --title "Wrong total on the receipt" --ticket TAT-1 --json`
+  },
   {
     name: "execution-template",
     summary: "Discover, validate, and materialize shared agent checklists.",
@@ -698,7 +778,7 @@ const HELP_GROUPS = [
   {
     title: "DAILY LOOP",
     blurb: "what a teammate runs many times a day (auto-ensures the overlay; --heal owns recovery)",
-    commands: ["status", "launch", "stop", "logs", "debug", "reload", "fixtures"]
+    commands: ["status", "task", "prepare", "launch", "stop", "logs", "debug", "reload", "fixtures"]
   },
   {
     title: "DISCOVER",

package/dist/paths.js

@@ -11,6 +11,9 @@ function recipeRuntimeDir() {
 function recipeHarnessRoot() {
   return validateRelativeRecipePath("RECIPE_HARNESS_ROOT", process.env.RECIPE_HARNESS_ROOT || DEFAULT_RECIPE_HARNESS_ROOT);
 }
+function harnessExecutable() {
+  return path.resolve(process.env.MM_HARNESS_EXECUTABLE ?? path.join(runnerDir, "bin/mm-harness"));
+}
 function readPathDefaults() {
   const defaultsPath = path.join(runnerDir, "adapters/shared/path-defaults.json");
   const parsed = JSON.parse(fs.readFileSync(defaultsPath, "utf8"));
@@ -170,6 +173,7 @@ export {
   DEFAULT_RECIPE_RUNTIME_DIR,
   assertAdapter,
   extensionIdPath,
+  harnessExecutable,
   importMetaMaskNativeUiProvider,
   importRecipeHarness,
   importRecipeHarnessAppLifecycle,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.50.6",
+  "version": "0.51.0",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"
@@ -20,11 +20,11 @@
     "check:syntax": "find . -name '*.mjs' -print0 | xargs -0 -n1 node --check"
   },
   "dependencies": {
-    "@farmslot/agent-runtime": "0.8.1",
-    "@farmslot/expo-recipe": "0.9.0",
+    "@farmslot/agent-runtime": "0.9.0",
+    "@farmslot/expo-recipe": "0.9.1",
     "@farmslot/handoff": "^0.3.1",
-    "@farmslot/protocol": "0.21.0",
-    "@farmslot/recipe-harness": "0.16.1",
+    "@farmslot/protocol": "0.26.0",
+    "@farmslot/recipe-harness": "0.16.2",
     "agent-device": "0.19.3",
     "commander": "^12.0.0",
     "es-module-lexer": "2.3.1",