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

@deeeed/metamask-harness 0.47.0 → 0.47.1

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 (25) hide show

package/CHANGELOG.md +7 -0
package/dist/commands/tutorial.js +4 -4
package/dist/mm-harness-cli.js +2 -2
package/package.json +2 -2
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/tutorials/v3.html DELETED Viewed

@@ -1,258 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>V3 — Skills and your team's library</title>
-<meta name="description" content="Install the agentic skills into a checkout and declare your team's recipe library, with the perps library as the worked example.">
-<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="v3">
-<a class="skip" href="#steps">Skip to the checklist</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">Team / Perps</a>
-      <a href="../cheatsheet.html">Cheatsheet</a>
-      <a href="../architecture.html">Architecture</a>
-      <a href="index.html" aria-current="page">Tutorials</a>
-    </nav>
-  </div>
-</header>
-<div class="progress-rail">
-  <div class="wrap progress-inner">
-    <div class="progress-track" role="progressbar" aria-label="Tutorial progress" aria-valuemin="0" aria-valuemax="100" aria-valuenow="0">
-      <div class="progress-fill"></div>
-    </div>
-    <span class="progress-label">0/5 steps</span>
-    <button type="button" class="progress-reset">Reset</button>
-  </div>
-</div>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Tutorial V3 · 5 minutes</span>
-  <h1>Skills and your team's library</h1>
-  <p class="lede">
-    Two things turn a bare harness into your team's setup: skills that carry the workflow, and a library
-    that carries the recipes. Both install into a checkout.
-  </p>
-  <div class="hero-meta">
-    <span>prerequisite: <a href="../how-it-works.html#steps">the walkthrough</a></span>
-    <span>worked example: the perps library</span>
-  </div>
-</section>
-<section class="wrap">
-  <div class="vid-thumb" style="border-radius:var(--radius);border:1px solid var(--line);margin-bottom:1.5rem">
-    <div style="text-align:center;padding:1rem">
-      <div class="vid-id" style="font-size:2.6rem">V3</div>
-      <p style="color:var(--text-dim);margin:.5rem 0 0;font-size:.92rem">Video recording in progress</p>
-    </div>
-  </div>
-  <h2>Skills versus libraries</h2>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th></th><th>Skills</th><th>Recipe library</th></tr></thead>
-      <tbody>
-        <tr><td>Carry</td><td>The workflow an agent follows.</td><td>Recipes and domain actions.</td></tr>
-        <tr><td>Live in</td><td><code>Consensys/skills</code>, installed per checkout.</td><td>A team repo, declared by path.</td></tr>
-        <tr><td>Needed to run a recipe</td><td>No.</td><td>Yes, for your team's recipes.</td></tr>
-      </tbody>
-    </table>
-  </div>
-  <div class="note blue">
-    <span class="note-title">Layering</span>
-    <p>
-      Personal beats domain beats default, for skills and libraries alike. Your own overrides your team's,
-      which overrides what ships. A library that shadows another is reported in the run summary's
-      <code>shadowed</code> list rather than silently winning.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="steps">Set it up</h2>
-  <div class="agent-card">
-    <h3 style="margin-top:0">Paste this into your agent</h3>
-    <div class="cmd cmd-hero"><pre><code>Task: install the latest recipe skills and shared MetaMask Perps recipe library,
-then prove one real recipe runs end to end.
-1. Work from the MetaMask product checkout I started you in. Run
-   `npm i -g @deeeed/metamask-harness@latest` and `mm-harness --version`.
-2. Install the latest Consensys recipe skills into this checkout:
-   `yarn skills --maturity experimental --include
-   agentic/recipe-cook,agentic/recipe-quality --save`
-   This command updates the skills sources before syncing. Show me that
-   recipe-cook and recipe-quality were installed.
-3. Use this exact library directory:
-   `$HOME/shared-library/metamask-recipe-perps`.
-   If it does not exist, clone
-   `git@github.com:MetaMask/experimental-metamask-recipe-perps.git` there.
-   If it exists and is clean, update it with `git pull --ff-only`; if it is
-   dirty, preserve it and report that instead of changing its files.
-   If cloning reports 404 or permission denied, stop and tell me that repository
-   access is missing; do not search for a substitute repository.
-4. Run `mm-harness run --list --library
-   "perps=$HOME/shared-library/metamask-recipe-perps"` and show me the recipes
-   tagged `[perps]`. Use this explicit `--library` on every later command; do not
-   assume an `export` survives between tool shells.
-5. Run `mm-harness status`. If the app is not ready, follow its public `Next:`
-   command while preserving the same device UUID or serial used during setup.
-6. Choose only a recipe actually printed by step 4 for THIS checkout — the
-   `[perps]` set differs per adapter, so do not copy a name from the docs.
-   `perps.snapshot-market` is a good non-mutating pick on Core;
-   `perps.open-market` is its Extension/Mobile counterpart. If neither is in
-   your list, use the bundled `wallet.smoke` (Extension/Mobile) or
-   `runner.smoke` (Core).
-7. Run the chosen recipe with `--describe`, then `--plan`, then for real with
-   `--artifacts-dir ./first-team-recipe-artifacts`. Include
-   `--library "perps=$HOME/shared-library/metamask-recipe-perps"` each time.
-   For a Perps recipe use `network=testnet market=BTC`. Never place an order or
-   use mainnet in this setup proof.
-8. Show me summary.json status, every trace.json node result, and all artifact
-   paths. Then confirm the checkout is ready for a bug-fix task using the
-   installed recipe-cook skill.</code></pre></div>
-  </div>
-  <ol class="steps">
-    <li class="step" data-step="skills">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v3-skills" aria-labelledby="t3-skills">
-        <h3 class="step-title" id="t3-skills">Install the skills into your checkout</h3>
-      </div>
-      <p class="step-why">Run this from the product checkout you work in.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>yarn skills --maturity experimental --include agentic/recipe-cook,agentic/recipe-quality --save</code></pre></div>
-      <p class="step-why">
-        The agentic skills carry <code>experimental</code> maturity, so they are visible only when
-        experimental skills are enabled. <code>recipe-cook</code> is the one you want first — it owns
-        the authoring and review flows covered in <a href="v4.html">V4</a>.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p><strong>No <code>skills</code> script</strong> — not every repo has the tooling wired yet. Check the skills repo for the current install path for your checkout.</p>
-          <p><strong>The skill does not appear</strong> — confirm experimental maturity is enabled; that is the usual cause.</p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="clone">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v3-clone" aria-labelledby="t3-clone">
-        <h3 class="step-title" id="t3-clone">Clone your team's library</h3>
-      </div>
-      <p class="step-why">The perps library, as the worked example:</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"</code></pre></div>
-      <div class="note">
-        <span class="note-title">A 404 means access, not a typo</span>
-        <p>
-          The repository is private. If the clone fails with a 404, your account cannot see it yet — ask
-          for access rather than hunting for the right URL.
-        </p>
-      </div>
-      <p class="step-why">
-        Already have it somewhere? Symlink that checkout instead of making a second copy.
-      </p>
-    </li>
-    <li class="step" data-step="declare">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v3-declare" aria-labelledby="t3-declare">
-        <h3 class="step-title" id="t3-declare">Declare it</h3>
-      </div>
-      <p class="step-why">One <code>name=path</code> entry, absolute path:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>export RECIPE_LIBRARY_PATH="perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
-      <p class="step-why">Several libraries are colon-separated, and the name is how they are labelled in output:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>export RECIPE_LIBRARY_PATH="perps=$HOME/shared-library/metamask-recipe-perps:mine=$HOME/dev/my-recipes"</code></pre></div>
-      <p class="step-why">
-        Put it in your shell profile so every session has it. Per-command, <code>--library
-        perps=&lt;path&gt;</code> does the same thing and is repeatable.
-      </p>
-    </li>
-    <li class="step" data-step="verify">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v3-verify" aria-labelledby="t3-verify">
-        <h3 class="step-title" id="t3-verify">Prove discovery sees it</h3>
-      </div>
-      <p class="step-why">This is the step people skip, then spend an afternoon on.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run --list</code></pre></div>
-      <div class="out-label">Expected — library recipes tagged with your library's name</div>
-      <div class="out">runnable recipes (core)
-Inspect: mm-harness run &lt;recipe&gt; --describe
-  perps.ensure-market-state <span class="hint">[perps]</span> variant=core params=network,market,side,…
-  perps.prove-order <span class="hint">[perps]</span> variant=core params=network,market,side,order_type,…
-  perps.snapshot-market <span class="hint">[perps]</span> variant=core params=network,market
-  perps.smoke <span class="dim">[metamask]</span> variant=core — Non-mutating Perps domain smoke…
-  runner.smoke <span class="dim">[metamask]</span> variant=core — Proves the headless Core runner…</div>
-      <p class="step-why">
-        The tag is the proof: <code>[perps]</code> came from your library, <code>[metamask]</code> ships
-        with the harness. No tags from your library means it was not loaded. This example is a Core
-        checkout; Extension and Mobile print their own variants, so work from your list, not this one.
-      </p>
-      <details class="fail">
-        <summary>If it fails</summary>
-        <div class="fail-body">
-          <p><strong>Only <code>[metamask]</code> recipes</strong> — the variable is unset in this shell, or the path is wrong or relative. Echo it and check the path exists.</p>
-          <p><strong>Fewer recipes than expected</strong> — recipes declare which adapters they support. A mobile-only recipe will not appear in a core checkout. <code>--describe</code> shows the variant.</p>
-        </div>
-      </details>
-    </li>
-    <li class="step" data-step="run">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v3-run" aria-labelledby="t3-run">
-        <h3 class="step-title" id="t3-run">Read one before running it</h3>
-      </div>
-      <p class="step-why">Team recipes take parameters and many mutate testnet state.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.prove-order --describe
-<span class="p">$ </span>mm-harness run perps.prove-order market=ETH side=short order_type=limit --plan</code></pre></div>
-      <p class="step-why">
-        Drop <code>--plan</code> when the mutation and its cleanup are what you want. The perps library's
-        <code>README.md</code> is its onboarding doc, and <code>docs/AUTHORING.md</code> covers writing
-        recipes into it.
-      </p>
-    </li>
-  </ol>
-  <div class="doctrine">
-    <p>
-      <span class="k">Your team's library follows the same pattern:</span> a repo of recipes plus domain
-      actions, cloned and declared by path. Nothing about the perps setup above is perps-specific except
-      the URL.
-    </p>
-  </div>
-  <hr class="sep">
-  <div class="btn-row">
-    <a class="btn btn-primary" href="v4.html">Next: cook a recipe →</a>
-    <a class="btn btn-ghost" href="../architecture.html#libraries">Where libraries fit</a>
-    <a class="btn btn-ghost" href="index.html">Back to the series</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>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>

package/site/tutorials/v4.html DELETED Viewed

@@ -1,196 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>V4 — Cook a recipe from an acceptance criterion</title>
-<meta name="description" content="Turn one acceptance criterion into a proof with the recipe-cook skill: discover, author, validate, run.">
-<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="v4">
-<a class="skip" href="#steps">Skip to the checklist</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">Team / Perps</a>
-      <a href="../cheatsheet.html">Cheatsheet</a>
-      <a href="../architecture.html">Architecture</a>
-      <a href="index.html" aria-current="page">Tutorials</a>
-    </nav>
-  </div>
-</header>
-<div class="progress-rail">
-  <div class="wrap progress-inner">
-    <div class="progress-track" role="progressbar" aria-label="Tutorial progress" aria-valuemin="0" aria-valuemax="100" aria-valuenow="0">
-      <div class="progress-fill"></div>
-    </div>
-    <span class="progress-label">0/5 steps</span>
-    <button type="button" class="progress-reset">Reset</button>
-  </div>
-</div>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Tutorial V4 · 8–10 minutes</span>
-  <h1>Cook a recipe from an acceptance criterion</h1>
-  <p class="lede">
-    Take one criterion off a ticket and end with a rerunnable proof of it. The
-    <code>recipe-cook</code> skill drives this; you steer at the gates.
-  </p>
-  <div class="hero-meta">
-    <span>prerequisite: <a href="v3.html">V3</a></span>
-    <span>skill maturity: experimental</span>
-  </div>
-</section>
-<section class="wrap">
-  <div class="vid-thumb" style="border-radius:var(--radius);border:1px solid var(--line);margin-bottom:1.5rem">
-    <div style="text-align:center;padding:1rem">
-      <div class="vid-id" style="font-size:2.6rem">V4</div>
-      <p style="color:var(--text-dim);margin:.5rem 0 0;font-size:.92rem">Video recording in progress</p>
-    </div>
-  </div>
-  <h2>The flow</h2>
-  <p>Cook classifies the request, then runs one checklist to completion.</p>
-  <div class="stack">
-    <div class="layer layer-static">
-      <span class="layer-n">1</span><span class="layer-name">Classify</span>
-      <span class="layer-sub">dev · fix-bug · review-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">List and select a template</span>
-      <span class="layer-sub">discovery, then your pick</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">3</span><span class="layer-name">Materialize one task</span>
-      <span class="layer-sub">an immutable checklist, one harness</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">4</span><span class="layer-name">Execute the gates</span>
-      <span class="layer-sub">author, validate, run, mark</span>
-    </div>
-  </div>
-  <p>
-    Template discovery runs through <code>mm-harness execution-template</code>, the same discovery
-    contract as actions and recipes. Your team's library can supply its own templates.
-  </p>
-  <div class="note">
-    <span class="note-title">Step 2 stops for you</span>
-    <p>
-      For <code>dev</code> and <code>fix-bug</code>, Cook prints the compatible template IDs with a
-      recommendation and then stops. It takes no further action until you reply with a number or an
-      exact ID. This is the steering point: the flow is chosen by you, not inferred.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="steps">Follow along</h2>
-  <p>Pick a small, real criterion — one observable behaviour, not a whole epic.</p>
-  <ol class="steps">
-    <li class="step" data-step="invoke">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v4-invoke" aria-labelledby="t4-invoke">
-        <h3 class="step-title" id="t4-invoke">Start Cook in your checkout</h3>
-      </div>
-      <p class="step-why">In Claude or Cursor, invoke the skill with your task in plain language:</p>
-      <div class="cmd"><pre><code>/mms-recipe-cook Prove that a resting limit order can be repriced without losing its trigger</code></pre></div>
-      <p class="step-why">In Codex, the same skill is addressed as <code>$mms-recipe-cook</code>. Product is auto-detected; you will not be asked which repo you are in.</p>
-    </li>
-    <li class="step" data-step="select">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v4-select" aria-labelledby="t4-select">
-        <h3 class="step-title" id="t4-select">Choose the template</h3>
-      </div>
-      <p class="step-why">
-        Cook lists compatible IDs with one recommended. Reply with the number. It recommends an
-        interactive template when human judgment is still needed and an autonomous one when it is not.
-      </p>
-    </li>
-    <li class="step" data-step="discover">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v4-discover" aria-labelledby="t4-discover">
-        <h3 class="step-title" id="t4-discover">Watch discovery set the boundary</h3>
-      </div>
-      <p class="step-why">
-        Before authoring anything, the vocabulary is fixed. Run it yourself to see what Cook is choosing
-        from:
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness actions --categories
-<span class="p">$ </span>mm-harness actions --action assert_orders</code></pre></div>
-      <p class="step-why">
-        An action outside this list cannot be written into a working recipe — validation rejects it
-        before execution. That constraint is what makes the output trustworthy rather than plausible.
-      </p>
-    </li>
-    <li class="step" data-step="plan">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v4-plan" aria-labelledby="t4-plan">
-        <h3 class="step-title" id="t4-plan">Validate before executing</h3>
-      </div>
-      <p class="step-why">Exit 5 means the recipe is wrong and nothing ran.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run ./my-recipe.json --plan</code></pre></div>
-      <div class="out"><span class="ok">✓</span> [static] validate.schema: recipe document schema + action existence/platform vs the adapter manifest
-<span class="dim">·</span> [conditional] execute.nodes: would execute 4 recipe node(s)</div>
-    </li>
-    <li class="step" data-step="prove">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v4-prove" aria-labelledby="t4-prove">
-        <h3 class="step-title" id="t4-prove">Run it, then try to break it</h3>
-      </div>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run ./my-recipe.json --artifacts-dir ./proof</code></pre></div>
-      <div class="doctrine">
-        <p>
-          <span class="k">Then revert the change and run it again.</span> A recipe you have watched fail
-          for the right reason is one you can trust when it passes. If reverting the behaviour leaves it
-          green, it is not proving what you think.
-        </p>
-      </div>
-      <p class="step-why">
-        Expect one failure-and-fix loop during authoring. Each error names its own next command; follow
-        it rather than guessing. <a href="../recipes.html#falsifiability">The falsifiability test</a>
-        lists the four shapes that pass for the wrong reasons.
-      </p>
-    </li>
-  </ol>
-  <hr class="sep">
-  <div class="btn-row">
-    <a class="btn btn-primary" href="v5.html">Next: PR QA review →</a>
-    <a class="btn btn-ghost" href="../recipes.html">What makes a recipe good</a>
-    <a class="btn btn-ghost" href="index.html">Back to the series</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>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>

package/site/tutorials/v5.html DELETED Viewed

@@ -1,164 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>V5 — PR QA review from one link</title>
-<meta name="description" content="Give the review skill one pull request URL and get a per-criterion verdict table backed by on-device evidence.">
-<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="v5">
-<a class="skip" href="#flow">Skip to the flow</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">Team / Perps</a>
-      <a href="../cheatsheet.html">Cheatsheet</a>
-      <a href="../architecture.html">Architecture</a>
-      <a href="index.html" aria-current="page">Tutorials</a>
-    </nav>
-  </div>
-</header>
-<div class="progress-rail">
-  <div class="wrap progress-inner">
-    <div class="progress-track" role="progressbar" aria-label="Tutorial progress" aria-valuemin="0" aria-valuemax="100" aria-valuenow="0">
-      <div class="progress-fill"></div>
-    </div>
-    <span class="progress-label">0/4 steps</span>
-    <button type="button" class="progress-reset">Reset</button>
-  </div>
-</div>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Tutorial V5 · 8–10 minutes</span>
-  <h1>PR QA review from one link</h1>
-  <p class="lede">
-    One pull request URL in, a per-criterion verdict table with evidence paths out. You confirm nothing
-    gets posted.
-  </p>
-  <div class="hero-meta">
-    <span class="badge soon">skill not merged yet</span>
-    <span>maturity: experimental</span>
-  </div>
-</section>
-<section class="wrap">
-  <div class="vid-thumb" style="border-radius:var(--radius);border:1px solid var(--line);margin-bottom:1.5rem">
-    <div style="text-align:center;padding:1rem">
-      <div class="vid-id" style="font-size:2.6rem">V5</div>
-      <p style="color:var(--text-dim);margin:.5rem 0 0;font-size:.92rem">Video recording in progress</p>
-    </div>
-  </div>
-  <div class="note">
-    <span class="note-title">Status: shipping, not yet merged</span>
-    <p>
-      The PR QA review skill is on a branch, not on the skills repo's main branch. This page describes
-      the flow as built so you know what is coming; there is no install command here yet, because one
-      that does not resolve is worse than none. <a href="v4.html">V4's</a> <code>recipe-cook</code> is
-      merged and available today — the review flow is one of its modes.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="flow">The flow</h2>
-  <ol class="steps">
-    <li class="step" data-step="url">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v5-url" aria-labelledby="t5-url">
-        <h3 class="step-title" id="t5-url">One URL, matched to your checkout</h3>
-      </div>
-      <p class="step-why">
-        Exactly one pull request from <code>metamask-mobile</code> or <code>metamask-extension</code>. A
-        URL for the other client is rejected before any checkout or runtime work — the review runs
-        against a real build, so it has to be the right one. Given no URL, it reads the current branch's
-        pull request.
-      </p>
-    </li>
-    <li class="step" data-step="ac">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v5-ac" aria-labelledby="t5-ac">
-        <h3 class="step-title" id="t5-ac">Criteria are extracted, then frozen</h3>
-      </div>
-      <p class="step-why">
-        Supply criteria and they are preserved verbatim, never merged with or overwritten by the pull
-        request body. Supply none and they are extracted from it. Either way they are frozen before any
-        runtime work starts, so the thing being proven cannot drift to match what turned out to be
-        provable.
-      </p>
-      <div class="note blue">
-        <span class="note-title">Missing criteria are a finding, not a gap to fill</span>
-        <p>
-          A pull request with nothing to extract produces a hygiene finding. The skill does not invent
-          criteria to have something to test.
-        </p>
-      </div>
-    </li>
-    <li class="step" data-step="run">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v5-run" aria-labelledby="t5-run">
-        <h3 class="step-title" id="t5-run">Proof runs on a real device</h3>
-      </div>
-      <p class="step-why">
-        The branch is checked out, the app launched under harness control, and each criterion exercised
-        against the running build. Evidence lands in a bundle you can open — the same structure
-        <a href="v2.html">V2</a> walks.
-      </p>
-    </li>
-    <li class="step" data-step="verdict">
-      <div class="step-head">
-        <input type="checkbox" class="step-check" id="v5-verdict" aria-labelledby="t5-verdict">
-        <h3 class="step-title" id="t5-verdict">A verdict table you post yourself</h3>
-      </div>
-      <p class="step-why">
-        Output is a QA report plus a proposed review reply, per criterion, with evidence paths.
-      </p>
-      <div class="doctrine">
-        <p>
-          <span class="k">It never posts.</span> The reply comes back for you to read, edit, and submit.
-          A machine-generated review that appears on a colleague's pull request without a human deciding
-          to send it is not review — it is noise with your name on it.
-        </p>
-      </div>
-      <p class="step-why">
-        The verdict that matters most is the honest one: a criterion the surface genuinely cannot
-        demonstrate is reported as needing a human, not quietly passed. A gesture-driven interaction with
-        no automatable surface is the standard example — it gets classified, not faked.
-      </p>
-    </li>
-  </ol>
-  <hr class="sep">
-  <div class="btn-row">
-    <a class="btn btn-primary" href="v6.html">Next: release validation →</a>
-    <a class="btn btn-ghost" href="../reviewers.html">How to read the evidence it produces</a>
-    <a class="btn btn-ghost" href="index.html">Back to the series</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>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>