npm - @deeeed/metamask-harness - Versions diffs - 0.28.0 → 0.29.0 - Mend

@deeeed/metamask-harness 0.28.0 → 0.29.0

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

package/CHANGELOG.md +19 -0
package/README.md +41 -0
package/adapters/extension/build-lavamoat.sh +2 -1
package/adapters/extension/ensure-browser.sh +82 -9
package/adapters/extension/inject.mjs +1 -0
package/adapters/extension/launch-browser.cjs +83 -1
package/adapters/extension/lib/chrome-args.cjs +325 -1
package/adapters/extension/lib/playwright-cdp.cjs +34 -0
package/adapters/extension/lib/slot-title.cjs +2 -4
package/adapters/extension/lib/validation-launch-supervisor.cjs +292 -0
package/adapters/extension/lib/validation-process-ownership.cjs +69 -0
package/adapters/extension/reattach.sh +2 -1
package/adapters/extension/sidepanel-toggle.sh +14 -96
package/adapters/extension/wallet-fixture-state.cjs +8 -31
package/adapters/manifest.json +16 -0
package/adapters/shared/private-atomic-write.cjs +47 -0
package/adapters/shared/setup-base.sh +864 -0
package/dist/adapters/extension/runtime.js +367 -24
package/dist/adapters/extension/validation-process-ownership.js +10 -0
package/dist/cli-commands.js +1 -0
package/dist/command-contract.js +12 -0
package/dist/commands/launch/extension.js +130 -19
package/dist/commands/setup-base.js +24 -0
package/dist/mm-harness-cli.js +28 -2
package/library/actions/extension/analytics/consent.mjs +203 -0
package/library/actions/extension/analytics/set_consent.mjs +19 -143
package/library/actions/extension/perps/perps.mjs +2 -16
package/library/actions/extension/perps/state.mjs +20 -0
package/library/actions/extension/wallet/list_accounts.mjs +3 -25
package/library/actions/extension/wallet/read_state.mjs +3 -23
package/library/actions/extension/wallet/select_account.mjs +6 -33
package/library/actions/extension/wallet/setup.mjs +2 -20
package/library/actions/extension/wallet/state.mjs +111 -0
package/library/recipes/runner/action-validation.extension.recipe.json +1 -1
package/library/recipes/runner/action-validation.mobile.recipe.json +1 -1
package/package.json +7 -4
package/scripts/site-contrast.mjs +538 -0
package/site/architecture.html +415 -0
package/site/assets/progress.mjs +272 -0
package/site/assets/style.css +808 -0
package/site/cheatsheet.html +305 -0
package/site/index.html +643 -0
package/site/recipes.html +396 -0
package/site/reviewers.html +374 -0
package/site/tutorials/index.html +180 -0
package/site/tutorials/v1.html +211 -0
package/site/tutorials/v2.html +207 -0
package/site/tutorials/v3.html +214 -0
package/site/tutorials/v4.html +195 -0
package/site/tutorials/v5.html +163 -0
package/site/tutorials/v6.html +165 -0
package/site/tutorials/v7.html +184 -0

package/site/tutorials/v4.html ADDED Viewed

@@ -0,0 +1,195 @@
+<!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="stylesheet" href="../assets/style.css">
+</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">
+      <span class="brand-mark" aria-hidden="true"></span>
+      <span class="brand-name">mm-harness</span>
+    </a>
+    <nav class="nav" aria-label="Main">
+      <a href="../index.html">Start Here</a>
+      <a href="../recipes.html">Recipes</a>
+      <a href="../cheatsheet.html">Cheatsheet</a>
+      <a href="../architecture.html">Architecture</a>
+      <a href="index.html" aria-current="page">Tutorials</a>
+      <a href="../reviewers.html">For Reviewers</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 the MetaMask agentic coding workflow. Not official MetaMask product documentation.</p>
+    <p>Verified against mm-harness 0.26+.</p>
+  </div>
+</footer>
+<script type="module" src="../assets/progress.mjs"></script>
+</body>
+</html>

package/site/tutorials/v5.html ADDED Viewed

@@ -0,0 +1,163 @@
+<!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="stylesheet" href="../assets/style.css">
+</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">
+      <span class="brand-mark" aria-hidden="true"></span>
+      <span class="brand-name">mm-harness</span>
+    </a>
+    <nav class="nav" aria-label="Main">
+      <a href="../index.html">Start Here</a>
+      <a href="../recipes.html">Recipes</a>
+      <a href="../cheatsheet.html">Cheatsheet</a>
+      <a href="../architecture.html">Architecture</a>
+      <a href="index.html" aria-current="page">Tutorials</a>
+      <a href="../reviewers.html">For Reviewers</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 the MetaMask agentic coding workflow. Not official MetaMask product documentation.</p>
+    <p>Verified against mm-harness 0.26+.</p>
+  </div>
+</footer>
+<script type="module" src="../assets/progress.mjs"></script>
+</body>
+</html>

package/site/tutorials/v6.html ADDED Viewed

@@ -0,0 +1,165 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>V6 — Release validation</title>
+<meta name="description" content="Validate one team's changes on a frozen release candidate, with a four-verdict vocabulary that includes NOT RUN.">
+<link rel="stylesheet" href="../assets/style.css">
+</head>
+<body data-progress-page="v6">
+<a class="skip" href="#flow">Skip to the flow</a>
+<header class="topbar">
+  <div class="wrap topbar-inner">
+    <a class="brand" href="../index.html">
+      <span class="brand-mark" aria-hidden="true"></span>
+      <span class="brand-name">mm-harness</span>
+    </a>
+    <nav class="nav" aria-label="Main">
+      <a href="../index.html">Start Here</a>
+      <a href="../recipes.html">Recipes</a>
+      <a href="../cheatsheet.html">Cheatsheet</a>
+      <a href="../architecture.html">Architecture</a>
+      <a href="index.html" aria-current="page">Tutorials</a>
+      <a href="../reviewers.html">For Reviewers</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 V6 · 6 minutes</span>
+  <h1>Release validation</h1>
+  <p class="lede">
+    One release candidate, one team's changes, one report. For leads and QA deciding whether a build is
+    ready for sign-off.
+  </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">V6</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>
+      Like <a href="v5.html">V5</a>, this skill lives on a branch rather than the skills repo's main
+      branch. No install command here until it lands.
+    </p>
+  </div>
+  <p>
+    <a href="v5.html">V5</a> reviews one pull request head. This sits a layer above: it takes the team's
+    changes that actually shipped into one frozen release head and validates their assembled flows on
+    that build.
+  </p>
+</section>
+<section class="wrap">
+  <h2 id="flow">The flow</h2>
+  <ol class="steps">
+    <li class="step" data-step="target">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v6-target" aria-labelledby="t6-target">
+        <h3 class="step-title" id="t6-target">Two things, both exact</h3>
+      </div>
+      <p class="step-why">
+        One release target — a <code>release/X.Y.Z</code> ref, its release pull request, or an
+        unambiguous version — and one team scope, given as explicit pull request URLs, owned paths,
+        release labels, or a repository team definition. Ambiguity in either is refused rather than
+        guessed, because a report scoped to the wrong changes is worse than no report.
+      </p>
+    </li>
+    <li class="step" data-step="assemble">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v6-assemble" aria-labelledby="t6-assemble">
+        <h3 class="step-title" id="t6-assemble">Criteria assembled across the release</h3>
+      </div>
+      <p class="step-why">
+        It reuses the same acceptance-criteria contract as PR review, then combines the criteria from
+        every in-scope change into the user flows they add up to on the release build. A flow can break
+        from the interaction of two individually correct changes; that is the class of problem this
+        catches and per-PR review cannot.
+      </p>
+    </li>
+    <li class="step" data-step="verdicts">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v6-verdicts" aria-labelledby="t6-verdicts">
+        <h3 class="step-title" id="t6-verdicts">Four verdicts, not two</h3>
+      </div>
+      <div class="table-scroll">
+        <table>
+          <thead><tr><th>Verdict</th><th>Means</th></tr></thead>
+          <tbody>
+            <tr><td><span class="verdict pass">PASS</span></td><td>Demonstrated on the release build, with evidence.</td></tr>
+            <tr><td><span class="verdict fail">FAIL</span></td><td>Exercised and did not hold. A real result.</td></tr>
+            <tr><td><code>UNTESTABLE</code></td><td>The surface cannot demonstrate it. Needs a human.</td></tr>
+            <tr><td><code>NOT RUN</code></td><td>In scope, not attempted. Stated rather than omitted.</td></tr>
+          </tbody>
+        </table>
+      </div>
+      <p class="step-why">
+        <code>NOT RUN</code> is the one that keeps the report honest. A run that skipped something says
+        so, instead of leaving a silent gap that reads as coverage.
+      </p>
+    </li>
+    <li class="step" data-step="signoff">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v6-signoff" aria-labelledby="t6-signoff">
+        <h3 class="step-title" id="t6-signoff">Ready for sign-off, which is not sign-off</h3>
+      </div>
+      <div class="doctrine">
+        <p>
+          <span class="k">A first autonomous release QA result, not an approval.</span> The report frames
+          itself as ready for team QA sign-off. The sign-off is still a person's, and the report is the
+          evidence they read to give it.
+        </p>
+      </div>
+      <p class="step-why">
+        What changes is where the human starts: from a report with per-criterion verdicts and evidence
+        paths, rather than from a build and a list of tickets.
+      </p>
+    </li>
+  </ol>
+  <hr class="sep">
+  <div class="btn-row">
+    <a class="btn btn-primary" href="v7.html">Next: a ticket end to end →</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 the MetaMask agentic coding workflow. Not official MetaMask product documentation.</p>
+    <p>Verified against mm-harness 0.26+.</p>
+  </div>
+</footer>
+<script type="module" src="../assets/progress.mjs"></script>
+</body>
+</html>