@deeeed/metamask-harness 0.92.15 → 0.92.17

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.
package/CHANGELOG.md CHANGED
@@ -4,8 +4,21 @@
4
4
 
5
5
  ### Changed
6
6
 
7
+ - Point task initialization, closeout and PR-body documentation at the shared Farmslot commands.
7
8
  - Refresh Terminal contract goldens for the shipped console-error window, capture-provider metadata and engine evidence inventories.
8
9
 
10
+ ## 0.92.17 - 2026-10-16
11
+
12
+ ### Changed
13
+
14
+ - Consume the published pipeline-review contracts, native review results and aligned worker dependency set.
15
+
16
+ ## 0.92.16 - 2026-10-16
17
+
18
+ ### Fixed
19
+
20
+ - Consume the published hosted-task runtime and aligned dependency set so task tooling retains owning workspaces, declared dependencies and hoisted peers.
21
+
9
22
  ## 0.92.15 - 2026-10-16
10
23
 
11
24
  ### Fixed
package/README.md CHANGED
@@ -93,7 +93,7 @@ mm-harness fixtures init --from /secure/path/wallet-fixture.json
93
93
  mm-harness fixtures init --dev
94
94
  ```
95
95
 
96
- Use `mm-harness update` to update a published installation. `npm i -g` and `update` rewrite the global install in place, so a task that must survive an upgrade records `mm-harness pin` instead: it copies the running install into an immutable, versioned store and prints the copy's executable.
96
+ Use `mm-harness update` to update a published installation. New tasks use `farmslot task init` to retain their CLI, provider and library inputs before writing the task marker. Run `farmslot task verify <task-dir>` to check those inputs before resuming. Global upgrades preserve an existing task's recorded tooling and marker.
97
97
 
98
98
  ## Operate
99
99
 
@@ -400,10 +400,12 @@ check for upstream updates. Keep the selected library unchanged during a run.
400
400
  ```bash
401
401
  # Write artifacts/pr-description.md in the repository PR template shape (prose
402
402
  # only), then render the publishable body.
403
- mm-harness pr-body render temp/tasks/dev/TAT-1 --command 'mm-harness run artifacts/recipe.json'
403
+ farmslot recipe artifacts temp/tasks/dev/TAT-1 --format markdown \
404
+ --out temp/tasks/dev/TAT-1/artifacts/pr-body.md \
405
+ --command 'farmslot recipe run artifacts/recipe.json'
404
406
  ```
405
407
 
406
- `pr-body render` writes `artifacts/pr-body.md`: the description with the "Validation
408
+ The Markdown renderer writes `artifacts/pr-body.md`: the description with the "Validation
407
409
  Recipe" and "Validation Logs" sections rendered from `artifacts/recipe.json` and
408
410
  `artifacts/recipe-run/report.md` (and "Recipe Workflow" from `artifacts/workflow.mmd`
409
411
  when it exists), replacing any pasted by hand. The worker never pastes artifacts
@@ -35,9 +35,9 @@ Generic bootstrap, trust, receipts, and recovery belong upstream. MetaMask
35
35
  platform behavior and risk classification belong here. Ticket assertions stay
36
36
  task-local.
37
37
 
38
- `mm-harness checklist` is only the MetaMask-facing dispatch layer. Terminal
39
- marks stage learnings through Handoff; sharing always requires a separate
40
- explicit `--share` call.
38
+ `farmslot task mark` applies the selected provider's MetaMask task gates. Terminal
39
+ marks stage learnings through Handoff; sharing requires a separate explicit
40
+ `farmslot task closeout <task-dir> --share` call.
41
41
 
42
42
  ## Repository map
43
43
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@deeeed/metamask-harness",
3
- "version": "0.92.15",
3
+ "version": "0.92.17",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "mm-harness": "bin/mm-harness"
@@ -21,15 +21,15 @@
21
21
  "check:syntax": "find . -name '*.mjs' -print0 | xargs -0 -n1 node --check"
22
22
  },
23
23
  "dependencies": {
24
- "@farmslot/adapter-node": "0.1.30",
25
- "@farmslot/adapter-rn": "0.22.19",
26
- "@farmslot/adapter-sdk": "0.16.1",
27
- "@farmslot/adapter-web": "0.10.10",
28
- "@farmslot/agent-runtime": "0.25.4",
24
+ "@farmslot/adapter-node": "0.1.32",
25
+ "@farmslot/adapter-rn": "0.22.21",
26
+ "@farmslot/adapter-sdk": "0.17.0",
27
+ "@farmslot/adapter-web": "0.10.12",
28
+ "@farmslot/agent-runtime": "0.27.0",
29
29
  "@farmslot/handoff": "^0.3.1",
30
- "@farmslot/protocol": "0.50.0",
31
- "@farmslot/recipe-cli": "0.22.2",
32
- "@farmslot/recipe-runner": "0.38.1",
30
+ "@farmslot/protocol": "0.52.0",
31
+ "@farmslot/recipe-cli": "0.22.4",
32
+ "@farmslot/recipe-runner": "0.38.3",
33
33
  "agent-device": "0.19.3",
34
34
  "commander": "^12.0.0",
35
35
  "esbuild": "0.28.1",