@muggleai/works 4.13.0 → 4.14.0

package/plugin/skills/muggle-test-feature-local/SKILL.md

@@ -51,6 +51,7 @@ Gates run per `preference-gates/README.md`.
 | `openTestResultsAfterRun` | 8 | Open results page on Muggle Test dashboard after run |
 | `postPRVisualWalkthrough` | 10 | Post visual walkthrough to PR after results |
 | `autoCreatePR` | 10 (if no PR) | Auto-create the PR when posting the walkthrough has no PR to target |
+| `autoWatchPR` | 10.5 (if a PR exists) | Start a `muggle-pr-followup` watcher on the PR after the run |
 | `autoCleanup` | post-merge | Run cleanup after the PR for this work is merged (see [`_shared/post-merge-cleanup.md`](../_shared/post-merge-cleanup.md)) |
 
 ## Workflow
@@ -127,6 +128,12 @@ Gate `autoSelectLocalHost` per `preference-gates/README.md` + `preference-gates/
 
 Remind them: local URL is only the execution target, not tied to cloud project config.
 
+### 4a. Satisfy the test case chain (prerequisite parents)
+
+Before deciding the target's script, resolve its prerequisite chain from the backend test-plan graph and ensure every ancestor already has a ready script — generating any that don't, **test-generation only**, root-first. Follow [`_shared/test-case-chain-readiness.md`](../_shared/test-case-chain-readiness.md).
+
+`muggle-remote-test-case-ancestors-get` returns the chain; an `orphan` test case has no prerequisites — skip straight to Step 5. Do **not** infer parents from `precondition` text; the graph is authoritative.
+
 ### 5. Existing scripts vs new generation
 
 `muggle-remote-test-script-list` with `testCaseId`.
@@ -236,17 +243,30 @@ Non-blocking — one click to dismiss. Do not re-ask for the same `runId` within
 
 After reporting results:
 
-1. Fire [`postPRVisualWalkthrough`](../muggle-preferences/preference-gates/postPRVisualWalkthrough.md). On skip → end.
+1. Fire [`postPRVisualWalkthrough`](../muggle-preferences/preference-gates/postPRVisualWalkthrough.md). On skip → 10.5.
 2. `gh pr view --json number,title,url 2>/dev/null` — find the PR.
-3. If no PR: fire [`autoCreatePR`](../muggle-preferences/preference-gates/autoCreatePR.md). On skip → end.
+3. If no PR: fire [`autoCreatePR`](../muggle-preferences/preference-gates/autoCreatePR.md). On skip → 10.5.
 4. Assemble the `E2eReport` — see [`../muggle-pr-visual-walkthrough/e2e-report-assembly.md`](../muggle-pr-visual-walkthrough/e2e-report-assembly.md).
 5. Invoke [`../muggle-pr-visual-walkthrough/SKILL.md`](../muggle-pr-visual-walkthrough/SKILL.md) Mode A with the `E2eReport`.
 
+### 10.5. Offer to watch the PR for review follow-ups
+
+Once a PR exists for this work, offer to keep watching its review thread.
+
+1. Identify the PR — reuse the `gh pr view --json number,title,url` result from section 10 if available, else run it now. No PR (none exists, none created) → end.
+2. Fire [`autoWatchPR`](../muggle-preferences/preference-gates/autoWatchPR.md) with `{pr}` = `<owner>/<repo>#<number>`. On skip → end.
+3. On proceed: start the watcher reusing this run's context so it never re-prompts —
+   - Seed the `muggle-pr-followup` session slot and dispatch its loop per the stage-8 seeding in [`../do/open-prs/forward.md`](../do/open-prs/forward.md) (default slug `<repo>-pr<number>`).
+   - Additionally write `state.md`'s `## Pre-flight answers` block from the context resolved this run — validation strategy, local URL, project, credentials, auth, working tree — per [`../_shared/resolve-e2e-validation-context.md`](../_shared/resolve-e2e-validation-context.md#persisted-fields). Strategy = `local-e2e` for this local E2E run.
+
+The `/mprfollowup` shortcut starts the same watcher manually at any time.
+
 ## Non-negotiables
 
 - No silent auth skip.
 - **Never prompt for Electron launch approval** before execution — invoking this skill is the approval. Just run.
 - **Never diagnose a failed run from `execute`'s response stdout tail.** Always call `muggle-local-run-result-get` first; classify only from its structured fields and (when present) the artifacts it names. The execute tail is an excerpt and routinely truncates the failure cause.
+- Satisfy the prerequisite chain (Step 4a) before generating or replaying the target. Read it from `muggle-remote-test-case-ancestors-get` — never infer parents from `precondition` text. Generate any not-ready ancestor test-generation-only, root-first.
 - If replayable scripts exist, do not default to generation without user choice.
 - No hiding failures: surface errors and artifact paths.
 - **Always offer the agent-guidance reminder after every Electron run** (Step 9b) — pass or fail — unless 9a already routed the user into `muggle-feedback`. Never silently end a run without giving the user a one-click path to flag what was wrong.

package/plugin/skills/muggle-test-prepare/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: muggle-test-prepare
-description: "Make sure dev servers and sibling services are ready on the user's machine before running E2E acceptance tests. Checks which services need to be running, discovers sibling directories by folder name, verifies what's already listening, and offers to start anything that's missing — with the user's approval at every step. Use this skill whenever the user needs to prepare their local environment for E2E testing, verify their services are up, get their local dev stack ready, or when other muggle skills detect that required services are not listening on common ports. Triggers on: 'prepare for testing', 'make sure my services are running', 'check my local env', 'get ready for tests', 'are my services up', 'prepare local environment', 'spin up services', 'set up for E2E', 'verify my setup'. Also use when muggle-test, muggle-do, or muggle-test-feature-local need services running."
+description: "Use this skill to get a user's local environment ready before running E2E acceptance tests — verifying that the dev servers, APIs, and sibling services they need are actually up and responding, and offering to start whatever is missing (with approval at each step). Trigger whenever the user wants to confirm that specific ports or localhost URLs are listening/up before testing (e.g. 'check if localhost:3000 and the api on 8080 are listening', 'are my services up?'), make sure required services are running, spin up or prepare their local dev stack, or verify their setup — and whenever another muggle skill (muggle-test, muggle-do, muggle-test-feature-local) needs services running but they're not listening on the expected ports. This is environment readiness and service startup, not running the tests themselves."
 ---
 
 # Muggle Test Prepare
@@ -45,6 +45,8 @@ All launched processes are tracked in `/tmp/muggle-test-prepare.json`:
 
 `testing_scope` records what the user is testing (from [scope](./steps/scope.md)). `excluded_services` records services the user said can't run locally (from [viability-check](./steps/viability-check.md)).
 
+This file is **ephemeral runtime state**, not the saved recipe. The durable plan lives at `<repo>/.muggle-ai/prepare-plan.json` (or the parent-dir-keyed entry in `~/.muggle-ai/prepare-plans.json`) and is consulted in [reuse-plan](./steps/reuse-plan.md) before any other stage. The two files never merge.
+
 **On every invocation**, check this file first. If it exists with live PIDs (verify with `kill -0`), `AskUserQuestion`:
 - Option 1: "Keep them running — skip to testing"
 - Option 2: "Tear down and start fresh"
@@ -59,6 +61,7 @@ Gates run per [`preference-gates/README.md`](../muggle-preferences/preference-ga
 | Preference | Gates |
 |------------|-------|
 | `autoRebase` | [rebase-check](./steps/rebase-check.md) — rebase onto `origin/<default>` before starting dev servers |
+| `reusePreparePlan` | [reuse-plan](./steps/reuse-plan.md) — reuse the saved prepare plan for this stack, or rediscover |
 
 ## Workflow
 
@@ -66,6 +69,7 @@ Run the stages in this order. The sequence number is display-only — it lives o
 
 | # | Stage | Summary |
 |:--|:------|:--------|
+| 0 | [reuse-plan](./steps/reuse-plan.md) | Reuse saved prepare plan (gated); short-circuits to check-running on reuse |
 | 1 | [rebase-check](./steps/rebase-check.md) | Rebase onto default branch (gated) |
 | 2 | [scope](./steps/scope.md) | Frontend / backend / full stack |
 | 3 | [viability-check](./steps/viability-check.md) | Exclude services that can't run locally |

package/plugin/skills/muggle-test-prepare/steps/check-running.md

@@ -6,7 +6,7 @@ Run port detection and (when an app declares a backend URL) backend-health probe
 
 If **all** required services are running, skip straight to [smoke-test](./smoke-test.md) — don't trust port-listening alone.
 
-If some are running, acknowledge and continue to [start-commands](./start-commands.md) only for the missing ones. For already-running services:
+If some are running, acknowledge and continue to [start-commands](./start-commands.md) only for the missing ones. **Exception:** when this stage is entered via the [reuse-plan](./reuse-plan.md) short-circuit, the missing entries already have their `command` populated in `/tmp/muggle-test-prepare.json` from the reused plan — skip `start-commands` and go straight to [env-file](./env-file.md). For already-running services:
 - Option 1: "It's fine, keep it"
 - Option 2: "Restart it"
 
@@ -16,11 +16,13 @@ Mark kept services as `external: true` in the tracking file so cleanup leaves th
 
 When the user wants a port held by a process they did **not** select (typically a stale dev server from a sibling worktree):
 
-> "Port 3999 is held by PID 87421 (you didn't select this process). How do you want to proceed?"
+The held process is likely something the user is still using — a current test or dev server they value more than this prepare run. Don't auto-decide; leave the kill-vs-pause call to them.
 
-- Option 1: "Use the next available port" (recommended — non-destructive)
-- Option 2: "Force-kill PID 87421 and claim port 3999"
-- Option 3: "Abort"
+> "Port 3999 is held by PID 87421 (you didn't select this process — it may be a test or dev server you're still using). How do you want to proceed?"
+
+- Option 1: "Use the next available port" (recommended — non-destructive, leaves the existing process running)
+- Option 2: "Force-kill PID 87421 and claim port 3999" (kill-switch — only if you don't need that process)
+- Option 3: "Pause — leave it running, I'll finish up and re-run prepare later"
 
 **Option 1**: probe `3999 + N` for `N = 1, 2, …` until nothing listens. Record the new port and any env file edit (`PORT=` in `.env.local` etc.). Dev server may need restart to pick up.
 

package/plugin/skills/muggle-test-prepare/steps/identify-services.md

@@ -1,5 +1,7 @@
 # Identify required services & startup mode
 
+> Skipped when [reuse-plan](./reuse-plan.md) short-circuits — a reused plan supplies the service list and startup mode.
+
 List folder names in the **parent directory** of the current working directory:
 
 ```bash

package/plugin/skills/muggle-test-prepare/steps/readiness-report.md

@@ -24,3 +24,33 @@ If you launched the services:
 Logs: /tmp/muggle-prepare-*.log
 Cleanup: say "stop services" or re-invoke this skill.
 ```
+
+## Save the plan
+
+If this run came through discovery (i.e. Stage 0 [reuse-plan](./reuse-plan.md) did **not** short-circuit), persist the plan so the next run can skip the questions.
+
+Build the JSON from the in-memory tracking file, dropping runtime fields:
+
+```bash
+jq '{
+  version: 1,
+  updated: now | todate,
+  testing_scope: .testing_scope,
+  excluded_services: .excluded_services,
+  services: [.services[] | {name, dir, command, port}]
+}' /tmp/muggle-test-prepare.json
+```
+
+Resolve the write location:
+
+- If `git rev-parse --show-toplevel` succeeds (call the result `$REPO`) → write `$REPO/.muggle-ai/prepare-plan.json`. Create `$REPO/.muggle-ai/` if missing.
+- Else → upsert the entry under key `$(dirname "$PWD")` (absolute) in `~/.muggle-ai/prepare-plans.json`. Create the file as `{}` if missing.
+
+Then print, once:
+
+```
+✓ Saved this stack as your prepare plan — next run can skip the questions.
+  (Disable with `/muggle-preferences reusePreparePlan`.)
+```
+
+If this run short-circuited via [reuse-plan](./reuse-plan.md), don't rewrite — but **do** refresh `updated` and any `command` that was re-derived during validation. Skip the announcement on the refresh path.

package/plugin/skills/muggle-test-prepare/steps/reuse-plan.md

@@ -0,0 +1,44 @@
+# Stage 0 — reuse saved plan (or fall through)
+
+A previously saved **prepare plan** is the durable recipe for this stack. Distinct from the ephemeral `/tmp/muggle-test-prepare.json` tracker — that file holds live PIDs/logs and is rebuilt every run.
+
+## Resolve
+
+In order; first hit wins.
+
+1. **Project plan.** If `git rev-parse --show-toplevel` succeeds (call the result `$REPO`) and `$REPO/.muggle-ai/prepare-plan.json` exists → load it.
+2. **Global plan.** Else if `~/.muggle-ai/prepare-plans.json` exists, read the entry keyed by `$(dirname "$PWD")` (absolute path). If present → load that entry's value.
+3. **No plan found** → exit this step; the workflow continues at [rebase-check](./rebase-check.md).
+
+A loaded plan is a JSON object with `version`, `updated`, `testing_scope`, `excluded_services`, `services`. Reject and treat as "no plan" if `version != 1` or `services` is empty.
+
+## Gate `reusePreparePlan`
+
+Per [`muggle-preferences/preference-gates/README.md`](../../muggle-preferences/preference-gates/README.md). Read the current value from the `Muggle Test Preferences` session-context line; absent → `ask`.
+
+- `always` → silently take the **reuse path** (below). Print the silent footer (substitute `{services}` with the comma-separated names from the loaded plan).
+- `never` → take the **rediscover path**: exit this step; continue at [rebase-check](./rebase-check.md).
+- `ask` → print the loaded plan as a table:
+
+  ```
+  Service              Directory                          Command          Port
+  ──────────────────────────────────────────────────────────────────────────────
+  backend-api          ~/Github/backend-api               npm run dev      3001
+  …
+  ──────────────────────────────────────────────────────────────────────────────
+  ```
+
+  Run Picker 1 from the gate file (substitute `{services}`). Then Picker 2 ("Remember this choice?") per the shared template. Branch by Picker 1.
+
+## Reuse path
+
+1. **Validate per service entry.** For each `{name, dir, command, port}`:
+   - `dir` exists → keep. Else drop the entry and log `"Dropped <name>: directory <dir> no longer exists"`.
+   - The indicator file that produced `command` still exists in `dir` (e.g. `package.json` for an `npm`/`node` command; see the indicator table in [start-commands](./start-commands.md)) → keep. Else re-derive **just that one entry** by running the indicator-detection from [start-commands](./start-commands.md) against `dir`, and replace its `command`. Log `"Re-derived <name>: <old> → <new>"`.
+2. **All entries dropped** → discard the plan; continue at [rebase-check](./rebase-check.md). Otherwise proceed with surviving + re-derived entries.
+3. **Hydrate** `/tmp/muggle-test-prepare.json` with the surviving entries (no PIDs yet, `testing_scope` from the plan, `excluded_services` from the plan).
+4. **Short-circuit** to [check-running](./check-running.md). The skipped stages are [scope](./scope.md), [viability-check](./viability-check.md), [identify-services](./identify-services.md), [start-commands](./start-commands.md) — the reused plan supplies their answers. The remaining stages run normally: [env-file](./env-file.md), [fresh-install](./fresh-install.md), [start-services](./start-services.md) (only for entries not already listening), [smoke-test](./smoke-test.md), [readiness-report](./readiness-report.md).
+
+## Rediscover path
+
+Continue at [rebase-check](./rebase-check.md). The full normal flow runs.

package/dist/plugin/commands/mrelease.md

@@ -1,7 +0,0 @@
----
-description: Cut a @muggleai/works npm release (alias for /muggle-works-npm-release)
-argument-hint: [major|minor|patch]
-allowed-tools: [Skill]
----
-
-Invoke the `muggle-works-npm-release` skill via the Skill tool. Forward `$ARGUMENTS` as the skill's `args`.

package/dist/plugin/skills/mrelease/SKILL.md

@@ -1,8 +0,0 @@
----
-name: mrelease
-description: Explicit short alias for the `muggle-works-npm-release` skill. ONLY invoke when the user explicitly types `mrelease` or `/mrelease` — never auto-trigger from any other phrasing.
----
-
-# mrelease — alias for muggle-works-npm-release
-
-Invoke the `muggle-works-npm-release` skill via the Skill tool. Forward any user-provided arguments unchanged.

package/dist/plugin/skills/muggle-works-npm-release/SKILL.md

@@ -1,200 +0,0 @@
----
-name: muggle-works-npm-release
-description: >-
-  Cut @muggleai/works release: AskUserQuestion (major/minor/patch), sync master, stop if
-  nothing ships, semver baseline + Electron from GitHub, confirm plan, bump
-  package.json + sync:versions, full local verify, chore(release) PR, merge via gh,
-  dispatch publish-works-to-npm.yml—no local npm publish.
----
-
-# Muggle Test Works — npm release (single playbook)
-
-> Telemetry first step: see [`_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle-works-npm-release"`.
-
-Repo: **`multiplex-ai/muggle-ai-works`**. Workflow: **`.github/workflows/publish-works-to-npm.yml`** (“Publish Works to npm”). **Never** run local **`npm publish`** (OIDC trusted publishing in CI).
-
----
-
-## Phase 1 — Ask bump type (do this first)
-
-**Stop until the user answers.**
-
-**Prefer `AskUserQuestion`** with exactly these three options: **major**, **minor**, **patch** (fix). If the environment has no structured question tool, ask the same in plain text:
-
-> Is this release a **major**, **minor**, or **patch** (fix)?
-
-You may **recommend** a bump from commit subjects (e.g. `feat!` / breaking → major, `feat` → minor, `fix` / `chore` → patch) but **do not** choose for them. **Do not** edit files yet.
-
----
-
-## Phase 2 — Sync, surface state, empty-release gate
-
-Run from **`muggle-ai-works`**:
-
-```bash
-git checkout master && git pull --ff-only && git fetch --tags
-```
-
-Show what is shipping:
-
-```bash
-node -e 'console.log("master package.json:", require("./package.json").version)'
-npm view @muggleai/works version 2>&1 | sed 's/^/npm latest: /'
-```
-
-**Commits since the last release commit** (stop if there is nothing to ship):
-
-```bash
-LAST_RELEASE_SHA=$(git log --grep='chore(release)' --format='%H' -1)
-git log --oneline "$LAST_RELEASE_SHA..HEAD"
-```
-
-- If the log is **empty**, tell the user there is **nothing to ship** and **stop** (no branch, no bump, no PR).
-- If non-empty, present commits as a short table (subject; PR number from title/body if present).
-
----
-
-## Phase 3 — Version baseline, Electron, print summary, confirm
-
-### npm version (`nextNpmVersion`)
-
-1. **`npm view @muggleai/works version`** — last published on npm.
-2. Root **`package.json` → `version`** on current **`master`** checkout.
-3. **Baseline** = **semver-higher** of those two (never target below repo or npm).
-4. Apply the user’s **major / minor / patch** to that baseline → **`nextNpmVersion`** (semver-correct).
-
-### Electron (`muggleConfig`)
-
-1. Read **`package.json` → `muggleConfig.electronAppVersion`**.
-2. **Latest desktop on GitHub:**  
-   `https://api.github.com/repos/multiplex-ai/muggle-ai-works/releases?per_page=30`  
-   → newest **`tag_name`** matching **`electron-app-v*`** → strip prefix → **`latestElectronVersion`** (semver only).
-
-### Print (always)
-
-| Item | Value |
-| :--- | :---- |
-| Last **@muggleai/works** on npm | … |
-| **Baseline** for bump | … |
-| **`nextNpmVersion`** (to publish) | … |
-| Current **`electronAppVersion`** | … |
-| Latest **`electron-app-v…`** on GitHub | … |
-
-### Electron bump decision
-
-If **`latestElectronVersion`** ≠ current **`electronAppVersion`**, ask: **bump** Electron + all four **`muggleConfig.checksums`** to **`latestElectronVersion`**, or **keep** current.
-
-If bumping, checksums from:
-
-`https://github.com/multiplex-ai/muggle-ai-works/releases/download/electron-app-vVERSION/checksums.txt`
-
-Map zip artifacts → **`darwin-arm64`**, **`darwin-x64`**, **`win32-x64`**, **`linux-x64`** (same mapping rules as today).
-
-**Stop again:** user must **confirm** the full plan (**`nextNpmVersion`** + Electron choice). If they cancel, **do not** branch, merge, or dispatch CI.
-
----
-
-## Phase 4 — After explicit confirmation only
-
-### 1. Branch and bump
-
-```bash
-git checkout -b "chore/release-<VERSION>"
-npm version "<VERSION>" --no-git-tag-version
-```
-
-Replace **`<VERSION>`** with **`nextNpmVersion`** (dots in the branch name are fine, e.g. `chore/release-4.8.0`).
-
-- If Electron bump agreed: set **`muggleConfig.electronAppVersion`** and all four **`muggleConfig.checksums`** in **`package.json`**.
-
-### 2. Propagate versions (do not hand-edit manifests)
-
-```bash
-pnpm run sync:versions
-```
-
-Never hand-edit **`.claude-plugin/marketplace.json`**, **`.cursor-plugin/marketplace.json`**, **`plugin/.claude-plugin/plugin.json`**, **`plugin/.cursor-plugin/plugin.json`**, or **`server.json`** — **`sync-versions`** (and **`build`**) owns them.
-
-If you changed Electron after the first sync, run **`pnpm run sync:versions`** again.
-
-### 3. Full local verify (before push)
-
-```bash
-pnpm run lint:check && pnpm run typecheck && pnpm test && pnpm run build && pnpm run verify:plugin && pnpm run verify:contracts && pnpm run verify:electron-release-checksums
-```
-
-- **`pnpm run build`** is required before **`verify:plugin`** — the verifier reads the **built** plugin under **`dist/plugin/`**, not source under **`plugin/`**.
-- If **anything** fails, **stop** and surface the error; **do not** push a broken release.
-
-### 4. Commit (**`chore(release)`**)
-
-Stage version-touched files (at minimum **`package.json`** plus whatever **`sync:versions`** changed — typically the marketplace/plugin **`server.json`** paths above).
-
-**Subject:** `chore(release): @muggleai/works <VERSION>`
-
-**Body:** one bullet per shipping PR / theme, note **Electron** bump or unchanged, and any coordinated follow-ups in sibling repos (e.g. teaching-service, UI). Use a **heredoc** for `git commit` so newlines are preserved.
-
-### 5. PR, merge, update local **`master`**
-
-```bash
-git push -u origin HEAD
-gh pr create --repo multiplex-ai/muggle-ai-works --base master --head <branch> \
-  --title "chore(release): @muggleai/works <VERSION>" \
-  --body "<PR body: version delta, bump rationale, shipping list, Electron status, manifests touched by sync:versions, short test plan checklist>"
-```
-
-**Merge:** when the human has approved the release in this session, run **`gh pr merge`** (squash is fine unless the repo prefers merge commits), then:
-
-```bash
-git checkout master && git pull --ff-only
-node -e 'console.log("master now:", require("./package.json").version)'
-```
-
-Confirm **`package.json`** on **`master`** matches **`nextNpmVersion`** before publishing.
-
----
-
-## Phase 5 — Trigger publish (CI only)
-
-Prefer **explicit version** (not “auto bump”):
-
-```bash
-gh workflow run publish-works-to-npm.yml --repo multiplex-ai/muggle-ai-works --ref master \
-  --field "version=<VERSION>" --field "bump=patch"
-```
-
-The `bump=patch` field is a harmless placeholder when `version` is set; the workflow prefers the explicit `version` input.
-
-**Or** **`git tag "v<VERSION>"`** && **`git push origin "v<VERSION>"`** only if that tag **does not** already exist on the remote; if the tag exists, use **`workflow_dispatch`** with **`version`**.
-
-Watch the run and confirm jobs succeed:
-
-```bash
-gh run list --repo multiplex-ai/muggle-ai-works --workflow=publish-works-to-npm.yml --limit 1
-gh run watch <RUN_ID> --repo multiplex-ai/muggle-ai-works --exit-status
-```
-
-Verify the registry:
-
-```bash
-npm view @muggleai/works version
-```
-
-Give the user the **Actions run URL**. If npm lags, wait ~60s and retry.
-
----
-
-## Rules
-
-- **No local `npm publish`.**
-- **Phase 1:** use **`AskUserQuestion`** for major / minor / patch when available (see Phase 1).
-- Phases 1–3: keep chat concise; Phase 4–5 can be terse status lines.
-- If the user cancels after Phase 3, **do not** merge or dispatch CI.
-- **Tag vs npm:** **`v*`** tags are for the **npm** package; **`electron-app-v*`** is separate — **`electronAppVersion`** can move independently of **`version`**.
-
----
-
-## Notes (troubleshooting)
-
-- Workflow **`name:`** / filename is tied to npm **Trusted Publishing** — see the comment block at the top of **`publish-works-to-npm.yml`** if auth fails.
-- If commits land on **`master`** between opening the PR and merging, re-check **`git log`** vs the last **`chore(release)`** before merging; rebasing the release branch may be needed so **`master`** still matches what you intend to ship.

package/plugin/commands/mrelease.md

@@ -1,7 +0,0 @@
----
-description: Cut a @muggleai/works npm release (alias for /muggle-works-npm-release)
-argument-hint: [major|minor|patch]
-allowed-tools: [Skill]
----
-
-Invoke the `muggle-works-npm-release` skill via the Skill tool. Forward `$ARGUMENTS` as the skill's `args`.

package/plugin/skills/mrelease/SKILL.md

@@ -1,8 +0,0 @@
----
-name: mrelease
-description: Explicit short alias for the `muggle-works-npm-release` skill. ONLY invoke when the user explicitly types `mrelease` or `/mrelease` — never auto-trigger from any other phrasing.
----
-
-# mrelease — alias for muggle-works-npm-release
-
-Invoke the `muggle-works-npm-release` skill via the Skill tool. Forward any user-provided arguments unchanged.

package/plugin/skills/muggle-works-npm-release/SKILL.md

@@ -1,200 +0,0 @@
----
-name: muggle-works-npm-release
-description: >-
-  Cut @muggleai/works release: AskUserQuestion (major/minor/patch), sync master, stop if
-  nothing ships, semver baseline + Electron from GitHub, confirm plan, bump
-  package.json + sync:versions, full local verify, chore(release) PR, merge via gh,
-  dispatch publish-works-to-npm.yml—no local npm publish.
----
-
-# Muggle Test Works — npm release (single playbook)
-
-> Telemetry first step: see [`_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle-works-npm-release"`.
-
-Repo: **`multiplex-ai/muggle-ai-works`**. Workflow: **`.github/workflows/publish-works-to-npm.yml`** (“Publish Works to npm”). **Never** run local **`npm publish`** (OIDC trusted publishing in CI).
-
----
-
-## Phase 1 — Ask bump type (do this first)
-
-**Stop until the user answers.**
-
-**Prefer `AskUserQuestion`** with exactly these three options: **major**, **minor**, **patch** (fix). If the environment has no structured question tool, ask the same in plain text:
-
-> Is this release a **major**, **minor**, or **patch** (fix)?
-
-You may **recommend** a bump from commit subjects (e.g. `feat!` / breaking → major, `feat` → minor, `fix` / `chore` → patch) but **do not** choose for them. **Do not** edit files yet.
-
----
-
-## Phase 2 — Sync, surface state, empty-release gate
-
-Run from **`muggle-ai-works`**:
-
-```bash
-git checkout master && git pull --ff-only && git fetch --tags
-```
-
-Show what is shipping:
-
-```bash
-node -e 'console.log("master package.json:", require("./package.json").version)'
-npm view @muggleai/works version 2>&1 | sed 's/^/npm latest: /'
-```
-
-**Commits since the last release commit** (stop if there is nothing to ship):
-
-```bash
-LAST_RELEASE_SHA=$(git log --grep='chore(release)' --format='%H' -1)
-git log --oneline "$LAST_RELEASE_SHA..HEAD"
-```
-
-- If the log is **empty**, tell the user there is **nothing to ship** and **stop** (no branch, no bump, no PR).
-- If non-empty, present commits as a short table (subject; PR number from title/body if present).
-
----
-
-## Phase 3 — Version baseline, Electron, print summary, confirm
-
-### npm version (`nextNpmVersion`)
-
-1. **`npm view @muggleai/works version`** — last published on npm.
-2. Root **`package.json` → `version`** on current **`master`** checkout.
-3. **Baseline** = **semver-higher** of those two (never target below repo or npm).
-4. Apply the user’s **major / minor / patch** to that baseline → **`nextNpmVersion`** (semver-correct).
-
-### Electron (`muggleConfig`)
-
-1. Read **`package.json` → `muggleConfig.electronAppVersion`**.
-2. **Latest desktop on GitHub:**  
-   `https://api.github.com/repos/multiplex-ai/muggle-ai-works/releases?per_page=30`  
-   → newest **`tag_name`** matching **`electron-app-v*`** → strip prefix → **`latestElectronVersion`** (semver only).
-
-### Print (always)
-
-| Item | Value |
-| :--- | :---- |
-| Last **@muggleai/works** on npm | … |
-| **Baseline** for bump | … |
-| **`nextNpmVersion`** (to publish) | … |
-| Current **`electronAppVersion`** | … |
-| Latest **`electron-app-v…`** on GitHub | … |
-
-### Electron bump decision
-
-If **`latestElectronVersion`** ≠ current **`electronAppVersion`**, ask: **bump** Electron + all four **`muggleConfig.checksums`** to **`latestElectronVersion`**, or **keep** current.
-
-If bumping, checksums from:
-
-`https://github.com/multiplex-ai/muggle-ai-works/releases/download/electron-app-vVERSION/checksums.txt`
-
-Map zip artifacts → **`darwin-arm64`**, **`darwin-x64`**, **`win32-x64`**, **`linux-x64`** (same mapping rules as today).
-
-**Stop again:** user must **confirm** the full plan (**`nextNpmVersion`** + Electron choice). If they cancel, **do not** branch, merge, or dispatch CI.
-
----
-
-## Phase 4 — After explicit confirmation only
-
-### 1. Branch and bump
-
-```bash
-git checkout -b "chore/release-<VERSION>"
-npm version "<VERSION>" --no-git-tag-version
-```
-
-Replace **`<VERSION>`** with **`nextNpmVersion`** (dots in the branch name are fine, e.g. `chore/release-4.8.0`).
-
-- If Electron bump agreed: set **`muggleConfig.electronAppVersion`** and all four **`muggleConfig.checksums`** in **`package.json`**.
-
-### 2. Propagate versions (do not hand-edit manifests)
-
-```bash
-pnpm run sync:versions
-```
-
-Never hand-edit **`.claude-plugin/marketplace.json`**, **`.cursor-plugin/marketplace.json`**, **`plugin/.claude-plugin/plugin.json`**, **`plugin/.cursor-plugin/plugin.json`**, or **`server.json`** — **`sync-versions`** (and **`build`**) owns them.
-
-If you changed Electron after the first sync, run **`pnpm run sync:versions`** again.
-
-### 3. Full local verify (before push)
-
-```bash
-pnpm run lint:check && pnpm run typecheck && pnpm test && pnpm run build && pnpm run verify:plugin && pnpm run verify:contracts && pnpm run verify:electron-release-checksums
-```
-
-- **`pnpm run build`** is required before **`verify:plugin`** — the verifier reads the **built** plugin under **`dist/plugin/`**, not source under **`plugin/`**.
-- If **anything** fails, **stop** and surface the error; **do not** push a broken release.
-
-### 4. Commit (**`chore(release)`**)
-
-Stage version-touched files (at minimum **`package.json`** plus whatever **`sync:versions`** changed — typically the marketplace/plugin **`server.json`** paths above).
-
-**Subject:** `chore(release): @muggleai/works <VERSION>`
-
-**Body:** one bullet per shipping PR / theme, note **Electron** bump or unchanged, and any coordinated follow-ups in sibling repos (e.g. teaching-service, UI). Use a **heredoc** for `git commit` so newlines are preserved.
-
-### 5. PR, merge, update local **`master`**
-
-```bash
-git push -u origin HEAD
-gh pr create --repo multiplex-ai/muggle-ai-works --base master --head <branch> \
-  --title "chore(release): @muggleai/works <VERSION>" \
-  --body "<PR body: version delta, bump rationale, shipping list, Electron status, manifests touched by sync:versions, short test plan checklist>"
-```
-
-**Merge:** when the human has approved the release in this session, run **`gh pr merge`** (squash is fine unless the repo prefers merge commits), then:
-
-```bash
-git checkout master && git pull --ff-only
-node -e 'console.log("master now:", require("./package.json").version)'
-```
-
-Confirm **`package.json`** on **`master`** matches **`nextNpmVersion`** before publishing.
-
----
-
-## Phase 5 — Trigger publish (CI only)
-
-Prefer **explicit version** (not “auto bump”):
-
-```bash
-gh workflow run publish-works-to-npm.yml --repo multiplex-ai/muggle-ai-works --ref master \
-  --field "version=<VERSION>" --field "bump=patch"
-```
-
-The `bump=patch` field is a harmless placeholder when `version` is set; the workflow prefers the explicit `version` input.
-
-**Or** **`git tag "v<VERSION>"`** && **`git push origin "v<VERSION>"`** only if that tag **does not** already exist on the remote; if the tag exists, use **`workflow_dispatch`** with **`version`**.
-
-Watch the run and confirm jobs succeed:
-
-```bash
-gh run list --repo multiplex-ai/muggle-ai-works --workflow=publish-works-to-npm.yml --limit 1
-gh run watch <RUN_ID> --repo multiplex-ai/muggle-ai-works --exit-status
-```
-
-Verify the registry:
-
-```bash
-npm view @muggleai/works version
-```
-
-Give the user the **Actions run URL**. If npm lags, wait ~60s and retry.
-
----
-
-## Rules
-
-- **No local `npm publish`.**
-- **Phase 1:** use **`AskUserQuestion`** for major / minor / patch when available (see Phase 1).
-- Phases 1–3: keep chat concise; Phase 4–5 can be terse status lines.
-- If the user cancels after Phase 3, **do not** merge or dispatch CI.
-- **Tag vs npm:** **`v*`** tags are for the **npm** package; **`electron-app-v*`** is separate — **`electronAppVersion`** can move independently of **`version`**.
-
----
-
-## Notes (troubleshooting)
-
-- Workflow **`name:`** / filename is tied to npm **Trusted Publishing** — see the comment block at the top of **`publish-works-to-npm.yml`** if auth fails.
-- If commits land on **`master`** between opening the PR and merging, re-check **`git log`** vs the last **`chore(release)`** before merging; rebasing the release branch may be needed so **`master`** still matches what you intend to ship.