@deeeed/metamask-harness 0.54.0 → 0.54.1

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## Unreleased
 
+## 0.54.1 - 2026-09-18
+
+### Changed
+
+- `help --json` quality section carries the verdict rules (pass, warn, fail), the shape of an independent critique, and per-adapter review notes for Mobile, Extension and Core; the separate recipe-quality skill is retired in favour of this guidance.
+
 ## 0.54.0 - 2026-09-17
 
 ### Changed

package/README.md

@@ -271,7 +271,7 @@ Unset `MM_HARNESS_BIN` to return to the published installation.
 
 ### Workflow entry points and completion
 
-Explicitly invoke `mms-recipe-dev`, `mms-recipe-fixbug`, `mms-recipe-qa` or the team's static review skill. `mms-recipe-cook` selects or resumes their shared Markdown checklist. Matching descriptions or changed paths never activates these workflows.
+Explicitly invoke `mms-recipe-dev`, `mms-recipe-fix-bug`, `mms-recipe-qa` or the team's static review skill. `mms-recipe-cook` selects or resumes their shared Markdown checklist. Matching descriptions or changed paths never activates these workflows.
 
 Static Perps review uses a generated source checklist without installing or launching the app harness. `recipe-qa` freezes a PR, range or daily change window and requires runtime smoke plus selected recipe proof. Official release validation uses its named release profile and proof lane.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.54.0",
+  "version": "0.54.1",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"

package/scripts/site-contrast.mjs

@@ -394,9 +394,9 @@ async function checkBehavior(browserEndpoint, port, pages) {
       ['/mms-recipe-qa', copied.work.join('\n')],
       ['/mms-recipe-cook', copied.work.join('\n')],
       ['/mms-recipe-performance', copied.work.join('\n')],
-      ['/mms-recipe-evidence', copied.work.join('\n')],
-      ['agentic/recipe-performance', copied.setup],
-      ['agentic/recipe-evidence', copied.setup],
+      ['/mms-recipe-pretty-pr', copied.work.join('\n')],
+      ['perps/recipe-performance', copied.setup],
+      ['agentic/recipe-pretty-pr', copied.setup],
     ];
     const missing = expected.filter(([line, text]) => !text?.includes(line)).map(([line]) => line);
     if (missing.length) {

package/site/assets/help-recipes.json

@@ -212,6 +212,26 @@
             "mobile",
             "extension"
           ]
+        },
+        "Verdict: pass when every named claim ran an executable path with an assertion and consistent evidence; warn when the supported claims pass but non-blocking gaps remain; fail when a named claim has no executable path or assertion, the graph can pass unconditionally, required evidence is missing or contradictory, or the relevant path did not run. A visual claim cannot pass without a settled capture. Write only the compact {verdict, reasons} to artifacts/recipe-quality-input.json and build the artifact with mm-harness recipe-quality build; never hand-author it.",
+        "Independent critique, when one is requested: the verdict with one evidence-backed sentence, uncovered or weak proof targets, graph, composition, adapter and reuse findings, evidence mismatches and flake risks, and the three highest-value concrete edits.",
+        {
+          "text": "State the simulator or device, build type and app state. Unlock through a fixture or a documented primitive; keep account, balance, network, permissions and feature flags deterministic; use existing page objects, test ids and fixtures; capture only after ui.wait_for, a route assertion or a state assertion; teardown must not leak balances, pending transactions, selected network, permissions or onboarding state into the next run.",
+          "adapters": [
+            "mobile"
+          ]
+        },
+        {
+          "text": "State browser, build, fixture and the popup, fullscreen or service-worker context. Popup UI proven only through CDP eval or controller reads fails a visual claim; capture after settle; prefer existing e2e and fixture helpers over raw steps.",
+          "adapters": [
+            "extension"
+          ]
+        },
+        {
+          "text": "Core is headless: prove claims with summary.json, trace.json, logs or package tests, never screenshots; use manifest-declared headless actions only; state the target package or workspace, fixture, start state and teardown for controller mutations; a non-visual criterion needs unit or package test coverage.",
+          "adapters": [
+            "core"
+          ]
         }
       ],
       "commands": [