@muggleai/works 5.0.4 → 5.2.0

package/plugin/skills/muggle-test/execute-remote.md

@@ -0,0 +1,49 @@
+# Muggle Test — Remote Execution Path (Mode B)
+
+> The Remote execution process for the `muggle-test` router: trigger cloud test-script generation/replay against a preview/staging URL and monitor. Returns a uniform runs list to the router.
+
+## Inputs (the router passes these in)
+
+- The hydrated test cases (fetched once by the router before dispatch).
+- Per-case `mode` — `replay` or `regen`, chosen during replay-vs-regen classification.
+- `projectId`, `useCaseId`.
+
+## Ask for target URL
+
+> "What's the preview/staging URL to test against?"
+
+## Trigger remote workflows (in parallel)
+
+Branch each test case on its `mode`, then issue **all** workflow-start calls in parallel — never loop them sequentially. Mix regen and replay starts in the same parallel batch.
+
+**Regen-mode test case** — `muggle-remote-workflow-start-test-script-generation`:
+
+- `projectId`: The project ID
+- `useCaseId`: The use case ID
+- `testCaseId`: The test case ID
+- `name`: `"muggle-test: {test case title}"`
+- `url`: The preview/staging URL
+- `goal`: From the test case
+- `precondition`: From the test case (use `"None"` if empty)
+- `instructions`: From the test case
+- `expectedResult`: From the test case
+
+**Replay-mode test case** — `muggle-remote-workflow-start-test-script-replay` against the latest replayable script for that test case (resolve via `muggle-remote-test-script-list` if not already in hand from the classification step). Tag results with `mode: "replay"` so the router routes failures correctly.
+
+Store each returned workflow runtime ID along with its mode tag.
+
+## Monitor and report (in parallel)
+
+Issue all `muggle-remote-wf-get-ts-gen-latest-run` calls in parallel, one per runtime ID.
+
+```
+Test Case                  Workflow Status   Runtime ID
+────────────────────────────────────────────────────────
+Login with valid creds     RUNNING           rt-abc123
+Login with invalid creds   COMPLETED         rt-def456
+Checkout flow              QUEUED            rt-ghi789
+```
+
+## Output
+
+Return the uniform runs list the router consumes: `[{ testCaseId, mode, runtimeId, status }]`.

package/plugin/skills/muggle-test/reference.md

@@ -23,9 +23,8 @@ Lookup material pulled out of `SKILL.md` to keep the always-loaded body lean. Ev
 | Execute (regen) | `muggle-remote-workflow-start-test-script-generation` | Remote |
 | Execute (replay) | `muggle-remote-workflow-start-test-script-replay` | Remote |
 | Failure-mode telemetry | `muggle-local-telemetry-event-emit` | Both |
-| Results | `muggle-local-run-result-get` | Local |
+| Results + cloud refs (studio-published `viewUrl` / `cloudTestScriptId` / `cloudActionScriptId`) | `muggle-local-run-result-get` | Local |
 | Results | `muggle-remote-wf-get-ts-gen-latest-run`, `muggle-remote-wf-get-ts-replay-latest-run` | Remote |
-| Publish | `muggle-local-publish-test-script` | Local |
 | Per-step screenshots (for walkthrough) | `muggle-remote-test-script-get` | Both |
 | Browser | `open` (shell command) | Both |
 | PR walkthrough | `muggle-pr-visual-walkthrough` (shared skill) | Both |

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

@@ -12,7 +12,7 @@ description: Run a real-browser end-to-end (E2E) acceptance test against localho
 | Scope | MCP tools |
 | :---- | :-------- |
 | Cloud (projects, cases, scripts, auth) | `muggle-remote-*` |
-| Local (Electron run, publish, results) | `muggle-local-*` |
+| Local (Electron run, results — the studio publishes during the run) | `muggle-local-*` |
 | Create new entities (preview / create) | `muggle-remote-project-create`, `muggle-remote-use-case-prompt-preview`, `muggle-remote-use-case-create-from-prompts`, `muggle-remote-test-case-generate-from-prompt`, `muggle-remote-test-case-create` |
 
 The local URL only changes where the browser opens; it does not change the remote project or test definitions.
@@ -158,11 +158,11 @@ Gate `showElectronBrowser` (per `preference-gates/README.md`). Reuse the choice
 
 `showUi` is only ever omitted or `false` — never pass `showUi: true`.
 
-### 8. Upload run to cloud (every completed run; open `viewUrl` gated by `openTestResultsAfterRun`)
+### 8. Open the run on the dashboard (`viewUrl` gated by `openTestResultsAfterRun`)
 
-Upload pass-or-fail. Failed runs still need cloud-hosted screenshots and per-step actions for the PR walkthrough — without them reviewers see only a generic "failed" link. The `status` field in the upload payload tells the backend whether to promote the run's action script as the test case's canonical replay script (passed → promote; failed → record only).
+The studio publishes every completed run — pass or fail — to the cloud during execution, so the run result already carries the cloud refs. Failed runs are published too, so reviewers get the per-step screenshots, not just a generic "failed" link.
 
-- Publish per [`../_shared/dev-loop/publish.md`](../_shared/dev-loop/publish.md) — includes the zero-step `muggle-remote-local-run-upload` fallback.
+- Read the cloud refs per [`../_shared/dev-loop/publish.md`](../_shared/dev-loop/publish.md): `viewUrl` / `cloudTestScriptId` / `cloudActionScriptId` from `muggle-local-run-result-get`.
 - Gate `openTestResultsAfterRun` (per `preference-gates/README.md`):
   - `always` → open `viewUrl` automatically (`open "<viewUrl>"` on macOS or OS equivalent).
   - `never` → print the URL only.
@@ -172,7 +172,7 @@ Upload pass-or-fail. Failed runs still need cloud-hosted screenshots and per-ste
 
 Read the run record per [`../_shared/dev-loop/failures.md`](../_shared/dev-loop/failures.md) and [failure interpretation](../_shared/dev-loop/failures.md) — never diagnose from `execute`'s stdout tail.
 
-- Include in the report: status, duration, pass/fail summary, per-step summary (passed runs), artifact paths, errors if failed, and script view URL when publishing ran.
+- Include in the report: status, duration, pass/fail summary, per-step summary (passed runs), artifact paths, errors if failed, and the `viewUrl` from the run result.
 
 ### 9a. Route a failed run through the debug path
 

package/dist/plugin/skills/_shared/github-cli-recipes.md

@@ -1,21 +0,0 @@
-# GitHub CLI Recipes
-
-Reusable `gh` / `git` snippets used by `muggle-pr-followup` (watcher + bootstrap) and `/muggle-do` (address-reviews + open-prs). Each recipe is one file — load only what you need.
-
-Skills assume a working `gh auth status`. Auth errors surface verbatim from `gh`.
-
-## Index
-
-| Recipe | Use case |
-| :----- | :------- |
-| [`pr-metadata`](github-cli-recipes/pr-metadata.md) | Snapshot PR state, head SHA, branch, conflict + `behind_by` out-of-date detection — watcher + bootstrap. |
-| [`submitted-reviews`](github-cli-recipes/submitted-reviews.md) | Fetch a review by id / watcher's body-only-review check. |
-| [`pr-checks`](github-cli-recipes/pr-checks.md) | Check-run rollup for the head SHA — watcher's CI poll. |
-| [`line-comments-for-review`](github-cli-recipes/line-comments-for-review.md) | Pull a review's line comments — `/muggle-do` per-comment routing. |
-| [`unresolved-threads`](github-cli-recipes/unresolved-threads.md) | GraphQL unresolved-thread state — watcher's dispatch trigger + resolve-reminder. |
-| [`reply-line-comment`](github-cli-recipes/reply-line-comment.md) | POST a threaded reply on a line comment. |
-| [`top-level-comment`](github-cli-recipes/top-level-comment.md) | POST a top-level PR comment — resolve-reminder + overflow. |
-| [`push-to-branch`](github-cli-recipes/push-to-branch.md) | Push + capture new SHA after address-reviews work. |
-| [`verify-working-tree`](github-cli-recipes/verify-working-tree.md) | Three checks bootstrap runs before seeding state. |
-| [`pr-edit`](github-cli-recipes/pr-edit.md) | Refresh title or body when address-reviews mode flips state. |
-| [`loop-user-identity`](github-cli-recipes/loop-user-identity.md) | Resolve the GitHub login of the loop user. |

package/dist/plugin/skills/muggle-preferences/preference-gates/autoPublishLocalResults.md

@@ -1,11 +0,0 @@
-# `autoPublishLocalResults`
-
-Upload local run artifacts to the Muggle Test cloud, or keep them local.
-
-**Picker 1** — header `Share results?`, question `"Upload these results to the Muggle Test dashboard?"`
-- `Upload them` — `Needed for the dashboard view, PR walkthrough, and team visibility.` → `always`
-- `Keep local-only` — `Stay on this machine — no dashboard view or PR walkthrough.` → `never`
-
-**Silent action**
-- `always` → `Uploading to the dashboard`
-- `never` → `Keeping results local`

package/plugin/skills/_shared/github-cli-recipes.md

@@ -1,21 +0,0 @@
-# GitHub CLI Recipes
-
-Reusable `gh` / `git` snippets used by `muggle-pr-followup` (watcher + bootstrap) and `/muggle-do` (address-reviews + open-prs). Each recipe is one file — load only what you need.
-
-Skills assume a working `gh auth status`. Auth errors surface verbatim from `gh`.
-
-## Index
-
-| Recipe | Use case |
-| :----- | :------- |
-| [`pr-metadata`](github-cli-recipes/pr-metadata.md) | Snapshot PR state, head SHA, branch, conflict + `behind_by` out-of-date detection — watcher + bootstrap. |
-| [`submitted-reviews`](github-cli-recipes/submitted-reviews.md) | Fetch a review by id / watcher's body-only-review check. |
-| [`pr-checks`](github-cli-recipes/pr-checks.md) | Check-run rollup for the head SHA — watcher's CI poll. |
-| [`line-comments-for-review`](github-cli-recipes/line-comments-for-review.md) | Pull a review's line comments — `/muggle-do` per-comment routing. |
-| [`unresolved-threads`](github-cli-recipes/unresolved-threads.md) | GraphQL unresolved-thread state — watcher's dispatch trigger + resolve-reminder. |
-| [`reply-line-comment`](github-cli-recipes/reply-line-comment.md) | POST a threaded reply on a line comment. |
-| [`top-level-comment`](github-cli-recipes/top-level-comment.md) | POST a top-level PR comment — resolve-reminder + overflow. |
-| [`push-to-branch`](github-cli-recipes/push-to-branch.md) | Push + capture new SHA after address-reviews work. |
-| [`verify-working-tree`](github-cli-recipes/verify-working-tree.md) | Three checks bootstrap runs before seeding state. |
-| [`pr-edit`](github-cli-recipes/pr-edit.md) | Refresh title or body when address-reviews mode flips state. |
-| [`loop-user-identity`](github-cli-recipes/loop-user-identity.md) | Resolve the GitHub login of the loop user. |

package/plugin/skills/muggle-preferences/preference-gates/autoPublishLocalResults.md

@@ -1,11 +0,0 @@
-# `autoPublishLocalResults`
-
-Upload local run artifacts to the Muggle Test cloud, or keep them local.
-
-**Picker 1** — header `Share results?`, question `"Upload these results to the Muggle Test dashboard?"`
-- `Upload them` — `Needed for the dashboard view, PR walkthrough, and team visibility.` → `always`
-- `Keep local-only` — `Stay on this machine — no dashboard view or PR walkthrough.` → `never`
-
-**Silent action**
-- `always` → `Uploading to the dashboard`
-- `never` → `Keeping results local`