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

@deeeed/metamask-harness 0.46.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 (42) hide show

package/CHANGELOG.md +28 -0
package/README.md +1 -1
package/adapters/manifest.json +12 -4
package/adapters/mobile/wait-for-bridge.cjs +550 -0
package/adapters/mobile/wait-for-bridge.sh +11 -148
package/bin/mm-harness +7 -2
package/dist/adapters/mobile/prepare.js +26 -18
package/dist/adapters/mobile/runtime-decision.js +1 -0
package/dist/cli-commands.js +2 -0
package/dist/command-contract.js +7 -0
package/dist/commands/checklist.js +1 -0
package/dist/commands/help.js +76 -0
package/dist/commands/parse-args.js +2 -1
package/dist/commands/recipe-quality.js +1 -1
package/dist/commands/tutorial.js +46 -0
package/dist/mm-harness-cli.js +45 -6
package/docs/CONTRIBUTING.md +2 -0
package/docs/QA.md +2 -2
package/library/actions/mobile/perps/perps.mjs +1 -1
package/package.json +2 -2
package/scripts/site-contrast.mjs +6 -2
package/site/assets/help-recipes.json +113 -0
package/site/architecture.html +0 -497
package/site/assets/metamask-fox.svg +0 -24
package/site/assets/progress.mjs +0 -323
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 -692
package/site/index.html +0 -184
package/site/perps-advanced-orders-qa.html +0 -96
package/site/perps.html +0 -265
package/site/recipes.html +0 -423
package/site/reviewers.html +0 -375
package/site/tutorials/index.html +0 -181
package/site/tutorials/v1.html +0 -212
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/v6.html DELETED Viewed

@@ -1,166 +0,0 @@
-<!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="icon" href="../assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="../assets/style.css?v=4">
-</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">
-      <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 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 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/v7.html DELETED Viewed

@@ -1,185 +0,0 @@
-<!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="icon" href="../assets/metamask-fox.svg" type="image/svg+xml">
-<link rel="stylesheet" href="../assets/style.css?v=4">
-</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">
-      <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/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 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>