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/CHANGELOG.md CHANGED Viewed

@@ -2,6 +2,13 @@
 ## Unreleased
+## 0.47.1 - 2026-09-04
+### Fixed
+- Open the tutorial on the protected MetaMask GitHub Pages site instead of the public unpkg CDN.
+- Stop shipping the static HTML site in the public npm package; retain only the recipe-help JSON required by the CLI.
 ## 0.47.0 - 2026-09-04
 ### Added

package/dist/commands/tutorial.js CHANGED Viewed

@@ -1,11 +1,11 @@
 import { spawnSync } from "node:child_process";
 import { parseArgs } from "./parse-args.js";
-const PACKAGE_NAME = "@deeeed/metamask-harness";
-function recipeTutorialUrl(harnessVersion, runMode = process.env.MM_HARNESS_RUN_MODE) {
+const PROTECTED_TUTORIAL_URL = "https://glowing-chainsaw-gwzrn8k.pages.github.io/recipes.html#agent-method";
+function recipeTutorialUrl(runMode = process.env.MM_HARNESS_RUN_MODE) {
   if (runMode === "src") {
     return "http://127.0.0.1:8765/site/recipes.html#agent-method";
   }
-  return `https://unpkg.com/${PACKAGE_NAME}@${harnessVersion}/site/recipes.html#agent-method`;
+  return PROTECTED_TUTORIAL_URL;
 }
 function openUrl(url) {
   const command = process.platform === "darwin" ? ["open", url] : process.platform === "win32" ? ["cmd", "/c", "start", "", url] : ["xdg-open", url];
@@ -14,7 +14,7 @@ function openUrl(url) {
 }
 function handleTutorial(argv, context) {
   const parsed = parseArgs(argv, "tutorial");
-  const url = recipeTutorialUrl(context.harnessVersion);
+  const url = recipeTutorialUrl();
   const noOpen = parsed.options.noOpen === true;
   const opened = noOpen ? false : (context.open ?? openUrl)(url);
   const payload = {

package/dist/mm-harness-cli.js CHANGED Viewed

@@ -41,12 +41,12 @@ Example:
   },
   {
     name: "tutorial",
-    summary: "Open the visual recipe tutorial for this harness version.",
+    summary: "Open the protected visual recipe tutorial.",
     example: "mm-harness tutorial",
     helpText: `mm-harness tutorial [flags]
   Source checkouts open the local tutorial on port 8765. Installed releases
-  open the tutorial published with that exact harness version.
+  open the protected MetaMask GitHub Pages site.
   --no-open                          Print the tutorial URL without opening it
   --json                             Print version, URL, and open status as JSON

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.47.0",
+  "version": "0.47.1",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"
@@ -64,7 +64,7 @@
     "dist",
     "adapters",
     "library",
-    "site",
+    "site/assets/help-recipes.json",
     "scripts/completions.sh",
     "scripts/install-completions.sh",
     "scripts/site-contrast.mjs",

package/site/architecture.html DELETED Viewed

@@ -1,497 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>Architecture — how the pieces fit</title>
-<meta name="description" content="Skills, mm-harness, team recipe libraries, product repos: what lives where, the three workflows, and the mistakes newcomers make.">
-<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="architecture">
-<a class="skip" href="#stack">Skip to the stack map</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" aria-current="page">Architecture</a>
-      <a href="tutorials/index.html">Tutorials</a>
-    </nav>
-  </div>
-</header>
-<main>
-<section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">The stack behind a recipe</span>
-  <h1>How the pieces fit together</h1>
-  <p class="lede">
-    The recipe is the unit of trust; the rest of the stack runs it. Four moving parts, two of which
-    people routinely confuse. What each layer is, where it lives, which workflow you are in, and the
-    mistakes that cost newcomers their first afternoon.
-  </p>
-</section>
-<section class="wrap">
-  <h2 id="model">The one-paragraph model</h2>
-  <div class="doctrine">
-    <p>
-      <span class="k">A recipe proves a task with actions.</span> Recipes are JSON graphs of typed
-      actions; <code>mm-harness</code> executes them against a real app and produces an evidence bundle
-      a reviewer can trust. <strong>Skills</strong> teach an agent a workflow — author a recipe, review
-      a PR, validate a release — and are the layer you work through; they call the harness, which runs
-      the recipe. <strong>Recipe libraries</strong> hold each team's recipes and domain actions.
-      Compose in that order, against the product repo under test.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="stack">The layers</h2>
-  <p>Click a layer to see what it is responsible for and when you touch it.</p>
-  <div class="stack">
-    <button type="button" class="layer" aria-expanded="false" aria-controls="l-skills">
-      <span class="layer-n">1</span>
-      <span class="layer-name">Skills</span>
-      <span class="layer-sub">the workflow an agent follows</span>
-    </button>
-    <div class="layer-detail" id="l-skills" hidden>
-      <p>
-        A packaged workflow — author a recipe from a criterion, review a pull request, validate a
-        release — turning "figure it out" into a procedure with gates you can steer.
-      </p>
-      <p>
-        Skills come from the public <code>MetaMask/skills</code> repo plus the internal
-        <code>Consensys/skills</code> overlay, which needs access to that org; private skills override
-        public ones on a name collision. Clone each, point <code>METAMASK_SKILLS_DIR</code> and
-        <code>CONSENSYS_SKILLS_DIR</code> at them, then install per checkout with
-        <code>yarn skills</code>. <strong>You do not need skills to run a recipe</strong>, only to have
-        an agent follow a proven workflow instead of improvising one.
-        <a href="tutorials/v3.html">V3 walks the install.</a>
-      </p>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <button type="button" class="layer" aria-expanded="false" aria-controls="l-harness">
-      <span class="layer-n">2</span>
-      <span class="layer-name">mm-harness</span>
-      <span class="layer-sub">execution and evidence</span>
-    </button>
-    <div class="layer-detail" id="l-harness" hidden>
-      <p>
-        The CLI: launches the app, exposes the action vocabulary, executes recipe graphs against a real
-        build, writes the evidence. The only layer everyone needs, and the only one installed globally:
-      </p>
-      <div class="cmd"><pre><code><span class="p">$ </span>npm i -g @deeeed/metamask-harness@latest</code></pre></div>
-      <p style="margin-bottom:0">
-        It owns MetaMask runtime control and the domain capabilities; the generic graph engine and the
-        evidence schemas underneath it are separate packages it depends on.
-      </p>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <button type="button" class="layer" aria-expanded="false" aria-controls="l-libs">
-      <span class="layer-n">3</span>
-      <span class="layer-name">Team recipe libraries</span>
-      <span class="layer-sub">your team's recipes and domain actions</span>
-    </button>
-    <div class="layer-detail" id="l-libs" hidden>
-      <p>
-        A team-owned repo of reusable recipes plus the domain actions they need. The harness ships a
-        bundled library so a fresh install can prove something immediately; your team's library is where
-        the recipes that matter to your work live.
-      </p>
-      <p>Libraries must be declared, or the harness only sees the bundled set:</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>export RECIPE_LIBRARY_PATH="perps=$HOME/dev/my-recipe-library"
-<span class="p">$ </span>mm-harness run &lt;recipe&gt; --library perps=$HOME/dev/my-recipe-library</code></pre></div>
-      <p style="margin-bottom:0">
-        Each library carries its own setup notes — read those before running anything domain-specific.
-      </p>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <button type="button" class="layer" aria-expanded="false" aria-controls="l-product">
-      <span class="layer-n">4</span>
-      <span class="layer-name">Product repos</span>
-      <span class="layer-sub">the thing under test</span>
-    </button>
-    <div class="layer-detail" id="l-product" hidden>
-      <p>
-        <code>metamask-extension</code>, <code>metamask-mobile</code>, and <code>core</code>. Recipes
-        execute against a real build, never a mock. Run <code>mm-harness</code> from inside the checkout
-        and it detects the product, ports, and runtime paths.
-      </p>
-      <p style="margin-bottom:0">
-        They differ, and the harness says so rather than pretending otherwise: Core is headless with
-        nothing to launch and no UI actions; Extension and iOS can record full-run video; Android
-        replay video is not implemented yet, so use screenshot evidence there.
-      </p>
-    </div>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="spec">The spec underneath</h2>
-  <p>
-    <code>mm-harness</code> implements <strong><a href="https://farmslot.io">Farmslot</a></strong>, a versioned specification for agentic
-    proof work. The CLI is one implementation of it, not the thing itself.
-  </p>
-  <div class="stack">
-    <div class="layer layer-static">
-      <span class="layer-n">1</span>
-      <span class="layer-name">The specification</span>
-      <span class="layer-sub">recipes, action manifests, observations and traces, evidence, handoff</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">2</span>
-      <span class="layer-name">mm-harness implements it</span>
-      <span class="layer-sub">for MetaMask products</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">3</span>
-      <span class="layer-name">Skills drive it</span>
-      <span class="layer-sub">the workflows an agent follows</span>
-    </div>
-  </div>
-  <p>Schemas are published and versioned. Every recipe carries the URL it validates against:</p>
-  <div class="out">"$schema": <a href="https://farmslot.io/schemas/recipe-v1.schema.json">"https://farmslot.io/schemas/recipe-v1.schema.json"</a></div>
-  <p>
-    Action manifests carry <code>action-manifest-v1</code>; evidence records its own
-    <code>schemaVersion</code> and <code>runner_protocol_version</code>. Versioning is what keeps a
-    bundle readable by tooling written after it was produced.
-  </p>
-  <h3>Why the spec is the scaling mechanism</h3>
-  <p>
-    The recipe you run from the CLI is the same artifact a control plane dispatches to a worker,
-    monitors, and gates — dispatch, worker, self-review, human gate, publication, each step speaking
-    these contracts. Evidence returns in the same shape either way, so a fleet result is reviewable by
-    whoever wrote the recipe. Parity is structural: one spec, both sides.
-  </p>
-  <p>
-    That is what makes the trust layer scale. A proof written once becomes a permanent guard: it is
-    replayed by whoever changes that code next, it stays readable as evidence no matter who or what ran
-    it, and the bug it was written for cannot quietly return. Review does not get weaker as volume
-    grows.
-  </p>
-  <p>The seam shows in the CLI's own help — the flags a control plane supplies:</p>
-  <div class="out">managed trust boundary (not needed for normal runs; <a href="https://farmslot.io">Farmslot</a> supplies it):
-  --source-trust, --source-kind, --source-name, --source-digest,
-  <span class="hint">--approve-plan</span> (binds approval to the exact reviewed plan)</div>
-  <p>Approve a plan and only that plan runs — which is what keeps the gate a gate.</p>
-  <div class="note">
-    <span class="note-title">What you actually need</span>
-    <p>
-      The <a href="https://farmslot.io">Farmslot</a> control plane is <strong>experimental and sole-maintained</strong>. Nothing this site
-      teaches requires it — the harness, recipes, and skills are complete on their own, and the CLI says
-      as much: those flags are "not needed for normal runs". The specification is what you adopt; the
-      control plane is one consumer of it.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="loop">The improvement loop</h2>
-  <p>
-    A recipe guards the regression it was written for. This is how a team catches the ones nobody has
-    written down yet — each run leaving the next one better informed.
-  </p>
-  <div class="doctrine">
-    <p>
-      <span class="k">Learnings are written, not collected.</span> The checklist an agent follows carries
-      a step instructing it to write what it learned as human-readable markdown, bundled beside the
-      execution plan and the evidence. A run ends with prose — what was hard, what surprised it, what
-      the next run should know — sitting next to the proof. A deliverable, not telemetry: nobody mines
-      traces for insight; the agent is asked and answers.
-    </p>
-  </div>
-  <h3>The chain</h3>
-  <div class="stack">
-    <div class="layer layer-static">
-      <span class="layer-n">1</span>
-      <span class="layer-name">A checklist step asks for learnings</span>
-      <span class="layer-sub">part of the execution plan</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">2</span>
-      <span class="layer-name">The run writes learnings.md beside its evidence</span>
-      <span class="layer-sub">prose, in the run artifacts</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">3</span>
-      <span class="layer-name">Curation promotes the durable ones</span>
-      <span class="layer-sub">a human decides what generalises</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">4</span>
-      <span class="layer-name">They become team knowledge</span>
-      <span class="layer-sub">in the library, beside the recipes</span>
-    </div>
-    <div class="arrow" aria-hidden="true">↓</div>
-    <div class="layer layer-static">
-      <span class="layer-n">5</span>
-      <span class="layer-name">The next run loads it before acting</span>
-      <span class="layer-sub">discovery, not recall</span>
-    </div>
-  </div>
-  <p>
-    Step 3 is a person on purpose: a run produces plenty of true-but-local detail, and promoting all of
-    it buries what matters — the same judgement as deciding what belongs in a code comment.
-  </p>
-  <div class="note blue">
-    <span class="note-title">Where learnings collect</span>
-    <p>
-      Scrubbed packages from approved runs land in
-      <code>MetaMask/experimental-distributed-learnings</code>, a private append-only inbox — the same
-      repository as <code>experimental-agentic-learnings</code>, which was its earlier name and still
-      redirects. Capture records the observation, review later decides whether it warrants a proposal,
-      and proposals go to whichever repo owns the affected layer. Sharing is opt-in: without a local
-      <code>learning.config.json</code> a run stages locally and publishes nothing. Packages are
-      date-partitioned and the indexes are scaffolded, but only one day of runs has landed so far —
-      collection is beginning, so treat it as the destination rather than a corpus to read today.
-    </p>
-  </div>
-  <h3>What works today</h3>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th>Mechanism</th><th>Its part in the loop</th></tr></thead>
-      <tbody>
-        <tr>
-          <td>The evidence bundle</td>
-          <td>Produces the raw material. <code>diagnostics.json</code> in particular is where side findings land — application warnings and errors captured during the run, kept out of the verdict precisely so they survive as observations rather than being flattened into pass or fail.</td>
-        </tr>
-        <tr>
-          <td>Team recipe libraries</td>
-          <td>The place shared understanding accumulates. A recipe that encodes "get to a clean market first" <em>is</em> a piece of team knowledge, already reusable by everyone who declares the library.</td>
-        </tr>
-        <tr>
-          <td><code>mm-harness recipe-quality</code></td>
-          <td>Turns a review's verdicts into a quality artifact, so an assessment of a proof is itself a durable record rather than a comment that scrolls away.</td>
-        </tr>
-        <tr>
-          <td><code>mm-harness execution-template</code></td>
-          <td>Discovers, validates, and materialises shared agent checklists — a curated procedure written once and picked up by everyone, which is the loop working at the level of process.</td>
-        </tr>
-        <tr>
-          <td>Skills</td>
-          <td>The same idea for workflows. A skill is a procedure someone got right, packaged so nobody has to rediscover it.</td>
-        </tr>
-      </tbody>
-    </table>
-  </div>
-  <h3>Where this is heading</h3>
-  <p>
-    The gap is the middle of the loop: recipes and actions have a home in a team library; the sharper
-    things a run teaches you do not yet. Worth capturing:
-  </p>
-  <ul>
-    <li><strong>Gotchas</strong> — the non-obvious precondition that cost someone an afternoon, written down once.</li>
-    <li><strong>Screen maps</strong> — how a surface is actually reached and identified in the current build, so the next author is not re-deriving it.</li>
-    <li><strong>Flakes</strong> — the step known to be intermittent, with what is known about when and why, so an author can distinguish a real failure from a familiar one.</li>
-  </ul>
-  <p>
-    The intended shape is the one proven everywhere else here: <strong>discovery rather than
-    recall</strong>. Just as you ask the checkout what actions exist, you would ask what is already
-    known about a surface before authoring against it — a <code>knowledge</code> surface alongside
-    <code>actions</code> and <code>run --list</code>, resolving the way libraries already do, layered
-    most-specific-wins: yours, your team's, the workflow's, then defaults shipping with the harness
-    release so tool facts cannot drift out of date in a document nobody re-reads.
-  </p>
-  <p>
-    Entries stay small and curated: a short index of what exists and when to load it, topic files under
-    a size cap, each entry carrying a stable id and the same symptom → cause → what to do shape the
-    error messages use. Promotion happens through an ordinary reviewed pull request, so a human is in
-    the loop by construction.
-  </p>
-  <div class="note">
-    <span class="note-title">Being straight about status</span>
-    <p style="margin-bottom:0">
-      <strong>Not shipping yet.</strong> There is no <code>knowledge</code> command today, which is why
-      you will not find one in a copyable block on this page. Meanwhile the useful part is unblocked:
-      keep what your runs teach you in the library repo beside the recipes. Tooling makes it
-      discoverable later; writing it down is what makes it exist.
-    </p>
-  </div>
-  <div class="doctrine">
-    <p>
-      <span class="k">The skills teach the workflow; the knowledge teaches the product.</span> Runs
-      produce learnings, curation promotes them, discovery serves them to every run after.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="libraries">Where everything lives</h2>
-  <div class="table-scroll">
-    <table>
-      <thead><tr><th>What</th><th>Is</th><th>You need it when</th></tr></thead>
-      <tbody>
-        <tr>
-          <td><code>@deeeed/metamask-harness</code><br><span style="color:var(--text-faint);font-size:.85rem">the <code>mm-harness</code> CLI, on npm</span></td>
-          <td>The execution engine and evidence producer: <code>doctor</code>, <code>launch</code>, <code>actions</code>, <code>call</code>, <code>run</code>, <code>last</code>.</td>
-          <td><strong>Always.</strong> Install and update with <code>npm i -g @deeeed/metamask-harness@latest</code>.</td>
-        </tr>
-        <tr>
-          <td><code>Consensys/skills</code><br><span style="color:var(--text-faint);font-size:.85rem">internal repo</span></td>
-          <td>Agentic skills — recipe authoring, PR QA review, release validation. Installed into a checkout via that repo's tooling.</td>
-          <td>When you want an agent to follow a proven workflow instead of improvising one.</td>
-        </tr>
-        <tr>
-          <td>Team recipe libraries<br><span style="color:var(--text-faint);font-size:.85rem">e.g. the perps and money-movement libraries</span></td>
-          <td>Team-owned recipes, domain actions, and domain knowledge. Declared with <code>RECIPE_LIBRARY_PATH</code> or <code>--library</code>.</td>
-          <td>When running or authoring anything domain-specific. <a href="tutorials/v3.html#steps">V3 walks the setup</a> with the perps library as the worked example.</td>
-        </tr>
-        <tr>
-          <td>Product repos<br><span style="color:var(--text-faint);font-size:.85rem">extension · mobile · core</span></td>
-          <td>The thing under test. The harness runs against a real checkout and a real build.</td>
-          <td><strong>Always</strong> — there is nothing to prove without one.</td>
-        </tr>
-      </tbody>
-    </table>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="workflows">The three workflows — pick one, do not blend them</h2>
-  <p>Most confusion here is someone doing two at once. They need different setup and fail differently.</p>
-  <div class="grid grid-3">
-    <div class="card">
-      <h3>1 · Run an existing recipe</h3>
-      <p style="color:var(--text-dim);font-size:.92rem">No skills needed. This is the majority of daily use.</p>
-      <div class="cmd"><pre><code><span class="p">$ </span>mm-harness update
-<span class="p">$ </span>cd &lt;product checkout&gt;
-<span class="p">$ </span>export RECIPE_LIBRARY_PATH=&lt;name=path&gt;
-<span class="p">$ </span>mm-harness doctor
-<span class="p">$ </span>mm-harness launch
-<span class="p">$ </span>mm-harness run &lt;recipe&gt; \
-    --artifacts-dir ./out</code></pre></div>
-      <p style="margin-bottom:0;font-size:.92rem">Evidence lands in the artifacts dir. That is the whole workflow.</p>
-    </div>
-    <div class="card">
-      <h3>2 · Author a recipe</h3>
-      <p style="color:var(--text-dim);font-size:.92rem">For a specific acceptance criterion. Skills earn their keep here.</p>
-      <p style="font-size:.92rem">
-        Install the recipe-authoring skill. It discovers the vocabulary with
-        <code>mm-harness actions</code> — <strong>the discovered list is law, action names are never
-        invented</strong> — composes the graph, validates it with <code>run --plan</code>, then runs it
-        for real.
-      </p>
-      <p style="margin-bottom:0;font-size:.92rem">
-        Expect one honest failure-and-fix loop. That is the error messages doing their job.
-      </p>
-    </div>
-    <div class="card">
-      <h3>3 · Review a PR / validate a release</h3>
-      <p style="color:var(--text-dim);font-size:.92rem">Requires the QA skills.</p>
-      <p style="font-size:.92rem">
-        Give the skill one PR URL. It extracts the acceptance criteria verbatim — missing ones become a
-        hygiene finding, never an invented criterion — waits for you to confirm or edit the table, runs
-        the proof on a real device, and produces a per-criterion verdict with evidence paths.
-      </p>
-      <p style="margin-bottom:0;font-size:.92rem">
-        A criterion the surface genuinely cannot prove is reported as needing a human, not quietly
-        passed.
-      </p>
-    </div>
-  </div>
-  <div class="note blue">
-    <span class="note-title">Why "do not blend them" is a real instruction</span>
-    <p>
-      Running a recipe needs no skills; reviewing a PR does. Install everything and ask an agent to
-      "just handle it" and you get an agent choosing between procedures with no basis to pick. Name the
-      workflow you are in.
-    </p>
-  </div>
-</section>
-<section class="wrap">
-  <h2 id="mistakes">The five mistakes every newcomer makes</h2>
-  <ol style="padding-left:1.2rem">
-    <li style="margin-bottom:1rem">
-      <strong>Asking the agent to figure it all out from one sentence.</strong> The skills <em>are</em>
-      the figured-out part. Name the workflow you want; do not make the agent guess which of the three
-      you are in.
-    </li>
-    <li style="margin-bottom:1rem">
-      <strong>A stale harness.</strong> This one costs the most afternoons. The CLI ships often and
-      recipes assume current behaviour. Run <code>mm-harness update</code> before you debug anything
-      that "used to work".
-    </li>
-    <li style="margin-bottom:1rem">
-      <strong>Not declaring the library.</strong> Without <code>RECIPE_LIBRARY_PATH</code> (or
-      <code>--library</code>) the harness only sees bundled recipes — so your team's recipe appears not
-      to exist, and the error is telling the literal truth.
-    </li>
-    <li style="margin-bottom:1rem">
-      <strong>Skipping <code>doctor</code>.</strong> It tells you exactly what is missing and the exact
-      command that fixes it. Every error in this stack carries a <code>Next:</code> action. Read them —
-      that is the whole design.
-    </li>
-    <li>
-      <strong>Blending the workflows.</strong> See above. Mixing "run a recipe" with "review a PR"
-      confuses the agent and produces work you then have to check by hand.
-    </li>
-  </ol>
-  <hr class="sep">
-  <h2>Which repo is which</h2>
-  <p>
-    The layers above are the design. The <a href="ecosystem.html">Ecosystem map</a> is the concrete
-    version: the six repositories and packages behind a run, each with its URL, and which way the
-    dependencies point.
-  </p>
-  <div class="btn-row">
-    <a class="btn btn-primary" href="ecosystem.html">See the repo map →</a>
-    <a class="btn btn-ghost" href="how-it-works.html#steps">Do the walkthrough</a>
-    <a class="btn btn-ghost" href="reviewers.html">Read an evidence bundle</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/assets/help-recipes.mjs DELETED Viewed

@@ -1,25 +0,0 @@
-const root = document.querySelector('[data-help-recipes]');
-if (root) {
-  const response = await fetch(new URL('help-recipes.json', import.meta.url));
-  if (!response.ok) throw new Error(`Recipe help failed to load: ${response.status}`);
-  const topic = await response.json();
-  const code = document.createElement('code');
-  const lines = [
-    'Task: use the installed mm-harness for recipe-backed work. Follow these steps in order.',
-    topic.summary,
-    topic.capabilities,
-    topic.scopeNotice,
-  ];
-  for (const [index, section] of topic.sections.entries()) {
-    lines.push('', `${index + 1}. ${section.title}`, `   ${section.instruction}`);
-    for (const detail of section.details) lines.push(`   - ${detail}`);
-    for (const command of section.commands) lines.push(`   ${command}`);
-  }
-  lines.push('', `Safety: ${topic.safety}`);
-  code.textContent = lines.join('\n');
-  const pre = document.createElement('pre');
-  pre.append(code);
-  root.replaceChildren(pre);
-  document.dispatchEvent(new CustomEvent('mm-harness-content-rendered'));
-}

package/site/assets/metamask-fox.svg DELETED Viewed

@@ -1,24 +0,0 @@
-<svg width="35" height="34" viewBox="0 0 35 34" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M32.7077 32.7522L25.1688 30.5174L19.4833 33.9008L15.5167 33.8991L9.82793 30.5174L2.29225 32.7522L0 25.0489L2.29225 16.4993L0 9.27094L2.29225 0.312256L14.0674 7.31554H20.9326L32.7077 0.312256L35 9.27094L32.7077 16.4993L35 25.0489L32.7077 32.7522Z" fill="#FF5C16"/>
-<path d="M2.29395 0.312256L14.0691 7.32047L13.6008 12.1301L2.29395 0.312256Z" fill="#FF5C16"/>
-<path d="M9.82959 25.0522L15.0106 28.9811L9.82959 30.5175V25.0522Z" fill="#FF5C16"/>
-<path d="M14.5966 18.5565L13.6009 12.1333L7.22692 16.5009L7.22363 16.4993V16.5025L7.24335 20.9983L9.82809 18.5565H9.82974H14.5966Z" fill="#FF5C16"/>
-<path d="M32.7077 0.312256L20.9326 7.32047L21.3993 12.1301L32.7077 0.312256Z" fill="#FF5C16"/>
-<path d="M25.1722 25.0522L19.9912 28.9811L25.1722 30.5175V25.0522Z" fill="#FF5C16"/>
-<path d="M27.7766 16.5025H27.7783H27.7766V16.4993L27.775 16.5009L21.401 12.1333L20.4053 18.5565H25.1722L27.7586 20.9983L27.7766 16.5025Z" fill="#FF5C16"/>
-<path d="M9.82793 30.5175L2.29225 32.7522L0 25.0522H9.82793V30.5175Z" fill="#E34807"/>
-<path d="M14.5947 18.5549L16.0341 27.8406L14.0393 22.6777L7.23975 20.9984L9.82613 18.5549H14.593H14.5947Z" fill="#E34807"/>
-<path d="M25.1721 30.5175L32.7078 32.7522L35.0001 25.0522H25.1721V30.5175Z" fill="#E34807"/>
-<path d="M20.4053 18.5549L18.9658 27.8406L20.9607 22.6777L27.7602 20.9984L25.1722 18.5549H20.4053Z" fill="#E34807"/>
-<path d="M0 25.0488L2.29225 16.4993H7.22183L7.23991 20.9967L14.0394 22.676L16.0343 27.8389L15.0089 28.976L9.82793 25.0472H0V25.0488Z" fill="#FF8D5D"/>
-<path d="M35.0001 25.0488L32.7078 16.4993H27.7783L27.7602 20.9967L20.9607 22.676L18.9658 27.8389L19.9912 28.976L25.1722 25.0472H35.0001V25.0488Z" fill="#FF8D5D"/>
-<path d="M20.9325 7.31543H17.4999H14.0673L13.6006 12.1251L16.0342 27.834H18.9656L21.4008 12.1251L20.9325 7.31543Z" fill="#FF8D5D"/>
-<path d="M2.29225 0.312256L0 9.27094L2.29225 16.4993H7.22183L13.5991 12.1301L2.29225 0.312256Z" fill="#661800"/>
-<path d="M13.17 20.4199H10.9369L9.72095 21.6062L14.0409 22.6727L13.17 20.4182V20.4199Z" fill="#661800"/>
-<path d="M32.7077 0.312256L34.9999 9.27094L32.7077 16.4993H27.7781L21.4009 12.1301L32.7077 0.312256Z" fill="#661800"/>
-<path d="M21.833 20.4199H24.0694L25.2853 21.6079L20.9604 22.676L21.833 20.4182V20.4199Z" fill="#661800"/>
-<path d="M19.4817 30.8362L19.9911 28.9794L18.9658 27.8423H16.0327L15.0073 28.9794L15.5167 30.8362" fill="#661800"/>
-<path d="M19.4816 30.8359V33.9021H15.5166V30.8359H19.4816Z" fill="#C0C4CD"/>
-<path d="M9.82959 30.5142L15.52 33.9008V30.8346L15.0106 28.9778L9.82959 30.5142Z" fill="#E7EBF6"/>
-<path d="M25.1721 30.5142L19.4817 33.9008V30.8346L19.9911 28.9778L25.1721 30.5142Z" fill="#E7EBF6"/>
-</svg>