@deeeed/metamask-harness 0.75.0 → 0.77.0

package/docs/CONTRIBUTING.md

@@ -62,25 +62,35 @@ exits.
 
 Commands resolve shared platform behavior through
 `src/adapters/surface.ts`. Each platform's surface registers itself in
-`src/adapters/registry.ts` when its module loads. A platform registered the same
-way is reached by `launch`, by the `run`/`call` engine and by the runner's
-action set with no edit to shared code (`tests/fixtures/example-adapter.ts`).
-The CLI front door still validates `--adapter` against the four built-ins
-(`src/command-contract.ts`), and the other commands still branch on the name,
-so a new platform reaches `bin/mm-harness` only when those families move and a
-plugin loader registers it.
+`src/adapters/registry.ts` when its module loads, and commands look adapters up
+in the registry, so a platform registered the same way is reached by the
+commands that take `--adapter` with no edit to shared code
+(`tests/fixtures/example-adapter.ts`); `status` detects the adapter from the
+checkout.
+The CLI contract (`src/command-contract.ts`) still lists the four built-ins for
+`--adapter`, so a new platform reaches `bin/mm-harness` once a plugin loader
+registers it and extends that list.
 
 Extend `AdapterSurface` when a platform owns the behavior; members a platform
-does not need are optional (`actions` is required: every platform has an
-action set), and Core reports headless/N/A explicitly. Put each platform's
-implementation under `src/adapters/<adapter>/` (`launch.ts`, `run.ts`,
-`actions.ts`). Do not add command-local platform ladders for surface-owned
-behavior: `launch` dispatches through `AdapterSurface.launch` (the device
-platforms share `src/commands/launch/device.ts` through a
-`DeviceLaunchProfile`), `run`/`call` read `run`, `recording`, `diagnostics`,
-`observation` and `sourceFingerprint`, and the runner reads `actions`
-(manifest, bundled semantic actions, live adapter scripts, `cdp.target`, the
-`ui.*` transport, adapter wrappers, input checks).
+does not need are optional, and Core reports headless/N/A explicitly. Put each
+platform's implementation under `src/adapters/<adapter>/`: `launch.ts`,
+`run.ts`, `actions.ts`, `overlay.ts` (install/verify/cleanup, the runtime
+context, prepare) and `readiness.ts` (doctor and status). Do not add
+command-local platform ladders for surface-owned behavior:
+- `launch` dispatches through `AdapterSurface.launch` (the device platforms
+  share `src/commands/launch/device.ts` through a `DeviceLaunchProfile`);
+- `run`/`call` read `run`, `recording`, `diagnostics`, `observation` and
+  `sourceFingerprint`;
+- the runner reads `actions` (manifest, bundled semantic actions, live adapter
+  scripts, `cdp.target`, the `ui.*` transport, adapter wrappers, input checks);
+- `install`/`verify`/`cleanup` read `harness`, `agentic-runtime.json` reads
+  `runtimeContext`, `doctor`/`status` read `readiness`, and `fixtures`,
+  `prepare`, `debug`, `reload` and `runtime-decision` read their own members.
+
+A few comparisons remain where a command exists for one platform
+(`runtime-health`, `resolve-extension`, `ensure-ready`, `runtime-launch`) or
+code compares a platform's own data (`review/knowledge.ts`, the Core jest
+grouping in `check.ts`, the Mobile release-artifact state file).
 
 Each checkout owns:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deeeed/metamask-harness",
-  "version": "0.75.0",
+  "version": "0.77.0",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"
@@ -25,7 +25,7 @@
     "@farmslot/expo-recipe": "0.13.1",
     "@farmslot/handoff": "^0.3.1",
     "@farmslot/protocol": "0.34.0",
-    "@farmslot/recipe-cli": "0.1.1",
+    "@farmslot/recipe-cli": "0.1.2",
     "@farmslot/recipe-harness": "0.22.1",
     "agent-device": "0.19.3",
     "commander": "^12.0.0",