@deeeed/metamask-harness 0.74.0 → 0.76.0

package/docs/CONTRIBUTING.md

@@ -62,13 +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 new platform registers the
-same way and needs no edit to shared code. Extend `AdapterSurface` only when all
-platforms need the concept, implement it in every adapter, and let Core report
-headless/N/A explicitly. Do not add command-local platform ladders for
-surface-owned behavior: `launch` already dispatches through
-`AdapterSurface.launch`, and the device platforms supply a `DeviceLaunchProfile`
-(`src/commands/launch/device.ts`).
+`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, 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.74.0",
+  "version": "0.76.0",
   "type": "module",
   "bin": {
     "mm-harness": "bin/mm-harness"
@@ -45,6 +45,7 @@
     "@vitest/coverage-v8": "^4.1.10",
     "eslint": "^9",
     "globals": "^17.7.0",
+    "proper-lockfile": "^4.1.2",
     "tsx": "^4.23.0",
     "typescript": "^5.6.0",
     "typescript-eslint": "^8",

package/scripts/completions.sh

@@ -29,13 +29,14 @@ _mmh_bin() {
   return 1
 }
 
-_mmh_commands="launch stop logs debug reload fixtures actions call run doctor check checklist execution-template recipe-quality install verify cleanup completions"
+_mmh_commands="launch stop logs debug reload fixtures actions call run doctor check checklist execution-template recipe-quality install verify cleanup pin completions"
 
 # Per-command flags (static, from the mm-harness surface).
 _mmh_flags_for() {
   case "$1" in
     launch)   printf '%s' "--build --watch --verify --sidepanel --fullscreen --runway --device --cdp-port --watcher-port --heal --adapter --target --json" ;;
     stop)     printf '%s' "--port --target --json" ;;
+    pin)      printf '%s' "--json" ;;
     logs)     printf '%s' "--full --events --source --adapter --target --json" ;;
     debug)    printf '%s' "--worker --dev-menu --adapter --target --json" ;;
     reload)   printf '%s' "--adapter --platform --target --json" ;;