@mutmutco/pi-plugin 4.5.217 → 4.5.218

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/pi-plugin",
3
- "version": "4.5.217",
3
+ "version": "4.5.218",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
@@ -32,7 +32,13 @@ a universal test count. Run only the focused checks the repository policy permit
32
32
  substitute a broad local build or full suite. MMI worktrees install vitest under `cli/node_modules`,
33
33
  not at the root, so never run `npx vitest` there (#8967): invoke the worktree-local runner directly,
34
34
  `node <worktree>/cli/node_modules/vitest/vitest.mjs run <suite>` (or `npm --prefix cli exec -- vitest run <suite>`),
35
- and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Complete the documentation preflight below before pushing.
35
+ and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Run `mmi-cli tests policy`
36
+ and every focused test from the assigned issue worktree whose session cwd selects it — policy receipts
37
+ are recorded per worktree, so a receipt from another tree does not clear the guard; never cd-prefix into
38
+ a lane root or sibling worktree (use `git -C` / `npm --prefix` instead, #3187). A historical main-based
39
+ hotfix worktree without test-policy.json chains
40
+ `mmi-cli tests policy --json --base origin/main --policy-ref <current origin/development commit> && <focused test>`
41
+ in one command (#3243). Complete the documentation preflight below before pushing.
36
42
  Open a PR through `mmi-cli devops pr create` with a closing issue link, and land through
37
43
  `mmi-cli devops pr land`. Verify required checks, merge, issue closure, and cleanup before calling
38
44
  the implementation complete. A merged implementation is not a production release.