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/v7.html ADDED Viewed

@@ -0,0 +1,184 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>V7 — A ticket end to end</title>
+<meta name="description" content="One real ticket from assignment to a pull request that carries proof, and what the reviewer sees.">
+<link rel="stylesheet" href="../assets/style.css">
+</head>
+<body data-progress-page="v7">
+<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/6 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 V7 · 10 minutes</span>
+  <h1>A ticket end to end</h1>
+  <p class="lede">
+    How the pieces combine on ordinary work: one ticket, implemented, proven, and opened as a pull
+    request a reviewer can check without rebuilding it themselves.
+  </p>
+  <div class="hero-meta">
+    <span>prerequisites: <a href="v3.html">V3</a> and <a href="v4.html">V4</a></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">V7</div>
+      <p style="color:var(--text-dim);margin:.5rem 0 0;font-size:.92rem">Video recording in progress</p>
+    </div>
+  </div>
+  <div class="doctrine">
+    <p>
+      <span class="k">The through-line:</span> you steered at every gate, the system did the labour, and
+      the pull request carries proof instead of claims.
+    </p>
+  </div>
+</section>
+<section class="wrap">
+  <h2 id="steps">The walkthrough</h2>
+  <ol class="steps">
+    <li class="step" data-step="setup">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-setup" aria-labelledby="t7-setup">
+        <h3 class="step-title" id="t7-setup">Start from a working checkout</h3>
+      </div>
+      <p class="step-why">Current harness, library declared, app reachable.</p>
+      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness update
+<span class="p">$ </span>mm-harness doctor
+<span class="p">$ </span>mm-harness run --list</code></pre></div>
+      <p class="step-why">
+        If your team's recipes are not in that list, fix it now rather than mid-task —
+        <a href="v3.html#steps">V3</a> covers it.
+      </p>
+    </li>
+    <li class="step" data-step="criteria">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-criteria" aria-labelledby="t7-criteria">
+        <h3 class="step-title" id="t7-criteria">Read the ticket for what is observable</h3>
+      </div>
+      <p class="step-why">
+        Separate the criteria that describe behaviour someone could watch happen from the ones that
+        describe intent. The first kind is what a recipe can prove. Naming that split up front decides
+        the shape of everything after it.
+      </p>
+    </li>
+    <li class="step" data-step="implement">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-implement" aria-labelledby="t7-implement">
+        <h3 class="step-title" id="t7-implement">Implement, using the harness to look</h3>
+      </div>
+      <p class="step-why">
+        <code>call</code> is the fast loop while developing — one action against the running app, no
+        recipe needed. This is the same execution path a recipe uses, so what works here works there.
+      </p>
+      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness call read_state
+<span class="p">$ </span>mm-harness call navigate page=perps
+<span class="p">$ </span>mm-harness logs</code></pre></div>
+    </li>
+    <li class="step" data-step="cook">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-cook" aria-labelledby="t7-cook">
+        <h3 class="step-title" id="t7-cook">Cook the proof for the criteria</h3>
+      </div>
+      <p class="step-why">
+        <a href="v4.html">V4's</a> flow, pointed at this ticket. Author against the discovered actions,
+        validate with <code>--plan</code>, run it.
+      </p>
+      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run ./proof.json --plan
+<span class="p">$ </span>mm-harness run ./proof.json --artifacts-dir ./proof-artifacts</code></pre></div>
+      <p class="step-why">
+        Then revert your change and run it again. Green after a revert means the recipe is not testing
+        your work.
+      </p>
+    </li>
+    <li class="step" data-step="pr">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-pr" aria-labelledby="t7-pr">
+        <h3 class="step-title" id="t7-pr">Open the pull request with the evidence</h3>
+      </div>
+      <p class="step-why">
+        Check your diff before you push, then link the criteria to the nodes that prove them. A reviewer
+        should not have to guess which part of the bundle answers which criterion.
+      </p>
+      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness check diff --profile fast</code></pre></div>
+      <p class="step-why">
+        The recipe is the durable half. It stays in the library and fails later if someone breaks the
+        behaviour — the difference between evidence and a regression test is only whether you keep it.
+      </p>
+    </li>
+    <li class="step" data-step="review">
+      <div class="step-head">
+        <input type="checkbox" class="step-check" id="v7-review" aria-labelledby="t7-review">
+        <h3 class="step-title" id="t7-review">Look at it as the reviewer</h3>
+      </div>
+      <p class="step-why">
+        Open your own bundle the way <a href="v2.html">V2</a> does: read the intents in order and ask
+        whether they add up to the claim in the description. Anything you cannot answer from the trace is
+        something you are asking a colleague to take on trust.
+      </p>
+      <div class="cmd"><pre><code><span class="p">$ </span>cat proof-artifacts/report.md</code></pre></div>
+      <p class="step-why">
+        If the agent's checklist asked for learnings, they are written beside the evidence — worth
+        reading before you close the ticket, and the raw material for what eventually reaches
+        <a href="../architecture.html#loop">the team's shared knowledge</a>.
+      </p>
+    </li>
+  </ol>
+  <hr class="sep">
+  <div class="btn-row">
+    <a class="btn btn-primary" href="index.html">Back to the series</a>
+    <a class="btn btn-ghost" href="../reviewers.html">The reviewer's guide</a>
+    <a class="btn btn-ghost" href="../cheatsheet.html">Cheatsheet</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>