npm - @deeeed/metamask-harness - Versions diffs - 0.34.3 → 0.35.0 - Mend

@deeeed/metamask-harness 0.34.3 → 0.35.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 (31) hide show

package/CHANGELOG.md +21 -0
package/adapters/core/inject.sh +3 -3
package/adapters/extension/inject.mjs +3 -4
package/adapters/mobile/inject.sh +4 -3
package/adapters/mobile/verify.sh +37 -0
package/dist/adapters/extension/runtime.js +60 -15
package/dist/adapters/extension/surface.js +6 -1
package/dist/adapters/mobile/source-freshness.js +51 -14
package/dist/adapters/mobile/surface.js +6 -1
package/dist/doctor.js +30 -1
package/package.json +1 -1
package/scripts/site-contrast.mjs +38 -11
package/site/architecture.html +14 -7
package/site/assets/metamask-fox.svg +24 -0
package/site/assets/progress.mjs +52 -1
package/site/assets/style.css +152 -25
package/site/cheatsheet.html +5 -6
package/site/ecosystem.html +162 -0
package/site/how-it-works.html +8 -9
package/site/index.html +104 -39
package/site/perps.html +103 -45
package/site/recipes.html +5 -6
package/site/reviewers.html +5 -6
package/site/tutorials/index.html +5 -6
package/site/tutorials/v1.html +5 -6
package/site/tutorials/v2.html +6 -8
package/site/tutorials/v3.html +5 -6
package/site/tutorials/v4.html +5 -6
package/site/tutorials/v5.html +5 -6
package/site/tutorials/v6.html +5 -6
package/site/tutorials/v7.html +5 -6

package/site/index.html CHANGED Viewed

@@ -5,14 +5,15 @@
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Recipes — build with proof, not hope</title>
 <meta name="description" content="A skill drives the change. The recipe proves it on a real MetaMask build as it is written, self-checked in the same context and kept as a regression guard.">
-<link rel="stylesheet" href="assets/style.css">
+<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
+<link rel="stylesheet" href="assets/style.css?v=4">
 </head>
 <body>
 <a class="skip" href="#prompt">Skip to the prompt</a>
 <main class="lobby">
   <div class="lobby-inner">
-    <span class="lobby-mark" aria-hidden="true"></span>
+    <img class="lobby-mark" src="assets/metamask-fox.svg" alt="" width="52" height="52">
     <span class="eyebrow">Proven as it's built</span>
     <h1>Build agentically, with confidence.</h1>
@@ -21,14 +22,20 @@
       self-checked in the same context, then kept as a regression guard.
     </p>
     <p class="lobby-sub">
-      Set up, then work a real ticket. Paste this into your agent:
+      Set up once, then work a real ticket.
     </p>
-    <div class="cmd cmd-hero" id="prompt"><pre><code>Task: set me up with the MetaMask skills + recipe workflow, then use it on real
-work. Follow these steps in order. When a command fails, its message names the
-exact next command — run that instead of improvising.
+    <section class="qs">
-PART 1 — SET UP
+      <div class="qs-step">
+        <h2 class="qs-title"><span class="qs-num" aria-hidden="true">1</span>Set up</h2>
+        <p class="qs-why">
+          One time per machine. Paste this into your agent inside a MetaMask checkout.
+        </p>
+        <div class="cmd cmd-hero" id="prompt"><pre><code>Task: set me up for recipe-backed work on MetaMask. Follow these steps in order.
+When a command fails, its message names the exact next command — run that
+instead of improvising.
 1. Install the harness: `npm i -g @deeeed/metamask-harness@latest`, then
    `mm-harness --version` to confirm it resolved.
@@ -58,14 +65,18 @@ PART 1 — SET UP
    `--preflight-mode` is an internal adapter flag, not a public launch flag.
 6. On Extension run `mm-harness fixtures set`. On Mobile include the same
    `--device &lt;UUID-or-serial&gt;` used for launch. Wait for it to succeed.
-7. Install the skills — they are how the work actually gets driven. The
-   installer reads from LOCAL CLONES, so clone the sources first and add both
-   exports to my shell rc:
+7. Install the skills — they are how the work actually gets driven. First
+   inspect `METAMASK_SKILLS_DIR` and `CONSENSYS_SKILLS_DIR`, then check the
+   expected local layout below. Reuse every valid existing clone. For each
+   missing source, show me the proposed path and ask before cloning:
      `git clone https://github.com/MetaMask/skills.git ~/dev/metamask/skills`
-     `export METAMASK_SKILLS_DIR=~/dev/metamask/skills`
-   Then the internal overlay, which needs access to the Consensys org:
      `git clone git@github.com:Consensys/skills.git ~/dev/Consensys/skills`
+   The internal overlay needs access to the Consensys org. Export the paths in
+   the current shell for setup:
+     `export METAMASK_SKILLS_DIR=~/dev/metamask/skills`
      `export CONSENSYS_SKILLS_DIR=~/dev/Consensys/skills`
+   Never edit `.zshrc`, `.bashrc`, or another shell startup file unless I
+   explicitly consent; ask separately if I want these exports persisted.
    If that clone fails, tell me — I may not have access, and the next step
    depends on it. Then, from inside the checkout:
      `yarn metamask-skills list --maturity experimental`   everything installable
@@ -74,46 +85,100 @@ PART 1 — SET UP
    metamask-extension, metamask-mobile, and core. Use `--maturity experimental`
    when listing: the default only prints stable skills, so the recipe skills
    below do not appear without it.
-8. Add the skill that drives recipe-backed work:
-     `yarn skills --include agentic/recipe-cook --save`
-   It installs as `mms-recipe-cook`. It comes from the `Consensys/skills` clone
-   in step 7 and is marked experimental, which is why the explicit `--include`
+8. Add the skills that drive recipe-backed work:
+     `yarn skills --include agentic/recipe-cook,agentic/recipe-quality,agentic/recipe-pr-qa-review --save`
+   They install as `mms-recipe-cook`, `mms-recipe-quality`, and
+   `mms-recipe-pr-qa-review`. They come from the `Consensys/skills` clone in
+   step 7 and are marked experimental, which is why the explicit `--include`
    is required. If `yarn metamask-skills describe agentic/recipe-cook` cannot
    find it, check `CONSENSYS_SKILLS_DIR` points at that clone, then stop and
    tell me. Do not substitute a different skill.
+9. Run `mm-harness actions`. That list is the ONLY set of capabilities you may
+   use, now and in every later session — never invent an action or a flag. Then
+   stop and tell me setup is done.
+Not optional, from here on: evidence comes only from executed actions — never
+fabricate a result or edit state to manufacture one. If the harness reports a
+capability as unsupported, stop and tell me rather than working around it. If a
+step fails twice after following its error's instructions, stop and show me the
+exact error.</code></pre></div>
+      </div>
+      <div class="qs-step">
+        <h2 class="qs-title"><span class="qs-num" aria-hidden="true">2</span>Do real work</h2>
+        <p class="qs-why">
+          Pick what you are doing. Each one runs the skill that owns that flow, and leaves a
+          rerunnable recipe behind as the proof.
+        </p>
+        <div class="tabs">
+          <div class="tablist" role="tablist" aria-label="Choose what to do" hidden>
+            <button type="button" role="tab" id="tab-review" class="tab" aria-controls="panel-review" aria-selected="true" tabindex="0">Review a PR</button>
+            <button type="button" role="tab" id="tab-fix" class="tab" aria-controls="panel-fix" aria-selected="false" tabindex="-1">Fix a bug</button>
+            <button type="button" role="tab" id="tab-build" class="tab" aria-controls="panel-build" aria-selected="false" tabindex="-1">Build a feature</button>
+          </div>
+          <div class="qs-panel" role="tabpanel" id="panel-review" aria-labelledby="tab-review" tabindex="0">
+            <p class="qs-panel-why">
+              <code>mms-recipe-pr-qa-review</code> — read-only. It freezes the acceptance criteria
+              before it touches the runtime, validates each one on a real build, and returns a report.
+              It never edits product code and never posts to GitHub. The PR must be in the same
+              product as your checkout.
+            </p>
+            <div class="cmd"><pre><code>/mms-recipe-pr-qa-review https://github.com/MetaMask/metamask-mobile/pull/&lt;number&gt;
+Extract the acceptance criteria from the PR yourself and freeze them before any
+runtime work. Validate each one against the running build, then give me the
+per-AC verdict table, the overall verdict, and the artifact paths. Do not post
+anything on the PR.</code></pre></div>
+          </div>
+          <div class="qs-panel" role="tabpanel" id="panel-fix" aria-labelledby="tab-fix" tabindex="0">
+            <p class="qs-panel-why">
+              <code>mms-recipe-cook</code>, classified as <code>fix-bug</code>. It lists the
+              compatible checklist templates and stops for your pick, then works on a local task
+              branch. No product edits until the bug is proven to reproduce.
+            </p>
+            <div class="cmd"><pre><code>/mms-recipe-cook
+Fix this in the checkout I started you in — treat it as fix-bug:
+&lt;paste the ticket, or the broken behaviour and how to reproduce it&gt;
+Reproduce it on the real build first and keep that failing run as the baseline.
+Then fix it and re-run the same recipe until it passes. Show me the recipe
+status, the per-node results, and the artifact paths.</code></pre></div>
+          </div>
+          <div class="qs-panel" role="tabpanel" id="panel-build" aria-labelledby="tab-build" tabindex="0">
+            <p class="qs-panel-why">
+              <code>mms-recipe-cook</code>, classified as <code>dev</code>. Same flow: it lists the
+              compatible templates, stops for your pick, and keeps the diff uncommitted until you
+              ask it to package the PR.
+            </p>
+            <div class="cmd"><pre><code>/mms-recipe-cook
+Build this in the checkout I started you in — treat it as dev:
+&lt;paste the ticket, or the change you want&gt;
+Plan the proof before you edit anything, implement it, then prove it with a
+recipe that drives the real build. Show me the recipe status, the per-node
+results, and the artifact paths.</code></pre></div>
+          </div>
+        </div>
+      </div>
-PART 2 — DO REAL WORK
-9. Discover before acting: run `mm-harness actions`. That list is the ONLY set
-   of capabilities you may use, now and in every later session. Never invent an
-   action or a flag. If you need something not listed, stop and tell me.
-10. Ask me for a ticket or a bug to work on. Then run `/mms-recipe-cook` and
-   follow it. It classifies the task as dev, fix-bug, or review-pr, lists the
-   compatible checklist templates, and stops for my choice — do not choose for
-   me, and do not create a second task if one is already materialized.
-11. Work the checklist it gives you. The recipe it runs is the proof: it drives
-   the real build, asserts, and writes the evidence. Show me the status from
-   summary.json, the per-node results from trace.json, and the artifact paths.
-12. Re-run that recipe without starting a new session and confirm it still
-   passes. Checking your own work in the context you did it in is the point;
-   replay it after every change you make from here on.
-Not optional: evidence comes only from executed actions — never fabricate a
-result or edit state to manufacture one. If the harness reports a capability as
-unsupported, stop and tell me rather than working around it. If a step fails
-twice after following its error's instructions, stop and show me the exact
-error.</code></pre></div>
+    </section>
     <div class="lobby-cta">
       <a class="btn btn-primary" href="how-it-works.html">How it works →</a>
     </div>
     <p class="lobby-fine">
-      A proposal for how agents can code at MetaMask — offered for teams to try, not an official standard.
+      A proposal for how agents can code at MetaMask — offered for teams to try.
     </p>
   </div>
 </main>
-<script type="module" src="assets/progress.mjs"></script>
+<script type="module" src="assets/progress.mjs?v=4"></script>
 </body>
 </html>

package/site/perps.html CHANGED Viewed

@@ -3,9 +3,10 @@
 <head>
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
-<title>Perps recipes — MetaMask recipe workflow</title>
-<meta name="description" content="Install the shared MetaMask Perps recipe library and run live, testnet-first proof across Extension, Mobile, and Core.">
-<link rel="stylesheet" href="assets/style.css">
+<title>Team / Perps — customize the harness for your team</title>
+<meta name="description" content="Every team points the harness at its own recipe library. The MetaMask Perps library is the worked example: recipes, actions, checklist templates, and the team's own knowledge.">
+<link rel="icon" href="assets/metamask-fox.svg" type="image/svg+xml">
+<link rel="stylesheet" href="assets/style.css?v=4">
 </head>
 <body>
 <a class="skip" href="#setup">Skip to setup</a>
@@ -13,42 +14,43 @@
 <header class="topbar">
   <div class="wrap topbar-inner">
     <a class="brand" href="index.html">
-      <span class="brand-mark" aria-hidden="true"></span>
+      <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="recipes.html">Recipe anatomy</a>
-      <a href="perps.html" aria-current="page">Perps</a>
+      <a href="perps.html" aria-current="page">Team / Perps</a>
       <a href="cheatsheet.html">Cheatsheet</a>
       <a href="architecture.html">Architecture</a>
       <a href="tutorials/index.html">Tutorials</a>
-      <a href="reviewers.html">For Reviewers</a>
     </nav>
   </div>
 </header>
 <main>
 <section class="wrap hero" style="padding-bottom:1rem">
-  <span class="eyebrow">Shared MetaMask recipe library</span>
-  <h1>Prove Perps changes in the real product</h1>
+  <span class="eyebrow">Customization</span>
+  <h1>Make it your team's harness</h1>
   <p class="lede">
-    The private Perps library gives Extension, Mobile, and Core one set of small, parameterized
-    recipes for live UI journeys, controller state, analytics, performance, and testnet mutations.
+    The harness ships an execution standard and a deliberately small bundled library. Everything that
+    is specific to what <em>you</em> work on — the journeys, the assertions, the checklists, the review
+    knowledge — lives in a library you own and point the harness at. MetaMask Perps is the worked
+    example on this page.
   </p>
   <div class="hero-meta">
-    <span>library name: perps</span>
-    <span>defaults to testnet</span>
-    <span>requires repository access</span>
+    <span>per team</span>
+    <span>per engineer</span>
+    <span>one env var</span>
   </div>
 </section>
 <section class="wrap">
   <div class="doctrine">
     <p>
-      <span class="k">The harness supplies the execution standard; the Perps library supplies the domain proof.</span>
-      Keep the shared library small: compose or repair the closest recipe before creating another one.
+      <span class="k">The harness supplies the execution standard; your library supplies the domain.</span>
+      A team shares one library. An engineer can add their own on top. Neither requires a change to
+      the harness.
     </p>
   </div>
@@ -60,11 +62,11 @@
         <tr>
           <td><code>mm-harness</code></td>
           <td>Launch, typed actions, graph execution, screenshots, video, traces, and artifact contracts.</td>
-          <td>Ticket-specific Perps scenarios.</td>
+          <td>Anything specific to one team's domain.</td>
         </tr>
         <tr>
-          <td><code>perps</code> library</td>
-          <td>Reusable Perps setup, journeys, assertions, cleanup, and platform variants.</td>
+          <td>Your library</td>
+          <td>Reusable setup, journeys, assertions, cleanup, platform variants, and checklist templates.</td>
           <td>Wallet credentials, generated evidence, or product source.</td>
         </tr>
         <tr>
@@ -78,56 +80,102 @@
 </section>
 <section class="wrap">
-  <h2 id="setup">Install and discover it</h2>
+  <h2 id="setup">Point the harness at a library</h2>
   <p>
-    Run these commands from the MetaMask product checkout you want to exercise. The repository is
-    private; a clone failure means your GitHub account needs access.
+    One environment variable does it. The Perps library is private, so start by asking its owners for
+    access — a clone failure means your GitHub account does not have it yet.
   </p>
-  <div class="cmd"><pre><code><span class="p">$ </span>npm i -g @deeeed/metamask-harness@latest
-<span class="p">$ </span>git clone git@github.com:MetaMask/experimental-metamask-recipe-perps.git \
+  <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"
-<span class="p">$ </span>mm-harness run --list \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
+<span class="p">$ </span>export RECIPE_LIBRARY_PATH="perps=$HOME/shared-library/metamask-recipe-perps"
+<span class="p">$ </span>mm-harness run --list</code></pre></div>
   <p>
-    If the checkout already exists and is clean, update it with <code>git pull --ff-only</code>.
-    Preserve and report a dirty checkout instead of overwriting it. Keep <code>--library</code> on each
-    command so separate tool shells do not lose an exported variable.
+    <code>name=path</code> gives the source its alias; without one the directory name is used. Separate
+    several libraries with <code>:</code> — order is precedence, first wins:
   </p>
+  <div class="cmd"><pre><code><span class="p">$ </span>export RECIPE_LIBRARY_PATH="mine=$HOME/my-recipes:perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
+  <p>
+    Use <code>--library name=/path</code> for a single command instead — useful when a tool shell loses
+    an exported variable. Resolution follows your library order, then the bundled MetaMask library.
+  </p>
+  <div class="note blue">
+    <span class="note-title">Your own library, with no configuration</span>
+    <p>
+      A directory at <code>~/.farmslot/recipe-library</code> is picked up automatically as
+      <code>personal</code> when you set no library at all. It is a fallback, not an addition: as soon
+      as <code>RECIPE_LIBRARY_PATH</code> or <code>--library</code> is set, only those sources are used.
+      List it explicitly to keep both.
+    </p>
+  </div>
   <div class="note blue">
     <span class="note-title">Discovery is adapter-aware</span>
     <p>
       The list shows only recipes runnable in the current product checkout. A recipe marked
-      <code>[perps]</code> came from the shared library; <code>[metamask]</code> means it ships with the
+      <code>[perps]</code> came from that library; <code>[metamask]</code> means it ships with the
       harness. Read the selected platform variant with <code>--describe</code> before running it.
     </p>
   </div>
 </section>
+<section class="wrap">
+  <h2>What a team library actually holds</h2>
+  <p>
+    Every path below is real, from the Perps library. Copy the shape, not the contents — it is the
+    reference structure for a MetaMask team building its own.
+  </p>
+  <div class="cmd"><pre><code>manifests/extension.action-manifest.json     types the actions you add
+actions/extension/perps/                     domain actions the product needs
+recipes/mobile/perps/                        per-adapter journeys
+recipes/extension/perps/
+recipes/core/perps/
+checklists/dev/                              your own Recipe Cook checklist templates
+checklists/fix-bug/
+docs/                                        the knowledge: authoring rules,
+                                             performance evidence, analytics</code></pre></div>
+  <p>
+    The <code>docs/</code> and <code>checklists/</code> directories are the part teams underestimate.
+    They are how a team's hard-won conventions — how performance evidence is gathered here, which
+    analytics events matter, what a finished task looks like — stop living in one engineer's head.
+  </p>
+  <div class="note">
+    <span class="note-title">Review knowledge lives with the skills</span>
+    <p>
+      One team surface sits outside the recipe library: the static antipattern packs the PR QA review
+      reads, which ship with the skills as
+      <code>references/antipatterns/&lt;repo&gt;/&lt;pack&gt;.md</code>. Today there is a
+      <code>perps</code> pack for Mobile, Extension, and Core, and a Mobile-only
+      <code>unit-vs-cv</code> pack. A pack is advisory: it never changes an acceptance-criterion
+      verdict.
+    </p>
+  </div>
+</section>
 <section class="wrap">
   <h2>Your first live proof</h2>
   <p>
     Complete <a href="how-it-works.html#steps">the walkthrough</a> first so the app, device, and wallet fixture are
-    ready. Then use a read-only recipe as the first proof.
+    ready. With <code>RECIPE_LIBRARY_PATH</code> exported, the library's recipes are just names.
   </p>
   <h3>Extension or Mobile</h3>
-  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.open-market --describe \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"
-<span class="p">$ </span>mm-harness run perps.open-market network=testnet market=BTC --plan \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"
+  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.open-market --describe
+<span class="p">$ </span>mm-harness run perps.open-market network=testnet market=BTC --plan
 <span class="p">$ </span>mm-harness run perps.open-market network=testnet market=BTC \
-    --record-video=full-run --artifacts-dir ./perps-open-market-evidence \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
+    --record-video=full-run --artifacts-dir ./perps-open-market-evidence</code></pre></div>
   <h3>Core</h3>
-  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.snapshot-market --describe \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"
+  <div class="cmd"><pre><code><span class="p">$ </span>mm-harness run perps.snapshot-market --describe
 <span class="p">$ </span>mm-harness run perps.snapshot-market network=testnet market=BTC \
-    --artifacts-dir ./perps-market-evidence \
-    --library "perps=$HOME/shared-library/metamask-recipe-perps"</code></pre></div>
+    --artifacts-dir ./perps-market-evidence</code></pre></div>
   <p>
     A passing run writes <code>summary.json</code>, per-node results in <code>trace.json</code>, and an
@@ -137,7 +185,11 @@
 </section>
 <section class="wrap">
-  <h2>Choose the recipe that owns the claim</h2>
+  <h2>What the Perps team put in theirs</h2>
+  <p>
+    A sample of the library's recipes, as an idea of the granularity that works: small, parameterized,
+    composed rather than duplicated.
+  </p>
   <div class="table-scroll">
     <table>
       <thead><tr><th>Claim</th><th>Recipe</th><th>Platforms</th></tr></thead>
@@ -164,8 +216,9 @@
 </section>
 <section class="wrap">
-  <h2>Maintain the proof, not a pile of scenarios</h2>
+  <h2>Starting your team's library</h2>
   <ol>
+    <li>Create a repository with the directory shape above. It holds no accounts, fixtures, credentials, or generated evidence.</li>
     <li>Parameterize stable choices such as market, side, order type, and network.</li>
     <li>Compose existing setup, assertion, and cleanup recipes before adding a new top-level recipe.</li>
     <li>Add a platform variant only when the products genuinely differ.</li>
@@ -177,10 +230,15 @@
     <li>Re-run every caller after a shared node changes and attach the fresh evidence.</li>
   </ol>
+  <p>
+    Keep it small. Compose or repair the closest recipe before creating another one — a library that
+    grows a scenario per ticket stops being maintainable faster than the product does.
+  </p>
   <div class="btn-row">
     <a class="btn btn-primary" href="tutorials/v3.html">Install skills and the library →</a>
+    <a class="btn btn-ghost" href="ecosystem.html">Where this sits in the stack</a>
     <a class="btn btn-ghost" href="recipes.html">How recipes prove claims</a>
-    <a class="btn btn-ghost" href="reviewers.html">How to review evidence</a>
   </div>
 </section>
 </main>
@@ -191,6 +249,6 @@
     <p>Written against the shared MetaMask Perps recipe library. Sample output moves between releases; trust your terminal over this page.</p>
   </div>
 </footer>
-<script type="module" src="assets/progress.mjs"></script>
+<script type="module" src="assets/progress.mjs?v=4"></script>
 </body>
 </html>

package/site/recipes.html CHANGED Viewed

@@ -5,7 +5,8 @@
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>What is a recipe?</title>
 <meta name="description" content="The anatomy of a recipe: a JSON graph of typed actions, human-authored intent, first-class assertions, and a verdict derived from the trace.">
-<link rel="stylesheet" href="assets/style.css">
+<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="recipes">
 <a class="skip" href="#anatomy">Skip to the anatomy</a>
@@ -13,18 +14,16 @@
 <header class="topbar">
   <div class="wrap topbar-inner">
     <a class="brand" href="index.html">
-      <span class="brand-mark" aria-hidden="true"></span>
+      <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="recipes.html" aria-current="page">Recipe anatomy</a>
-      <a href="perps.html">Perps</a>
+      <a href="perps.html">Team / Perps</a>
       <a href="cheatsheet.html">Cheatsheet</a>
       <a href="architecture.html">Architecture</a>
       <a href="tutorials/index.html">Tutorials</a>
-      <a href="reviewers.html">For Reviewers</a>
     </nav>
   </div>
 </header>
@@ -419,6 +418,6 @@
   </div>
 </footer>
-<script type="module" src="assets/progress.mjs"></script>
+<script type="module" src="assets/progress.mjs?v=4"></script>
 </body>
 </html>

package/site/reviewers.html CHANGED Viewed

@@ -5,7 +5,8 @@
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>For Reviewers — how to read an evidence bundle</title>
 <meta name="description" content="An annotated walkthrough of a real mm-harness evidence bundle: summary.json, trace.json, diagnostics, and what an honest degraded capture looks like.">
-<link rel="stylesheet" href="assets/style.css">
+<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="reviewers">
 <a class="skip" href="#summary">Skip to the walkthrough</a>
@@ -13,18 +14,16 @@
 <header class="topbar">
   <div class="wrap topbar-inner">
     <a class="brand" href="index.html">
-      <span class="brand-mark" aria-hidden="true"></span>
+      <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="recipes.html">Recipe anatomy</a>
-      <a href="perps.html">Perps</a>
+      <a href="perps.html">Team / Perps</a>
       <a href="cheatsheet.html">Cheatsheet</a>
       <a href="architecture.html">Architecture</a>
       <a href="tutorials/index.html">Tutorials</a>
-      <a href="reviewers.html" aria-current="page">For Reviewers</a>
     </nav>
   </div>
 </header>
@@ -371,6 +370,6 @@ Nodes: 6/6 passed
   </div>
 </footer>
-<script type="module" src="assets/progress.mjs"></script>
+<script type="module" src="assets/progress.mjs?v=4"></script>
 </body>
 </html>

package/site/tutorials/index.html CHANGED Viewed

@@ -5,7 +5,8 @@
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Tutorials — the series</title>
 <meta name="description" content="Seven tutorials taking a new engineer from an empty terminal to pull requests that carry proof.">
-<link rel="stylesheet" href="../assets/style.css">
+<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="tutorials">
 <a class="skip" href="#series">Skip to the series</a>
@@ -13,18 +14,16 @@
 <header class="topbar">
   <div class="wrap-wide topbar-inner">
     <a class="brand" href="../index.html">
-      <span class="brand-mark" aria-hidden="true"></span>
+      <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="../recipes.html">Recipe anatomy</a>
-      <a href="../perps.html">Perps</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>
-      <a href="../reviewers.html">For Reviewers</a>
     </nav>
   </div>
 </header>
@@ -177,6 +176,6 @@
   </div>
 </footer>
-<script type="module" src="../assets/progress.mjs"></script>
+<script type="module" src="../assets/progress.mjs?v=4"></script>
 </body>
 </html>

package/site/tutorials/v1.html CHANGED Viewed

@@ -5,7 +5,8 @@
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>V1 — Getting started with recipes</title>
 <meta name="description" content="Video one of the series: one CLI drives the wallet and proves what happened. With the same checklist as the How it works walkthrough.">
-<link rel="stylesheet" href="../assets/style.css">
+<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="start">
 <a class="skip" href="#steps">Skip to the checklist</a>
@@ -13,18 +14,16 @@
 <header class="topbar">
   <div class="wrap topbar-inner">
     <a class="brand" href="../index.html">
-      <span class="brand-mark" aria-hidden="true"></span>
+      <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="../recipes.html">Recipe anatomy</a>
-      <a href="../perps.html">Perps</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>
-      <a href="../reviewers.html">For Reviewers</a>
     </nav>
   </div>
 </header>
@@ -208,6 +207,6 @@
   </div>
 </footer>
-<script type="module" src="../assets/progress.mjs"></script>
+<script type="module" src="../assets/progress.mjs?v=4"></script>
 </body>
 </html>