@mutmutco/opencode-mmi 2.54.0 → 2.54.1
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/opencode-mmi",
|
|
3
|
-
"version": "2.54.
|
|
3
|
+
"version": "2.54.1",
|
|
4
4
|
"description": "MMI Future OpenCode adapter — registers mmi, secrets, stage, rcand, release, hotfix, bootstrap, grind, build, handoff, coop, and browser-automation skills, workflow commands, and deterministic guardrail hooks.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -145,6 +145,7 @@ Org-wide session doctrine lives in **`AGENTS.md` § Session workflow** — grind
|
|
|
145
145
|
|
|
146
146
|
- **Trivial-task escape hatch.** A genuinely tiny, low-risk change — a one-line edit, a typo, a string tweak — does **not** need a worktree or even a feature branch. Spinning a full worktree for a ten-letter one-liner is waste. Edit on a normal branch (or directly where the user is working), verify, PR. Use a worktree once the change has real scope, parallel sites, or `/stage` needs. When unsure whether it's trivial, use a worktree.
|
|
147
147
|
- Branch from latest `origin/development` into `../mmi-worktrees/<branch>` — **never edit the main checkout** during grind/build runs.
|
|
148
|
+
- If a generic/native worktree helper would create `.claude/worktrees/`, `.worktrees/`, or another non-Hub path, skip it for MMI org repos and use `mmi-cli worktree create` / `setup`.
|
|
148
149
|
- One worktree per grind/build run until integration boundary; multi-worktree waves merge via `mmi-cli wave land`.
|
|
149
150
|
- Return to the main checkout mid-run only for a new unrelated branch, real base drift, final integrated validation, cleanup after merge, explicit user request, or a broken/unsafe worktree. Otherwise keep implementation, verification, commits, PR prep, saga, and North Star updates in the active worktree.
|
|
150
151
|
- A local `/stage` belongs to the active worktree that started it. Do not disrupt a running stage for git bookkeeping alone. Before moving to a different worktree, stop/destroy the stage and recreate it from the new worktree, or warn first when the user's intent is unclear. Linked worktrees share stage state through the git common dir, so a new worktree can still stop the previous local stage.
|