@muggleai/works 5.19.0-staging.128 → 5.19.0-staging.129

package/dist/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "muggle",
   "description": "Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.",
-  "version": "5.19.0-staging.128",
+  "version": "5.19.0-staging.129",
   "author": {
     "name": "Muggle AI",
     "email": "support@muggle-ai.com"

package/dist/plugin/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "muggle",
   "displayName": "Muggle AI",
   "description": "Ship quality products with AI-powered end-to-end (E2E) acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
-  "version": "5.19.0-staging.128",
+  "version": "5.19.0-staging.129",
   "author": {
     "name": "Muggle AI",
     "email": "support@muggle-ai.com"

package/dist/plugin/skills/_shared/post-merge-cleanup.md

@@ -34,15 +34,26 @@ Only if a worktree was used.
 
 A worktree's dependency dir (`node_modules`, and nested workspace copies) is often a **link** — a symlink or a Windows junction — to a shared tree rather than a real copy. A forced or recursive delete follows the link and wipes that shared target, breaking every other worktree.
 
+`git worktree remove` refuses for two unrelated reasons, and **both texts lead to the same forbidden flag** — one because it is the obvious fix, the other because git prints it as the suggestion. Clear each cause at its source; neither is a reason to reconsider the flag.
+
 1. **Never `--force`.** It is the one flag that follows links.
 2. Clear the dependency and build dirs first, nested workspace ones included (`packages/*/node_modules`, `dist`). A plain `git worktree remove` fails with `Directory not empty` while they remain, and the obvious fix for that error is exactly the forbidden flag.
    - A **link** → unlink it first with the host OS's unlink, removing the link only and never its target.
    - A **real directory** → delete it in place.
    Check which it is before deleting; the two are indistinguishable from a listing but not from a `rm -r`.
-3. Then plain `git worktree remove {worktreePath}`.
-4. `git worktree prune` to drop the administrative entry when the directory went away out from under git.
+3. Clear the worktree's own dirty state — what the merge already landed, and nothing else. While anything remains, removal fails with `contains modified or untracked files, use --force to delete it`, an error that prescribes the forbidden flag in its own text.
+
+   Expect this on any cycle that pushed through a server-side signed commit: that mutation writes to the remote only, so the worktree keeps the edits as modifications of a commit it never made locally. The dirt is this cycle's own landed work, not something the user left behind.
+
+   Read the dirt with `git -C {worktreePath} status --porcelain`, then settle each kind on whether the base already carries it:
+   - **Tracked modifications** — when `git -C {worktreePath} diff origin/<base>` is empty the working tree holds nothing the merge did not land, so `git -C {worktreePath} reset --hard` discards a copy rather than work. A non-empty diff stops the sequence: that diff is unlanded work, and this step would be the thing that destroyed it.
+   - **Untracked files** — never on the base, so no diff can clear them. Delete only the paths this procedure itself created: the dependency and build dirs cleared above. Anything else stops the sequence and is reported by name; an untracked file is the one thing in the worktree with no copy anywhere.
+
+   **Never `git clean -x`.** `-x` is what reaches the ignored dependency dir, and clean recurses through a link exactly as a forced remove does — it undoes the unlink above under a different name.
+4. Then plain `git worktree remove {worktreePath}`.
+5. `git worktree prune` to drop the administrative entry when the directory went away out from under git.
 
-**Verify:** the path is gone, it no longer appears in `git worktree list`, **and** the shared dependency tree the links pointed at still exists. That last check is the one that catches a link-follow.
+**Verify:** the path is gone, it no longer appears in `git worktree list`, the removal ran without `--force`, **and** the shared dependency tree the links pointed at still exists. That last check is the one that catches a link-follow.
 
 ## 3. Delete the local branch
 

package/dist/release-manifest.json

@@ -1,7 +1,7 @@
 {
   "release": "5.18.0",
-  "buildId": "run-128-1",
-  "commitSha": "f1af44f6fff370b4e9bc4e16a4fc5601bdca2163",
-  "buildTime": "2026-09-22T17:31:39Z",
+  "buildId": "run-129-1",
+  "commitSha": "0d87587f70defe63f99a2bb64cd41366dd1b78e8",
+  "buildTime": "2026-09-22T18:01:23Z",
   "serviceName": "muggle-ai-works-mcp"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@muggleai/works",
   "mcpName": "io.github.multiplex-ai/muggle",
-  "version": "5.19.0-staging.128",
+  "version": "5.19.0-staging.129",
   "description": "Ship quality products with AI-powered E2E acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
   "type": "module",
   "main": "dist/index.js",

package/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "muggle",
   "description": "Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.",
-  "version": "5.19.0-staging.128",
+  "version": "5.19.0-staging.129",
   "author": {
     "name": "Muggle AI",
     "email": "support@muggle-ai.com"

package/plugin/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "muggle",
   "displayName": "Muggle AI",
   "description": "Ship quality products with AI-powered end-to-end (E2E) acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
-  "version": "5.19.0-staging.128",
+  "version": "5.19.0-staging.129",
   "author": {
     "name": "Muggle AI",
     "email": "support@muggle-ai.com"

package/plugin/skills/_shared/post-merge-cleanup.md

@@ -34,15 +34,26 @@ Only if a worktree was used.
 
 A worktree's dependency dir (`node_modules`, and nested workspace copies) is often a **link** — a symlink or a Windows junction — to a shared tree rather than a real copy. A forced or recursive delete follows the link and wipes that shared target, breaking every other worktree.
 
+`git worktree remove` refuses for two unrelated reasons, and **both texts lead to the same forbidden flag** — one because it is the obvious fix, the other because git prints it as the suggestion. Clear each cause at its source; neither is a reason to reconsider the flag.
+
 1. **Never `--force`.** It is the one flag that follows links.
 2. Clear the dependency and build dirs first, nested workspace ones included (`packages/*/node_modules`, `dist`). A plain `git worktree remove` fails with `Directory not empty` while they remain, and the obvious fix for that error is exactly the forbidden flag.
    - A **link** → unlink it first with the host OS's unlink, removing the link only and never its target.
    - A **real directory** → delete it in place.
    Check which it is before deleting; the two are indistinguishable from a listing but not from a `rm -r`.
-3. Then plain `git worktree remove {worktreePath}`.
-4. `git worktree prune` to drop the administrative entry when the directory went away out from under git.
+3. Clear the worktree's own dirty state — what the merge already landed, and nothing else. While anything remains, removal fails with `contains modified or untracked files, use --force to delete it`, an error that prescribes the forbidden flag in its own text.
+
+   Expect this on any cycle that pushed through a server-side signed commit: that mutation writes to the remote only, so the worktree keeps the edits as modifications of a commit it never made locally. The dirt is this cycle's own landed work, not something the user left behind.
+
+   Read the dirt with `git -C {worktreePath} status --porcelain`, then settle each kind on whether the base already carries it:
+   - **Tracked modifications** — when `git -C {worktreePath} diff origin/<base>` is empty the working tree holds nothing the merge did not land, so `git -C {worktreePath} reset --hard` discards a copy rather than work. A non-empty diff stops the sequence: that diff is unlanded work, and this step would be the thing that destroyed it.
+   - **Untracked files** — never on the base, so no diff can clear them. Delete only the paths this procedure itself created: the dependency and build dirs cleared above. Anything else stops the sequence and is reported by name; an untracked file is the one thing in the worktree with no copy anywhere.
+
+   **Never `git clean -x`.** `-x` is what reaches the ignored dependency dir, and clean recurses through a link exactly as a forced remove does — it undoes the unlink above under a different name.
+4. Then plain `git worktree remove {worktreePath}`.
+5. `git worktree prune` to drop the administrative entry when the directory went away out from under git.
 
-**Verify:** the path is gone, it no longer appears in `git worktree list`, **and** the shared dependency tree the links pointed at still exists. That last check is the one that catches a link-follow.
+**Verify:** the path is gone, it no longer appears in `git worktree list`, the removal ran without `--force`, **and** the shared dependency tree the links pointed at still exists. That last check is the one that catches a link-follow.
 
 ## 3. Delete the local branch