@mutmutco/pi-plugin 4.6.4 → 4.6.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/pi-plugin",
-  "version": "4.6.4",
+  "version": "4.6.5",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/org-guide/references/work-and-releases.md

@@ -165,7 +165,11 @@ that actually ships in the cut: the train refuses an issue or PR number the rele
 commit, so build and verify the lines from one pass over that range —
 `git log --stat --format='%h %s%n%b' origin/main..origin/development`, which carries each commit's
 subject, body and changed files — never from subjects, PR titles or memory; a line whose claim is not
-in that output does not go in the file. A Hub summary never mentions a Jerv-side project; the train
+in that output does not go in the file. Release recovery can re-cut the same `v*` tag on a new SHA, so
+other checkouts still holding the old tag reject a plain `git fetch origin --tags` (`would clobber existing tag`);
+refresh tags with `git fetch origin --tags --force` (or `git fetch origin '+refs/tags/*:refs/tags/*'`) and
+never chain a plain tag fetch with `&&` ahead of a read-only `git log <tag>..origin/<branch>` range (#9517).
+A Hub summary never mentions a Jerv-side project; the train
 refuses such a line.
 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. On its own an agent runs only `suite rcand --dry-run` and `suite hotfix <member> --dry-run`; it never runs `suite release` or `suite abandon`, which have no dry-run. Details: the release skill.