[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72CDK2X4KC15HGCGSS46NG3":3,"skill-same:01M72CDK2X4KC15HGCGSS46NG3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M72CDK2X4KC15HGCGSS46NG3","desktop-e2e",null,"Run or author DOM-driven end-to-end scenarios against the bundled Maude desktop app (Tauri + WKWebView) using WebdriverIO. Use when the user asks to \"run desktop e2e\", \"test the native app\", \"regression-test the desktop build\", \"add a desktop scenario\", or when closing a feature that touched the native shell (apps\u002Fdesktop) \u002F studio UI and needs native verification beyond browser-mode agent-browser.","1aGh\u002Fmaude","1aGh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17166964?v=4","01M72CAQDBB0YG724KFT7WEYRF","Michal Dovrtel","01M72CAQDXC32AWQRZYNJXXDC4",3,"MIT","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdesktop-e2e\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: desktop-e2e\ndescription: Run or author DOM-driven end-to-end scenarios against the bundled Maude desktop app (Tauri + WKWebView) using WebdriverIO. Use when the user asks to \"run desktop e2e\", \"test the native app\", \"regression-test the desktop build\", \"add a desktop scenario\", or when closing a feature that touched the native shell (apps\u002Fdesktop) \u002F studio UI and needs native verification beyond browser-mode agent-browser.\n---\n\n# desktop-e2e — DOM-driven E2E for the native Maude `.app`\n\nRepo-internal skill (Maude-specific; lives in `.claude\u002Fskills\u002F`, **not** shipped via the marketplace or npm). It owns how we drive the **real bundled desktop app** in scenario tests — the native counterpart to `agent-browser` (which only reaches the web layer at `http:\u002F\u002Flocalhost:\u003Cport>`, never the native shell).\n\nBackground + decisions: `.ai\u002Fplans\u002Ffeature-desktop-e2e-scenario-harness.md`, memory `project_tauri_desktop_e2e_testing_path`, and `feedback_prefer_dom_driven_e2e_not_computer_use`.\n\n## The one rule\n\n**DOM-driven, never computer-use.** Find elements by `data-testid`, click\u002Ftype, assert on DOM\u002Ftext, screenshot for evidence. Computer-use\u002Fpixel-vision is too flaky (user feedback) and is NOT used here. Native menu actions are invoked via `window.__TAURI__` commands (see `helpers\u002Fnative.ts`), not by clicking native chrome.\n\n## What it is\n\n- **Harness:** `apps\u002Fdesktop\u002Fe2e\u002F` — WebdriverIO + [`@wdio\u002Ftauri-service`](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@wdio\u002Ftauri-service) (Tauri's official E2E path). On macOS the service runs an **embedded W3C WebDriver server inside the app** (no external driver — Apple ships none for WKWebView). The Rust crate `tauri-plugin-wdio-webdriver` is registered in `apps\u002Fdesktop\u002Fsrc-tauri\u002Fsrc\u002Flib.rs` under `#[cfg(debug_assertions)]`, so the **shipped release `.app` never starts a WebDriver server** — only `tauri dev` and the `--debug` test build do.\n- **Scenarios:** `apps\u002Fdesktop\u002Fe2e\u002Fscenarios\u002F*.e2e.ts`. The committed **spec** lives in `.ai\u002Fscenarios\u002F\u003Cslug>\u002Fspec.md`. **Run outputs go to the SAME place as `\u002Fflow:validate --scenario`** — `.ai\u002Fdevice\u002Fscenario-runs\u002F\u003Cslug>\u002F\u003CYYYY-MM-DD-HHMM>\u002F` (gitignored): `report.md` at the run root + screenshots under `native-desktop\u002F`. Per the scenario convention, **never write run outputs into `.ai\u002Fscenarios\u002F\u003Cslug>\u002F`** (that's spec\u002Frunners only).\n- **Fixture:** `apps\u002Fdesktop\u002Fe2e\u002Ffixtures\u002Fproject\u002F` — a minimal `.design\u002F` project the test app opens via `MAUDE_PROJECT_ROOT`, bypassing first-run\u002Fproject-picker so scenarios need no native dialog.\n\n## How to run\n\n```sh\n# 1. (once \u002F after harness or dep changes) install the e2e workspace deps\npnpm install\n\n# 2. (once \u002F on studio-client or Rust source change) build the test app\npnpm test:e2e:desktop:build      # → apps\u002Fdesktop: tauri build --debug\n\n# 3. run the scenarios\npnpm test:e2e:desktop            # → wdio run apps\u002Fdesktop\u002Fe2e\u002Fwdio.conf.ts\n```\n\nRequires the macOS\u002FWindows toolchain (cargo + tauri-cli). The `tauri build` `beforeBuildCommand` syncs the Bun sidecar binary automatically.\n\n> **Where a lane runs, and no dialogs on a person's screen (2.1.1).** Heavy work goes to the Mac mini through `scripts\u002Fremote-lane.sh` whenever it can run there: the studio suite, builds and headless screenshot chains. The desktop e2e lanes themselves cannot run there yet. The script refuses them, because the mini has no Rust toolchain for the debug `.app` and no unlocked GUI session; `MAUDE_REMOTE_ALLOW_DESKTOP_E2E=1` is for the day it does. So a lane run on a person's Mac must never raise a system dialog over their work. `wdio.conf.ts` sets `MAUDE_E2E_NO_DIALOGS=1` for every lane. The debug build then writes what it would have asked to `~\u002FLibrary\u002FLogs\u002Fcom.maude.app.e2e\u002Fshell.log` (`e2e: native dialog not shown`) and takes the dismiss answer (Close \u002F Cancel \u002F Not now). A release build never reads that variable. Never unset it in a lane config (`scripts\u002Ftest\u002Fdesktop-e2e-no-dialogs.test.mjs`). Delete fixture roots only in the lane's `onComplete`, after `await completeLane()` has stopped the app, so no tab is left open on a folder that is gone.\n\n> **Studio client changes need a bundle rebuild first.** The test app serves the committed `apps\u002Fstudio\u002Fdist\u002Fclient.bundle.js`. If you added\u002Fchanged `data-testid`s in `apps\u002Fstudio\u002Fclient\u002F`, rebuild release-minified before `test:e2e:desktop:build`: `cd apps\u002Fstudio && MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release` and commit `dist\u002Fclient.bundle.js` + `dist\u002Fstyles.css` (CLAUDE.md rule).\n\n> **The e2e sidecar is built with `--e2e`.** A plain `--release` server binary ignores every `MAUDE_E2E_*` switch (`apps\u002Fstudio\u002Frelease-build.ts`, #168), so the lanes that force a claude status, fake the installer or use the e2e port ladder need the sidecar from `cd apps\u002Fstudio && MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release --e2e` before `test:e2e:desktop:build`. CI never passes `--e2e`.\n\n## The `data-testid` convention\n\nScenarios target `data-testid`, never CSS classes (classes churn with the DS). Format: `data-testid=\"\u003Carea>-\u003Cthing>[-\u003Cid>]\"`, kebab-case, slug-derived for list items. Established hooks in `apps\u002Fstudio\u002Fclient\u002Fapp.jsx`:\n\n| testid | Element |\n| --- | --- |\n| `canvas-list` | the sidebar file tree (`.st-tree`) |\n| `canvas-row-\u003Cslug>` | a canvas row; `\u003Cslug>` = the canvas path kebab-cased (e.g. `ui\u002FSmoke.tsx` → `canvas-row-ui-smoke`) |\n| `canvas-frame` | the **active** canvas iframe |\n| `smoke-artboard-content` | content inside the fixture canvas |\n\nWhen a new feature adds UI a scenario must reach, add a `data-testid` to that element in the same change.\n\n### The v2 shell's hooks (where to look, what to use)\n\nThe v2 shell re-emits the v1 hooks that kept their meaning and adds about 1,700 new ones. **The inventory is the source of truth:** `apps\u002Fstudio\u002Fclient\u002Ftestids.json` (one record per hook: `hook`, `pattern`, `meaning`, `producer`, `region`, `consumers`, `v2`) and its readable twin `apps\u002Fstudio\u002Fclient\u002FTESTIDS.md`. A hook marked `retired` has a `notes` field naming its replacement; never target one. Look a hook up before you write a selector: `jq -r '.[] | select(.hook|test(\"^vh-\")) | [.hook,.v2,.meaning] | @tsv' apps\u002Fstudio\u002Fclient\u002Ftestids.json`. Testids are an API: a new hook goes into both files in the same commit, an existing one is never renamed.\n\nRegions a scenario usually needs (all live; `\u003C…>` is a pattern):\n\n| Area | Anchor hooks |\n| --- | --- |\n| Shell chrome | `project-pill` (opens `project-menu`; rows are `project-menu-row-\u003Caction-id>`, submenus `project-menu-row-sub-\u003Cname>`), `share-cluster` · `share-cluster-share` · `share-cluster-status` (`data-status`), `panel-icon-\u003Cwhich>`, `palette-input` · `palette-row-\u003Cid>` (⌘K), `settings-sheet` |\n| Home and sign-in | `home-root`, `home-search`, `home-recent-row-\u003Cpid>-\u003Cslug>`, `signin-card` · `signin-local` · `signin-cloud`, `onb-\u003Csheet>` (Advanced sheets) |\n| Canvases and the open canvas | `canvas-list`, `canvas-row-\u003Cslug>`, `canvas-row-trashed-\u003Cslug>`, `canvas-frame`, `empty-canvas`, `toolbar-\u003Cmode>` · `toolbar-slot-\u003CtoolId>`, `edit-name-tag` and the other `edit-*` object hooks |\n| AI chat | `ai-chat-header`, `ai-chat-island`, `chat-composer`, `chat-tool-row`, `takes-island` |\n| Version history and Trash | `vh-panel`, `vh-now`, `vh-filter-\u003Cid>`, `vh-list`, `project-history-row-\u003Crevision>` · `project-history-restore-\u003Crevision>` · `project-history-undo-\u003Crevision>`, `all-trashed` · `all-trashed-restore` |\n| Comments and annotations | `comments-panel`, `comment-item-\u003Cid>`, `comment-filter-\u003Cid>`, `annotation-list`, `stickers-*`, `vote-sheet` |\n| Present and video | `present-controls`, `present-zone`, `presenter-view`, `timeline-panel`, `transcript-panel`, `video-scrub-bar` |\n| Export, assets, handoff | `export-format-\u003Cid>`, `export-scope`, `exports-panel`, `assets-panel`, `assets-search`, `handoff-sheet`, `handoff-target-\u003Cid>` |\n| Design system | `ds-bar`, `ds-section-\u003Ckind>`, `ds-bar-pending`, `ds-review-scrim`, `canvases-ds-row` |\n| Diagnostics and sync | `diag-tab-\u003Cview>`, `diag-logs`, `diag-logs-filter-\u003Csource>`, `sync-panel`, `sync-row-\u003Cslug>`, `sync-resync` |\n| Inspector | `inspector-panel`, `insp-sec-\u003Cid>`, `insp-row-\u003Cname>`, `layers-panel` |\n\nNotes for v2 scenarios: the canvas is a separate origin (see the gotchas), so drive it by coordinates or a structural route, not by selectors inside it; words in assertions come from the CONTRACT (`.design\u002Fsystem\u002Fmaude-v2\u002FCONTRACT.md` §3), so assert \"Version history\", \"Trash\", \"Annotations\", never the v1 names; and a scenario for a role-gated action asserts the server's refusal, not only a hidden button.\n\n## How to add a new scenario\n\n1. **Add testids** to the studio-client (or native) elements the flow touches; rebuild the bundle (above).\n2. **Write the spec:** `.ai\u002Fscenarios\u002F\u003Cslug>\u002Fspec.md` (mirror `app-boots-and-renders-canvas\u002Fspec.md`; platform matrix lists `native-desktop`).\n3. **Write the test:** `apps\u002Fdesktop\u002Fe2e\u002Fscenarios\u002F\u003Cslug>.e2e.ts`. Use the helpers: `waitForSidecar()`, `enterCanvasFrame()`\u002F`exitToTop()`, `capture(label)` (screenshot + report row), `invokeTauri(cmd, args)` \u002F `isNativeShell()`.\n4. **Run** via `\u002Fdesktop-e2e \u003Cslug>` or `pnpm test:e2e:desktop`.\n\n### Scenarios that need native dialogs \u002F OAuth — debug-only stubs (BUILT)\n\nThe pilot avoids native chrome by opening the fixture via `MAUDE_PROJECT_ROOT` and calling Tauri commands directly. A scenario that genuinely needs the native file picker or the GitHub device flow drives Home's sheets via two **deterministic stubs** gated behind `#[cfg(debug_assertions)]` (so NEVER in the release `.app`):\n\n- **`MAUDE_E2E_PICK_DIR`** → `pick_directory` (`src-tauri\u002Fsrc\u002Flib.rs`) returns this path instead of opening the native folder dialog.\n- **`MAUDE_E2E_FAKE_GITHUB_LOGIN`** → `github_sign_in` (`src-tauri\u002Fsrc\u002Foauth.rs`) emits a deterministic device-code (`E2E-CODE`) for ~2.5 s, then \"authorizes\" and reports the fake login — no browser, no network, no keychain write.\n\nThe first-run scenario is **`onboarding.e2e.ts`** + **`wdio.onboarding.conf.ts`** (`pnpm test:e2e:desktop:onboarding`). First launch IS Home (S6.8; S6.15 retired the v1 `OnboardingWizard`, `app_is_first_run` and `MAUDE_FORCE_ONBOARDING`): the config DROPS `MAUDE_PROJECT_ROOT`, wipes the `com.maude.app.e2e` app-state and points `MAUDE_HOME_PROJECTS_DIR` at a throwaway dir, so the boot opens the `home` window with the sign-in card (`signin-card`, `signin-local`, `signin-advanced`, `signin-adv-\u003Cid>`). A new project starts EMPTY (Q10, `scaffoldDesign` seeds no canvas); Help › Help and guides (`help-add-guides`) adds the two guide canvases. Lanes that start on a clean profile enter a project through `helpers\u002Fhome-entry.ts` (`connectHubFromHome`, `focusHome`, `followNewTab`). The retired wizard hooks (`onboarding-wizard`, `ob-door-*`, `ob-device-*`, …) are marked `retired` in `client\u002Ftestids.json` with their new home. A `project-switch`-style scenario can still reuse `MAUDE_E2E_PICK_DIR`.\n\n## Known gotchas (all VERIFIED on the first real run, 2026-06-29)\n\nThe pilot run surfaced five real integration issues — every one is now fixed\u002Fencoded in the harness. Keep these in mind when extending:\n\n- **Pin `@wdio\u002Ftauri-service` to `1.1.0` (exact, not `^`).** `1.2.0` (current latest) is published broken — it imports `installMockSyncOverride` from `@wdio\u002Fnative-utils`, which that version doesn't export, so the service fails to initialize. `^1.2.0` would regress to it. Re-check when a `1.2.1+` ships.\n- **Distinct bundle identifier for the e2e build (`com.maude.app.e2e`, in `tauri.e2e.conf.json`).** Without it, the `tauri_plugin_single_instance` plugin makes the test launch **focus a developer's already-running Maude** (same `com.maude.app`) instead of spawning a fresh fixture instance — the test then drives the wrong project. The distinct id isolates the e2e instance (own single-instance lock, own app-state dir).\n- **Pin a non-default embedded WebDriver port (`embeddedPort: 4455`, in `wdio.conf.ts`).** The default is 4445; a developer's running **debug** Maude also carries the wdio plugin (it's `#[cfg(debug_assertions)]`) and answers on 4445, so the harness would connect to the wrong instance. 4455 sidesteps the collision.\n- **First-run wizard suppression.** A distinct identifier ⇒ fresh app-state ⇒ `is_first_run` true ⇒ the OnboardingWizard renders over everything. `app_state::is_first_run` now returns false when `MAUDE_PROJECT_ROOT` is set (an explicit project target = not a first run). `MAUDE_PROJECT_ROOT` reliably forwards: the embedded provider spawns the app with `{...process.env}`.\n- **`data-testid` for canvas rows strips the designRoot prefix.** `file.path` is `.design\u002Fui\u002FSmoke.tsx` (with the `.design\u002F` root), so the slug derivation strips a leading dot-folder → `canvas-row-ui-smoke` (not `…-design-ui-smoke`).\n- **Canvas iframe content is a SOFT assertion (step 5b).** The canvas takes a few seconds to build+render after opening (an immediate post-click screenshot can show \"0 ARTBOARDS\" — it's timing, not a runtime gap; a later screenshot shows the full render). The hard assertion is the top-frame `canvas-frame` element + its `data-path`; the in-frame DOM check is best-effort (cross-origin DDR-054 if the split is on; with `MAUDE_CANVAS_ORIGIN_SPLIT=0` it's same-origin and renders — confirmed visually in the evidence). Tighten to a hard in-frame assertion (with generous waits) when a scenario must prove deep canvas DOM.\n- **A git-repo fixture must be OFFLINE (refs-only, no configured remote URL).** A fixture with a real `remote.origin.url` (e.g. `https:\u002F\u002Fgithub.com\u002F…`) makes the dev-server's unattended ahead\u002Fbehind probe spawn a `git fetch` to that host during boot; that network call keeps the WKWebView JS unresponsive long enough that the embedded WebDriver's `execute`\u002F`getUrl` time out — the harness hangs at `waitForSidecar` and the scenario fails before its first assertion (observed on `git-branch-switcher`, 2026-06-30). Fix: write `refs\u002Fremotes\u002Forigin\u002F*` directly with `git update-ref`\u002F`git symbolic-ref` and do NOT `git remote add` → `classifyRemoteUrl` returns `none`, the probe is a no-op, boot is deterministic. The \"remote · not downloaded yet\" rows still render (they read disk refs, not the remote config). See `apps\u002Fdesktop\u002Fe2e\u002Ffixtures\u002Fmake-git-fixture.ts`.\n- **`tauri-service: Failed to wait for plugin initialization` (script timeout) is non-fatal.** It's the service's wdio mock-store injection giving up; scenarios that don't use request mocking (all of ours) still run + pass once the webview settles. Don't chase it.\n- **No active display ⇒ the whole harness wedges (run it on a machine with a woken screen).** If EVERY WebDriver command times out — `execute\u002Fasync`, then `getUrl` \u002F `element` at 60 s each, so `waitForSidecar` fails before the first assertion — the cause is usually that the session has **no awake display**. macOS throttles the off-screen WKWebView (occlusion \u002F App-Nap) so its embedded WebDriver can't answer. Confirm in seconds WITHOUT WebDriver: `screencapture -x` comes back **fully black**, `pmset -g powerstate IODisplayWrangler` errors, and `osascript … get size of windows` returns empty bounds — meanwhile `curl http:\u002F\u002Flocalhost:\u003Cport>\u002F_health` is `ok` (the sidecar is fine; only the webview is throttled). This is the `feedback_native_app_verification_ceiling` in its \"headless \u002F display-asleep\" form — it is NOT a scenario or app defect. Re-run with the screen awake (or hand the run to the user's interactive session, as the git scenarios were verified). `caffeinate` can't conjure a display that isn't attached.\n- **Signed vs test build:** the harness drives a `--debug` build (embedded WebDriver), not the exact signed release. Same source, different profile — a near-release smoke, documented.\n- **Not covered:** the Bun sidecar process itself, native OS dialogs, and the macOS menu bar chrome — assert their *effects* via the webview \u002F Tauri commands, or a separate probe. Dialog\u002FOAuth stubs (for first-run\u002Fproject-switch scenarios) are still deferred (above).\n\n## When NOT to use\n\nBrowser-renderable studio UI is cheaper to verify with `agent-browser` in browser mode (`maude design serve`). Reach for desktop-e2e only for native-shell behavior: sidecar lifecycle, webview navigation, first-run, project switch, native menus, OAuth\u002Fkeychain, updater.\n","# desktop-e2e — DOM-driven E2E for the native Maude `.app`\n\nRepo-internal skill (Maude-specific; lives in `.claude\u002Fskills\u002F`, **not** shipped via the marketplace or npm). It owns how we drive the **real bundled desktop app** in scenario tests — the native counterpart to `agent-browser` (which only reaches the web layer at `http:\u002F\u002Flocalhost:\u003Cport>`, never the native shell).\n\nBackground + decisions: `.ai\u002Fplans\u002Ffeature-desktop-e2e-scenario-harness.md`, memory `project_tauri_desktop_e2e_testing_path`, and `feedback_prefer_dom_driven_e2e_not_computer_use`.\n\n## The one rule\n\n**DOM-driven, never computer-use.** Find elements by `data-testid`, click\u002Ftype, assert on DOM\u002Ftext, screenshot for evidence. Computer-use\u002Fpixel-vision is too flaky (user feedback) and is NOT used here. Native menu actions are invoked via `window.__TAURI__` commands (see `helpers\u002Fnative.ts`), not by clicking native chrome.\n\n## What it is\n\n- **Harness:** `apps\u002Fdesktop\u002Fe2e\u002F` — WebdriverIO + [`@wdio\u002Ftauri-service`](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@wdio\u002Ftauri-service) (Tauri's official E2E path). On macOS the service runs an **embedded W3C WebDriver server inside the app** (no external driver — Apple ships none for WKWebView). The Rust crate `tauri-plugin-wdio-webdriver` is registered in `apps\u002Fdesktop\u002Fsrc-tauri\u002Fsrc\u002Flib.rs` under `#[cfg(debug_assertions)]`, so the **shipped release `.app` never starts a WebDriver server** — only `tauri dev` and the `--debug` test build do.\n- **Scenarios:** `apps\u002Fdesktop\u002Fe2e\u002Fscenarios\u002F*.e2e.ts`. The committed **spec** lives in `.ai\u002Fscenarios\u002F\u003Cslug>\u002Fspec.md`. **Run outputs go to the SAME place as `\u002Fflow:validate --scenario`** — `.ai\u002Fdevice\u002Fscenario-runs\u002F\u003Cslug>\u002F\u003CYYYY-MM-DD-HHMM>\u002F` (gitignored): `report.md` at the run root + screenshots under `native-desktop\u002F`. Per the scenario convention, **never write run outputs into `.ai\u002Fscenarios\u002F\u003Cslug>\u002F`** (that's spec\u002Frunners only).\n- **Fixture:** `apps\u002Fdesktop\u002Fe2e\u002Ffixtures\u002Fproject\u002F` — a minimal `.design\u002F` project the test app opens via `MAUDE_PROJECT_ROOT`, bypassing first-run\u002Fproject-picker so scenarios need no native dialog.\n\n## How to run\n\n```sh\n# 1. (once \u002F after harness or dep changes) install the e2e workspace deps\npnpm install\n\n# 2. (once \u002F on studio-client or Rust source change) build the test app\npnpm test:e2e:desktop:build      # → apps\u002Fdesktop: tauri build --debug\n\n# 3. run the scenarios\npnpm test:e2e:desktop            # → wdio run apps\u002Fdesktop\u002Fe2e\u002Fwdio.conf.ts\n```\n\nRequires the macOS\u002FWindows toolchain (cargo + tauri-cli). The `tauri build` `beforeBuildCommand` syncs the Bun sidecar binary automatically.\n\n> **Where a lane runs, and no dialogs on a person's screen (2.1.1).** Heavy work goes to the Mac mini through `scripts\u002Fremote-lane.sh` whenever it can run there: the studio suite, builds and headless screenshot chains. The desktop e2e lanes themselves cannot run there yet. The script refuses them, because the mini has no Rust toolchain for the debug `.app` and no unlocked GUI session; `MAUDE_REMOTE_ALLOW_DESKTOP_E2E=1` is for the day it does. So a lane run on a person's Mac must never raise a system dialog over their work. `wdio.conf.ts` sets `MAUDE_E2E_NO_DIALOGS=1` for every lane. The debug build then writes what it would have asked to `~\u002FLibrary\u002FLogs\u002Fcom.maude.app.e2e\u002Fshell.log` (`e2e: native dialog not shown`) and takes the dismiss answer (Close \u002F Cancel \u002F Not now). A release build never reads that variable. Never unset it in a lane config (`scripts\u002Ftest\u002Fdesktop-e2e-no-dialogs.test.mjs`). Delete fixture roots only in the lane's `onComplete`, after `await completeLane()` has stopped the app, so no tab is left open on a folder that is gone.\n\n> **Studio client changes need a bundle rebuild first.** The test app serves the committed `apps\u002Fstudio\u002Fdist\u002Fclient.bundle.js`. If you added\u002Fchanged `data-testid`s in `apps\u002Fstudio\u002Fclient\u002F`, rebuild release-minified before `test:e2e:desktop:build`: `cd apps\u002Fstudio && MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release` and commit `dist\u002Fclient.bundle.js` + `dist\u002Fstyles.css` (CLAUDE.md rule).\n\n> **The e2e sidecar is built with `--e2e`.** A plain `--release` server binary ignores every `MAUDE_E2E_*` switch (`apps\u002Fstudio\u002Frelease-build.ts`, #168), so the lanes that force a claude status, fake the installer or use the e2e port ladder need the sidecar from `cd apps\u002Fstudio && MAUDE_SKIP_RUNTIME_BUILD=1 bun run build.ts --release --e2e` before `test:e2e:desktop:build`. CI never passes `--e2e`.\n\n## The `data-testid` convention\n\nScenarios target `data-testid`, never CSS classes (classes churn with the DS). Format: `data-testid=\"\u003Carea>-\u003Cthing>[-\u003Cid>]\"`, kebab-case, slug-derived for list items. Established hooks in `apps\u002Fstudio\u002Fclient\u002Fapp.jsx`:\n\n| testid | Element |\n| --- | --- |\n| `canvas-list` | the sidebar file tree (`.st-tree`) |\n| `canvas-row-\u003Cslug>` | a canvas row; `\u003Cslug>` = the canvas path kebab-cased (e.g. `ui\u002FSmoke.tsx` → `canvas-row-ui-smoke`) |\n| `canvas-frame` | the **active** canvas iframe |\n| `smoke-artboard-content` | content inside the fixture canvas |\n\nWhen a new feature adds UI a scenario must reach, add a `data-testid` to that element in the same change.\n\n### The v2 shell's hooks (where to look, what to use)\n\nThe v2 shell re-emits the v1 hooks that kept their meaning and adds about 1,700 new ones. **The inventory is the source of truth:** `apps\u002Fstudio\u002Fclient\u002Ftestids.json` (one record per hook: `hook`, `pattern`, `meaning`, `producer`, `region`, `consumers`, `v2`) and its readable twin `apps\u002Fstudio\u002Fclient\u002FTESTIDS.md`. A hook marked `retired` has a `notes` field naming its replacement; never target one. Look a hook up before you write a selector: `jq -r '.[] | select(.hook|test(\"^vh-\")) | [.hook,.v2,.meaning] | @tsv' apps\u002Fstudio\u002Fclient\u002Ftestids.json`. Testids are an API: a new hook goes into both files in the same commit, an existing one is never renamed.\n\nRegions a scenario usually needs (all live; `\u003C…>` is a pattern):\n\n| Area | Anchor hooks |\n| --- | --- |\n| Shell chrome | `project-pill` (opens `project-menu`; rows are `project-menu-row-\u003Caction-id>`, submenus `project-menu-row-sub-\u003Cname>`), `share-cluster` · `share-cluster-share` · `share-cluster-status` (`data-status`), `panel-icon-\u003Cwhich>`, `palette-input` · `palette-row-\u003Cid>` (⌘K), `settings-sheet` |\n| Home and sign-in | `home-root`, `home-search`, `home-recent-row-\u003Cpid>-\u003Cslug>`, `signin-card` · `signin-local` · `signin-cloud`, `onb-\u003Csheet>` (Advanced sheets) |\n| Canvases and the open canvas | `canvas-list`, `canvas-row-\u003Cslug>`, `canvas-row-trashed-\u003Cslug>`, `canvas-frame`, `empty-canvas`, `toolbar-\u003Cmode>` · `toolbar-slot-\u003CtoolId>`, `edit-name-tag` and the other `edit-*` object hooks |\n| AI chat | `ai-chat-header`, `ai-chat-island`, `chat-composer`, `chat-tool-row`, `takes-island` |\n| Version history and Trash | `vh-panel`, `vh-now`, `vh-filter-\u003Cid>`, `vh-list`, `project-history-row-\u003Crevision>` · `project-history-restore-\u003Crevision>` · `project-history-undo-\u003Crevision>`, `all-trashed` · `all-trashed-restore` |\n| Comments and annotations | `comments-panel`, `comment-item-\u003Cid>`, `comment-filter-\u003Cid>`, `annotation-list`, `stickers-*`, `vote-sheet` |\n| Present and video | `present-controls`, `present-zone`, `presenter-view`, `timeline-panel`, `transcript-panel`, `video-scrub-bar` |\n| Export, assets, handoff | `export-format-\u003Cid>`, `export-scope`, `exports-panel`, `assets-panel`, `assets-search`, `handoff-sheet`, `handoff-target-\u003Cid>` |\n| Design system | `ds-bar`, `ds-section-\u003Ckind>`, `ds-bar-pending`, `ds-review-scrim`, `canvases-ds-row` |\n| Diagnostics and sync | `diag-tab-\u003Cview>`, `diag-logs`, `diag-logs-filter-\u003Csource>`, `sync-panel`, `sync-row-\u003Cslug>`, `sync-resync` |\n| Inspector | `inspector-panel`, `insp-sec-\u003Cid>`, `insp-row-\u003Cname>`, `layers-panel` |\n\nNotes for v2 scenarios: the canvas is a separate origin (see the gotchas), so drive it by coordinates or a structural route, not by selectors inside it; words in assertions come from the CONTRACT (`.design\u002Fsystem\u002Fmaude-v2\u002FCONTRACT.md` §3), so assert \"Version history\", \"Trash\", \"Annotations\", never the v1 names; and a scenario for a role-gated action asserts the server's refusal, not only a hidden button.\n\n## How to add a new scenario\n\n1. **Add testids** to the studio-client (or native) elements the flow touches; rebuild the bundle (above).\n2. **Write the spec:** `.ai\u002Fscenarios\u002F\u003Cslug>\u002Fspec.md` (mirror `app-boots-and-renders-canvas\u002Fspec.md`; platform matrix lists `native-desktop`).\n3. **Write the test:** `apps\u002Fdesktop\u002Fe2e\u002Fscenarios\u002F\u003Cslug>.e2e.ts`. Use the helpers: `waitForSidecar()`, `enterCanvasFrame()`\u002F`exitToTop()`, `capture(label)` (screenshot + report row), `invokeTauri(cmd, args)` \u002F `isNativeShell()`.\n4. **Run** via `\u002Fdesktop-e2e \u003Cslug>` or `pnpm test:e2e:desktop`.\n\n### Scenarios that need native dialogs \u002F OAuth — debug-only stubs (BUILT)\n\nThe pilot avoids native chrome by opening the fixture via `MAUDE_PROJECT_ROOT` and calling Tauri commands directly. A scenario that genuinely needs the native file picker or the GitHub device flow drives Home's sheets via two **deterministic stubs** gated behind `#[cfg(debug_assertions)]` (so NEVER in the release `.app`):\n\n- **`MAUDE_E2E_PICK_DIR`** → `pick_directory` (`src-tauri\u002Fsrc\u002Flib.rs`) returns this path instead of opening the native folder dialog.\n- **`MAUDE_E2E_FAKE_GITHUB_LOGIN`** → `github_sign_in` (`src-tauri\u002Fsrc\u002Foauth.rs`) emits a deterministic device-code (`E2E-CODE`) for ~2.5 s, then \"authorizes\" and reports the fake login — no browser, no network, no keychain write.\n\nThe first-run scenario is **`onboarding.e2e.ts`** + **`wdio.onboarding.conf.ts`** (`pnpm test:e2e:desktop:onboarding`). First launch IS Home (S6.8; S6.15 retired the v1 `OnboardingWizard`, `app_is_first_run` and `MAUDE_FORCE_ONBOARDING`): the config DROPS `MAUDE_PROJECT_ROOT`, wipes the `com.maude.app.e2e` app-state and points `MAUDE_HOME_PROJECTS_DIR` at a throwaway dir, so the boot opens the `home` window with the sign-in card (`signin-card`, `signin-local`, `signin-advanced`, `signin-adv-\u003Cid>`). A new project starts EMPTY (Q10, `scaffoldDesign` seeds no canvas); Help › Help and guides (`help-add-guides`) adds the two guide canvases. Lanes that start on a clean profile enter a project through `helpers\u002Fhome-entry.ts` (`connectHubFromHome`, `focusHome`, `followNewTab`). The retired wizard hooks (`onboarding-wizard`, `ob-door-*`, `ob-device-*`, …) are marked `retired` in `client\u002Ftestids.json` with their new home. A `project-switch`-style scenario can still reuse `MAUDE_E2E_PICK_DIR`.\n\n## Known gotchas (all VERIFIED on the first real run, 2026-06-29)\n\nThe pilot run surfaced five real integration issues — every one is now fixed\u002Fencoded in the harness. Keep these in mind when extending:\n\n- **Pin `@wdio\u002Ftauri-service` to `1.1.0` (exact, not `^`).** `1.2.0` (current latest) is published broken — it imports `installMockSyncOverride` from `@wdio\u002Fnative-utils`, which that version doesn't export, so the service fails to initialize. `^1.2.0` would regress to it. Re-check when a `1.2.1+` ships.\n- **Distinct bundle identifier for the e2e build (`com.maude.app.e2e`, in `tauri.e2e.conf.json`).** Without it, the `tauri_plugin_single_instance` plugin makes the test launch **focus a developer's already-running Maude** (same `com.maude.app`) instead of spawning a fresh fixture instance — the test then drives the wrong project. The distinct id isolates the e2e instance (own single-instance lock, own app-state dir).\n- **Pin a non-default embedded WebDriver port (`embeddedPort: 4455`, in `wdio.conf.ts`).** The default is 4445; a developer's running **debug** Maude also carries the wdio plugin (it's `#[cfg(debug_assertions)]`) and answers on 4445, so the harness would connect to the wrong instance. 4455 sidesteps the collision.\n- **First-run wizard suppression.** A distinct identifier ⇒ fresh app-state ⇒ `is_first_run` true ⇒ the OnboardingWizard renders over everything. `app_state::is_first_run` now returns false when `MAUDE_PROJECT_ROOT` is set (an explicit project target = not a first run). `MAUDE_PROJECT_ROOT` reliably forwards: the embedded provider spawns the app with `{...process.env}`.\n- **`data-testid` for canvas rows strips the designRoot prefix.** `file.path` is `.design\u002Fui\u002FSmoke.tsx` (with the `.design\u002F` root), so the slug derivation strips a leading dot-folder → `canvas-row-ui-smoke` (not `…-design-ui-smoke`).\n- **Canvas iframe content is a SOFT assertion (step 5b).** The canvas takes a few seconds to build+render after opening (an immediate post-click screenshot can show \"0 ARTBOARDS\" — it's timing, not a runtime gap; a later screenshot shows the full render). The hard assertion is the top-frame `canvas-frame` element + its `data-path`; the in-frame DOM check is best-effort (cross-origin DDR-054 if the split is on; with `MAUDE_CANVAS_ORIGIN_SPLIT=0` it's same-origin and renders — confirmed visually in the evidence). Tighten to a hard in-frame assertion (with generous waits) when a scenario must prove deep canvas DOM.\n- **A git-repo fixture must be OFFLINE (refs-only, no configured remote URL).** A fixture with a real `remote.origin.url` (e.g. `https:\u002F\u002Fgithub.com\u002F…`) makes the dev-server's unattended ahead\u002Fbehind probe spawn a `git fetch` to that host during boot; that network call keeps the WKWebView JS unresponsive long enough that the embedded WebDriver's `execute`\u002F`getUrl` time out — the harness hangs at `waitForSidecar` and the scenario fails before its first assertion (observed on `git-branch-switcher`, 2026-06-30). Fix: write `refs\u002Fremotes\u002Forigin\u002F*` directly with `git update-ref`\u002F`git symbolic-ref` and do NOT `git remote add` → `classifyRemoteUrl` returns `none`, the probe is a no-op, boot is deterministic. The \"remote · not downloaded yet\" rows still render (they read disk refs, not the remote config). See `apps\u002Fdesktop\u002Fe2e\u002Ffixtures\u002Fmake-git-fixture.ts`.\n- **`tauri-service: Failed to wait for plugin initialization` (script timeout) is non-fatal.** It's the service's wdio mock-store injection giving up; scenarios that don't use request mocking (all of ours) still run + pass once the webview settles. Don't chase it.\n- **No active display ⇒ the whole harness wedges (run it on a machine with a woken screen).** If EVERY WebDriver command times out — `execute\u002Fasync`, then `getUrl` \u002F `element` at 60 s each, so `waitForSidecar` fails before the first assertion — the cause is usually that the session has **no awake display**. macOS throttles the off-screen WKWebView (occlusion \u002F App-Nap) so its embedded WebDriver can't answer. Confirm in seconds WITHOUT WebDriver: `screencapture -x` comes back **fully black**, `pmset -g powerstate IODisplayWrangler` errors, and `osascript … get size of windows` returns empty bounds — meanwhile `curl http:\u002F\u002Flocalhost:\u003Cport>\u002F_health` is `ok` (the sidecar is fine; only the webview is throttled). This is the `feedback_native_app_verification_ceiling` in its \"headless \u002F display-asleep\" form — it is NOT a scenario or app defect. Re-run with the screen awake (or hand the run to the user's interactive session, as the git scenarios were verified). `caffeinate` can't conjure a display that isn't attached.\n- **Signed vs test build:** the harness drives a `--debug` build (embedded WebDriver), not the exact signed release. Same source, different profile — a near-release smoke, documented.\n- **Not covered:** the Bun sidecar process itself, native OS dialogs, and the macOS menu bar chrome — assert their *effects* via the webview \u002F Tauri commands, or a separate probe. Dialog\u002FOAuth stubs (for first-run\u002Fproject-switch scenarios) are still deferred (above).\n\n## When NOT to use\n\nBrowser-renderable studio UI is cheaper to verify with `agent-browser` in browser mode (`maude design serve`). Reach for desktop-e2e only for native-shell behavior: sidecar lifecycle, webview navigation, first-run, project switch, native menus, OAuth\u002Fkeychain, updater.\n",{"name":5,"description":7},"main","cfde9d2b169e4b418a5c5efb35297cc575dc764c",".claude\u002Fskills\u002Fdesktop-e2e",0,"https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude","https:\u002F\u002Fmaude.sh","https:\u002F\u002Fgithub.com\u002F1aGh","www.iagh.cz","2026-11-13 20:38:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add 1aGh\u002Fmaude --skill desktop-e2e",{"tool":39,"command":40},"bunx","bunx skills add 1aGh\u002Fmaude --skill desktop-e2e",{"tool":42,"command":43},"pnpm","pnpm dlx skills add 1aGh\u002Fmaude --skill desktop-e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdesktop-e2e\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M72CJCVNC5JB3M36ES649CTY","workflow-state","Read and update workflow state when planning, executing, completing, pausing or resuming project work.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fworkflow-state\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M72CJAJBZT2RHE97ND8EFTA3","ui-rules","UI hard-stop rules and audit method: WCAG 2.1 AA accessibility, responsive layout and motion.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fui-rules\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M72CJ857314HCC8A99T4K0D2","testing-rules","Apply test quality rules during implementation and review: meaningful assertions, isolation and coverage.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Ftesting-rules\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M72CJ6N80HW2WRS8BV4QSS4V","security-rules","Apply application and AI security checks to code reviews, implementation and threat-driven validation.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fsecurity-rules\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M72CJ4C41Q4E1WDTFMKYFX3Q","scenario","Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fscenario\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72CJ1QYX752BM7G12250YJR","question-protocol","Batch necessary questions from workflow participants, collect user answers and route them to the requester.","https:\u002F\u002Fgithub.com\u002F1aGh\u002Fmaude\u002Fblob\u002Fmain\u002Fplugins\u002Fflow\u002Fskills\u002Fquestion-protocol\u002FSKILL.md",[],[]]