@mutmutco/pi-plugin 4.5.221 → 4.5.223
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
|
@@ -13,7 +13,10 @@ Reading or discussing the board is read-only until the developer authorizes work
|
|
|
13
13
|
Claim approved work with `mmi-cli oracle board claim <issue>`, then prepare an isolated task
|
|
14
14
|
workspace through the host. Preserve other developers' work.
|
|
15
15
|
|
|
16
|
-
Use host worktrees and MMI cleanup; no personal Jerv is required.
|
|
16
|
+
Use host worktrees and MMI cleanup; no personal Jerv is required. At handoff, state worktree facts
|
|
17
|
+
(dirty paths, unregistered trees, kept branches) only from `git worktree list --porcelain` run in this
|
|
18
|
+
session; never copy them forward from an earlier handoff, even labelled unverified (#9039).
|
|
19
|
+
Report skill misfires to Hub
|
|
17
20
|
with `mmi-cli learning skill-lesson --skill <name> --title <summary> --body-file <path>`.
|
|
18
21
|
Under the App pool,
|
|
19
22
|
`--jq`/`-q`/`--template`/`--web` are refused: use
|
|
@@ -411,7 +414,7 @@ commit, so build and verify the lines from one pass over that range —
|
|
|
411
414
|
subject, body and changed files — never from subjects, PR titles or memory; a line whose claim is not
|
|
412
415
|
in that output does not go in the file. A Hub summary never mentions a Jerv-side project; the train
|
|
413
416
|
refuses such a line.
|
|
414
|
-
Every new MM-Work suite Release, solo and hotfix included, requires `--announce-summary-file` and `--announce-summary-file-tr` in the bilingual update-notes template of the [MM-Work GUIDE, "Update notes"](https://github.com/mutmutco/MM-Work/blob/development/packages/mmwork-ds/GUIDE.md#update-notes) (`Fixed`/`Düzeldi`, then `New`/`Yeni`, with `<Area>: <sentence>.` lines; a Fixed line states what works now, never the problem). A suite release requires `--member-summary-file owner/repo=path` and `--member-summary-file-tr owner/repo=path` for every member it releases. Details: the release skill.
|
|
417
|
+
Every new MM-Work suite Release, solo and hotfix included, requires `--announce-summary-file` and `--announce-summary-file-tr` in the bilingual update-notes template of the [MM-Work GUIDE, "Update notes"](https://github.com/mutmutco/MM-Work/blob/development/packages/mmwork-ds/GUIDE.md#update-notes) (`Fixed`/`Düzeldi`, then `New`/`Yeni`, with `<Area>: <sentence>.` lines; a Fixed line states what works now, never the problem). A suite release requires `--member-summary-file owner/repo=path` and `--member-summary-file-tr owner/repo=path` for every member it releases. A suite cut's `--owner-go` records the owner's explicit go for that one cut, never an agent's own decision: a held train or stale MM-Work cut goes to the suite orchestrator with the exact owner-gated commands. Details: the release skill.
|
|
415
418
|
|
|
416
419
|
Announcement delivery uses the developer's GitHub-authenticated Hub session. The Hub checks project
|
|
417
420
|
authority, resolves the registered channel, and reads the MMI Future Slack key inside its vault boundary.
|
package/skills/rcand/suite.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
In the suite lead (MM-Work) a plain rcand, release or hotfix refuses:
|
|
1
|
+
In the suite lead (MM-Work) a plain rcand, release or hotfix refuses: the suite path is `mmi-cli devops suite rcand --owner-go` or `mmi-cli devops suite release --owner-go` (a lead-only cut needs `--suite-solo --owner-go`). `--owner-go` records Jervaise's explicit go for that one cut; it is never the agent's own flag. Never pass it on your own authority: a held train or a stale MM-Work cut (`suite abandon --owner-go`, then `suite rcand --owner-go`) is handed to the suite orchestrator with that exact command sequence, and runs only after the owner says go. A suite member cannot run standalone rcand, release or hotfix: cut from the suite lead; only a backward-compatible solo backend release/hotfix with explicit owner approval may pass `--suite-solo --owner-go`, and its MM-Work development pin PR must land before the suite is in sync.
|
|
2
2
|
|
|
3
3
|
Support sessions (MMI-Hub, Jerv-Hub, Jerv-JervCode) are not suite members and hold standing owner authorization (2026-10-25) to cut and ship releases at their discretion during suite runs without repeated per-release approval; record this standing rule in every suite session's working note and briefing while keeping all standard release preflight, gate, and verification checks.
|
|
4
4
|
|
package/skills/release/suite.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
In the suite lead (MM-Work) a plain rcand, release or hotfix refuses:
|
|
1
|
+
In the suite lead (MM-Work) a plain rcand, release or hotfix refuses: the suite path is `mmi-cli devops suite rcand --owner-go` or `mmi-cli devops suite release --owner-go` (a lead-only cut needs `--suite-solo --owner-go`). `--owner-go` records Jervaise's explicit go for that one cut; it is never the agent's own flag. Never pass it on your own authority: a held train or a stale MM-Work cut (`suite abandon --owner-go`, then `suite rcand --owner-go`) is handed to the suite orchestrator with that exact command sequence, and runs only after the owner says go. A suite member cannot run standalone rcand, release or hotfix: cut from the suite lead; only a backward-compatible solo backend release/hotfix with explicit owner approval may pass `--suite-solo --owner-go`, and its MM-Work development pin PR must land before the suite is in sync.
|
|
2
2
|
|
|
3
3
|
Support sessions (MMI-Hub, Jerv-Hub, Jerv-JervCode) are not suite members and hold standing owner authorization (2026-10-25) to cut and ship releases at their discretion during suite runs without repeated per-release approval; record this standing rule in every suite session's working note and briefing while keeping all standard release preflight, gate, and verification checks.
|
|
4
4
|
|