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/index.html DELETED Viewed

@@ -1,236 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>The trust layer for MetaMask agentic development</title>
-<meta name="description" content="Skills encode MetaMask engineering workflows. Recipes prove the work against real builds, preserve the evidence, and remain as regression checks.">
-<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="assets/style.css?v=4">
-</head>
-<body>
-<a class="skip" href="#prompt">Skip to the prompt</a>
-<main class="lobby">
-  <div class="lobby-inner">
-    <img class="lobby-mark" src="assets/metamask-fox.svg" alt="" width="52" height="52">
-    <span class="eyebrow">Built for MetaMask engineering workflows</span>
-    <h1>The trust layer for agentic development.</h1>
-    <p class="lobby-lede">
-      Skills encode MetaMask's engineering workflows. Recipes prove the work against real builds,
-      preserve the evidence, and remain as regression checks.
-    </p>
-    <p class="lobby-sub">
-      Set up once, then work a real ticket.
-    </p>
-    <section class="qs">
-      <div class="qs-step">
-        <h2 class="qs-title"><span class="qs-num" aria-hidden="true">1</span>Set up</h2>
-        <p class="qs-why">
-          One time per machine. Paste this into your agent inside a MetaMask checkout.
-        </p>
-        <div class="cmd cmd-hero" id="prompt"><pre><code>Task: set me up for recipe-backed work on MetaMask. Follow these steps in order.
-When a command fails, its message names the exact next command — run that
-instead of improvising.
-1. Install the harness: `npm i -g @deeeed/metamask-harness@latest`, then
-   `mm-harness --version` to confirm it resolved.
-2. Checkout: if I started you inside a MetaMask product checkout
-   (metamask-extension, metamask-mobile, or core), use it. If not, run
-   `mm-harness setup-base --dry-run` to show me the layout it would create,
-   and ask me before running it for real. Everything below runs from inside
-   the checkout.
-3. Run `mm-harness doctor` and fix every finding by following its own
-   instructions until doctor passes. `mm-harness doctor --fix` repairs
-   harness-owned runtime state; it will not invent credentials or pick a
-   wallet fixture for me.
-4. Run `mm-harness fixtures`. If no fixture exists, run
-   `mm-harness fixtures init --dev`; this creates a disposable public test
-   wallet that must never receive real funds.
-5. Launch and wait for readiness:
-   - Extension: `mm-harness launch --verify`.
-   - Android: `mm-harness launch android --verify`; if more than one device is
-     listed, choose one serial and repeat it with `--device &lt;serial&gt;`.
-   - iOS: run `xcrun simctl list devices available`, choose ONE available iPhone
-     UUID (ask me if the choice is ambiguous), and use that literal UUID in all
-     three commands below — never substitute the simulator name:
-       `mm-harness provision runway ios --device '&lt;UUID&gt;' --force`
-       `xcrun simctl get_app_container '&lt;UUID&gt;' io.metamask.MetaMask app`
-       `mm-harness launch ios --device '&lt;UUID&gt;' --verify`
-   - Core: `mm-harness verify`; it has no app to launch.
-   `--preflight-mode` is an internal adapter flag, not a public launch flag.
-6. On Extension run `mm-harness fixtures set`. On Mobile include the same
-   `--device &lt;UUID-or-serial&gt;` used for launch. Wait for it to succeed.
-7. Install the skills — they are how the work actually gets driven. First
-   inspect `METAMASK_SKILLS_DIR` and `CONSENSYS_SKILLS_DIR`, then check the
-   expected local layout below. Reuse every valid existing clone. For each
-   missing source, show me the proposed path and ask before cloning:
-     `git clone https://github.com/MetaMask/skills.git ~/dev/metamask/skills`
-     `git clone git@github.com:Consensys/skills.git ~/dev/Consensys/skills`
-   The internal overlay needs access to the Consensys org. Export the paths in
-   the current shell for setup:
-     `export METAMASK_SKILLS_DIR=~/dev/metamask/skills`
-     `export CONSENSYS_SKILLS_DIR=~/dev/Consensys/skills`
-   Never edit `.zshrc`, `.bashrc`, or another shell startup file unless I
-   explicitly consent; ask separately if I want these exports persisted.
-   If that clone fails, tell me — I may not have access, and the next step
-   depends on it. Then, from inside the checkout:
-     `yarn metamask-skills list --maturity experimental`   everything installable
-     `yarn skills`                                         installs the stable set
-   `yarn skills` runs `metamask-skills sync` and is already wired in
-   metamask-extension, metamask-mobile, and core. Use `--maturity experimental`
-   when listing: the default only prints stable skills, so the recipe skills
-   below do not appear without it.
-8. Add the skills that drive recipe-backed work:
-     `yarn skills --include agentic/recipe-harness,agentic/recipe-cook,agentic/recipe-quality,agentic/recipe-performance,agentic/recipe-pr-qa-review,agentic/recipe-evidence --save`
-   They install as `mms-recipe-harness`, `mms-recipe-cook`, `mms-recipe-quality`,
-   `mms-recipe-performance`, `mms-recipe-pr-qa-review`, and
-   `mms-recipe-evidence`. They come from the `Consensys/skills` clone in
-   step 7 and are marked experimental, which is why the explicit `--include`
-   is required. If `yarn metamask-skills describe agentic/recipe-cook` cannot
-   find it, check `CONSENSYS_SKILLS_DIR` points at that clone, then stop and
-   tell me. Do not substitute a different skill.
-9. Run `mm-harness actions`. That list is the ONLY set of capabilities you may
-   use, now and in every later session — never invent an action or a flag. Then
-   stop and tell me setup is done.
-Not optional, from here on: evidence comes only from executed actions — never
-fabricate a result or edit state to manufacture one. If the harness reports a
-capability as unsupported, stop and tell me rather than working around it. If a
-step fails twice after following its error's instructions, stop and show me the
-exact error.</code></pre></div>
-      </div>
-      <div class="qs-step">
-        <h2 class="qs-title"><span class="qs-num" aria-hidden="true">2</span>Do real work</h2>
-        <p class="qs-why">
-          Pick what you are doing. Each one runs the skill that owns that flow, and leaves a
-          rerunnable recipe behind as the proof.
-        </p>
-        <div class="tabs">
-          <div class="tablist" role="tablist" aria-label="Choose what to do" hidden>
-            <button type="button" role="tab" id="tab-fix" class="tab" aria-controls="panel-fix" aria-selected="true" tabindex="0">Fix a bug</button>
-            <button type="button" role="tab" id="tab-build" class="tab" aria-controls="panel-build" aria-selected="false" tabindex="-1">Build a feature</button>
-            <button type="button" role="tab" id="tab-review" class="tab" aria-controls="panel-review" aria-selected="false" tabindex="-1">QA + Review PR</button>
-            <button type="button" role="tab" id="tab-performance" class="tab" aria-controls="panel-performance" aria-selected="false" tabindex="-1">Performance</button>
-            <button type="button" role="tab" id="tab-evidence" class="tab" aria-controls="panel-evidence" aria-selected="false" tabindex="-1">Pretty PR</button>
-          </div>
-          <div class="qs-panel" role="tabpanel" id="panel-review" aria-labelledby="tab-review" tabindex="0">
-            <p class="qs-panel-why">
-              <code>mms-recipe-pr-qa-review</code> runs full read-only QA and code-risk review. It
-              freezes the acceptance criteria before it touches the runtime, validates each one on a real build, and returns a report.
-              It never edits product code and never posts to GitHub. The PR must be in the same
-              product as your checkout.
-            </p>
-            <div class="cmd"><pre><code>/mms-recipe-pr-qa-review https://github.com/MetaMask/metamask-mobile/pull/&lt;number&gt;
-Extract the acceptance criteria from the PR yourself and freeze them before any
-runtime work. Validate each one against the running build, then give me the
-per-AC verdict table, the overall verdict, and the artifact paths. Do not post
-anything on the PR.</code></pre></div>
-          </div>
-          <div class="qs-panel" role="tabpanel" id="panel-fix" aria-labelledby="tab-fix" tabindex="0">
-            <p class="qs-panel-why">
-              <code>mms-recipe-cook</code>, classified as <code>fix-bug</code>. It lists the
-              compatible checklist templates and stops for your pick, then works on a local task
-              branch. No product edits until the bug is proven to reproduce.
-            </p>
-            <div class="cmd"><pre><code>/mms-recipe-cook
-Fix this in the checkout I started you in — treat it as fix-bug:
-&lt;paste the ticket, or the broken behaviour and how to reproduce it&gt;
-Reproduce it on the real build first and keep that failing run as the baseline.
-Then fix it and re-run the same recipe until it passes. Show me the recipe
-status, the per-node results, and the artifact paths.</code></pre></div>
-          </div>
-          <div class="qs-panel" role="tabpanel" id="panel-build" aria-labelledby="tab-build" tabindex="0">
-            <p class="qs-panel-why">
-              <code>mms-recipe-cook</code>, classified as <code>dev</code>. Same flow: it lists the
-              compatible templates, stops for your pick, and keeps the diff uncommitted until you
-              ask it to package the PR.
-            </p>
-            <div class="cmd"><pre><code>/mms-recipe-cook
-Build this in the checkout I started you in — treat it as dev:
-&lt;paste the ticket, or the change you want&gt;
-Plan the proof before you edit anything, implement it, then prove it with a
-recipe that drives the real build. Show me the recipe status, the per-node
-results, and the artifact paths.</code></pre></div>
-          </div>
-          <div class="qs-panel" role="tabpanel" id="panel-performance" aria-labelledby="tab-performance" tabindex="0">
-            <p class="qs-panel-why">
-              <code>mms-recipe-performance</code> measures one real MetaMask flow with
-              evidence tied to the recipe run. It freezes the user journey and measurement boundaries,
-              keeps setup outside the measured window, and requires approval before any fix.
-            </p>
-            <div class="cmd"><pre><code>/mms-recipe-performance
-Measure this MetaMask flow:
-&lt;describe the exact user journey and suspected performance problem&gt;
-Propose the measured start and end, client, lifecycle state, environment,
-evidence sources, and failure threshold. Wait for my approval before measuring.
-Run one real-app baseline and return the recipe, trace, measurements, verdict,
-and artifact paths. Do not edit product code unless I approve a proven fix.
-If I approve one, rerun the identical recipe after the change.</code></pre></div>
-          </div>
-          <div class="qs-panel" role="tabpanel" id="panel-evidence" aria-labelledby="tab-evidence" tabindex="0">
-            <p class="qs-panel-why">
-              <code>mms-recipe-evidence</code> — the PR evidence skill. It first checks that every
-              claim has strong reviewable evidence, then turns the completed Recipe Cook task into
-              a clear, template-preserving PR description. Packaging is local; uploads and PR writes
-              require your separate approval.
-            </p>
-            <div class="cmd"><pre><code>From the MetaMask checkout, install the PR evidence skill if it is missing:
-  yarn skills --maturity experimental --include agentic/recipe-evidence --save
-Then run:
-  /mms-recipe-evidence
-Use the completed Recipe Cook task in this checkout. Before packaging, verify
-that every PR claim maps to executed recipe evidence. Inspect each selected
-screenshot or video and keep only the strongest reviewer-useful artifacts. If
-the proof is weak, missing, stale, or does not show the claimed result, stop and
-tell me what recipe or evidence must be rerun instead of polishing the PR.
-Once the evidence is good, preserve the repository PR template and build the
-cleanest reviewer-facing package. Show me pr-package/pr-desc.md, the selected
-screenshots or videos, proved claims, and honest gaps before doing anything
-external.
-Do not upload screenshots or create/update the PR until I approve that outward
-step. Warn me that uploaded screenshots go to a public evidence repository and
-may show wallet state. Never invent evidence or turn an incomplete run into a
-pass.</code></pre></div>
-          </div>
-        </div>
-      </div>
-    </section>
-    <div class="lobby-cta">
-      <a class="btn btn-primary" href="how-it-works.html">How it works →</a>
-    </div>
-    <p class="lobby-fine">
-      A proposal for how agents can code at MetaMask — offered for teams to try.
-    </p>
-  </div>
-</main>
-<script type="module" src="assets/progress.mjs?v=4"></script>
-</body>
-</html>

package/site/perps-advanced-orders-qa.html DELETED Viewed

@@ -1,96 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>Mobile Pro advanced orders — QA walkthrough</title>
-<meta name="description" content="Offline QA walkthrough and reusable mm-harness commands for Mobile Pro TWAP, Chase, and Scale orders.">
-<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="assets/style.css?v=4">
-</head>
-<body>
-<a class="skip" href="#checks">Skip to checks</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">How it works</a>
-      <a href="perps.html" aria-current="page">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>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Mobile Pro QA</span>
-  <h1>Advanced orders must remain observable</h1>
-  <p class="lede">Place TWAP, Chase, and Scale through visible Pro controls, then prove the resulting work remains available where a trader expects to monitor it.</p>
-  <div class="hero-meta"><span>Hyperliquid testnet</span><span>visible UI only</span><span>parameterized recipes</span></div>
-</section>
-<section class="wrap" id="checks">
-  <div class="note blue">
-    <span class="note-title">Safety boundary</span>
-    <p>Use a prepared fixture wallet with the three Mobile flags enabled. Omit <code>account</code> to keep the account already selected in MetaMask. Provider, network, and market use the recipe defaults; every recipe defaults to testnet. Mainnet requires an explicit user request; never infer it from context. Assertions preserve orders on either network, and placement preserves existing mainnet trading state. Do not use React state overrides, coordinate gestures, reloads, or background transitions to repair a failed proof.</p>
-  </div>
-  <h2>Preflight</h2>
-  <ol>
-    <li>Launch and verify the prepared Mobile slot with <code>mm-harness launch ios --verify --adapter mobile --target &lt;mobile-checkout&gt;</code>.</li>
-    <li>Confirm the recipes appear in <code>mm-harness run --list --adapter mobile</code>.</li>
-    <li>Choose a funded testnet account and market, and pass explicit parameters when its safe ladder prices differ from the BTC defaults.</li>
-    <li>Let cleanup finish after every lane. Preserve the first failure and its trace.</li>
-  </ol>
-  <h2>TWAP: place, then monitor</h2>
-  <div class="cmd"><pre><code>mm-harness run perps.twap-place account=dev1 provider=hyperliquid network=testnet market=BTC side=long notional=110 randomize=false --adapter mobile
-mm-harness run perps.twap-assert-active account=dev1 provider=hyperliquid network=testnet market=BTC --adapter mobile</code></pre></div>
-  <ol>
-    <li>The Advanced picker visibly offers TWAP.</li>
-    <li>The five-minute schedule is accepted and the form resets.</li>
-    <li>The TWAP tab opens on Active and shows a card for the selected market.</li>
-  </ol>
-  <p>A placement toast without an active card is a product failure: the schedule has vanished from the trader's monitoring surface. Mobile supports a 24-hour venue maximum; do not claim a seven-day duration, trigger price, or max price.</p>
-  <h2>Chase: survive a foreground dwell</h2>
-  <div class="cmd"><pre><code>mm-harness run perps.chase-place account=dev1 provider=hyperliquid network=testnet market=BTC side=long notional=100 max_distance=5000 --adapter mobile
-mm-harness run perps.chase-assert-running account=dev1 provider=hyperliquid network=testnet market=BTC dwell_ms=12000 --adapter mobile
-mm-harness run perps.chase-terminate account=dev1 provider=hyperliquid network=testnet market=BTC --adapter mobile</code></pre></div>
-  <ol>
-    <li>The Advanced picker visibly offers Chase and the form shows its foreground disclosure.</li>
-    <li>After placement, the Chase tab shows the market as Running.</li>
-    <li>The app remains foregrounded for the full dwell. The same row must still be visible afterward.</li>
-    <li>Terminate the session and confirm it leaves the active list.</li>
-  </ol>
-  <p>If the row disappears during the dwell, classify whether the trace shows product state loss, selector drift, harness transport failure, or a venue rejection. Do not claim force-kill conversion; Mobile's supported boundary is graceful foreground/background lifecycle handling.</p>
-  <h2>Scale: expose every child order</h2>
-  <div class="cmd"><pre><code>mm-harness run perps.scale-place account=dev1 provider=hyperliquid network=testnet market=BTC side=long notional=100 orders=3 skew=1 start_price=70000 end_price=75000 --adapter mobile
-mm-harness run perps.scale-assert-orders account=dev1 provider=hyperliquid network=testnet market=BTC orders=3 --adapter mobile</code></pre></div>
-  <ol>
-    <li>The Advanced picker visibly offers Scale.</li>
-    <li>Start, end, order count, skew, and notional produce a visible preview before submission.</li>
-    <li>The standard Orders tab reports the requested count and shows the child entries as Limit orders.</li>
-  </ol>
-  <p>Partial venue acceptance is a failed full-ladder proof. This walkthrough does not claim group cancellation.</p>
-  <h2>Classify and report</h2>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th>Class</th><th>Evidence</th><th>Action</th></tr></thead>
-      <tbody>
-        <tr><td>Product defect</td><td>Bridge remains live; product selector/state disappears or venue-backed UI contradicts acceptance.</td><td>Record the first failing node, trace, screenshot, market, side, and elapsed time.</td></tr>
-        <tr><td>Recipe drift</td><td>Current product source or live tree establishes an intentional selector/flow change.</td><td>Repair the smallest node and rerun every caller.</td></tr>
-        <tr><td>Harness defect</td><td>A declared action violates its schema or reports a false verdict independent of product behavior.</td><td>Fix the harness and retain before/after proof.</td></tr>
-        <tr><td>Environment or venue</td><td>Fixture, funding, connectivity, capability, or exchange rejection prevents the product claim.</td><td>Fail closed and report the precise prerequisite; do not manufacture state.</td></tr>
-      </tbody>
-    </table>
-  </div>
-</section>
-</main>
-<script type="module" src="assets/progress.mjs?v=4"></script>
-</body>
-</html>

package/site/perps.html DELETED Viewed

@@ -1,265 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>Team / Perps — customize the harness for your team</title>
-<meta name="description" content="Every team points the harness at its own recipe library. The MetaMask Perps library is the worked example: recipes, actions, checklist templates, and the team's own knowledge.">
-<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="assets/style.css?v=4">
-</head>
-<body>
-<a class="skip" href="#setup">Skip to setup</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">How it works</a>
-      <a href="perps.html" aria-current="page">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>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Customization</span>
-  <h1>Make it your team's harness</h1>
-  <p class="lede">
-    The harness ships an execution standard and a deliberately small bundled library. Everything that
-    is specific to what <em>you</em> work on — the journeys, the assertions, the checklists, the review
-    knowledge — lives in a library you own and point the harness at. MetaMask Perps is the worked
-    example on this page.
-  </p>
-  <div class="hero-meta">
-    <span>per team</span>
-    <span>per engineer</span>
-    <span>one env var</span>
-  </div>
-</section>
-<section class="wrap" aria-labelledby="advanced-orders-qa">
-  <div class="note blue">
-    <span class="note-title" id="advanced-orders-qa">Mobile Pro advanced-order QA</span>
-    <p>
-      Validate TWAP monitoring, foreground Chase persistence, and Scale child orders with the
-      parameterized Mobile recipe family.
-      <a href="perps-advanced-orders-qa.html">Open the offline walkthrough</a>.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <div class="doctrine">
-    <p>
-      <span class="k">The harness supplies the execution standard; your library supplies the domain.</span>
-      A team shares one library. An engineer can add their own on top. Neither requires a change to
-      the harness.
-    </p>
-  </div>
-  <h2>What lives where</h2>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th>Layer</th><th>Owns</th><th>Does not own</th></tr></thead>
-      <tbody>
-        <tr>
-          <td><code>mm-harness</code></td>
-          <td>Launch, typed actions, graph execution, screenshots, video, traces, and artifact contracts.</td>
-          <td>Anything specific to one team's domain.</td>
-        </tr>
-        <tr>
-          <td>Your library</td>
-          <td>Reusable setup, journeys, assertions, cleanup, platform variants, and checklist templates.</td>
-          <td>Wallet credentials, generated evidence, or product source.</td>
-        </tr>
-        <tr>
-          <td>Product checkout</td>
-          <td>The real Extension, Mobile, or Core code and runtime being proved.</td>
-          <td>A substitute test implementation.</td>
-        </tr>
-      </tbody>
-    </table>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="setup">Point the harness at a library</h2>
-  <p>
-    One environment variable does it. The Perps library is private, so start by asking its owners for
-    access — a clone failure means your GitHub account does not have it yet.
-  </p>
-  <div class="cmd"><pre><code><span class="p">$ </span>git clone git@github.com:MetaMask/experimental-metamask-recipe-perps.git \
-    "$HOME/shared-library/metamask-recipe-perps"
-<span class="p">$ </span>export RECIPE_LIBRARY_PATH="perps=$HOME/shared-library/metamask-recipe-perps"
-<span class="p">$ </span>mm-harness run --list</code></pre></div>
-  <p>
-    <code>name=path</code> gives the source its alias; without one the directory name is used. Separate
-    several libraries with <code>:</code> — order is precedence, first wins:
-  </p>
-  <div class="cmd"><pre><code><span class="p">$ </span>export RECIPE_LIBRARY_PATH="mine=$HOME/my-recipes:perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
-  <p>
-    Use <code>--library name=/path</code> for a single command instead — useful when a tool shell loses
-    an exported variable. Resolution follows your library order, then the bundled MetaMask library.
-  </p>
-  <div class="note blue">
-    <span class="note-title">Your own library, with no configuration</span>
-    <p>
-      A directory at <code>~/.farmslot/recipe-library</code> is picked up automatically as
-      <code>personal</code> when you set no library at all. It is a fallback, not an addition: as soon
-      as <code>RECIPE_LIBRARY_PATH</code> or <code>--library</code> is set, only those sources are used.
-      List it explicitly to keep both.
-    </p>
-  </div>
-  <div class="note blue">
-    <span class="note-title">Discovery is adapter-aware</span>
-    <p>
-      The list shows only recipes runnable in the current product checkout. A recipe marked
-      <code>[perps]</code> came from that library; <code>[metamask]</code> means it ships with the
-      harness. Read the selected platform variant with <code>--describe</code> before running it.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2>What a team library actually holds</h2>
-  <p>
-    Every path below is real, from the Perps library. Copy the shape, not the contents — it is the
-    reference structure for a MetaMask team building its own.
-  </p>
-  <div class="cmd"><pre><code>manifests/extension.action-manifest.json     types the actions you add
-actions/extension/perps/                     domain actions the product needs
-recipes/mobile/perps/                        per-adapter journeys
-recipes/extension/perps/
-recipes/core/perps/
-checklists/dev/                              your own Recipe Cook checklist templates
-checklists/fix-bug/
-docs/                                        the knowledge: authoring rules,
-                                             performance evidence, analytics</code></pre></div>
-  <p>
-    The <code>docs/</code> and <code>checklists/</code> directories are the part teams underestimate.
-    They are how a team's hard-won conventions — how performance evidence is gathered here, which
-    analytics events matter, what a finished task looks like — stop living in one engineer's head.
-  </p>
-  <div class="note">
-    <span class="note-title">Review knowledge lives with the skills</span>
-    <p>
-      One team surface sits outside the recipe library: the static antipattern packs the PR QA review
-      reads, which ship with the skills as
-      <code>references/antipatterns/&lt;repo&gt;/&lt;pack&gt;.md</code>. Today there is a
-      <code>perps</code> pack for Mobile, Extension, and Core, and a Mobile-only
-      <code>unit-vs-cv</code> pack. A pack is advisory: it never changes an acceptance-criterion
-      verdict.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2>Your first live proof</h2>
-  <p>
-    Complete <a href="how-it-works.html#steps">the walkthrough</a> first so the app, device, and wallet fixture are
-    ready. With <code>RECIPE_LIBRARY_PATH</code> exported, the library's recipes are just names.
-  </p>
-  <h3>Extension or Mobile</h3>
-  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.open-market --describe
-<span class="p">$ </span>mm-harness run perps.open-market network=testnet market=BTC --plan
-<span class="p">$ </span>mm-harness run perps.open-market network=testnet market=BTC \
-    --record-video=full-run --artifacts-dir ./perps-open-market-evidence</code></pre></div>
-  <h3>Core</h3>
-  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.snapshot-market --describe
-<span class="p">$ </span>mm-harness run perps.snapshot-market network=testnet market=BTC \
-    --artifacts-dir ./perps-market-evidence</code></pre></div>
-  <p>
-    A passing run writes <code>summary.json</code>, per-node results in <code>trace.json</code>, and an
-    artifact manifest beside screenshots or video. Visual review surfaces can render those same
-    recipe-derived artifacts without changing the proof graph.
-  </p>
-</section>
-<section class="wrap">
-  <h2>What the Perps team put in theirs</h2>
-  <p>
-    A sample of the library's recipes, as an idea of the granularity that works: small, parameterized,
-    composed rather than duplicated.
-  </p>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th>Claim</th><th>Recipe</th><th>Platforms</th></tr></thead>
-      <tbody>
-        <tr><td>Reach a live market detail screen</td><td><code>perps.open-market</code></td><td>Mobile, Extension</td></tr>
-        <tr><td>Read positions and orders</td><td><code>perps.snapshot-market</code></td><td>Mobile, Extension, Core</td></tr>
-        <tr><td>Place, assert, and clean up an order</td><td><code>perps.prove-order</code></td><td>Mobile, Extension, Core</td></tr>
-        <tr><td>Manage or close a position</td><td><code>perps.manage-position</code></td><td>Mobile, Extension, Core</td></tr>
-        <tr><td>Prove real MetaMetrics emissions</td><td><code>perps.analytics-lifecycle</code></td><td>Mobile, Extension</td></tr>
-        <tr><td>Measure the open-market journey</td><td><code>perps.performance-open-market</code></td><td>Mobile, Extension</td></tr>
-        <tr><td>Exercise edit-order contracts</td><td><code>perps.prove-edit-order</code></td><td>Core</td></tr>
-      </tbody>
-    </table>
-  </div>
-  <div class="note">
-    <span class="note-title">Mutation boundary</span>
-    <p>
-      Always run <code>--describe</code> and <code>--plan</code> before a state-changing recipe. The
-      library defaults to testnet and cleans up testnet state. Never turn an onboarding proof into a
-      mainnet mutation; mainnet operations require the recipe's explicit real-funds confirmation.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2>Starting your team's library</h2>
-  <ol>
-    <li>Create a repository with the directory shape above. It holds no accounts, fixtures, credentials, or generated evidence.</li>
-    <li>Parameterize stable choices such as market, side, order type, and network.</li>
-    <li>Compose existing setup, assertion, and cleanup recipes before adding a new top-level recipe.</li>
-    <li>Add a platform variant only when the products genuinely differ.</li>
-    <li>
-      If a locator or screen assertion fails, classify it first. Intentional product change may mean
-      small recipe drift; otherwise preserve the failure and fix the product, runtime, or harness layer
-      that owns it.
-    </li>
-    <li>Re-run every caller after a shared node changes and attach the fresh evidence.</li>
-  </ol>
-  <p>
-    Keep it small. Compose or repair the closest recipe before creating another one — a library that
-    grows a scenario per ticket stops being maintainable faster than the product does.
-  </p>
-  <div class="btn-row">
-    <a class="btn btn-primary" href="tutorials/v3.html">Install skills and the library →</a>
-    <a class="btn btn-ghost" href="ecosystem.html">Where this sits in the stack</a>
-    <a class="btn btn-ghost" href="recipes.html">How recipes prove claims</a>
-  </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>Written against the shared MetaMask Perps recipe library. Sample output moves between releases; trust your terminal over this page.</p>
-  </div>
-</footer>
-<script type="module" src="assets/progress.mjs?v=4"></script>
-</body>
-</html>