npm - @deeeed/metamask-harness - Versions diffs - 0.47.0 → 0.47.2 - Mend

@deeeed/metamask-harness 0.47.0 → 0.47.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (33) hide show

package/CHANGELOG.md +21 -0
package/adapters/mobile/bridge-runtime/lib/bridge-errors.cjs +15 -0
package/dist/commands/tutorial.js +4 -4
package/dist/mm-harness-cli.js +3 -3
package/library/actions/mobile/perps/perps.mjs +41 -12
package/library/actions/mobile/perps/set_market_favorite.mjs +0 -11
package/library/actions/mobile/platform/bridge.mjs +6 -1
package/library/actions/mobile/ui/native-navigation.mjs +9 -2
package/library/actions/mobile/ui/navigate.mjs +13 -4
package/library/manifests/mobile.action-manifest.json +1 -2
package/package.json +2 -2
package/site/assets/help-recipes.json +6 -1
package/site/architecture.html +0 -497
package/site/assets/help-recipes.mjs +0 -25
package/site/assets/metamask-fox.svg +0 -24
package/site/assets/progress.mjs +0 -325
package/site/assets/style.css +0 -1066
package/site/cheatsheet.html +0 -307
package/site/ecosystem.html +0 -162
package/site/how-it-works.html +0 -697
package/site/index.html +0 -236
package/site/perps-advanced-orders-qa.html +0 -96
package/site/perps.html +0 -265
package/site/recipes.html +0 -430
package/site/reviewers.html +0 -375
package/site/tutorials/index.html +0 -181
package/site/tutorials/v1.html +0 -216
package/site/tutorials/v2.html +0 -207
package/site/tutorials/v3.html +0 -258
package/site/tutorials/v4.html +0 -196
package/site/tutorials/v5.html +0 -164
package/site/tutorials/v6.html +0 -166
package/site/tutorials/v7.html +0 -185

package/site/how-it-works.html DELETED Viewed

@@ -1,697 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>How it works — proving a change with a recipe</title>
-<meta name="description" content="How a recipe proves a change on a real MetaMask build, checks itself before handoff, and stays behind as a regression guard. The full walkthrough, step by step.">
-<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="assets/style.css?v=4">
-</head>
-<body data-progress-page="start">
-<a class="skip" href="#steps">Skip to the walkthrough</a>
-<header class="topbar">
-  <div class="wrap topbar-inner">
-    <a class="brand" href="index.html">
-      <img class="brand-mark" src="assets/metamask-fox.svg" alt="" width="22" height="22">
-      <span class="brand-name">recipes</span>
-    </a>
-    <nav class="nav" aria-label="Main">
-      <a class="nav-cta" href="index.html#prompt">Quick start</a>
-      <a href="how-it-works.html" aria-current="page">How it works</a>
-      <a href="perps.html">Team / Perps</a>
-      <a href="cheatsheet.html">Cheatsheet</a>
-      <a href="architecture.html">Architecture</a>
-      <a href="tutorials/index.html">Tutorials</a>
-    </nav>
-  </div>
-</header>
-<div class="progress-rail">
-  <div class="wrap progress-inner">
-    <div class="progress-track" role="progressbar" aria-label="Walkthrough progress" aria-valuemin="0" aria-valuemax="100" aria-valuenow="0">
-      <div class="progress-fill"></div>
-    </div>
-    <span class="progress-label">0/8 steps</span>
-    <button type="button" class="progress-reset">Reset</button>
-  </div>
-</div>
-<main>
-<section class="wrap hero">
-  <span class="eyebrow">How it works</span>
-  <h1>How a recipe earns trust.</h1>
-  <p class="lede">
-    A recipe is a graph of typed actions run against a real MetaMask build — Extension, Mobile, or
-    Core. It runs while the change is being written, so the work is proven as it is made rather than
-    hoped about and checked at the end. <code>mm-harness</code> is the runner. Everything below, in
-    order.
-  </p>
-  <div class="hero-meta">
-    <span>requires mm-harness 0.34+</span>
-    <span>~20 minutes</span>
-    <span>progress saves in this browser</span>
-  </div>
-  <p style="margin-top:.9rem;opacity:.7;font-size:.9rem;max-width:60ch">
-    A proposal for how agents can code at MetaMask — offered for teams to try.
-  </p>
-</section>
-<section class="wrap">
-  <div class="note plain">
-    <span class="note-title">Rather hand it to your agent?</span>
-    <p style="margin-bottom:0">
-      The <a href="index.html">front page</a> carries one prompt that goes further than this page:
-      it sets up the harness and the skills, then drives a real ticket through one.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="why">Why a recipe</h2>
-  <p>
-    <strong>Proof, as the change is made.</strong> The agent drives a real build, asserts what should
-    be true, and leaves a trace: which actions ran, what they returned, how many times. On-device
-    evidence, produced while the work is happening.
-  </p>
-  <p>
-    <strong>Self-checked in the same context.</strong> Replaying a recipe needs no fresh session, no
-    human, and no wait for CI. The agent does it mid-task, in the context it made the change in — so a
-    broken step surfaces while it is still cheap to fix.
-  </p>
-  <p>
-    <strong>Prevents regressions.</strong> The recipe outlives the change it was written for. Every
-    later change has to pass it too, so the same bug cannot quietly come back: a one-time check becomes
-    a permanent guard.
-  </p>
-  <p>
-    <strong>Trust.</strong> Proven, self-checked, and still proving — so the change is trustworthy
-    while it is being built, not hoped about and verified afterwards. Everything downstream, review
-    included, inherits that.
-  </p>
-</section>
-<section class="wrap">
-  <h2 id="fit">How it fits your work</h2>
-  <p>
-    You use this through the skills. A <strong>skill</strong> is the interface — the packaged workflow
-    an agent follows to fix a bug, build a feature, or review a pull request. The skill calls
-    <code>mm-harness</code> underneath, and what the harness runs is a <strong>recipe</strong>: the
-    executable proof that drives a real build, asserts, and leaves the evidence.
-  </p>
-  <p>You do not add proof to your work. Working through a skill is what produces it.</p>
-  <p class="stack-caption">Top is how you interact; each layer calls the one below.</p>
-  <div class="stack">
-    <div class="layer layer-static">
-      <span class="layer-n">1</span>
-      <span class="layer-name">Skills</span>
-      <span class="layer-sub">how you use it — fix a bug, build a feature, review a PR</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">2</span>
-      <span class="layer-name">mm-harness</span>
-      <span class="layer-sub">what the skill calls underneath</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">3</span>
-      <span class="layer-name">Recipe</span>
-      <span class="layer-sub">what the harness runs — on-device proof, kept as a regression guard</span>
-    </div>
-  </div>
-  <p>
-    So what you are adopting is not a testing tool. It is a way of working where the proof comes out
-    of doing the work rather than out of a separate step afterwards.
-  </p>
-  <p>
-    Skills come from two sources: the public <code>MetaMask/skills</code> repo, and the internal
-    <code>Consensys/skills</code> overlay, which needs access to that org. Both are cloned locally and
-    installed per checkout with <code>yarn skills</code>. You can drive the harness directly — the
-    walkthrough below does, and uses no skill — but skills are the path day to day.
-    <a href="architecture.html#stack">The full stack is on Architecture.</a>
-  </p>
-</section>
-<section class="wrap">
-  <h2 id="model">Two words</h2>
-  <p>
-    An <strong>action</strong> is one typed operation: unlock the wallet, press a button, read the
-    account state. A <strong>recipe</strong> is a JSON graph of actions. The steps below follow
-    <strong>discover → drive → prove</strong>, which is also the order you will work in from here on.
-    <code>mm-harness</code> is the runner, and it implements a versioned recipe specification —
-    <a href="architecture.html#spec">see Architecture</a>.
-  </p>
-  <div class="doctrine">
-    <p>
-      <span class="k">You never guess capabilities — you discover them.</span>
-      <code>mm-harness actions</code> prints what this checkout can do, and that list is law. The tool
-      refuses an invented action rather than improvising one, which is why its output is worth
-      trusting.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="steps">The walkthrough, step by step</h2>
-  <p>Each piece on its own, from an empty terminal to an evidence bundle. Checkboxes persist in this browser, so you can close the tab and come back.</p>
-  <ol class="steps">
-    <li class="step" data-step="install">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-install" aria-labelledby="t-install">
-        <h3 class="step-title" id="t-install">Get the CLI</h3>
-      </div>
-      <p class="step-why">Both paths end with <code>mm-harness</code> on your PATH.</p>
-      <div class="grid grid-2" style="margin:1.2rem 0">
-        <div class="path-card">
-          <div class="path-tag">Path A — from zero</div>
-          <h4 style="margin:0 0 .5rem">No checkout yet</h4>
-          <p style="font-size:.92rem;color:var(--text-dim)">
-            Install below, then <code>mm-harness setup-base</code> clones the MetaMask product repos
-            into one standard layout and runs each repo's own dependency install. Use
-            <code>--dry-run</code> first to see the layout it would create.
-          </p>
-          <p style="margin-bottom:0"><span class="badge live">available now</span></p>
-        </div>
-        <div class="path-card">
-          <div class="path-tag">Path B — you already have a checkout</div>
-          <h4 style="margin:0 0 .5rem">Install and cd in</h4>
-          <p style="font-size:.92rem;color:var(--text-dim)">
-            Install globally, then work from inside the checkout. The product, ports, and runtime paths
-            are detected from where you are standing; there is no config file to write.
-          </p>
-          <p style="margin-bottom:0"><span class="badge live">available now</span></p>
-        </div>
-      </div>
-      <div class="cmd"><pre><code><span class="p">$ </span>npm i -g @deeeed/metamask-harness@latest
-<span class="p">$ </span>mm-harness --version</code></pre></div>
-      <div class="note plain">
-        <span class="note-title">Why @deeeed?</span>
-        <p>Arthur publishes the pre-1.0 builds from his personal npm scope while MetaMask teams validate the workflows. Version 1.0 will move to a MetaMask-owned npm package.</p>
-      </div>
-      <div class="out-label">Expected</div>
-      <div class="out">0.34.x  <span class="dim">— any 0.34 or newer</span></div>
-      <p class="step-why">Everything from here runs inside a product checkout:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>cd ~/dev/metamask/metamask-extension   <span class="dim"># or metamask-mobile, or core</span></code></pre></div>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong><code>mm-harness: command not found</code></strong> — your global npm bin is not on
-            PATH. <code>npm prefix -g</code> prints the global prefix; add its <code>bin</code>
-            directory to your shell profile.
-          </p>
-          <p>
-            <strong>Older than 0.34</strong> — a stale global install is the most common source of
-            "the docs don't match my terminal". Run <code>mm-harness update</code>, or
-            <code>update --check</code> to look without installing.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="doctor">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-doctor" aria-labelledby="t-doctor">
-        <h3 class="step-title" id="t-doctor">Run doctor — and learn to read the errors</h3>
-      </div>
-      <p class="step-why">
-        A read-only readiness check that launches nothing and names the exact command that fixes each
-        finding.
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness doctor</code></pre></div>
-      <div class="out-label">Expected — a checkout that needs one repair</div>
-      <div class="out"><span class="ok">pass</span> extension bridge present manifest=…/extension.action-manifest.json
-harness: @deeeed/metamask-harness@0.34.x
-runtime: decision=install (deps-missing) deps=missing webpack=down
-  Dependencies are not installed (no yarn install-state markers).
-runtime-context: temp/recipe/runtime/agentic-runtime.json (<span class="bad">absent</span> — run mm-harness doctor --fix)
-capture: <span class="ok">pass</span> (screenshots: capture-helper → cdp; video: capture-helper)
-  <span class="hint">Next: mm-harness launch --adapter extension --target '…'</span></div>
-      <div class="note">
-        <span class="note-title">The habit the toolchain is built around</span>
-        <p>
-          Every failure names one next action. Above, the finding tells you to run
-          <code>doctor --fix</code> and the <code>Next:</code> line says where to go once it passes.
-          Read the message and do what it says — that is also what lets an agent recover on its own
-          instead of guessing.
-        </p>
-      </div>
-      <p class="step-why">Do what it said:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness doctor --fix</code></pre></div>
-      <div class="out-label">Expected — the finding is gone</div>
-      <div class="out"><span class="ok">pass</span> extension bridge present ready=true <span class="ok">fixed=[runtime-context]</span> failed=[]</div>
-      <p class="step-why">
-        <code>--fix</code> repairs runtime state the harness owns. It will not launch the app, invent
-        credentials, or pick a wallet fixture; those are your decisions, so it stops and asks.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong><code>deps=missing</code></strong> — run <code>yarn install</code> as usual for
-            that repo. The harness does not manage your product repo's dependencies.
-          </p>
-          <p>
-            <strong>A finding you do not understand</strong> — <code>mm-harness doctor --json</code>
-            carries the same findings with structured detail, and is the form to paste to an agent or a
-            bug report.
-          </p>
-          <p>
-            <strong>Still failing after <code>--fix</code></strong> — <code>fixed=[…] failed=[…]</code>
-            separates the two. Anything in <code>failed</code> needs a human decision; the finding says
-            which.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="launch">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-launch" aria-labelledby="t-launch">
-        <h3 class="step-title" id="t-launch">Launch the app under harness control</h3>
-      </div>
-      <p class="step-why">
-        Starts the app and its dev server, installing the runtime overlay first if missing. Platform is
-        auto-detected. On iOS, pin one simulator UUID through provisioning and launch so duplicate device
-        names cannot select different simulators.
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness launch --verify          <span class="dim"># extension — fullscreen by default</span>
-<span class="p">$ </span>xcrun simctl list devices available <span class="dim"># choose one iPhone UUID</span>
-<span class="p">$ </span>mm-harness provision runway ios --device '&lt;UUID&gt;' --force
-<span class="p">$ </span>xcrun simctl get_app_container '&lt;UUID&gt;' io.metamask.MetaMask app
-<span class="p">$ </span>mm-harness launch ios --device '&lt;UUID&gt;' --verify
-<span class="p">$ </span>mm-harness launch android --verify</code></pre></div>
-      <p class="step-why">
-        Quick relaunch is the default and reuses a healthy runtime. <code>--build</code> is the escape
-        hatch that always clean-builds; reach for it only when native or bundler output changed.
-      </p>
-      <div class="out-label">Core is headless — and says so</div>
-      <div class="out"><span class="bad">✗</span> mm-harness launch: core is headless; there is nothing to launch.
-  <span class="hint">Next: mm-harness verify</span></div>
-      <p class="step-why">
-        In <code>core</code> there is no UI to launch, so you get the equivalent step instead of a
-        silent failure. Run <code>mm-harness verify</code> and continue.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Mobile: more than one device</strong> — the harness lists what it found rather than
-            guessing. Re-run with <code>--device &lt;udid|serial&gt;</code>. Prefer the iOS UUID over a name,
-            because Xcode can contain several simulators with the same display name.
-          </p>
-          <p>
-            <strong>iOS app missing after provisioning</strong> — repeat the provision command with
-            <code>--force</code> and the same UUID. Do not use <code>--preflight-mode</code>; it is an
-            internal adapter flag, not a public <code>mm-harness launch</code> option.
-          </p>
-          <p>
-            <strong>Stuck</strong> — <code>mm-harness logs</code> tails the dev server and app logs;
-            <code>mm-harness status</code> shows the adapter, devices, and next command.
-          </p>
-          <p>
-            <strong>Clean slate</strong> — <code>mm-harness stop</code> stops only what this checkout
-            owns, so parallel checkouts are untouched. Stopping nothing is success.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="actions">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-actions" aria-labelledby="t-actions">
-        <h3 class="step-title" id="t-actions">Discover what this checkout can do</h3>
-      </div>
-      <p class="step-why">
-        Prints every typed operation available here, with its fields. The set differs per product:
-        Mobile has UI actions, Core is headless and has none.
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness actions --categories</code></pre></div>
-      <div class="out-label">Expected — a mobile checkout, with its own counts</div>
-      <div class="out">analytics (4)
-assertion (4)
-control (4)
-deeplink (1)
-evidence (2)
-perps (11)
-runtime (4)
-ui (13)
-utility (1)
-wallet (6)</div>
-      <p class="step-why">
-        Categories and counts move with the release and the adapter. Read yours from the command; the
-        shape is the point, not the numbers.
-      </p>
-      <p class="step-why">Then look inside a category, search, or inspect one action's fields:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness actions --category ui
-<span class="p">$ </span>mm-harness actions positions
-<span class="p">$ </span>mm-harness actions --action read_state</code></pre></div>
-      <div class="doctrine">
-        <p>
-          <span class="k">The discovered list is law.</span> It is the capability boundary, not a
-          subset of some larger API. Call something not on it and the harness refuses, pointing you back
-          at discovery:
-        </p>
-      </div>
-      <div class="out"><span class="bad">✗</span> call: unknown action "totally_made_up" for the extension adapter.
-  <span class="hint">Next: mm-harness actions --adapter extension --json</span></div>
-      <p class="step-why">
-        That refusal is why the evidence is worth reading: a tool that invents an action when asked for
-        something impossible would also produce a plausible-looking result, and you would have no way to
-        tell. Add <code>--json</code> when feeding this to an agent.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Fewer actions than expected</strong> — you are seeing only the bundled set. Team
-            libraries add domain actions and must be declared: <a href="tutorials/v3.html">V3</a>.
-          </p>
-          <p>
-            <strong>Wrong product detected</strong> — pass <code>--adapter mobile|extension|core</code>
-            explicitly, and check you are inside the checkout you meant.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="call-read">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-call-read" aria-labelledby="t-call-read">
-        <h3 class="step-title" id="t-call-read">Drive it: read product state</h3>
-      </div>
-      <p class="step-why">
-        <code>call</code> runs one action as a one-node recipe through the real engine — same execution
-        path, trace, and evidence as a full run. Start with a read; reads cannot break anything.
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness call read_state</code></pre></div>
-      <div class="note blue">
-        <span class="note-title">Core branch</span>
-        <p>
-          Core has no wallet UI. Exercise its live controller boundary instead:
-          <code>mm-harness call read_positions mode=all</code>.
-        </p>
-      </div>
-      <p class="step-why">
-        Short names resolve when unambiguous: <code>read_state</code> finds
-        <code>metamask.wallet.read_state</code>. An ambiguous one stops and lists the candidates.
-      </p>
-      <div class="out-label">Expected — shape of the result</div>
-      <div class="out">call read_state: <span class="ok">pass</span>
-Result:
-{
-  "action": "metamask.wallet.read_state",
-  "state": {
-    "selectedAccount": { "name": "Account 1", "address": "0x…" },
-    "completedOnboarding": true
-  },
-  "redacted": true
-}</div>
-      <p class="step-why">
-        Note <code>"redacted": true</code> — wallet state passes through redaction before reaching an
-        artifact, because these bundles get attached to pull requests.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Runtime health check failed / CDP not reachable</strong> — the app is not running.
-            Complete the launch step; <code>mm-harness status</code> confirms what is live.
-          </p>
-          <p>
-            <strong>Mobile: more than one device</strong> — <code>call</code> fails fast and lists
-            them. Re-run with <code>--device</code>.
-          </p>
-          <p>
-            <strong><code>unknown action</code></strong> — not in this adapter's set.
-            <code>mm-harness call --list</code> shows what <code>call</code> accepts here.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="call-ui">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-call-ui" aria-labelledby="t-call-ui">
-        <h3 class="step-title" id="t-call-ui">Drive it again: UI or headless Core</h3>
-      </div>
-      <p class="step-why">Keep the app visible for this one.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness call navigate page=perps</code></pre></div>
-      <div class="note blue">
-        <span class="note-title">Core branch</span>
-        <p>
-          Prove a second headless action instead:
-          <code>mm-harness call command cmd="echo core-ready"</code>.
-        </p>
-      </div>
-      <p class="step-why">
-        Fields are passed as <code>key=value</code>, or <code>--arg k=v</code> for the same effect.
-      </p>
-      <div class="note blue">
-        <span class="note-title">Semantic intent, not coordinates</span>
-        <p>
-          You asked for a <em>page</em>, not a pixel or a route. The adapter owns the mapping and
-          verifies where it landed, so a drifted route fails loudly instead of quietly doing nothing —
-          which is why these actions survive redesigns.
-          <code>mm-harness actions --action navigate</code> lists accepted values.
-        </p>
-      </div>
-      <p class="step-why">Others worth trying, if your adapter lists them:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness call press text="Account 1"
-<span class="p">$ </span>mm-harness call screenshot path=proof.png</code></pre></div>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Target not found</strong> — the element is not on screen. Actions do not hunt
-            blindly; use <code>wait_for</code> when something needs to mount first.
-          </p>
-          <p>
-            <strong>Core has no UI actions</strong> — correct, it is headless. Try
-            <code>mm-harness call command cmd="echo hello"</code> there instead.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="run">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-run" aria-labelledby="t-run">
-        <h3 class="step-title" id="t-run">Prove it: run your first recipe</h3>
-      </div>
-      <p class="step-why">
-        Everything so far was driving by hand. A recipe composes the same operations into a graph that
-        runs identically every time and records what happened. Start with what ships:
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run --list</code></pre></div>
-      <div class="out-label">Expected — an extension checkout</div>
-      <div class="out">runnable recipes (extension)
-Inspect: mm-harness run &lt;recipe&gt; --describe
-  perps.clean-market-testnet [metamask] variant=all params=market — Converge one Perps testnet market…
-  perps.lifecycle            [metamask] variant=all — Opens a small ETH testnet position, verifies it, closes it…
-  perps.smoke                [metamask] variant=extension — Non-mutating Perps domain smoke…
-  runner.action-validation   [metamask] variant=extension — Exercises every manifest-declared action…
-  runner.smoke               [metamask] variant=extension — Proves the runner executes manifest-declared actions…
-  wallet.smoke               [metamask] variant=extension — Fixture-backed proof that the wallet is reachable…</div>
-      <p class="step-why">
-        The bundled set grows between releases; yours is whatever this command prints, not what is
-        printed here.
-      </p>
-      <p class="step-why">
-        Read one first. <code>--describe</code> shows its parameters and every action it composes:
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run wallet.smoke --describe
-<span class="p">$ </span>mm-harness run wallet.smoke --plan</code></pre></div>
-      <p class="step-why">
-        <code>--plan</code> validates and prints the execution plan while touching nothing, exiting 5 if
-        the recipe is invalid. Cheap check before the expensive one.
-      </p>
-      <p class="step-why">Now for real, with the evidence somewhere you chose:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run wallet.smoke --artifacts-dir ./first-recipe-artifacts</code></pre></div>
-      <div class="out-label">Expected</div>
-      <div class="out"><span class="ok">PASS</span> recipe run [extension]
-summary:
-  <span class="ok">PASS</span> status (app.status, 9ms): platform=extension
-  <span class="ok">PASS</span> fixture (metamask.wallet.fixture_status, 17ms): path=temp/recipe/runtime/wallet-fixture.json
-  <span class="ok">PASS</span> unlock (metamask.wallet.ensure_unlocked, 100ms): proof=extension-unlocked-state
-  <span class="ok">PASS</span> state (metamask.wallet.read_state, 94ms): proof=extension-wallet-state
-  <span class="ok">PASS</span> screenshot (ui.screenshot, 6.0s): path=screenshots/wallet-smoke.png
-  <span class="ok">PASS</span> done (end, 0ms)
-artifacts (6):
-  Human run report:  ./first-recipe-artifacts/report.md
-  Run summary:       ./first-recipe-artifacts/summary.json
-  Execution trace:   ./first-recipe-artifacts/trace.json
-  Executed recipe:   ./first-recipe-artifacts/recipe.json
-  <span class="dim">…</span></div>
-      <div class="note">
-        <span class="note-title">Wallet fixtures</span>
-        <p>
-          Recipes needing a signed-in wallet read one canonical fixture per checkout; the password comes
-          <em>from</em> the fixture and is never typed. On a missing fixture,
-          <code>mm-harness fixtures</code> shows its status and the safe next command.
-          <code>fixtures init --dev</code> creates a disposable public test wallet that must never hold
-          real funds.
-        </p>
-      </div>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Exit 5</strong> — validation or trust failure. The recipe is the problem, not your
-            environment; nothing executed. The message names the invalid part.
-          </p>
-          <p>
-            <strong>Exit 1</strong> — it ran and an action failed. A real result, not a tooling
-            problem: find the first node in <code>trace.json</code> with <code>"ok": false</code>.
-          </p>
-          <p>
-            <strong>Exit 3</strong> — infrastructure, not your recipe: the app or dev server fell over.
-            Try <code>mm-harness doctor</code> then <code>mm-harness logs</code>.
-          </p>
-          <p>
-            <strong>Lost track</strong> — <code>mm-harness last</code> prints the last significant
-            command with its verdict and evidence paths.
-          </p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="evidence">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="c-evidence" aria-labelledby="t-evidence">
-        <h3 class="step-title" id="t-evidence">Open the evidence bundle</h3>
-      </div>
-      <p class="step-why">The run left a directory behind. This is the part that beats clicking through by hand.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>ls first-recipe-artifacts
-<span class="p">$ </span>cat first-recipe-artifacts/summary.json
-<span class="p">$ </span>open first-recipe-artifacts/screenshots</code></pre></div>
-      <div class="table-scroll">
-        <table>
-          <thead><tr><th>File</th><th>What it answers</th></tr></thead>
-          <tbody>
-            <tr><td><code>summary.json</code></td><td>Did it pass? How many nodes, how long, which libraries were in play. The verdict.</td></tr>
-            <tr><td><code>trace.json</code></td><td>What happened at every step: per-node verdict, timing, inputs, outputs. Counts come from here.</td></tr>
-            <tr><td><code>recipe.json</code></td><td>The graph that actually executed, including each node's stated intent.</td></tr>
-            <tr><td><code>report.md</code></td><td>The same story in one readable page — the thing to skim first.</td></tr>
-            <tr><td><code>screenshots/</code></td><td>Visual evidence captured during the run.</td></tr>
-            <tr><td><code>diagnostics.json</code></td><td>Warnings and errors the app emitted, kept deliberately separate from the verdict.</td></tr>
-          </tbody>
-        </table>
-      </div>
-      <p class="step-why">
-        Read them in that order: <code>report.md</code>, then <code>summary.json</code> for the verdict,
-        then <code>trace.json</code> when you want to know why. Cite numbers from
-        <code>trace.json</code>, never from prose written around it.
-      </p>
-      <div class="btn-row" style="margin-top:1.2rem">
-        <a class="btn btn-primary" href="reviewers.html">Read a bundle line by line →</a>
-      </div>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p>
-            <strong>Cannot find the directory</strong> — without <code>--artifacts-dir</code> it goes
-            to a checkout-local run directory. <code>mm-harness last</code> prints the path.
-          </p>
-          <p>
-            <strong>No screenshots</strong> — capture differs per platform;
-            <code>mm-harness doctor</code> reports it on a <code>capture:</code> line. A degraded
-            fallback still succeeds and records that it degraded in the artifact metadata.
-          </p>
-        </div>
-      </details>
-    </li>
-  </ol>
-</section>
-<section class="wrap">
-  <hr class="sep">
-  <h2>Next</h2>
-  <div class="grid grid-3">
-    <div class="card">
-      <h3>Recipe anatomy</h3>
-      <p>The graph, the intents, the assertions, and the test of whether yours is worth keeping.</p>
-      <p><a href="recipes.html">Read the anatomy →</a></p>
-    </div>
-    <div class="card">
-      <h3>Your team's library</h3>
-      <p>Install the skills, declare your library, prove discovery sees it.</p>
-      <p><a href="tutorials/v3.html">Tutorial V3 →</a></p>
-    </div>
-    <div class="card">
-      <h3>Reviewing someone's proof</h3>
-      <p>A real bundle annotated, including a degraded capture that stayed honest about it.</p>
-      <p><a href="reviewers.html">For reviewers →</a></p>
-    </div>
-  </div>
-</section>
-</main>
-<footer class="footer">
-  <div class="wrap">
-    <p>Internal getting-started guide for proving MetaMask changes with recipes. Not official MetaMask product documentation.</p>
-    <p>Commands here are checked against the CLI's own <code>--help</code>. If one disagrees with your terminal, your terminal is right: run <code>mm-harness update</code>, then trust <code>--help</code>.</p>
-  </div>
-</footer>
-<script type="module" src="assets/progress.mjs?v=4"></script>
-</body>
-</html>