refactor: augment Window interface with LiteGraph globals

Declares the nine LiteGraph properties assigned to window for backward
compatibility (LiteGraph, LGraph, LLink, LGraphNode, LGraphGroup,
DragAndScale, LGraphCanvas, ContextMenu, LGraphBadge) directly in
useGlobalLitegraph.ts where the imports already exist, removing all
nine @ts-expect-error suppressions from the file.

Part of #11092 - Reduce type suppression comments (Phase 1).

.agents/checks/adr-compliance.md

@@ -33,15 +33,15 @@ Flag:
 - **New circular entity dependencies** — New circular imports between `LGraph` ↔ `Subgraph`, `LGraphNode` ↔ `LGraphCanvas`, or similar entity classes.
 - **Direct `graph._version++`** — Mutating the private version counter directly instead of through a public API. Extensions already depend on this side-channel; it must become a proper API.
 
-### Dedicated Stores and Data/Behavior Separation
+### Centralized Registries and ECS-Style Access
 
-Entity data lives in dedicated Pinia stores keyed by string IDs (`widgetValueStore`, `domWidgetStore`, `layoutStore`, `nodeOutputStore`, `subgraphNavigationStore`, `previewExposureStore`), not on entity instances.
+All entity data access should move toward centralized query patterns, not instance property access.
 
 Flag:
 
-- **New instance method/property patterns** — Adding `node.someProperty` or `node.someMethod()` for data that belongs in a dedicated store (e.g. widget values → `widgetValueStore` keyed by `WidgetId`).
+- **New instance method/property patterns** — Adding `node.someProperty` or `node.someMethod()` for data that should be a component in the World, queried via `world.getComponent(entityId, ComponentType)`.
 - **OOP inheritance for entity modeling** — Extending entity classes with new subclasses instead of composing behavior through components and systems.
-- **Duplicated authority** — Storing the same entity state in both a class property and a store, or across two stores, so ownership becomes ambiguous. Each piece of state should have one owning store.
+- **Scattered state** — New entity state stored in multiple locations (class properties, stores, local variables) instead of being consolidated in the World or in a single store.
 
 ### Extension Ecosystem Impact
 

.agents/skills/add-model-page/SKILL.md

@@ -1,173 +0,0 @@
----
-name: add-model-page
-description: 'add, update, or remove a model page entry on the comfy org website. creates a PR to Comfy-Org/ComfyUI_frontend apps/website folder with the change and posts a Vercel preview link back to Slack.'
----
-
-# add-model-page
-
-add, update, or remove model pages in the ComfyUI website.
-
-## Trigger phrases
-
-- `Add a model page for <model-name>`
-- `Update the model page for <model-name>`
-- `Remove <model-name> from model pages`
-
-## Phase 1 — Parse the request
-
-Extract:
-
-- **action**: `add` | `update` | `remove`
-- **model-name**: raw string (e.g. `flux1-schnell`, `flux1_dev.safetensors`)
-
-Normalize to a slug: lowercase, replace `_` and `.` with `-`, strip file extensions.
-Example: `flux1_dev.safetensors` → `flux1-dev`
-
-## Architecture overview
-
-Models come from two sources merged at build time:
-
-| File                                            | Purpose                                                                                                                           |
-| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `apps/website/src/config/generated-models.json` | Auto-generated from workflow_templates (slug, name, directory, huggingFaceUrl, workflowCount, displayName, thumbnailUrl, docsUrl) |
-| `apps/website/src/config/model-metadata.ts`     | Hand-curated overrides (docsUrl, blogUrl, featured) — only add entries that need overrides                                        |
-| `apps/website/src/config/models.ts`             | Merges the two above; exports typed `Model[]`                                                                                     |
-
-To regenerate the JSON from workflow_templates:
-
-```bash
-pnpm tsx apps/website/scripts/generate-models.ts
-```
-
-This writes `apps/website/src/config/generated-models.json` directly.
-Thumbnails are populated from local `.webp` files in `workflow_templates/templates/` — no network access needed.
-
----
-
-## Phase 2 — Gather model data (ADD / UPDATE)
-
-Run the generator to get fresh data, then find the model:
-
-```bash
-pnpm tsx apps/website/scripts/generate-models.ts
-jq '.[] | select(.slug | contains("MODEL_SLUG"))' \
-  apps/website/src/config/generated-models.json
-```
-
-The JSON fields are:
-
-- `slug` — URL slug
-- `name` — exact filename or display name for partner nodes
-- `huggingFaceUrl` — download URL (empty for partner nodes)
-- `directory` — `diffusion_models` | `loras` | … | `partner_nodes`
-- `workflowCount` — integer
-- `displayName` — human-readable name
-
-If no match and it is a known API/partner model, add it to `API_PROVIDER_MAP` in
-`generate-models.ts` and re-run. Otherwise tell the user.
-
----
-
-## Phase 3 — Check for existing entry
-
-```bash
-jq --arg slug "${SLUG}" '.[] | select(.slug == $slug)' \
-  apps/website/src/config/generated-models.json
-```
-
-- Match found + action is `add` → switch to UPDATE flow automatically
-- No match + action is `update` → stop and tell the user
-
----
-
-## Phase 4A — ADD: new partner/API model not in workflow_templates
-
-For partner nodes (no local file), add an entry to `API_PROVIDER_MAP` in
-`apps/website/scripts/generate-models.ts`:
-
-```typescript
-mymodel: { name: 'My Model', slug: 'my-model' },
-```
-
-Then re-run `pnpm tsx apps/website/scripts/generate-models.ts` — it will appear
-in `generated-models.json` automatically.
-
-If you also want a `docsUrl`, `blogUrl`, or a link to the hub model page, add an entry to `model-metadata.ts`:
-
-```typescript
-'my-model': {
-  docsUrl: 'https://docs.comfy.org/tutorials/...',
-  blogUrl: 'https://blog.comfy.org/...',
-  hubSlug: 'my-model',   // slug at comfy.org/workflows/model/{hubSlug} — only set if the page exists (returns 200)
-  featured: true
-}
-```
-
-No changes to `models.ts` or `translations.ts` are needed.
-
----
-
-## Phase 4B — UPDATE: edit existing entry
-
-Only `model-metadata.ts` needs editing for most updates (docsUrl, blogUrl,
-featured). For `displayName` or `directory` changes, edit the entry directly in
-`generated-models.json` (until the next generator run would overwrite it — then
-fix the source in `generate-models.ts`).
-
----
-
-## Phase 4C — REMOVE: delete entry
-
-Remove the entry from `generated-models.json` (or mark it with `canonicalSlug`
-pointing to the replacement). No translation file changes needed.
-
----
-
-## Phase 5 — Verify TypeScript
-
-```bash
-pnpm typecheck 2>&1 | grep -E "error|warning" | head -20
-```
-
-Fix any type errors before proceeding. Common issues:
-
-- `ModelDirectory` type not matching a new `directory` value — add it to the union
-- JSON import shape mismatch — `generated-models.json` must match `OutputModel`
-
----
-
-## Phase 6 — Create PR
-
-```bash
-BRANCH="add-model-page-MODEL-SLUG"   # or update- / remove-
-git checkout -b $BRANCH
-git add apps/website/src/config/generated-models.json \
-        apps/website/scripts/generate-models.ts \
-        apps/website/src/config/model-metadata.ts
-git commit -m "feat(models): add model page for MODEL-SLUG"
-git push -u origin $BRANCH
-gh pr create \
-  --title "Add model page: MODEL-SLUG" \
-  --body "$(cat <<'EOF'
-Adds a new model page entry for MODEL-SLUG.
-
-## Changes
-- `generated-models.json`: regenerated with new entry (workflowCount N, directory DIRECTORY)
-- `model-metadata.ts`: editorial overrides (docsUrl, featured) if needed
-EOF
-)"
-```
-
-For UPDATE use branch `update-model-page-MODEL-SLUG`.
-For REMOVE use `remove-model-page-MODEL-SLUG`.
-
----
-
-## Error states
-
-| Situation                       | Response                                                         |
-| ------------------------------- | ---------------------------------------------------------------- |
-| Model not in workflow templates | Ask user to verify spelling or add it manually as a partner node |
-| Slug already exists (add)       | Switch to update flow automatically                              |
-| Slug not found (update/remove)  | Stop and ask user to confirm                                     |
-| Typecheck fails                 | Fix the error before pushing                                     |

.agents/skills/adding-deprecation-warnings/SKILL.md

@@ -1,84 +0,0 @@
----
-name: adding-deprecation-warnings
-description: 'Adds deprecation warnings for renamed or removed properties/APIs. Searches custom node ecosystem for usage, applies defineDeprecatedProperty helper, adds JSDoc. Triggers on: deprecate, deprecation warning, rename property, backward compatibility.'
----
-
-# Adding Deprecation Warnings
-
-Adds backward-compatible deprecation warnings for renamed or removed
-properties using the `defineDeprecatedProperty` helper in
-`src/lib/litegraph/src/utils/feedback.ts`.
-
-## When to Use
-
-- A property or API has been renamed and custom nodes still use the old name
-- A property is being removed but needs a grace period
-- Backward compatibility must be preserved while nudging adoption
-
-## Steps
-
-### 1. Search the Custom Node Ecosystem
-
-Before implementing, assess impact by searching for usage of the
-deprecated property across ComfyUI custom nodes:
-
-```text
-Use the comfy_codesearch tool to search for the old property name.
-Search for both `widget.oldProp` and just `oldProp` to catch all patterns.
-```
-
-Document the usage patterns found (property access, truthiness checks,
-caching to local vars, style mutation, etc.) — these all must continue
-working.
-
-### 2. Apply the Deprecation
-
-Use `defineDeprecatedProperty` from `src/lib/litegraph/src/utils/feedback.ts`:
-
-```typescript
-import { defineDeprecatedProperty } from '@/lib/litegraph/src/utils/feedback'
-
-/** @deprecated Use {@link obj.newProp} instead. */
-defineDeprecatedProperty(
-  obj,
-  'oldProp',
-  'newProp',
-  'obj.oldProp is deprecated. Use obj.newProp instead.'
-)
-```
-
-### 3. Checklist
-
-- [ ] Ecosystem search completed — all usage patterns are compatible
-- [ ] `defineDeprecatedProperty` call added after the new property is assigned
-- [ ] JSDoc `@deprecated` tag added above the call for IDE support
-- [ ] Warning message names both old and new property clearly
-- [ ] `pnpm typecheck` passes
-- [ ] `pnpm lint` passes
-
-### 4. PR Comment
-
-Add a PR comment summarizing the ecosystem search results: which repos
-use the deprecated property, what access patterns were found, and
-confirmation that all patterns are compatible with the ODP getter/setter.
-
-## How `defineDeprecatedProperty` Works
-
-- Creates an `Object.defineProperty` getter/setter on the target object
-- Getter returns `this[currentKey]`, setter assigns `this[currentKey]`
-- Both log via `warnDeprecated`, which deduplicates (once per unique
-  message per session via a `Set`)
-- `enumerable: false` keeps the alias out of `Object.keys()` / `for...in`
-  / `JSON.stringify`
-- `configurable: true` allows further redefinition if needed
-
-## Edge Cases
-
-- **Truthiness checks** (`if (widget.oldProp)`) — works, getter fires
-- **Caching to local var** (`const el = widget.oldProp`) — works, warns
-  once then the cached ref is used directly
-- **Style/property mutation** (`widget.oldProp.style.color = 'red'`) —
-  works, getter returns the real object
-- **Serialization** (`JSON.stringify`) — `enumerable: false` excludes it
-- **Heavy access in loops** — `warnDeprecated` deduplicates, only warns
-  once per session regardless of call count

.agents/skills/backport-management/SKILL.md

@@ -1,390 +0,0 @@
----
-name: backport-management
-description: Manages cherry-pick backports across stable release branches. Discovers candidates from Slack/git, analyzes dependencies, resolves conflicts via worktree, and logs results. Use when asked to backport, cherry-pick to stable, manage release branches, do stable branch maintenance, or run a backport session.
----
-
-# Backport Management
-
-Cherry-pick backport management for Comfy-Org/ComfyUI_frontend stable release branches.
-
-## Quick Start
-
-1. **Discover** — Collect candidates from Slack bot + git log gap, then **reconcile both lists** (`reference/discovery.md`)
-2. **Pre-filter by path** — Auto-skip PRs whose changed files are entirely under `apps/website/`, `browser_tests/`, `.github/`, `packages/design-system/`, `packages/{cloud,registry}-types/`, `.Codex/`, `docs/`. Don't read PR bodies for these — they don't ship to core ComfyUI users (`reference/analysis.md`)
-3. **Verify target file existence** — For each surviving candidate, run `git cat-file -e origin/$TARGET:$path` for primary changed files. If they don't exist on the target, auto-mark SKIP with reason `feature-not-on-branch`
-4. **Tiered triage** — Bucket into **Tier 1 (core editor must-haves)**, **Tier 2 (cloud-distribution only)**, **Tier 3 (skip)** before reviewing individually (`reference/analysis.md`)
-5. **Analyze** — Categorize remaining MUST/SHOULD, check deps (`reference/analysis.md`)
-6. **Human Review** — Present candidates in batches for interactive approval, with tier context attached (see Interactive Approval Flow)
-7. **Plan** — Order by dependency (leaf fixes first), group into waves per branch
-8. **Test-then-resolve dry-run** — Classify clean vs conflict before committing time (`reference/execution.md`)
-9. **Execute** — Label-driven automation for clean PRs → worktree fallback for conflicts (`reference/execution.md`)
-10. **Public-API conflict review** — If conflict resolution touches a public LiteGraph callback, extension API, or `node.*` method, consult oracle for compat-regression review BEFORE pushing (`reference/execution.md`)
-11. **Verify** — Per-PR validation (typecheck + targeted tests + lint on changed files) AND per-wave verification (full typecheck + test:unit on branch HEAD)
-12. **Log & Report** — Generate session report + author accountability report + Slack status update (`reference/logging.md`)
-
-## System Context
-
-| Item           | Value                                                                       |
-| -------------- | --------------------------------------------------------------------------- |
-| Repo           | `~/ComfyUI_frontend` (Comfy-Org/ComfyUI_frontend)                           |
-| Merge strategy | Auto-merge via workflow (`--auto --squash`); `--admin` only after CI passes |
-| Automation     | `pr-backport.yaml` GitHub Action (label-driven, auto-merge enabled)         |
-| Tracking dir   | `~/temp/backport-session/`                                                  |
-
-## CI Safety Rules
-
-**NEVER merge a backport PR without all CI checks passing.** This applies to both automation-created and manual cherry-pick PRs.
-
-- **Automation PRs:** The `pr-backport.yaml` workflow now enables `gh pr merge --auto --squash`, so clean PRs auto-merge once CI passes. Monitor with polling (`gh pr list --base TARGET_BRANCH --state open`). Do not intervene unless CI fails.
-- **Manual cherry-pick PRs:** After `gh pr create`, wait for CI before merging. Poll with `gh pr checks $PR --watch` or use a sleep+check loop. Only merge after all checks pass.
-- **CI failures:** DO NOT use `--admin` to bypass failing CI. Analyze the failure, present it to the user with possible causes (test backported without implementation, missing dependency, flaky test), and let the user decide the next step.
-
-## Branch Scope Rules
-
-**Critical: Match PRs to the correct target branches.**
-
-| Branch prefix | Scope                          | Example                                           |
-| ------------- | ------------------------------ | ------------------------------------------------- |
-| `cloud/*`     | Cloud-hosted ComfyUI only      | Team workspaces, cloud queue, cloud-only login    |
-| `core/*`      | Local/self-hosted ComfyUI only | Core editor, local workflows, node system         |
-| Both          | Shared infrastructure          | App mode, Firebase auth (API nodes), payment URLs |
-
-### What Goes Where
-
-**Both core + cloud:**
-
-- **App mode** PRs — app mode is NOT cloud-only
-- **Firebase auth** PRs — Firebase auth is on core for API nodes
-- **Payment redirect** PRs — payment infrastructure shared
-- **Bug fixes** touching shared components
-
-**Cloud-only (skip for core):**
-
-- Team workspaces
-- Cloud queue virtualization
-- Hide API key login
-- Cloud-specific UI behind cloud feature flags
-
-**⚠️ NEVER backport cloud-only PRs to `core/*` branches.** But do NOT assume "app mode" or "Firebase" = cloud-only. Check the actual files changed.
-
-## ⚠️ Gotchas (Learn from Past Sessions)
-
-### Use `gh api` for Labels — NOT `gh pr edit`
-
-`gh pr edit --add-label` triggers Projects Classic deprecation errors. Always use:
-
-```bash
-gh api repos/Comfy-Org/ComfyUI_frontend/issues/$PR/labels \
-  -f "labels[]=needs-backport" -f "labels[]=TARGET_BRANCH"
-```
-
-### Automation Over-Reports Conflicts
-
-The `pr-backport.yaml` action reports more conflicts than reality. `git cherry-pick -m 1` with git auto-merge handles many cases the automation can't. Always attempt manual cherry-pick before skipping.
-
-### Never Skip Based on Conflict File Count
-
-12 or 27 conflicting files can be trivial (snapshots, new files). **Categorize conflicts first**, then decide. See Conflict Triage below.
-
-### Accept-Theirs Can Produce Broken Hybrids
-
-When a PR **rewrites a component** (e.g., PrimeVue → Reka UI), the accept-theirs regex produces a broken mix of old and new code. The template may reference new APIs while the script still has old imports, or vice versa.
-
-**Detection:** Content conflicts with 4+ conflict markers in a single `.vue` file, especially when imports change between component libraries.
-
-**Fix:** Instead of accept-theirs regex, use `git show MERGE_SHA:path/to/file > path/to/file` to get the complete correct version from the merge commit on main. This bypasses the conflict entirely.
-
-### Cherry-Picks Can Reference Missing Dependencies
-
-When PR A on main depends on code introduced by PR B (which was merged before A), cherry-picking A brings in code that references B's additions. The cherry-pick succeeds but the branch is broken.
-
-**Common pattern:** Composables, component files, or type definitions introduced by an earlier PR and used by the cherry-picked PR.
-
-**Detection:** `pnpm typecheck` fails with "Cannot find module" or "is not defined" errors after cherry-pick.
-
-**Fix:** Use `git show MERGE_SHA:path/to/missing/file > path/to/missing/file` to bring the missing files from main. Always verify with typecheck.
-
-### Use `--no-verify` for Worktree Pushes
-
-Husky hooks fail in worktrees (can't find lint-staged config). Always use `git push --no-verify` and `git commit --no-verify` when working in `/tmp/` worktrees.
-
-### Automation Success Varies Wildly by Branch
-
-In the 2026-04-06 session: core/1.42 got 18/26 auto-PRs, cloud/1.42 got only 1/25. The cloud branch has more divergence. **Always plan for manual fallback** — don't assume automation will handle most PRs.
-
-### Cherry-Picked Tests Can Reference Files Added By Earlier Unbackported PRs
-
-A common conflict: PR A on main modifies a test file that was _added_ on main by an earlier PR B (not backported to the target). The cherry-pick of A reports "modify/delete" on B's test file because the file doesn't exist on the target. Adding the new file would smuggle in B's test scaffolding without B's runtime changes.
-
-**Detection:** Conflict says `deleted in HEAD and modified in <PR>`. Verify with:
-
-```bash
-git log --diff-filter=A --oneline origin/main -- path/to/test.ts
-```
-
-If the introducing commit is **not** on the target branch, the test file isn't a real prerequisite for the runtime fix.
-
-**Fix:** `git rm` the test file (drop it from the backport). Document in the commit body which PR introduced it on main and why dropping it is safe. The runtime fix itself usually doesn't depend on these tests — coverage exists at the integration layer.
-
-### Backport-Only Compatibility Shims
-
-When a PR's _mechanism_ relies on changes upstream that aren't on the older branch, a literal cherry-pick can recreate the original bug for any consumer still using the old contract. This is most dangerous for **public LiteGraph callbacks, extension APIs, and `node.*` methods** that custom-node packages depend on.
-
-**Real example (#11541, core/1.43 backport):** The PR removed `LGraphNode.vue`'s legacy `handled === true` sync-return check from `handleDrop`, replacing it with `await node.onDragDrop(event, true)`. Safe on `main` because all in-repo `onDragDrop` handlers had migrated to participate in the new `claimEvent` flag. On `core/1.43`, `onDragDrop` is a public callback — custom-node packages with synchronous `onDragDrop` returning `true` would no longer have their event claimed, recreating the duplicate-node-creation bug the PR was fixing.
-
-**Detection:** The PR's diff modifies a file that is part of a public extension API surface. Look for:
-
-- `node.onXxx` callback assignments
-- Methods on `LGraphNode`, `LGraphCanvas`, `LGraph`, `Subgraph`
-- Public exports from `src/lib/litegraph/`
-- Type changes affecting `litegraph-augmentation.d.ts`
-
-**Fix:** Add a backport-only compatibility shim that preserves the old contract while keeping the new fix. Document it explicitly in the commit body under a `## Backport-only compatibility fix` heading. Consult oracle for review before pushing — a bad shim is worse than no fix.
-
-## Conflict Triage
-
-**Always categorize before deciding to skip. High conflict count ≠ hard conflicts.**
-
-| Type                         | Symptom                              | Resolution                                                      |
-| ---------------------------- | ------------------------------------ | --------------------------------------------------------------- |
-| **Binary snapshots (PNGs)**  | `.png` files in conflict list        | `git checkout --theirs $FILE && git add $FILE` — always trivial |
-| **Modify/delete (new file)** | PR introduces files not on target    | `git add $FILE` — keep the new file                             |
-| **Modify/delete (removed)**  | Target removed files the PR modifies | `git rm $FILE` — file no longer relevant                        |
-| **Content conflicts**        | Marker-based (`<<<<<<<`)             | Accept theirs via python regex (see below)                      |
-| **Component rewrites**       | 4+ markers in `.vue`, library change | Use `git show SHA:path > path` — do NOT accept-theirs           |
-| **Import-only conflicts**    | Only import lines differ             | Keep both imports if both used; remove unused after             |
-| **Add/add**                  | Both sides added same file           | Accept theirs, verify no logic conflict                         |
-| **Locale/JSON files**        | i18n key additions                   | Accept theirs, validate JSON after                              |
-
-```python
-# Accept theirs for content conflicts
-import re
-pattern = r'<<<<<<< HEAD\n(.*?)=======\n(.*?)>>>>>>> [^\n]+\n?'
-content = re.sub(pattern, r'\2', content, flags=re.DOTALL)
-```
-
-### Escalation Triggers (Flag for Human)
-
-- **Package.json/lockfile changes** → skip on stable (transitive dep regression risk)
-- **Core type definition changes** → requires human judgment
-- **Business logic conflicts** (not just imports/exports) → requires domain knowledge
-- **Admin-merged conflict resolutions** → get human review of the resolution before continuing the wave
-
-## Auto-Skip Categories
-
-Skip these without discussion:
-
-- **Dep refresh PRs** — Risk of transitive dep regressions on stable. Cherry-pick individual CVE fixes instead.
-- **CI/tooling changes** — Not user-facing
-- **Test-only / lint rule changes** — Not user-facing
-- **Revert pairs** — If PR A reverted by PR B, skip both. If fixed version (PR C) exists, backport only C.
-- **Features not on target branch** — e.g., Painter, GLSLShader, appModeStore on core/1.40
-- **Cloud-only PRs on core/\* branches** — Team workspaces, cloud queue, cloud-only login. (Note: app mode and Firebase auth are NOT cloud-only — see Branch Scope Rules)
-
-### Path Pre-Filter (run BEFORE reading PR bodies)
-
-For 50+ candidate PRs, classify by changed paths first to skip the unproductive ones without spending time on triage. Run `git show --stat $SHA` (or `gh pr view --json files`) and bucket:
-
-| Path prefix                                    | Bucket                 | Reason                                           |
-| ---------------------------------------------- | ---------------------- | ------------------------------------------------ |
-| `apps/website/`                                | SKIP                   | Marketing/platform site, not core ComfyUI bundle |
-| `apps/desktop-ui/`                             | SKIP for `core/*`      | Desktop app, separate release cadence            |
-| `browser_tests/` only (no `src/`)              | SKIP                   | Test-only                                        |
-| `.github/workflows/` only                      | SKIP                   | CI/release infra                                 |
-| `packages/design-system/` only                 | SKIP                   | Design tokens, not core                          |
-| `packages/{cloud,registry,ingest}-types/` only | SKIP                   | Generated types                                  |
-| `.Codex/`, `.agents/`, `docs/`                 | SKIP                   | Agent / documentation                            |
-| `*.stories.ts` only                            | SKIP                   | Storybook only                                   |
-| `src/` (core editor)                           | KEEP — analyze further | Runtime/editor code that requires full triage    |
-
-A PR touches multiple paths? Keep it if **any** changed file is under `src/` (or other core paths) and run normal analysis. Auto-skip is conservative — only skip when _all_ paths match the SKIP buckets.
-
-This filter alone removes ~30-50% of candidates in a typical session, leaving only the PRs that need real triage.
-
-## Wave Verification
-
-After merging each wave of PRs to a target branch, verify branch integrity before proceeding:
-
-```bash
-# Fetch latest state of target branch
-git fetch origin TARGET_BRANCH
-
-# Quick smoke check: does the branch build?
-git worktree add /tmp/verify-TARGET origin/TARGET_BRANCH
-cd /tmp/verify-TARGET
-source ~/.nvm/nvm.sh && nvm use 24 && pnpm install && pnpm typecheck && pnpm test:unit
-git worktree remove /tmp/verify-TARGET --force
-```
-
-If typecheck or tests fail, stop and investigate before continuing. A broken branch after wave N means all subsequent waves will compound the problem.
-
-### Fix PRs Are Normal
-
-Expect to create 1 fix PR per branch after verification. Common issues:
-
-1. **Component rewrite hybrids** — accept-theirs produced broken `.vue` files. Fix: overwrite with correct version from merge commit via `git show SHA:path > path`
-2. **Missing dependency files** — cherry-pick brought in code referencing composables/components not on the branch. Fix: add missing files from merge commit
-3. **Missing type properties** — cherry-picked code uses interface properties not yet on the branch (e.g., `key` on `ConfirmDialogOptions`). Fix: add the property to the interface
-4. **Unused imports** — conflict resolution kept imports that the branch doesn't use. Fix: remove unused imports
-5. **Wrong types from conflict resolution** — e.g., `{ top: number; right: number }` vs `{ top: number; left: number }`. Fix: match the return type of the actual function
-
-Create a fix PR on a branch from the target, verify typecheck passes, then merge with `--squash --admin`.
-
-### Never Admin-Merge Without CI
-
-In a previous bulk session, all 69 backport PRs were merged with `gh pr merge --squash --admin`, bypassing required CI checks. This shipped 3 test failures to a release branch. **Lesson: `--admin` skips all branch protection, including required status checks.** Only use `--admin` after confirming CI has passed (e.g., `gh pr checks $PR` shows all green), or rely on auto-merge (`--auto --squash`) which waits for CI by design.
-
-## Continuous Backporting Recommendation
-
-Large backport sessions (50+ PRs) are expensive and error-prone. Prefer continuous backporting:
-
-- Backport bug fixes as they merge to main (same day or next day)
-- Use the automation labels immediately after merge
-- Reserve session-style bulk backporting for catching up after gaps
-- When a release branch is created, immediately start the continuous process
-
-## Interactive Approval Flow
-
-After analysis, present ALL candidates (MUST, SHOULD, and borderline) to the human for interactive review before execution. Do not write a static decisions.md — collect approvals in conversation.
-
-### Batch Presentation
-
-Present PRs in batches of 5-10, grouped by theme (visual bugs, interaction bugs, cloud/auth, data correctness, etc.). Use this table format:
-
-```
- #  | PR     | Title                                    | Target        | Rec  | Context
-----+--------+------------------------------------------+---------------+------+--------
- 1  | #12345 | fix: broken thing                        | core+cloud/42 | Y    | Description here. Why it matters. Agent reasoning.
- 2  | #12346 | fix: another issue                       | core/42       | N    | Only affects removed feature. Not on target branch.
-```
-
-Each row includes:
-
-- PR number and title
-- Target branches
-- Agent recommendation: `Rec: Y` or `Rec: N` with brief reasoning
-- 2-3 sentence context: what the PR does, why it matters (or doesn't)
-
-### Human Response Format
-
-- `Y` — approve for backport
-- `N` — skip
-- `?` — investigate (agent shows PR description, files changed, detailed take, then re-asks)
-- Any freeform question or comment triggers discussion before moving on
-- Bulk responses accepted (e.g. `1 Y, 2 Y, 3 N, 4 ?`)
-
-### Rules
-
-- ALL candidates are reviewed, not just MUST items
-- When human responds `?`, show the PR description, files changed, and agent's detailed analysis, then re-ask for their decision
-- When human asks a question about a PR, answer with context and recommendation, then wait for their decision
-- Do not proceed to execution until all batches are reviewed and every candidate has a Y or N
-
-## Quick Reference
-
-### Label-Driven Automation (default path)
-
-```bash
-gh api repos/Comfy-Org/ComfyUI_frontend/issues/$PR/labels \
-  -f "labels[]=needs-backport" -f "labels[]=TARGET_BRANCH"
-# Wait 3 min, check: gh pr list --base TARGET_BRANCH --state open
-```
-
-### Manual Worktree Cherry-Pick (conflict fallback)
-
-```bash
-git worktree add /tmp/backport-$BRANCH origin/$BRANCH
-cd /tmp/backport-$BRANCH
-
-# For each PR:
-git fetch origin $BRANCH
-git checkout -b backport-$PR-to-$BRANCH origin/$BRANCH
-git cherry-pick -m 1 $MERGE_SHA
-# Resolve conflicts (see Conflict Triage)
-git push origin backport-$PR-to-$BRANCH --no-verify
-gh pr create --base $BRANCH --head backport-$PR-to-$BRANCH \
-  --title "[backport $BRANCH] $TITLE (#$PR)" \
-  --body "Backport of #$PR. [conflict notes]"
-gh pr merge $NEW_PR --squash --admin
-sleep 25
-```
-
-### Efficient Batch: Test-Then-Resolve Pattern
-
-When many PRs need manual cherry-pick (e.g., cloud branches), test all first:
-
-```bash
-cd /tmp/backport-$BRANCH
-for pr in "${ORDER[@]}"; do
-  git checkout -b test-$pr origin/$BRANCH
-  if git cherry-pick -m 1 $SHA 2>/dev/null; then
-    echo "CLEAN: $pr"
-  else
-    echo "CONFLICT: $pr"
-    git cherry-pick --abort
-  fi
-  git checkout --detach HEAD
-  git branch -D test-$pr
-done
-```
-
-Then process clean PRs in a batch loop, conflicts individually.
-
-### PR Title Convention
-
-```
-[backport TARGET_BRANCH] Original Title (#ORIGINAL_PR)
-```
-
-## Final Deliverables (Slack-Compatible)
-
-After execution completes, generate two files in `~/temp/backport-session/`. Both must be **Slack-compatible plain text** — no emojis, no markdown tables, no headers (`#`), no bold (`**`), no inline code. Use plain dashes, indentation, and line breaks only.
-
-### 1. Author Accountability Report
-
-File: `backport-author-accountability.md`
-
-Lists all backported PRs grouped by original author (via `gh pr view $PR --json author`). Surfaces who should be self-labeling.
-
-```
-Backport Session YYYY-MM-DD -- PRs that should have been labeled by authors
-
-- author-login
-    - #1234 fix: short title
-    - #5678 fix: another title
-- other-author
-    - #9012 fix: some other fix
-```
-
-Authors sorted alphabetically, 4-space indent for nested items.
-
-### 2. Slack Status Update
-
-File: `slack-status-update.md`
-
-A shareable summary of the session. Structure:
-
-```
-Backport session complete -- YYYY-MM-DD
-
-[1-sentence summary: N PRs backported to which branches. All pass typecheck.]
-
-Branches updated:
-- core/X.XX: N PRs + N fix PRs (N auto, N manual)
-- cloud/X.XX: N PRs + N fix PRs (N auto, N manual)
-- ...
-
-N total PRs created and merged (N backports + N fix PRs).
-
-Notable fixes included:
-- [category]: [list of fixes]
-- ...
-
-Conflict patterns encountered:
-- [pattern and how it was resolved]
-- ...
-
-N authors had PRs backported. See author accountability list for details.
-```
-
-No emojis, no tables, no bold, no headers. Plain text that pastes cleanly into Slack.

.agents/skills/backport-management/reference/analysis.md

@@ -1,149 +0,0 @@
-# Analysis & Decision Framework
-
-## Categorization
-
-| Category             | Criteria                                                                                                  | Action                                                                     |
-| -------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| **MUST**             | User-facing bug, crash, data corruption, security. Clear breakage that users will hit.                    | Backport (with deps if needed)                                             |
-| **SHOULD**           | UX improvement, minor bug, small dep chain. No user-visible breakage if skipped, but improves experience. | Backport if clean cherry-pick; defer if conflict resolution is non-trivial |
-| **SKIP**             | CI/tooling, test-only, lint rules, cosmetic, dep refresh                                                  | Skip with documented reason                                                |
-| **NEEDS DISCUSSION** | Large dep chain, unclear risk/benefit, touches core types                                                 | Flag for human                                                             |
-
-### MUST vs SHOULD Decision Guide
-
-When unsure, ask: "If a user on this stable branch reports this issue, would we consider it a bug?"
-
-- **Yes** → MUST. The fix addresses broken behavior.
-- **No, but it's noticeably better** → SHOULD. The fix is a quality-of-life improvement.
-- **No, and it's cosmetic or internal** → SKIP.
-
-For SHOULD items with conflicts: if conflict resolution requires more than trivial accept-theirs patterns (content conflicts in business logic, not just imports), downgrade to SKIP or escalate to NEEDS DISCUSSION.
-
-## Branch Scope Filtering
-
-**Before categorizing, filter by branch scope:**
-
-| Target branch | Skip if PR is...                                                                                                  |
-| ------------- | ----------------------------------------------------------------------------------------------------------------- |
-| `core/*`      | Cloud-only (team workspaces, cloud queue, cloud-only login). Note: app mode and Firebase auth are NOT cloud-only. |
-| `cloud/*`     | Local-only features not present on cloud branch                                                                   |
-
-Cloud-only PRs backported to `core/*` are wasted effort — `core/*` branches serve local/self-hosted users who never see cloud features. Check PR titles, descriptions, and files changed for cloud-specific indicators.
-
-## Features Not on Stable Branches
-
-Check before backporting — these don't exist on older branches:
-
-- **Painter** (`src/extensions/core/painter.ts`) — not on core/1.40
-- **GLSLShader** — not on core/1.40
-- **App builder** — check per branch
-- **appModeStore.ts** — not on core/1.40
-
-### Verify Target File Existence (Run Before Cherry-Pick)
-
-Before cherry-picking any PR, confirm the files it modifies actually exist on the target branch. If they don't, the PR's runtime fix is for a feature that hasn't been added yet — skip cleanly without attempting cherry-pick:
-
-```bash
-# For each file the PR changes
-for f in $(gh pr view $PR --json files --jq '.files[].path' | grep -v "^browser_tests/\|\.test\." ); do
-  if ! git cat-file -e origin/$TARGET:$f 2>/dev/null; then
-    echo "MISSING on $TARGET: $f"
-  fi
-done
-```
-
-If the _primary_ changed files (the runtime ones, not tests) are missing, mark the PR `SKIP / feature-not-on-branch`. This is faster than letting cherry-pick fail with modify/delete conflicts and gives a clean signal.
-
-This check is the first thing that runs after the path pre-filter and BEFORE you spend time reading PR descriptions.
-
-## Tiered Triage (Recommended for 30+ Candidates)
-
-Before the interactive Y/N approval flow, bucket all surviving candidates into three tiers. This surfaces release-engineering decisions that a flat MUST/SHOULD list obscures:
-
-### Tier 1 — Core Editor Must-Haves
-
-User-facing bugs, crashes, data corruption, or security issues in code paths that exist on the target branch. These are the strongest backport candidates.
-
-Indicators:
-
-- `fix:` prefix and the bug is reproducible on the target branch
-- Crash guards, runtime null checks, race-condition fixes
-- Data-loss bugs (state not persisted, duplicates, drops)
-- Security hardening (CSRF, XSS, auth)
-- Vue Nodes 2.0 regression cluster (if the target ships Vue Nodes 2.0)
-- Subgraph correctness fixes
-- Public-API extension callback fixes
-
-Recommend `Y` to user.
-
-### Tier 2 — Cloud-Distribution Only
-
-Bugs that only manifest on cloud-hosted distributions (Secrets panel, subscription flows, cloud signup, workspace tracking, etc.). Whether to backport depends on whether cloud ships from the target `core/*` branch in your release matrix.
-
-Indicators:
-
-- Files under `src/platform/secrets/`, `src/platform/subscription/`, signup flows
-- PR description mentions cloud staging issues
-- Fix gated behind cloud feature flags
-
-Default: ask the cloud release rotation owner. If unsure, defer.
-
-### Tier 3 — Skip
-
-Path pre-filter caught most of these. The rest are PRs where the diff _touches_ `src/` but the practical impact is non-user-facing or scoped to features the target doesn't ship.
-
-Indicators:
-
-- All changes in test files even if the PR touched `src/` test files
-- Storybook stories only
-- Lint config / lint rule additions
-- Documentation comments
-- Internal refactors with no behavior change
-
-### Presentation Format
-
-When showing tier results to the user, format as:
-
-```text
-Tier 1 (N PRs) — strong backport candidates
-- #11541 fix: stop duplicate node creation when dropping image on Vue nodes
-  Why: Vue Nodes 2.0 regression — async onDragDrop bypassed handled-check, drops bubble to document, spawns extra LoadImage nodes
-- #10849 fix: store promoted widget values per SubgraphNode instance
-  Why: Multiple instances overwriting each other's promoted widget values — data loss
-
-Tier 2 (N PRs) — cloud-distribution release rotation should decide
-- #11636 fix: enable Chrome password autofill on signup form
-- ...
-
-Tier 3 (N PRs) — skip recommended
-- #11586 fix: website polish (apps/website/ only)
-- ...
-```
-
-Then run interactive Y/N over Tier 1 and Tier 2; Tier 3 gets confirmed-skip without per-PR review.
-
-## Dep Refresh PRs
-
-Always SKIP on stable branches. Risk of transitive dependency regressions outweighs audit cleanup benefit. If a specific CVE fix is needed, cherry-pick that individual fix instead.
-
-## Revert Pairs
-
-If PR A is reverted by PR B:
-
-- Skip BOTH A and B
-- If a fixed version exists (PR C), backport only C
-
-## Dependency Analysis
-
-```bash
-# Find other PRs that touched the same files
-gh pr view $PR --json files --jq '.files[].path' | while read f; do
-  git log --oneline origin/TARGET..$MERGE_SHA -- "$f"
-done
-```
-
-## Human Review Checkpoint
-
-Use the Interactive Approval Flow (see SKILL.md) to review all candidates interactively. Do not write a static decisions.md for the human to edit — instead, present batches of 5-10 PRs with context and recommendations, and collect Y/N/? responses in conversation.
-
-All candidates must be reviewed (MUST, SHOULD, and borderline items), not just a subset.

.agents/skills/backport-management/reference/discovery.md

@@ -1,84 +0,0 @@
-# Discovery — Candidate Collection
-
-**Run all sources, then reconcile.** No single source is authoritative:
-
-- Slack bot may flag PRs that have already been backported (false positive)
-- Git gap may include PRs that don't need backport (test-only, design-system, website)
-- Bot can also miss PRs that landed without the right labels
-
-## Source 1: Slack Backport-Checker Bot
-
-Use `slackdump` skill to export `#frontend-releases` channel (C09K9TPU2G7):
-
-```bash
-slackdump export -o ~/slack-exports/frontend-releases.zip C09K9TPU2G7
-```
-
-Parse bot messages for PRs flagged "Might need backport" per release version.
-
-## Source 2: Git Log Gap Analysis
-
-```bash
-# Count gap
-git log --oneline origin/TARGET..origin/main | wc -l
-
-# List gap commits
-git log --oneline origin/TARGET..origin/main
-
-# Check if a PR is already on target
-git log --oneline origin/TARGET --grep="#PR_NUMBER"
-
-# Check for existing backport PRs
-gh pr list --base TARGET --state all --search "backport PR_NUMBER"
-```
-
-## Source 3: GitHub PR Details
-
-```bash
-# Get merge commit SHA
-gh pr view $PR --json mergeCommit,title --jq '"Title: \(.title)\nMerge: \(.mergeCommit.oid)"'
-
-# Get files changed
-gh pr view $PR --json files --jq '.files[].path'
-```
-
-## Source 4: Already-Backported PRs (cross-reference)
-
-When the target branch already has some cherry-picks on it (e.g., partway through a release window), extract the originals to avoid re-backporting:
-
-```bash
-# Get all original PR numbers already backported to TARGET since the last release tag
-git log --format="%H%n%B" $LAST_TAG..origin/$TARGET \
-  | grep -oiE "(backport of|cherry.picked) #?[0-9]+" \
-  | grep -oE "[0-9]+" \
-  | sort -un > /tmp/already-backported.txt
-```
-
-Subtract this list from your candidates.
-
-## Reconciliation Workflow
-
-```bash
-# 1. Slack bot list (parse from export)
-# /tmp/bot-flagged.txt — one PR# per line, sorted
-
-# 2. Git gap fix/perf only
-MB=$(git merge-base origin/main origin/$TARGET)
-git log --format="%h|%s" $MB..origin/main \
-  | grep -iE "^[a-f0-9]+\|(fix|perf)" \
-  | grep -oE "#[0-9]+\)" | grep -oE "[0-9]+" \
-  | sort -un > /tmp/gap-fixes.txt
-
-# 3. Already backported (Source 4 above)
-
-# 4. Candidates = (gap-fixes ∪ bot-flagged) − already-backported
-sort -u /tmp/gap-fixes.txt /tmp/bot-flagged.txt > /tmp/union.txt
-comm -23 /tmp/union.txt /tmp/already-backported.txt > /tmp/candidates.txt
-```
-
-The result is the input to the path pre-filter (`SKILL.md` Quick Start step 2).
-
-## Output: candidate_list.md
-
-Table per target branch:
-| PR# | Title | Source (bot/gap/both) | Path bucket | Tier | Decision |

.agents/skills/backport-management/reference/execution.md

@@ -1,380 +0,0 @@
-# Execution Workflow
-
-## Per-Branch Execution Order
-
-1. Smallest gap first (validation run)
-2. Medium gap next (quick win)
-3. Largest gap last (main effort)
-
-## Step 0: Test-Then-Resolve Pre-Pass (Recommended)
-
-Before triggering label-driven automation, run a dry-run cherry-pick loop to classify candidates. This is much faster than discovering conflicts after-the-fact across automation, manual cherry-picks, and CI failures.
-
-```bash
-git fetch origin TARGET_BRANCH
-git worktree add /tmp/dryrun-TARGET origin/TARGET_BRANCH
-cd /tmp/dryrun-TARGET
-
-CLEAN=()
-CONFLICT=()
-for pr in "${CANDIDATES[@]}"; do
-  SHA=$(gh pr view $pr --json mergeCommit --jq '.mergeCommit.oid')
-  git checkout -b dryrun-$pr origin/TARGET_BRANCH 2>/dev/null
-  if git cherry-pick -m 1 $SHA 2>/dev/null; then
-    CLEAN+=($pr)
-  else
-    CONFLICT+=($pr)
-    git cherry-pick --abort
-  fi
-  git checkout --detach HEAD 2>/dev/null
-  git branch -D dryrun-$pr 2>/dev/null
-done
-
-echo "CLEAN (${#CLEAN[@]}): ${CLEAN[*]}"
-echo "CONFLICT (${#CONFLICT[@]}): ${CONFLICT[*]}"
-
-cd -
-git worktree remove /tmp/dryrun-TARGET --force
-```
-
-Use the result to:
-
-- Send CLEAN PRs through label-driven automation (Step 1) — they'll typically self-merge
-- Reserve manual worktree time (Step 3) for CONFLICT PRs only
-- Surface PRs likely to need backport-only compat shims (CONFLICT files in `src/lib/litegraph/` or `src/scripts/app.ts`)
-
-## Step 1: Label-Driven Automation (Batch)
-
-```bash
-# Add labels to all candidates for a target branch
-for pr in $PR_LIST; do
-  gh api repos/Comfy-Org/ComfyUI_frontend/issues/$pr/labels \
-    -f "labels[]=needs-backport" -f "labels[]=TARGET_BRANCH" --silent
-  sleep 2
-done
-
-# Wait 3 minutes for automation
-sleep 180
-
-# Check which got auto-PRs (auto-merge is enabled, so clean ones will self-merge after CI)
-gh pr list --base TARGET_BRANCH --state open --limit 50 --json number,title
-```
-
-> **Note:** The `pr-backport.yaml` workflow now enables `gh pr merge --auto --squash` on automation-created PRs. Clean PRs will auto-merge once CI passes — no manual merge needed for those.
-
-## Step 2: Wait for CI & Merge Clean Auto-PRs
-
-Most automation PRs will auto-merge once CI passes (via `--auto --squash` in the workflow). Monitor and handle failures:
-
-```bash
-# Wait for CI to complete (~45 minutes for full suite)
-sleep 2700
-
-# Check which PRs are still open (CI may have failed, or auto-merge succeeded)
-STILL_OPEN_PRS=$(gh pr list --base TARGET_BRANCH --state open --limit 50 --json number --jq '.[].number')
-RECENTLY_MERGED=$(gh pr list --base TARGET_BRANCH --state merged --limit 50 --json number,title,mergedAt)
-
-# For PRs still open, check CI status
-for pr in $STILL_OPEN_PRS; do
-  CI_FAILED=$(gh pr checks $pr --json name,state --jq '[.[] | select(.state == "FAILURE")] | length')
-  CI_PENDING=$(gh pr checks $pr --json name,state --jq '[.[] | select(.state == "PENDING" or .state == "QUEUED")] | length')
-  if [ "$CI_FAILED" != "0" ]; then
-    # CI failed — collect details for triage
-    echo "PR #$pr — CI FAILED:"
-    gh pr checks $pr --json name,state,link --jq '.[] | select(.state == "FAILURE") | "\(.name): \(.state)"'
-  elif [ "$CI_PENDING" != "0" ]; then
-    echo "PR #$pr — CI still running ($CI_PENDING checks pending)"
-  else
-    # All checks passed but didn't auto-merge (race condition or label issue)
-    gh pr merge $pr --squash --admin
-    sleep 3
-  fi
-done
-```
-
-**⚠️ If CI fails: DO NOT admin-merge to bypass.** See "CI Failure Triage" below.
-
-## Step 3: Manual Worktree for Conflicts
-
-```bash
-git fetch origin TARGET_BRANCH
-git worktree add /tmp/backport-TARGET origin/TARGET_BRANCH
-cd /tmp/backport-TARGET
-
-for PR in ${CONFLICT_PRS[@]}; do
-  # Refresh target ref so each branch is based on current HEAD
-  git fetch origin TARGET_BRANCH
-  git checkout origin/TARGET_BRANCH
-
-  git checkout -b backport-$PR-to-TARGET origin/TARGET_BRANCH
-  git cherry-pick -m 1 $MERGE_SHA
-
-  # If conflict — NEVER skip based on file count alone!
-  # Categorize conflicts first: binary PNGs, modify/delete, content, add/add, component rewrites
-  # See SKILL.md Conflict Triage table for resolution per type.
-
-  # For component rewrites (4+ markers in a .vue file, library migration):
-  # DO NOT use accept-theirs regex — it produces broken hybrids.
-  # Instead, use the complete file from the merge commit:
-  # git show $MERGE_SHA:path/to/file > path/to/file
-
-  # For simple content conflicts, accept theirs:
-  # python3 -c "import re; ..."
-
-  # Resolve all conflicts, then:
-  git add .
-  GIT_EDITOR=true git cherry-pick --continue
-
-  # ── Public-API conflict review (REQUIRED for extension-API surfaces) ──
-  # If the conflict resolution touched any of these surfaces, consult oracle
-  # BEFORE pushing. A bad shim is worse than no fix:
-  #   - node.onXxx callback assignments (onDragDrop, onConnectionsChange, onRemoved, onConfigure, etc.)
-  #   - Methods on LGraphNode, LGraphCanvas, LGraph, Subgraph
-  #   - Public exports from src/lib/litegraph/
-  #   - Type changes in litegraph-augmentation.d.ts
-  # If a public callback's signature/contract changed: add a backport-only
-  # compatibility shim that preserves the OLD contract while keeping the
-  # new fix. Document it in the commit body under
-  # "## Backport-only compatibility fix". See SKILL.md gotcha section.
-  # ───────────────────────────────────────────────────────────────────────
-
-  # Per-PR validation BEFORE push (catches issues earlier than wave verification).
-  # Guard each targeted command against empty file lists — running `pnpm test:unit`
-  # with no path filter would run the full suite, and `pnpm exec eslint` with no args errors.
-  pnpm typecheck
-
-  mapfile -t TEST_FILES < <(git diff --name-only HEAD~1 | grep -E '\.test\.ts$' || true)
-  if [ ${#TEST_FILES[@]} -gt 0 ]; then
-    pnpm test:unit "${TEST_FILES[@]}"
-  else
-    echo "No changed test files — skipping targeted unit tests"
-  fi
-
-  mapfile -t CODE_FILES < <(git diff --name-only HEAD~1 | grep -E '\.(ts|vue)$' || true)
-  if [ ${#CODE_FILES[@]} -gt 0 ]; then
-    pnpm exec eslint "${CODE_FILES[@]}"
-    pnpm exec oxfmt --check "${CODE_FILES[@]}"
-  else
-    echo "No changed ts/vue files — skipping targeted lint/format"
-  fi
-
-  git push origin backport-$PR-to-TARGET --no-verify
-  NEW_PR=$(gh pr create --base TARGET_BRANCH --head backport-$PR-to-TARGET \
-    --title "[backport TARGET] TITLE (#$PR)" \
-    --body "Backport of #$PR..." | grep -oP '\d+$')
-
-  # Wait for CI before merging — NEVER admin-merge without CI passing
-  echo "Waiting for CI on PR #$NEW_PR..."
-  gh pr checks $NEW_PR --watch --fail-fast || {
-    echo "⚠️ CI failed on PR #$NEW_PR — skipping merge, needs triage"
-    continue
-  }
-  gh pr merge $NEW_PR --squash --admin
-  sleep 3
-done
-
-# Cleanup
-cd -
-git worktree remove /tmp/backport-TARGET --force
-```
-
-**⚠️ Human review for conflict resolutions:** When admin-merging a PR where you manually resolved conflicts (especially content conflicts beyond trivial accept-theirs), pause and present the resolution diff to the human for review before merging. Trivial resolutions (binary snapshots, modify/delete, locale key additions) can proceed without review.
-
-## Step 4: Wave Verification
-
-After completing all PRs in a wave for a target branch:
-
-```bash
-git fetch origin TARGET_BRANCH
-git worktree add /tmp/verify-TARGET origin/TARGET_BRANCH
-cd /tmp/verify-TARGET
-source ~/.nvm/nvm.sh && nvm use 24 && pnpm install && pnpm typecheck && pnpm test:unit
-git worktree remove /tmp/verify-TARGET --force
-```
-
-If verification fails, **do not skip** — create a fix PR:
-
-```bash
-# Stay in the verify worktree
-git checkout -b fix-backport-TARGET origin/TARGET_BRANCH
-
-# Common fixes:
-# 1. Component rewrite hybrids: overwrite with merge commit version
-git show MERGE_SHA:path/to/Component.vue > path/to/Component.vue
-
-# 2. Missing dependency files
-git show MERGE_SHA:path/to/missing.ts > path/to/missing.ts
-
-# 3. Missing type properties: edit the interface
-# 4. Unused imports: delete the import lines
-
-git add -A
-git commit --no-verify -m "fix: resolve backport typecheck issues on TARGET"
-git push origin fix-backport-TARGET --no-verify
-gh pr create --base TARGET --head fix-backport-TARGET --title "fix: resolve backport typecheck issues on TARGET" --body "..."
-gh pr merge $PR --squash --admin
-```
-
-Do not proceed to the next branch until typecheck passes.
-
-## Conflict Resolution Patterns
-
-### 1. Content Conflicts (accept theirs)
-
-```python
-import re
-pattern = r'<<<<<<< HEAD\n(.*?)=======\n(.*?)>>>>>>> [^\n]+\n?'
-content = re.sub(pattern, r'\2', content, flags=re.DOTALL)
-```
-
-### 2. Modify/Delete (two cases!)
-
-```bash
-# Case A: PR introduces NEW files not on target → keep them
-git add $FILE
-
-# Case B: Target REMOVED files the PR modifies → drop them
-git rm $FILE
-```
-
-### 3. Binary Files (snapshots)
-
-```bash
-git checkout --theirs $FILE && git add $FILE
-```
-
-### 4. Component Rewrites (DO NOT accept-theirs)
-
-When a PR completely rewrites a component (e.g., PrimeVue → Reka UI), accept-theirs produces
-a broken hybrid with mismatched template/script sections.
-
-```bash
-# Use the complete correct file from the merge commit instead:
-git show $MERGE_SHA:src/components/input/MultiSelect.vue > src/components/input/MultiSelect.vue
-git show $MERGE_SHA:src/components/input/SingleSelect.vue > src/components/input/SingleSelect.vue
-git add src/components/input/MultiSelect.vue src/components/input/SingleSelect.vue
-```
-
-**Detection:** 4+ conflict markers in a single `.vue` file, imports changing between component
-libraries (PrimeVue → Reka UI, etc.), template structure completely different on each side.
-
-### 5. Missing Dependencies After Cherry-Pick
-
-Cherry-picks can succeed but leave the branch broken because the PR's code on main
-references composables/components introduced by an earlier PR.
-
-```bash
-# Add the missing file from the merge commit:
-git show $MERGE_SHA:src/composables/queue/useJobDetailsHover.ts > src/composables/queue/useJobDetailsHover.ts
-git show $MERGE_SHA:src/components/builder/BuilderSaveDialogContent.vue > src/components/builder/BuilderSaveDialogContent.vue
-```
-
-**Detection:** `pnpm typecheck` fails with "Cannot find module" or "X is not defined" after cherry-pick succeeds cleanly.
-
-### 6. Locale Files
-
-Usually adding new i18n keys — accept theirs, validate JSON:
-
-```bash
-python3 -c "import json; json.load(open('src/locales/en/main.json'))" && echo "Valid"
-```
-
-## Merge Conflicts After Other Merges
-
-When merging multiple PRs to the same branch, later PRs may conflict with earlier merges:
-
-```bash
-git fetch origin TARGET_BRANCH
-git rebase origin/TARGET_BRANCH
-# Resolve new conflicts
-git push --force origin backport-$PR-to-TARGET
-sleep 20  # Wait for GitHub to recompute merge state
-# Wait for CI after rebase before merging
-gh pr checks $PR --watch --fail-fast && gh pr merge $PR --squash --admin
-```
-
-## Lessons Learned
-
-1. **Automation reports more conflicts than reality** — `cherry-pick -m 1` with git auto-merge handles many "conflicts" the automation can't
-2. **Never skip based on conflict file count** — 12 or 27 conflicts can be trivial (snapshots, new files). Categorize first: binary PNGs, modify/delete, content, add/add.
-3. **Modify/delete goes BOTH ways** — if the PR introduces new files (not on target), `git add` them. If target deleted files the PR modifies, `git rm`.
-4. **Binary snapshot PNGs** — always `git checkout --theirs && git add`. Never skip a PR just because it has many snapshot conflicts.
-5. **Batch label additions need 2s delay** between API calls to avoid rate limits
-6. **Merging 6+ PRs rapidly** can cause later PRs to become unmergeable — wait 20-30s for GitHub to recompute merge state
-7. **appModeStore.ts, painter files, GLSLShader files** don't exist on core/1.40 — `git rm` these
-8. **Always validate JSON** after resolving locale file conflicts
-9. **Dep refresh PRs** — skip on stable branches. Risk of transitive dep regressions outweighs audit cleanup. Cherry-pick individual CVE fixes instead.
-10. **Verify after each wave** — run `pnpm typecheck && pnpm test:unit` on the target branch after merging a batch. Catching breakage early prevents compounding errors.
-11. **App mode and Firebase auth are NOT cloud-only** — they go to both core and cloud branches. Only team workspaces, cloud queue, and cloud-specific login are cloud-only.
-12. **Never admin-merge without CI** — `--admin` bypasses all branch protections including required status checks. A bulk session of 69 admin-merges shipped 3 test failures. Always wait for CI to pass first, or use `--auto --squash` which waits by design.
-13. **Accept-theirs regex breaks component rewrites** — when a PR migrates between component libraries (PrimeVue → Reka UI), the regex produces a broken hybrid. Use `git show SHA:path > path` to get the complete correct version instead.
-14. **Cherry-picks can silently bring in missing-dependency code** — if PR A references a composable introduced by PR B, cherry-picking A succeeds but typecheck fails. Always run typecheck after each wave and add missing files from the merge commit.
-15. **Fix PRs are expected** — plan for 1 fix PR per branch to resolve typecheck issues from conflict resolutions. This is normal, not a failure.
-16. **Use `--no-verify` in worktrees** — husky hooks fail in `/tmp/` worktrees. Always push/commit with `--no-verify`.
-17. **Automation success varies by branch** — core/1.42 got 18/26 auto-PRs (69%), cloud/1.42 got 1/25 (4%). Cloud branches diverge more. Plan for manual fallback.
-18. **Test-then-resolve pattern** — for branches with low automation success, run a dry-run loop to classify clean vs conflict PRs before processing. This is much faster than resolving conflicts serially.
-19. **Public-API conflict resolutions need oracle review** — when a conflict touches `node.onXxx` callbacks, `LGraphNode`/`LGraphCanvas`/`LGraph`/`Subgraph` methods, or types in `litegraph-augmentation.d.ts`, consult oracle BEFORE pushing. Custom-node packages depend on these contracts. A literal cherry-pick of a refactor-style fix can silently break extensions still using the old contract — sometimes recreating the very bug the PR was fixing. Document any backport-only compatibility shim explicitly in the commit body.
-20. **Cherry-picked tests can require unbackported test scaffolding** — when a PR modifies a test file that was _added_ on main by an earlier unbackported PR, the cherry-pick reports modify/delete on that file. Drop it from the backport (`git rm`) and document which PR introduced it. Don't smuggle in test infrastructure without its runtime prerequisites.
-21. **Per-PR validation catches issues earlier than wave verification** — for high-stakes branches, run `pnpm typecheck && pnpm exec eslint <changed files> && pnpm exec oxfmt --check` per PR before pushing. Wave verification still matters (it catches cross-PR interactions), but per-PR makes attribution trivial when something fails.
-
-## CI Failure Triage
-
-When CI fails on a backport PR, present failures to the user using this template:
-
-```markdown
-### PR #XXXX — CI Failed
-
-- **Failing check:** test / lint / typecheck
-- **Error:** (summary of the failure message)
-- **Likely cause:** test backported without implementation / missing dependency / flaky test / snapshot mismatch
-- **Recommendation:** backport PR #YYYY first / skip this PR / rerun CI after fixing prerequisites
-```
-
-Common failure categories:
-
-| Category                    | Example                                  | Resolution                                |
-| --------------------------- | ---------------------------------------- | ----------------------------------------- |
-| Test without implementation | Test references function not on branch   | Backport the implementation PR first      |
-| Missing dependency          | Import from module not on branch         | Backport the dependency PR first, or skip |
-| Snapshot mismatch           | Screenshot test differs                  | Usually safe — update snapshots on branch |
-| Flaky test                  | Passes on retry                          | Re-run CI, merge if green on retry        |
-| Type error                  | Interface changed on main but not branch | May need manual adaptation                |
-
-**Never assume a failure is safe to skip.** Present all failures to the user with analysis.
-
-## PR Body Template (Manual Cherry-Picks)
-
-Manual cherry-pick PRs need detail beyond the automation's terse default. Use this template — reviewers will look here before re-deriving conflict-resolution logic from the diff.
-
-```markdown
-Manual backport of #ORIG to `TARGET` for inclusion in `vX.Y.Z`.
-
-Cherry-picked from upstream merge commit `SHORT_SHA`.
-
-## Why
-
-[1-2 sentences from the original PR's "Summary" — what bug, what fix mechanism]
-
-## Conflict resolution
-
-- **`path/to/file`** — [what conflicted on this branch] → [resolution chosen + why]
-- **`path/to/dropped-test.test.ts`** — added on main by unrelated PR #XXXX (not backported). Dropped from this backport; runtime fix intact.
-- [...]
-
-## Backport-only compatibility fix (if applicable)
-
-[If you added a shim that wasn't in the upstream PR, document it here — what extension surface, what contract, what the shim preserves, why the upstream version would have regressed it]
-
-## Validation
-
-- `pnpm typecheck` ✅
-- `pnpm test:unit <targeted suites>` ✅ (N/N passing)
-- `pnpm exec eslint <changed files>` ✅ (0 errors)
-- `pnpm exec oxfmt --check` ✅ (clean)
-
-[If manual e2e was skipped, explain why — e.g., requires live backend, headless not feasible. State that source is byte-identical to upstream + how long it's been baking on main.]
-
-Original PR: #ORIG / Original commit: `FULL_SHA`
-```
-
-The conflict-resolution section is non-negotiable — every conflict you resolved by hand needs a one-liner. This makes archaeology trivial six months later when someone asks "why does this look slightly different from main?"

.agents/skills/backport-management/reference/logging.md

@@ -1,103 +0,0 @@
-# Logging & Session Reports
-
-## During Execution
-
-Maintain `execution-log.md` with per-branch tables (this is internal, markdown tables are fine here):
-
-```markdown
-| PR#   | Title | Status | Backport PR | Notes   |
-| ----- | ----- | ------ | ----------- | ------- |
-| #XXXX | Title | merged | #YYYY       | Details |
-```
-
-## Wave Verification Log
-
-Track verification results per wave within execution-log.md:
-
-```markdown
-Wave N Verification -- TARGET_BRANCH
-
-- PRs merged: #A, #B, #C
-- Typecheck: pass / fail
-- Fix PR: #YYYY (if needed)
-- Issues found: (if any)
-```
-
-## Session Report Template
-
-```markdown
-# Backport Session Report
-
-## Summary
-
-| Branch | Candidates | Merged | Skipped | Deferred | Rate |
-| ------ | ---------- | ------ | ------- | -------- | ---- |
-
-## Deferred Items (Needs Human)
-
-| PR# | Title | Branch | Issue |
-
-## Conflict Resolutions Requiring Review
-
-| PR# | Branch | Conflict Type | Resolution Summary |
-
-## CI Failure Report
-
-| PR# | Branch | Failing Check | Error Summary | Cause | Resolution |
-| --- | ------ | ------------- | ------------- | ----- | ---------- |
-
-## Automation Performance
-
-| Metric                      | Value |
-| --------------------------- | ----- |
-| Auto success rate           | X%    |
-| Manual resolution rate      | X%    |
-| Overall clean rate          | X%    |
-| Wave verification pass rate | X%    |
-
-## Process Recommendations
-
-- Were there clusters of related PRs that should have been backported together?
-- Any PRs that should have been backported sooner (continuous backporting candidates)?
-- Feature branches that need tracking for future sessions?
-```
-
-## Final Deliverables
-
-After all branches are complete and verified, generate these files in `~/temp/backport-session/`:
-
-### 1. execution-log.md (internal)
-
-Per-branch tables with PR#, title, status, backport PR#, notes. Markdown tables are fine — this is for internal tracking, not Slack.
-
-### 2. backport-author-accountability.md (Slack-compatible)
-
-See SKILL.md "Final Deliverables" section. Plain text, no emojis/tables/headers/bold. Authors sorted alphabetically with PRs nested under each.
-
-### 3. slack-status-update.md (Slack-compatible)
-
-See SKILL.md "Final Deliverables" section. Plain text summary that pastes cleanly into Slack. Includes branch counts, notable fixes, conflict patterns, author count.
-
-## Slack Formatting Rules
-
-Both shareable files (author accountability + status update) must follow these rules:
-
-- No emojis (no checkmarks, no arrows, no icons)
-- No markdown tables (use plain lists with dashes)
-- No headers (no # or ##)
-- No bold (\*_) or italic (_)
-- No inline code backticks
-- Use -- instead of em dash
-- Use plain dashes (-) for lists with 4-space indent for nesting
-- Line breaks between sections for readability
-
-These files should paste directly into a Slack message and look clean.
-
-## Files to Track
-
-All in `~/temp/backport-session/`:
-
-- `execution-plan.md` -- approved PRs with merge SHAs (input)
-- `execution-log.md` -- real-time status with per-branch tables (internal)
-- `backport-author-accountability.md` -- PRs grouped by author (Slack-compatible)
-- `slack-status-update.md` -- session summary (Slack-compatible)

.agents/skills/contain-audit/SKILL.md

@@ -1,99 +0,0 @@
----
-name: contain-audit
-description: 'Detect DOM elements where CSS contain:layout+style would improve rendering performance. Runs a Playwright-based audit on a large workflow, scores candidates by subtree size and sizing constraints, measures performance impact, and generates a ranked report.'
----
-
-# CSS Containment Audit
-
-Automatically finds DOM elements where adding `contain: layout style` would reduce browser recalculation overhead.
-
-## What It Does
-
-1. Loads a large workflow (245 nodes) in a real browser
-2. Walks the DOM tree and scores every element as a containment candidate
-3. For each high-scoring candidate, applies `contain: layout style` via JavaScript
-4. Measures rendering performance (style recalcs, layouts, task duration) before and after
-5. Takes before/after screenshots to detect visual breakage
-6. Generates a ranked report with actionable recommendations
-
-## When to Use
-
-- After adding new Vue components to the node rendering pipeline
-- When investigating rendering performance on large workflows
-- Before and after refactoring node DOM structure
-- As part of periodic performance audits
-
-## How to Run
-
-```bash
-# Start the dev server first
-pnpm dev &
-
-# Run the audit (uses the @audit tag, not included in normal CI runs)
-pnpm exec playwright test browser_tests/tests/containAudit.spec.ts --project=audit
-
-# View the HTML report
-pnpm exec playwright show-report
-```
-
-## How to Read Results
-
-The audit outputs a table to the console:
-
-```text
-CSS Containment Audit Results
-=======================================================
-Rank | Selector                        | Subtree | Score | DRecalcs | DLayouts | Visual
-  1  | [data-testid="node-inner-wrap"] |     18  |  72   |    -34%  |    -12%  |   OK
-  2  | .node-body                      |     12  |  48   |     -8%  |     -3%  |   OK
-  3  | .node-header                    |      4  |  16   |     +1%  |      0%  |   OK
-```
-
-- **Subtree**: Number of descendant elements (higher = more to skip)
-- **Score**: Composite heuristic score (subtree size x sizing constraint bonus)
-- **DRecalcs / DLayouts**: Change in style recalcs / layout counts vs baseline (negative = improvement)
-- **Visual**: OK if no pixel change, DIFF if screenshot differs (may include subpixel noise — verify manually)
-
-## Candidate Scoring
-
-An element is a good containment candidate when:
-
-1. **Large subtree** -- many descendants that the browser can skip recalculating
-2. **Externally constrained size** -- width/height determined by CSS variables, flex, or explicit values (not by content)
-3. **No existing containment** -- `contain` is not already applied
-4. **Not a leaf** -- has at least a few child elements
-
-Elements that should NOT get containment:
-
-- Elements whose children overflow visually beyond bounds (e.g., absolute-positioned overlays with negative inset)
-- Elements whose height is determined by content and affects sibling layout
-- Very small subtrees (overhead of containment context outweighs benefit)
-
-## Limitations
-
-- Cannot fully guarantee `contain` safety -- visual review of screenshots is required
-- Performance measurements have natural variance; run multiple times for confidence
-- Only tests idle and pan scenarios; widget interactions may differ
-- The audit modifies styles at runtime via JS, which doesn't account for Tailwind purging or build-time optimizations
-
-## Example PR
-
-[#9946 — fix: add CSS contain:layout contain:style to node inner wrapper](https://github.com/Comfy-Org/ComfyUI_frontend/pull/9946)
-
-This PR added `contain-layout contain-style` to the node inner wrapper div in `LGraphNode.vue`. The audit tool would have flagged this element as a high-scoring candidate because:
-
-- **Large subtree** (18+ descendants: header, slots, widgets, content, badges)
-- **Externally constrained size** (`w-(--node-width)`, `flex-1` — dimensions set by CSS variables and flex parent)
-- **Natural isolation boundary** between frequently-changing content (widgets) and infrequently-changing overlays (selection outlines, borders)
-
-The actual change was a single line: adding `'contain-layout contain-style'` to the inner wrapper's class list at `src/renderer/extensions/vueNodes/components/LGraphNode.vue:79`.
-
-## Reference
-
-| Resource          | Path                                                    |
-| ----------------- | ------------------------------------------------------- |
-| Audit test        | `browser_tests/tests/containAudit.spec.ts`              |
-| PerformanceHelper | `browser_tests/fixtures/helpers/PerformanceHelper.ts`   |
-| Perf tests        | `browser_tests/tests/performance.spec.ts`               |
-| Large workflow    | `browser_tests/assets/large-graph-workflow.json`        |
-| Example PR        | https://github.com/Comfy-Org/ComfyUI_frontend/pull/9946 |

.agents/skills/hardening-flaky-e2e-tests/SKILL.md

@@ -1,246 +0,0 @@
----
-name: hardening-flaky-e2e-tests
-description: 'Diagnoses and fixes flaky Playwright e2e tests by replacing race-prone patterns with retry-safe alternatives. Use when triaging CI flakes, hardening spec files, fixing timing races, or asked to stabilize browser tests. Triggers on: flaky, flake, harden, stabilize, race condition in e2e, intermittent failure.'
----
-
-# Hardening Flaky E2E Tests
-
-Fix flaky Playwright specs by identifying race-prone patterns and replacing them with retry-safe alternatives. This skill covers diagnosis, pattern matching, and mechanical transforms — not writing new tests (see `writing-playwright-tests` for that).
-
-## Workflow
-
-### 1. Gather CI Evidence
-
-```bash
-gh run list --workflow=ci-test.yaml --limit=5
-gh run download <run-id> -n playwright-report
-```
-
-- Open `report.json` and search for `"status": "flaky"` entries.
-- Collect file paths, test titles, and error messages.
-- Do NOT trust green checks alone — flaky tests that passed on retry still need fixing.
-- Use `error-context.md`, traces, and page snapshots before editing code.
-- Pull the newest run after each push instead of assuming the flaky set is unchanged.
-
-### 2. Classify the Flake
-
-Read the failing assertion and match it against the pattern table. Most flakes fall into one of these categories:
-
-| #   | Pattern                               | Signature in Code                                         | Fix                                                              |
-| --- | ------------------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------- |
-| 1   | **Snapshot-then-assert**              | `expect(await evaluate()).toBe(x)`                        | `await expect.poll(() => evaluate()).toBe(x)`                    |
-| 2   | **Immediate count**                   | `const n = await loc.count(); expect(n).toBe(3)`          | `await expect(loc).toHaveCount(3)`                               |
-| 3   | **nextFrame after menu click**        | `clickMenuItem(x); nextFrame()`                           | `clickMenuItem(x); contextMenu.waitForHidden()`                  |
-| 4   | **Tight poll timeout**                | `expect.poll(..., { timeout: 250 })`                      | ≥2000 ms; prefer default 5000 ms                                 |
-| 5   | **Immediate evaluate after mutation** | `setSetting(k, v); expect(await evaluate()).toBe(x)`      | `await expect.poll(() => evaluate()).toBe(x)`                    |
-| 6   | **Screenshot without readiness**      | `loadWorkflow(); nextFrame(); toHaveScreenshot()`         | `waitForNodes()` or poll state first                             |
-| 7   | **Non-deterministic node order**      | `getNodeRefsByType('X')[0]` with >1 match                 | `getNodeRefById(id)` or guard `toHaveLength(1)`                  |
-| 8   | **Fake readiness helper**             | Helper clicks but doesn't assert state                    | Remove; poll the actual value                                    |
-| 9   | **Immediate graph state after drop**  | `expect(await getLinkCount()).toBe(1)`                    | `await expect.poll(() => getLinkCount()).toBe(1)`                |
-| 10  | **Immediate boundingBox/layout read** | `const box = await loc.boundingBox(); expect(box!.width)` | `await expect.poll(() => loc.boundingBox().then(b => b?.width))` |
-
-### 3. Apply the Transform
-
-#### Rule: Choose the Smallest Correct Assertion
-
-- **Locator state** → use built-in retrying assertions: `toBeVisible()`, `toHaveText()`, `toHaveCount()`, `toHaveClass()`
-- **Single async value** → `expect.poll(() => asyncFn()).toBe(expected)`
-- **Multiple assertions that must settle together** → `expect(async () => { ... }).toPass()`
-- **Never** use `waitForTimeout()` to hide a race.
-
-```typescript
-// ✅ Single value — use expect.poll
-await expect
-  .poll(() => comfyPage.page.evaluate(() => window.app!.graph.links.length))
-  .toBe(3)
-
-// ✅ Locator count — use toHaveCount
-await expect(comfyPage.page.locator('.dom-widget')).toHaveCount(2)
-
-// ✅ Multiple conditions — use toPass
-await expect(async () => {
-  expect(await node1.getValue()).toBe('foo')
-  expect(await node2.getValue()).toBe('bar')
-}).toPass({ timeout: 5000 })
-```
-
-#### Rule: Wait for the Real Readiness Boundary
-
-Visible is not always ready. Prefer user-facing assertions when possible; poll internal state only when there is no UI surface to assert on.
-
-Common readiness boundaries:
-
-| After this action...                   | Wait for...                                                  |
-| -------------------------------------- | ------------------------------------------------------------ |
-| Canvas interaction (drag, click node)  | `await comfyPage.nextFrame()`                                |
-| Menu item click                        | `await contextMenu.waitForHidden()`                          |
-| Workflow load                          | `await comfyPage.workflow.loadWorkflow(...)` (built-in wait) |
-| Settings write                         | Poll the setting value with `expect.poll()`                  |
-| Node pin/bypass/collapse toggle        | `await expect.poll(() => nodeRef.isPinned()).toBe(true)`     |
-| Graph mutation (add/remove node, link) | Poll link/node count                                         |
-| Clipboard write                        | Poll pasted value                                            |
-| Screenshot                             | Ensure nodes are rendered: `waitForNodes()` or poll state    |
-
-#### Rule: Expose Locators for Retrying Assertions
-
-When a helper returns a count via `await loc.count()`, callers can't use `toHaveCount()`. Expose the underlying `Locator` as a getter so callers choose between:
-
-```typescript
-// Helper exposes locator
-get domWidgets(): Locator {
-  return this.page.locator('.dom-widget')
-}
-
-// Caller uses retrying assertion
-await expect(comfyPage.domWidgets).toHaveCount(2)
-```
-
-Replace count methods with locator getters so callers can use retrying assertions directly.
-
-#### Rule: Fix Check-then-Act Races in Helpers
-
-```typescript
-// ❌ Race: count can change between check and waitFor
-const count = await locator.count()
-if (count > 0) {
-  await locator.waitFor({ state: 'hidden' })
-}
-
-// ✅ Direct: waitFor handles both cases
-await locator.waitFor({ state: 'hidden' })
-```
-
-#### Rule: Remove force:true from Clicks
-
-`force: true` bypasses actionability checks, hiding real animation/visibility races. Remove it and fix the underlying timing issue.
-
-```typescript
-// ❌ Hides the race
-await closeButton.click({ force: true })
-
-// ✅ Surfaces the real issue — fix with proper wait
-await closeButton.click()
-await dialog.waitForHidden()
-```
-
-#### Rule: Handle Non-deterministic Element Order
-
-When `getNodeRefsByType` returns multiple nodes, the order is not guaranteed. Don't use index `[0]` blindly.
-
-```typescript
-// ❌ Assumes order
-const node = (await comfyPage.nodeOps.getNodeRefsByType('CLIPTextEncode'))[0]
-
-// ✅ Find by ID or proximity
-const nodes = await comfyPage.nodeOps.getNodeRefsByType('CLIPTextEncode')
-let target = nodes[0]
-for (const n of nodes) {
-  const pos = await n.getPosition()
-  if (Math.abs(pos.y - expectedY) < minDist) target = n
-}
-```
-
-Or guard the assumption:
-
-```typescript
-const nodes = await comfyPage.nodeOps.getNodeRefsByType('CLIPTextEncode')
-expect(nodes).toHaveLength(1)
-const node = nodes[0]
-```
-
-#### Rule: Use toPass for Timing-sensitive Dismiss Guards
-
-Some UI elements (e.g. LiteGraph's graphdialog) have built-in dismiss delays. Retry the entire dismiss action:
-
-```typescript
-// ✅ Retry click+assert together
-await expect(async () => {
-  await comfyPage.canvas.click({ position: { x: 10, y: 10 } })
-  await expect(dialog).toBeHidden({ timeout: 500 })
-}).toPass({ timeout: 5000 })
-```
-
-### 4. Keep Changes Narrow
-
-- Shared helpers should drive setup to a stable boundary.
-- Do not encode one-spec timing assumptions into generic helpers.
-- If a race only matters to one spec, prefer a local wait in that spec.
-- If a helper fails before the real test begins, remove or relax the brittle precondition and let downstream UI interaction prove readiness.
-
-### 5. Verify Narrowly
-
-```bash
-# Targeted rerun with repetition
-pnpm test:browser:local -- browser_tests/tests/myFile.spec.ts --repeat-each 10
-
-# Single test by line number (avoids grep quoting issues on Windows)
-pnpm test:browser:local -- browser_tests/tests/myFile.spec.ts:42
-```
-
-- Use `--repeat-each 10` for targeted flake verification (use 20 for single test cases).
-- Verify with the smallest command that exercises the flaky path.
-
-### 6. Watch CI E2E Runs
-
-After pushing, use `gh` to monitor the E2E workflow:
-
-```bash
-# Find the run for the current branch
-gh run list --workflow="CI: Tests E2E" --branch=$(git branch --show-current) --limit=1
-
-# Watch it live (blocks until complete, streams logs)
-gh run watch <run-id>
-
-# One-liner: find and watch the latest E2E run for the current branch
-gh run list --workflow="CI: Tests E2E" --branch=$(git branch --show-current) --limit=1 --json databaseId --jq ".[0].databaseId" | xargs gh run watch
-```
-
-On Windows (PowerShell):
-
-```powershell
-# One-liner equivalent
-gh run watch (gh run list --workflow="CI: Tests E2E" --branch=$(git branch --show-current) --limit=1 --json databaseId --jq ".[0].databaseId")
-```
-
-After the run completes:
-
-```bash
-# Download the Playwright report artifact
-gh run download <run-id> -n playwright-report
-
-# View the run summary in browser
-gh run view <run-id> --web
-```
-
-Also watch the unit test workflow in parallel if you changed helpers:
-
-```bash
-gh run list --workflow="CI: Tests Unit" --branch=$(git branch --show-current) --limit=1
-```
-
-### 7. Pre-merge Checklist
-
-Before merging a flaky-test fix, confirm:
-
-- [ ] The latest CI artifact was inspected directly
-- [ ] The root cause is stated as a race or readiness mismatch
-- [ ] The fix waits on the real readiness boundary
-- [ ] The assertion primitive matches the job (poll vs toHaveCount vs toPass)
-- [ ] The fix stays local unless a shared helper truly owns the race
-- [ ] Local verification uses a targeted rerun
-- [ ] No behavioral changes to the test — only timing/retry strategy updated
-
-## Local Noise — Do Not Fix
-
-These are local distractions, not CI root causes:
-
-- Missing local input fixture files required by the test path
-- Missing local models directory
-- Teardown `EPERM` while restoring the local browser-test user data directory
-- Local screenshot baseline differences on Windows
-
-Rules:
-
-- First confirm whether it blocks the exact flaky path under investigation.
-- Do not commit temporary local assets used only for verification.
-- Do not commit local screenshot baselines.

.agents/skills/layer-audit/SKILL.md

@@ -1,82 +0,0 @@
----
-name: layer-audit
-description: 'Detect violations of the layered architecture import rules (base -> platform -> workbench -> renderer). Runs ESLint with the import-x/no-restricted-paths rule and generates a grouped report.'
----
-
-# Layer Architecture Audit
-
-Finds imports that violate the layered architecture boundary rules enforced by `import-x/no-restricted-paths` in `eslint.config.ts`.
-
-## Layer Hierarchy (bottom to top)
-
-```
-renderer  (top -- can import from all lower layers)
-   ^
-workbench
-   ^
-platform
-   ^
-  base    (bottom -- cannot import from any upper layer)
-```
-
-Each layer may only import from layers below it.
-
-## How to Run
-
-```bash
-# Run ESLint filtering for just the layer boundary rule violations
-pnpm lint 2>&1 | grep 'import-x/no-restricted-paths' -B1 | head -200
-```
-
-To get a full structured report, run:
-
-```bash
-# Collect all violations from base/, platform/, workbench/ layers
-pnpm eslint src/base/ src/platform/ src/workbench/ --no-error-on-unmatched-pattern --rule '{"import-x/no-restricted-paths": "warn"}' --format compact 2>&1 | grep 'no-restricted-paths' | sort
-```
-
-## How to Read Results
-
-Each violation line shows:
-
-- The **file** containing the bad import
-- The **import path** crossing the boundary
-- The **message** identifying which layer pair is violated
-
-### Grouping by Layer Pair
-
-After collecting violations, group them by the layer pair pattern:
-
-| Layer pair            | Meaning                             |
-| --------------------- | ----------------------------------- |
-| base -> platform      | base/ importing from platform/      |
-| base -> workbench     | base/ importing from workbench/     |
-| base -> renderer      | base/ importing from renderer/      |
-| platform -> workbench | platform/ importing from workbench/ |
-| platform -> renderer  | platform/ importing from renderer/  |
-| workbench -> renderer | workbench/ importing from renderer/ |
-
-## When to Use
-
-- Before creating a PR that adds imports between `src/base/`, `src/platform/`, `src/workbench/`, or `src/renderer/`
-- When auditing the codebase to find and plan migration of existing violations
-- After moving files between layers to verify no new violations were introduced
-
-## Fixing Violations
-
-Common strategies to resolve a layer violation:
-
-1. **Move the import target down** -- if the imported module doesn't depend on upper-layer concepts, move it to a lower layer
-2. **Introduce an interface** -- define an interface/type in the lower layer and implement it in the upper layer via dependency injection or a registration pattern
-3. **Move the importing file up** -- if the file logically belongs in a higher layer, relocate it
-4. **Extract shared logic** -- pull the shared functionality into `base/` or a shared utility
-
-## Reference
-
-| Resource                        | Path               |
-| ------------------------------- | ------------------ |
-| ESLint config (rule definition) | `eslint.config.ts` |
-| Base layer                      | `src/base/`        |
-| Platform layer                  | `src/platform/`    |
-| Workbench layer                 | `src/workbench/`   |
-| Renderer layer                  | `src/renderer/`    |

.agents/skills/perf-fix-with-proof/SKILL.md

@@ -1,179 +0,0 @@
----
-name: perf-fix-with-proof
-description: 'Ships performance fixes with CI-proven improvement using stacked PRs. PR1 adds a @perf test (establishes baseline on main), PR2 adds the fix (CI shows delta). Use when implementing a perf optimization and wanting to prove it in CI.'
----
-
-# Performance Fix with Proof
-
-Ships perf fixes as two stacked PRs so CI automatically proves the improvement.
-
-## Why Two PRs
-
-The `ci-perf-report.yaml` workflow compares PR metrics against the **base branch baseline**. If you add a new `@perf` test in the same PR as the fix, that test doesn't exist on main yet — no baseline, no delta, no proof. Stacking solves this:
-
-1. **PR1 (test-only)** — adds the `@perf` test that exercises the bottleneck. Merges to main. CI runs it on main → baseline established.
-2. **PR2 (fix)** — adds the optimization. CI runs the same test → compares against PR1's baseline → delta shows improvement.
-
-## Workflow
-
-### Step 1: Create the test branch
-
-```bash
-git worktree add <worktree-path> -b perf/test-<name> origin/main
-```
-
-### Step 2: Write the `@perf` test
-
-Add a test to `browser_tests/tests/performance.spec.ts` (or a new file with `@perf` tag). The test should stress the specific bottleneck.
-
-**Test structure:**
-
-```typescript
-test('<descriptive name>', async ({ comfyPage }) => {
-  // 1. Load a workflow that exercises the bottleneck
-  await comfyPage.workflow.loadWorkflow('<workflow>')
-
-  // 2. Start measuring
-  await comfyPage.perf.startMeasuring()
-
-  // 3. Perform the action that triggers the bottleneck (at scale)
-  for (let i = 0; i < N; i++) {
-    // ... stress the hot path ...
-    await comfyPage.nextFrame()
-  }
-
-  // 4. Stop measuring and record
-  const m = await comfyPage.perf.stopMeasuring('<metric-name>')
-  recordMeasurement(m)
-  console.log(`<name>: ${m.styleRecalcs} recalcs, ${m.layouts} layouts`)
-})
-```
-
-**Available metrics** (from `PerformanceHelper`):
-
-- `m.styleRecalcs` / `m.styleRecalcDurationMs` — style recalculation count and time
-- `m.layouts` / `m.layoutDurationMs` — forced layout count and time
-- `m.taskDurationMs` — total main-thread JS execution time
-- `m.heapDeltaBytes` — memory pressure delta
-
-**Key helpers** (from `ComfyPage`):
-
-- `comfyPage.perf.startMeasuring()` / `.stopMeasuring(name)` — CDP metrics capture
-- `comfyPage.nextFrame()` — wait one animation frame
-- `comfyPage.workflow.loadWorkflow(name)` — load a test workflow from `browser_tests/assets/`
-- `comfyPage.canvas` — the canvas locator
-- `comfyPage.page.mouse.move(x, y)` — mouse interaction
-
-### Step 3: Add test workflow asset (if needed)
-
-If the bottleneck needs a specific workflow (e.g., 50+ nodes, many DOM widgets), add it to `browser_tests/assets/`. Keep it minimal — only the structure needed to trigger the bottleneck.
-
-### Step 4: Verify locally
-
-```bash
-pnpm exec playwright test --project=performance --grep "<test name>"
-```
-
-Confirm the test runs and produces reasonable metric values.
-
-### Step 5: Create PR1 (test-only)
-
-```bash
-pnpm typecheck:browser
-pnpm lint
-git add browser_tests/
-git commit -m "test: add perf test for <bottleneck description>"
-git push -u origin perf/test-<name>
-gh pr create --title "test: add perf test for <bottleneck>" \
-  --body "Adds a @perf test to establish a baseline for <bottleneck>.
-
-This is PR 1 of 2. The fix will follow in a separate PR once this baseline is established on main.
-
-## What
-Adds \`<test-name>\` to the performance test suite measuring <metric> during <action>.
-
-## Why
-Needed to prove the improvement from the upcoming fix for backlog item #<N>." \
-  --base main
-```
-
-### Step 6: Get PR1 merged
-
-Once PR1 merges, CI runs the test on main → baseline artifact saved.
-
-### Step 7: Create PR2 (fix) on top of main
-
-```bash
-git worktree add <worktree-path> -b perf/fix-<name> origin/main
-```
-
-Implement the fix. The `@perf` test from PR1 is now on main and will run automatically. CI will:
-
-1. Run the test on the PR branch
-2. Download the baseline from main (which includes PR1's test results)
-3. Post a PR comment showing the delta
-
-### Step 8: Verify the improvement shows in CI
-
-The `ci-perf-report.yaml` posts a comment like:
-
-```markdown
-## ⚡ Performance Report
-
-| Metric                | Baseline | PR (n=3) | Δ    | Sig |
-| --------------------- | -------- | -------- | ---- | --- |
-| <name>: style recalcs | 450      | 12       | -97% | 🟢  |
-```
-
-If Δ is negative for the target metric, the fix is proven.
-
-## Test Design Guidelines
-
-1. **Stress the specific bottleneck** — don't measure everything, isolate the hot path
-2. **Use enough iterations** — the test should run long enough that the metric difference is clear (100+ frames for idle tests, 50+ interactions for event tests)
-3. **Keep it deterministic** — avoid timing-dependent assertions; measure counts not durations when possible
-4. **Match the backlog entry** — reference the backlog item number in the test name or PR description
-
-## Examples
-
-**Testing DOM widget reactive mutations (backlog #8):**
-
-```typescript
-test('DOM widget positioning recalculations', async ({ comfyPage }) => {
-  await comfyPage.workflow.loadWorkflow('default')
-  await comfyPage.perf.startMeasuring()
-  // Idle for 120 frames — DOM widgets update position every frame
-  for (let i = 0; i < 120; i++) {
-    await comfyPage.nextFrame()
-  }
-  const m = await comfyPage.perf.stopMeasuring('dom-widget-idle')
-  recordMeasurement(m)
-})
-```
-
-**Testing measureText caching (backlog #4):**
-
-```typescript
-test('canvas text rendering with many nodes', async ({ comfyPage }) => {
-  await comfyPage.workflow.loadWorkflow('large-workflow-50-nodes')
-  await comfyPage.perf.startMeasuring()
-  for (let i = 0; i < 60; i++) {
-    await comfyPage.nextFrame()
-  }
-  const m = await comfyPage.perf.stopMeasuring('text-rendering-50-nodes')
-  recordMeasurement(m)
-})
-```
-
-## Reference
-
-| Resource          | Path                                                  |
-| ----------------- | ----------------------------------------------------- |
-| Perf test file    | `browser_tests/tests/performance.spec.ts`             |
-| PerformanceHelper | `browser_tests/fixtures/helpers/PerformanceHelper.ts` |
-| Perf reporter     | `browser_tests/fixtures/utils/perfReporter.ts`        |
-| CI workflow       | `.github/workflows/ci-perf-report.yaml`               |
-| Report generator  | `scripts/perf-report.ts`                              |
-| Stats utilities   | `scripts/perf-stats.ts`                               |
-| Backlog           | `docs/perf/BACKLOG.md` (local only, not committed)    |
-| Playbook          | `docs/perf/PLAYBOOK.md` (local only, not committed)   |

.agents/skills/red-green-fix/SKILL.md

@@ -1,221 +0,0 @@
----
-name: red-green-fix
-description: 'Bug fix workflow that proves test validity with a red-then-green CI sequence. Commits a failing test first (CI red), then the minimal fix (CI green). Use when fixing a bug, writing a regression test, or when asked to prove a fix works.'
----
-
-# Red-Green Fix
-
-Fixes bugs as two commits so CI automatically proves the test catches the bug.
-
-## Why Two Commits
-
-If you commit the test and fix together, the test always passes — reviewers cannot tell whether the test actually detects the bug or is a no-op. Splitting into two commits creates a verifiable CI trail:
-
-1. **Commit 1 (test-only)** — adds a test that exercises the bug. CI runs it → test fails → red X.
-2. **Commit 2 (fix)** — adds the minimal fix. CI runs the same test → test passes → green check.
-
-The red-then-green sequence in the commit history proves the test is valid.
-
-## Input
-
-The user provides a bug description as an argument. If no description is given, ask the user to describe the bug before proceeding.
-
-Bug description: $ARGUMENTS
-
-## Step 0 — Setup
-
-Create an isolated branch from main:
-
-```bash
-git fetch origin main
-git checkout -b fix/<bug-name> origin/main
-```
-
-## Step 1 — Red: Failing Test Only
-
-Write a test that reproduces the bug. **Do NOT write any fix code.**
-
-### Choosing the Test Framework
-
-| Bug type                          | Framework  | File location                   |
-| --------------------------------- | ---------- | ------------------------------- |
-| Logic, utils, stores, composables | Vitest     | `src/**/*.test.ts` (colocated)  |
-| UI interaction, canvas, workflows | Playwright | `browser_tests/tests/*.spec.ts` |
-
-For Playwright tests, follow the `/writing-playwright-tests` skill for patterns, fixtures, and tags.
-
-### Rules
-
-- The test MUST fail against the current codebase (this is the whole point)
-- Do NOT modify any source code outside of test files
-- Do NOT include any fix, workaround, or behavioral change
-- Do NOT add unrelated tests or refactor existing tests
-- Keep the test minimal — only what is needed to reproduce the bug
-- Avoid common anti-patterns — see `reference/testing-anti-patterns.md`
-
-### Vitest Example
-
-```typescript
-// src/utils/pathUtil.test.ts
-import { describe, expect, it } from 'vitest'
-import { resolveModelPath } from './pathUtil'
-
-describe('resolveModelPath', () => {
-  it('handles absolute paths from folder_paths API', () => {
-    const result = resolveModelPath(
-      '/absolute/models',
-      '/absolute/models/checkpoints'
-    )
-    expect(result).toBe('/absolute/models/checkpoints')
-  })
-})
-```
-
-### Playwright Example
-
-```typescript
-import {
-  comfyPageFixture as test,
-  comfyExpect as expect
-} from '../fixtures/ComfyPage'
-
-test.describe('Model Download', { tag: ['@smoke'] }, () => {
-  test('downloads model when path is absolute', async ({ comfyPage }) => {
-    await comfyPage.workflow.loadWorkflow('missing-model')
-    const downloadBtn = comfyPage.page.getByTestId('download-model-button')
-    await downloadBtn.click()
-    await expect(comfyPage.page.getByText('Download complete')).toBeVisible()
-  })
-})
-```
-
-### Verify Locally First
-
-Run the test locally before pushing to confirm it fails for the right reason:
-
-```bash
-# Vitest
-pnpm test:unit <test-file>
-
-# Playwright
-pnpm test:browser:local -- --grep "<test name>"
-```
-
-If the test passes locally, it does not reproduce the bug — revisit your test before pushing.
-
-### Quality Checks and Commit
-
-```bash
-pnpm typecheck
-pnpm lint
-pnpm format:check
-
-git add <test-files-only>
-git commit -m "test: add failing test for <concise bug description>"
-git push -u origin HEAD
-```
-
-### Verify CI Failure
-
-```bash
-gh run list --branch $(git branch --show-current) --limit 1
-```
-
-**STOP HERE.** Inform the user of the CI status and wait for confirmation before proceeding to Step 2.
-
-- If CI passes: the test does not catch the bug. Revisit the test.
-- If CI fails for unrelated reasons: investigate and fix the test setup, not the bug.
-- If CI fails because the test correctly catches the bug: proceed to Step 2.
-
-## Step 2 — Green: Minimal Fix
-
-Write the minimum code change needed to make the failing test pass.
-
-### Rules
-
-- Do NOT modify, weaken, or delete the test from Step 1 — it is immutable. If the test needs changes, restart from Step 1 and re-prove the red.
-- Do NOT add new tests (tests were finalized in Step 1)
-- Do NOT refactor, clean up, or make "drive-by" improvements
-- Do NOT modify code unrelated to the bug
-- The fix should be the smallest correct change
-
-### Quality Checks and Commit
-
-```bash
-pnpm typecheck
-pnpm lint
-pnpm format
-
-git add <fix-files-only>
-git commit -m "fix: <concise bug description>"
-git push
-```
-
-### Verify CI Pass
-
-```bash
-gh run list --branch $(git branch --show-current) --limit 1
-```
-
-- If CI passes: the fix is verified. Proceed to PR creation.
-- If CI fails: investigate and fix. Do NOT change the test from Step 1.
-
-## Step 3 — Open Pull Request
-
-```bash
-gh pr create --title "fix: <description>" --body "$(cat <<'EOF'
-## Summary
-
-<Brief explanation of the bug and root cause>
-
-- Fixes #<issue-number>
-
-## Red-Green Verification
-
-| Commit | CI Status | Purpose |
-|--------|-----------|---------|
-| `test: ...` | :red_circle: Red | Proves the test catches the bug |
-| `fix: ...` | :green_circle: Green | Proves the fix resolves the bug |
-
-## Test Plan
-
-- [ ] CI red on test-only commit
-- [ ] CI green on fix commit
-- [ ] Added/updated E2E regression under `browser_tests/` or explained why not applicable
-- [ ] Manual verification (if applicable)
-EOF
-)"
-```
-
-## Gotchas
-
-### CI fails on test commit for unrelated reasons
-
-Lint, typecheck, or other tests may fail — not just your new test. Check the CI logs carefully. If the failure is unrelated, fix it in a separate commit before the `test:` commit so the red X is clearly attributable to your test.
-
-### Test passes when it should fail
-
-The bug may only manifest under specific conditions (e.g., Windows paths, external model directories, certain workflow structures). Make sure your test setup matches the actual bug scenario. Check that you're not accidentally testing the happy path.
-
-### Flaky Playwright tests
-
-If your e2e test is intermittent, it doesn't prove anything. Use retrying assertions (`toBeVisible`, `toHaveText`) instead of `waitForTimeout`. See the `/writing-playwright-tests` skill for anti-patterns.
-
-### Pre-existing CI failures on main
-
-If main itself is red, branch from the last green commit or fix the pre-existing failure first. A red-green proof is meaningless if the baseline is already red.
-
-## Reference
-
-| Resource              | Path                                              |
-| --------------------- | ------------------------------------------------- |
-| Unit test framework   | Vitest (`src/**/*.test.ts`)                       |
-| E2E test framework    | Playwright (`browser_tests/tests/*.spec.ts`)      |
-| E2E fixtures          | `browser_tests/fixtures/`                         |
-| E2E assets            | `browser_tests/assets/`                           |
-| Playwright skill      | `.Codex/skills/writing-playwright-tests/SKILL.md` |
-| Unit CI               | `.github/workflows/ci-tests-unit.yaml`            |
-| E2E CI                | `.github/workflows/ci-tests-e2e.yaml`             |
-| Lint CI               | `.github/workflows/ci-lint-format.yaml`           |
-| Testing anti-patterns | `reference/testing-anti-patterns.md`              |
-| Related skill         | `.Codex/skills/perf-fix-with-proof/SKILL.md`      |

.agents/skills/red-green-fix/reference/testing-anti-patterns.md

@@ -1,214 +0,0 @@
-# Testing Anti-Patterns for Red-Green Fixes
-
-Common mistakes that undermine the red-green proof. Avoid these when writing the test commit (Step 1).
-
-## Testing Implementation Details
-
-Test observable behavior, not internal state.
-
-**Bad** — coupling to internals:
-
-```typescript
-it('uses cache internally', () => {
-  const service = new UserService()
-  service.getUser(1)
-  expect(service._cache.has(1)).toBe(true) // Implementation detail
-})
-```
-
-**Good** — testing through the public interface:
-
-```typescript
-it('returns same user on repeated calls', async () => {
-  const service = new UserService()
-  const user1 = await service.getUser(1)
-  const user2 = await service.getUser(1)
-  expect(user1).toBe(user2) // Behavior, not implementation
-})
-```
-
-Why this matters for red-green: if your test is coupled to internals, a valid fix that changes the implementation may break the test — even though the bug is fixed. The green commit should only require changing source code, not rewriting the test.
-
-## Assertion-Free Tests
-
-Every test must assert something meaningful. A test without assertions always passes — it cannot produce the red X needed in Step 1.
-
-**Bad**:
-
-```typescript
-it('processes the download', () => {
-  processDownload('/models/checkpoints', 'model.safetensors')
-  // No expect()!
-})
-```
-
-**Good**:
-
-```typescript
-it('processes the download to correct path', () => {
-  const result = processDownload('/models/checkpoints', 'model.safetensors')
-  expect(result.savePath).toBe('/models/checkpoints/model.safetensors')
-})
-```
-
-## Over-Mocking
-
-Mock only system boundaries (network, filesystem, Electron APIs). If you mock the module under test, you are testing your mocks — the test will not detect the real bug.
-
-**Bad** — mocking everything:
-
-```typescript
-vi.mock('./pathResolver')
-vi.mock('./validator')
-vi.mock('./downloader')
-
-it('downloads model', () => {
-  // This only tests that mocks were called, not that the bug exists
-})
-```
-
-**Good** — mock only the boundary:
-
-```typescript
-vi.mock('./electronAPI') // Boundary: Electron IPC
-
-it('resolves absolute path correctly', () => {
-  const result = resolveModelPath('/root/models', '/root/models/checkpoints')
-  expect(result).toBe('/root/models/checkpoints')
-})
-```
-
-See also: [Don't Mock What You Don't Own](https://hynek.me/articles/what-to-mock-in-5-mins/)
-
-## Giant Tests
-
-A test that covers the entire flow makes it hard to pinpoint which part catches the bug. Keep it focused — one concept per test.
-
-**Bad**:
-
-```typescript
-it('full model download flow', async () => {
-  // 80 lines: load workflow, open dialog, select model,
-  // click download, verify path, check progress, confirm completion
-})
-```
-
-**Good**:
-
-```typescript
-it('resolves absolute savePath without nesting under modelsDirectory', () => {
-  const result = getLocalSavePath(
-    '/models',
-    '/models/checkpoints',
-    'file.safetensors'
-  )
-  expect(result).toBe('/models/checkpoints/file.safetensors')
-})
-```
-
-If the bug is in path resolution, test path resolution — not the entire download flow.
-
-## Test Duplication
-
-Duplicated test code hides what actually differs between cases. Use parameterized tests.
-
-**Bad**:
-
-```typescript
-it('resolves checkpoints path', () => {
-  expect(resolve('/models', '/models/checkpoints', 'a.safetensors')).toBe(
-    '/models/checkpoints/a.safetensors'
-  )
-})
-it('resolves loras path', () => {
-  expect(resolve('/models', '/models/loras', 'b.safetensors')).toBe(
-    '/models/loras/b.safetensors'
-  )
-})
-```
-
-**Good**:
-
-```typescript
-it.each([
-  ['/models/checkpoints', 'a.safetensors', '/models/checkpoints/a.safetensors'],
-  ['/models/loras', 'b.safetensors', '/models/loras/b.safetensors']
-])('resolves %s/%s to %s', (dir, file, expected) => {
-  expect(resolve('/models', dir, file)).toBe(expected)
-})
-```
-
-## Flaky Tests
-
-A flaky test cannot prove anything — it may show red for reasons unrelated to the bug, or green despite the bug still existing.
-
-**Common causes in this codebase:**
-
-| Cause                                  | Fix                                     |
-| -------------------------------------- | --------------------------------------- |
-| Missing `nextFrame()` after canvas ops | Add `await comfyPage.nextFrame()`       |
-| `waitForTimeout` instead of assertions | Use `toBeVisible()`, `toHaveText()`     |
-| Shared state between tests             | Isolate with `afterEach` / `beforeEach` |
-| Timing-dependent logic                 | Use `expect.poll()` or `toPass()`       |
-
-## Gaming the Red-Green Process
-
-These are ways the red-green proof gets invalidated during Step 2 (the fix commit). The test from Step 1 is immutable — if any of these happen, restart from Step 1.
-
-**Weakening the assertion to make it pass:**
-
-```typescript
-// Step 1 (red) — strict assertion
-expect(result).toBe('/external/drive/models/checkpoints/file.safetensors')
-
-// Step 2 (green) — weakened to pass without a real fix
-expect(result).toBeDefined() // This proves nothing
-```
-
-**Updating snapshots to bless the bug:**
-
-```bash
-# Instead of fixing the code, just updating the snapshot to match buggy output
-pnpm test:unit --update
-```
-
-If a snapshot needs updating, the fix should change the code behavior, not the expected output.
-
-**Adding mocks in Step 2 that hide the failure:**
-
-```typescript
-// Step 2 adds a mock that didn't exist in Step 1
-vi.mock('./pathResolver', () => ({
-  resolve: () => '/expected/path' // Hardcoded to pass
-}))
-```
-
-Step 2 should only change source code — not test infrastructure.
-
-## Testing the Happy Path Only
-
-The red-green pattern specifically requires the test to exercise the **broken path**. If you only test the case that already works, the test will pass (green) on Step 1 — defeating the purpose.
-
-**Bad** — testing the default case that works:
-
-```typescript
-it('downloads to default models directory', () => {
-  // This already works — it won't produce a red X
-  const result = resolve('/models', 'checkpoints', 'file.safetensors')
-  expect(result).toBe('/models/checkpoints/file.safetensors')
-})
-```
-
-**Good** — testing the case that is actually broken:
-
-```typescript
-it('downloads to external models directory configured via extra_model_paths', () => {
-  // This is the broken case — absolute path from folder_paths API
-  const result = resolve(
-    '/models',
-    '/external/drive/models/checkpoints',
-    'file.safetensors'
-  )
-  expect(result).toBe('/external/drive/models/checkpoints/file.safetensors')
-})
-```

.agents/skills/regenerating-screenshots/SKILL.md

@@ -1,83 +0,0 @@
----
-name: regenerating-screenshots
-description: 'Creates a PR to regenerate Playwright screenshot expectations. Use when screenshot tests are failing on main or PRs due to stale golden images. Triggers on: regen screenshots, regenerate screenshots, update expectations, fix screenshot tests.'
----
-
-# Regenerating Playwright Screenshot Expectations
-
-Automates the process of triggering the `PR: Update Playwright Expectations`
-GitHub Action by creating a labeled PR from `origin/main`.
-
-## Steps
-
-1. **Fetch latest main**
-
-   ```bash
-   git fetch origin main
-   ```
-
-2. **Create a timestamped branch** from `origin/main`
-
-   Format: `regen-screenshots/YYYY-MM-DDTHH` (hour resolution, local time)
-
-   ```bash
-   git checkout -b regen-screenshots/<datetime> origin/main
-   ```
-
-3. **Create an empty commit**
-
-   ```bash
-   git commit --allow-empty -m "test: regenerate screenshot expectations"
-   ```
-
-4. **Push the branch**
-
-   ```bash
-   git push origin regen-screenshots/<datetime>
-   ```
-
-5. **Generate a poem** about regenerating screenshots. Be creative — a
-   new, unique poem every time. Short (4–8 lines). Can be funny, wistful,
-   epic, haiku-style, limerick, sonnet fragment — vary the form.
-
-6. **Create the PR** with the poem as the body (no label yet).
-
-   Write the poem to a temp file and use `--body-file`:
-
-   ```bash
-   # Write poem to temp file
-   # Create PR:
-   gh pr create \
-     --base main \
-     --head regen-screenshots/<datetime> \
-     --title "test: regenerate screenshot expectations" \
-     --body-file <temp-file>
-   ```
-
-7. **Add the label** as a separate step to trigger the GitHub Action.
-
-   The `labeled` event only fires when a label is added after PR
-   creation, not when applied during creation via `--label`.
-
-   Use the GitHub API directly (`gh pr edit --add-label` fails due to
-   deprecated Projects Classic GraphQL errors):
-
-   ```bash
-   gh api repos/{owner}/{repo}/issues/<pr-number>/labels \
-     -f "labels[]=New Browser Test Expectations" --method POST
-   ```
-
-8. **Report the result** to the user:
-   - PR URL
-   - Branch name
-   - Note that the GitHub Action will run automatically and commit
-     updated screenshots to the branch.
-
-## Notes
-
-- The `New Browser Test Expectations` label triggers the
-  `pr-update-playwright-expectations.yaml` workflow.
-- The workflow runs Playwright with `--update-snapshots`, commits results
-  back to the PR branch, then removes the label.
-- This is fire-and-forget — no need to wait for or monitor the Action.
-- Always return to the original branch/worktree state after pushing.

.agents/skills/reviewing-unit-tests/SKILL.md

@@ -1,156 +0,0 @@
----
-name: reviewing-unit-tests
-description: Use when reviewing Vitest unit-test diffs in ComfyUI_frontend, especially new mocks, store tests, component tests, or bugfix regression tests.
----
-
-# Reviewing Unit Tests for ComfyUI_frontend
-
-## Overview
-
-Review for behavior and current repo rules, not motion. Compare to authoritative rules, not prior diffs or legacy snippets.
-
-## Review Workflow
-
-1. Identify the test type: component, store, composable, util, or bugfix regression.
-2. Name the behavior the test proves. If you cannot say it in one sentence, request changes.
-3. Open the authoritative doc section before judging structure.
-4. Scan the red flags below.
-5. State the verdict first. Name the failure mode. Cite the doc or rule.
-
-## Source of Truth / Precedence
-
-When docs and examples conflict, use this order:
-
-1. Explicit repo rules, lint rules, and note blocks.
-2. [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md)
-3. Rule sections in [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md), [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md), and [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)
-4. Example snippets
-5. Prior diffs
-
-Apply these repo-specific clarifications:
-
-- [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md) starts with the authoritative rule: new component tests use `@testing-library/vue` with `@testing-library/user-event`. The `@vue/test-utils` snippets below it are legacy examples.
-- [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md) still contains `as any` examples. Treat them as legacy snippets, not approval for new or edited test code.
-- If docs conflict, prefer the stricter newer rule and call out the doc ambiguity. Do not approve through it.
-- Motion != fix.
-
-## 30-Second Red Flags
-
-| If you see...                                                                             | Failure mode                    | Default action                                                |
-| ----------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------- |
-| New `@vue/test-utils` import in a new component test                                      | legacy test API                 | Request changes                                               |
-| `vi.mock('vue-i18n', ...)`                                                                | mocked i18n                     | Request changes                                               |
-| `as any`, `@ts-expect-error`, `as Mock`, `as ReturnType<typeof vi.fn>`, `as unknown as X` | unnecessary cast or type escape | Request changes unless the author proves no safer type exists |
-| `getXMock()`, renamed wrapper, or helper that only returns a mocked value                 | alias-by-renaming               | Request changes                                               |
-| `beforeEach` recreates the return object for a module-mocked composable or service        | shared mock setup drift         | Request changes                                               |
-| Assertions only check defaults, mock plumbing, or CSS hooks                               | non-behavioral test             | Request changes                                               |
-| Bugfix test has no proof it fails on pre-fix code                                         | unproven regression             | Request changes                                               |
-
-## Rationalization Table
-
-| Excuse                              | Reality                                                                                                |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| "I restructured the mocks"          | If the indirection stayed, nothing improved. Flag `alias-by-renaming`.                                 |
-| "The docs do it"                    | Rule, note, and lint beat legacy snippet. Compare to the current rule, not the nearest example.        |
-| "TypeScript required the cast"      | `vi.mocked()` usually narrows mock methods. Assertion-only references need no cast.                    |
-| "Putting it in `beforeEach` is DRY" | Recreating module mock state in hooks hides singleton behavior and drifts from the documented pattern. |
-| "It is only a nit"                  | Explicit repo-rule violations are never nits.                                                          |
-| "No behavior changed, just cleanup" | Motion != fix. Ask what behavior got stronger.                                                         |
-| "Mental revert is enough"           | For bugfix tests, establish red on pre-fix code or ask the author to show it.                          |
-
-## Mocking Rules
-
-- Fail helpers that do not remove repeated setup, encode domain meaning, or simplify assertions. Barely earning the abstraction is not enough.
-- For composables with reactive or singleton state, define stable mock state inside the `vi.mock()` factory. Access it per test via the composable itself. See [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md) "Mocking Composables with Reactive State".
-- This does not ban local test data builders or per-test `vi.spyOn(...)`.
-- Mock seams, not the project-owned module you are trying to exercise. For store tests, prefer real Pinia plus `createTestingPinia({ stubActions: false })` per [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) and [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md).
-
-### Alias-by-Renaming
-
-```ts
-// Before
-const mockAdd = vi.hoisted(() => vi.fn())
-
-// After: same indirection, new name
-function getToastAddMock() {
-  return useToast().add
-}
-```
-
-If the wrapper only renames or relays a mocked value, fail it. Inline the lookup at the call site or fetch the singleton mock via the documented pattern.
-
-### `vi.mocked()` Scope
-
-| Use case                                                        | `vi.mocked()` required? |
-| --------------------------------------------------------------- | ----------------------- |
-| `.mockReturnValue`, `.mockResolvedValue`, `.mockImplementation` | Yes                     |
-| `.mock.calls`, `.mock.results`                                  | Yes                     |
-| `expect(fn).toHaveBeenCalled()`                                 | No                      |
-| `expect(fn).toHaveBeenCalledWith(...)`                          | No                      |
-
-- Flag casts whenever `vi.mocked()` would narrow correctly.
-- Do not add `vi.mocked()` around assertion-only references just for style.
-
-### Reset Hygiene
-
-- Flag per-mock `mockClear()` or `mockReset()` when `vi.clearAllMocks()` or `vi.resetAllMocks()` already runs in the relevant hook chain.
-- Review for redundancy or broken state management. Do not bikeshed `clearAllMocks` vs `resetAllMocks` unless behavior depends on it.
-
-### Third-Party Seams
-
-- Distinguish trivial hooks from behavior-rich APIs.
-- Mocking single-method third-party hooks like `primevue/usetoast` is usually acceptable.
-- That exception does not justify mocking behavior-rich third-party modules.
-
-### `vue-i18n`
-
-- Never mock `vue-i18n` in component tests.
-- Use real `createI18n` per [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) and the shared [`testI18n`](../../../src/components/searchbox/v2/__test__/testUtils.ts) setup.
-
-## Test-Body Rules
-
-| Smell                                                             | Review bar                                                                                                                                    |
-| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| Change-detector test                                              | Reject. Default values alone prove nothing.                                                                                                   |
-| Mock-only assertion                                               | Accept collaborator-call assertions only when the call is the meaningful external effect and the test also exercises the triggering behavior. |
-| Non-behavioral assertion                                          | Reject tests that only check classes, utility hooks, or styling internals.                                                                    |
-| New component test using `@vue/test-utils`                        | Request changes. Use `@testing-library/vue` plus `@testing-library/user-event`.                                                               |
-| `any`, `as any`, or `@ts-expect-error` in new or edited test code | Request changes unless the author proves no safer type exists. Legacy doc snippets do not authorize it.                                       |
-
-## Bugfix Regression Proof
-
-For `fix:` PRs or bugfix diffs:
-
-1. Identify the production change that fixes the bug.
-2. Verify the new test fails on pre-fix code, or ask the author to show it.
-3. If the test passes on broken code, request changes.
-
-A regression test that never proves red does not pin the bug.
-
-## Review Output Rules
-
-- State verdict before procedural questions.
-- Do not lead with approval language like `LGTM, just one nit` or `approve and move on?`.
-- Name the failure mode directly: `alias-by-renaming`, `unnecessary cast`, `mocked i18n`, `mock-only assertion`, `unproven regression`.
-- Link the authoritative doc section in the review comment.
-- If an explicit repo rule, lint rule, or authoritative doc note is violated, do not downgrade it to "minor deviation" or "nit".
-
-## Quick Reference
-
-| When you see...                     | Read this                                                                                                                                                                                         |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| New `vi.mock(...)` for a composable | [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md) -> "Mocking Composables with Reactive State"                                                                              |
-| New store test or store mock        | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) setup + [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md)                                   |
-| New component test                  | Top note in [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)                                                                                                     |
-| `vue-i18n` in a component test      | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) + [`src/components/searchbox/v2/__test__/testUtils.ts`](../../../src/components/searchbox/v2/__test__/testUtils.ts) |
-| Cast around a mock                  | [`docs/guidance/typescript.md`](../../../docs/guidance/typescript.md) -> "Type Assertion Hierarchy"                                                                                               |
-
-## Key Files to Read
-
-| Purpose                              | Path                                                                                                              |
-| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
-| Composable mocking patterns          | [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md)                                           |
-| Store testing patterns               | [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md)                                         |
-| Repo-wide Vitest setup defaults      | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md)                                     |
-| Component testing rule for new tests | [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)                                 |
-| Real i18n setup                      | [`src/components/searchbox/v2/__test__/testUtils.ts`](../../../src/components/searchbox/v2/__test__/testUtils.ts) |

.agents/skills/writing-playwright-tests/SKILL.md

@@ -1,203 +0,0 @@
----
-name: writing-playwright-tests
-description: 'Writes Playwright e2e tests for ComfyUI_frontend. Use when creating, modifying, or debugging browser tests. Triggers on: playwright, e2e test, browser test, spec file.'
----
-
-# Writing Playwright Tests for ComfyUI_frontend
-
-## Golden Rules
-
-1. **ALWAYS look at existing tests first.** Search `browser_tests/tests/` for similar patterns before writing new tests.
-
-2. **ALWAYS read the fixture code.** The APIs are in `browser_tests/fixtures/` - read them directly instead of guessing.
-
-3. **Use premade JSON workflow assets** instead of building workflows programmatically.
-   - Assets live in `browser_tests/assets/`
-   - Load with `await comfyPage.workflow.loadWorkflow('feature/my_workflow')`
-   - Create new assets by starting with `browser_tests/assets/default.json` and manually editing the JSON to match your desired graph state
-
-## Vue Nodes vs LiteGraph: Decision Guide
-
-Choose based on **what you're testing**, not personal preference:
-
-| Testing...                                     | Use                              | Why                                      |
-| ---------------------------------------------- | -------------------------------- | ---------------------------------------- |
-| Vue-rendered node UI, DOM widgets, CSS states  | `comfyPage.vueNodes.*`           | Nodes are DOM elements, use locators     |
-| Canvas interactions, connections, legacy nodes | `comfyPage.nodeOps.*`            | Canvas-based, use coordinates/references |
-| Both in same test                              | Pick primary, minimize switching | Avoid confusion                          |
-
-**Vue Nodes requires explicit opt-in:**
-
-```typescript
-await comfyPage.settings.setSetting('Comfy.VueNodes.Enabled', true)
-await comfyPage.vueNodes.waitForNodes()
-```
-
-**Vue Node state uses CSS classes:**
-
-```typescript
-const BYPASS_CLASS = /before:bg-bypass\/60/
-await expect(node).toHaveClass(BYPASS_CLASS)
-```
-
-## Common Issues
-
-These are frequent causes of flaky tests - check them first, but investigate if they don't apply:
-
-| Symptom                             | Common Cause              | Typical Fix                                                                            |
-| ----------------------------------- | ------------------------- | -------------------------------------------------------------------------------------- |
-| Test passes locally, fails in CI    | Missing nextFrame()       | Add `await comfyPage.nextFrame()` after canvas ops (not needed after `loadWorkflow()`) |
-| Keyboard shortcuts don't work       | Missing focus             | Add `await comfyPage.canvas.click()` first                                             |
-| Double-click doesn't trigger        | Timing too fast           | Add `{ delay: 5 }` option                                                              |
-| Elements end up in wrong position   | Drag animation incomplete | Use `{ steps: 10 }` not `{ steps: 1 }`                                                 |
-| Widget value wrong after drag-drop  | Upload incomplete         | Add `{ waitForUpload: true }`                                                          |
-| Test fails when run with others     | Test pollution            | Add `afterEach` with `resetView()`                                                     |
-| Local screenshots don't match CI    | Platform differences      | Screenshots are Linux-only, use PR label                                               |
-| `subtree intercepts pointer events` | Canvas overlay (z-999)    | Use `dispatchEvent` on the DOM element to bypass overlay                               |
-| Context menu empty / wrong items    | Node not selected         | Select node first: `vueNodes.selectNode()` or `nodeRef.click('title')`                 |
-| `navigateIntoSubgraph` timeout      | Node too small in asset   | Use node size `[400, 200]` minimum in test asset JSON                                  |
-
-## Test Tags
-
-Add appropriate tags to every test:
-
-| Tag           | When to Use                               |
-| ------------- | ----------------------------------------- |
-| `@smoke`      | Quick essential tests                     |
-| `@slow`       | Tests > 10 seconds                        |
-| `@screenshot` | Visual regression tests                   |
-| `@canvas`     | Canvas interactions                       |
-| `@node`       | Node-related                              |
-| `@widget`     | Widget-related                            |
-| `@mobile`     | Mobile viewport (runs on Pixel 5 project) |
-| `@2x`         | HiDPI tests (runs on 2x scale project)    |
-
-```typescript
-test.describe('Feature', { tag: ['@screenshot', '@canvas'] }, () => {
-```
-
-## Retry Patterns
-
-**Never use `waitForTimeout`** - it's always wrong.
-
-| Pattern                  | Use Case                                             |
-| ------------------------ | ---------------------------------------------------- |
-| Auto-retrying assertions | `toBeVisible()`, `toHaveText()`, etc. (prefer these) |
-| `expect.poll()`          | Single value polling                                 |
-| `expect().toPass()`      | Multiple assertions that must all pass               |
-
-```typescript
-// Prefer auto-retrying assertions when possible
-await expect(node).toBeVisible()
-
-// Single value polling
-await expect.poll(() => widget.getValue(), { timeout: 2000 }).toBe(100)
-
-// Multiple conditions
-await expect(async () => {
-  expect(await node1.getValue()).toBe('foo')
-  expect(await node2.getValue()).toBe('bar')
-}).toPass({ timeout: 2000 })
-```
-
-## Screenshot Baselines
-
-- **Screenshots are Linux-only.** Don't commit local screenshots.
-- **To update baselines:** Add PR label `New Browser Test Expectations`
-- **Mask dynamic content:**
-  ```typescript
-  await expect(comfyPage.canvas).toHaveScreenshot('page.png', {
-    mask: [page.locator('.timestamp')]
-  })
-  ```
-
-## CI Debugging
-
-1. Download artifacts from failed CI run
-2. Extract and view trace: `pnpm dlx playwright show-trace trace.zip`
-3. CI deploys HTML report to Cloudflare Pages (link in PR comment)
-4. Reproduce CI: `CI=true pnpm test:browser`
-5. Local runs: `pnpm test:browser:local`
-
-## Anti-Patterns
-
-Avoid these common mistakes:
-
-1. **Arbitrary waits** - Use retrying assertions instead
-
-   ```typescript
-   // ❌ await page.waitForTimeout(500)
-   // ✅ await expect(element).toBeVisible()
-   ```
-
-2. **Implementation-tied selectors** - Use test IDs or semantic selectors
-
-   ```typescript
-   // ❌ page.locator('div.container > button.btn-primary')
-   // ✅ page.getByTestId('submit-button')
-   ```
-
-3. **Missing nextFrame after canvas ops** - Canvas needs sync time
-
-   ```typescript
-   await node.drag({ x: 50, y: 50 })
-   await comfyPage.nextFrame() // Required
-   ```
-
-4. **Shared state between tests** - Tests must be independent
-   ```typescript
-   // ❌ let sharedData  // Outside test
-   // ✅ Define state inside each test
-   ```
-
-## Quick Start Template
-
-```typescript
-// Path depends on test file location - adjust '../' segments accordingly
-import {
-  comfyPageFixture as test,
-  comfyExpect as expect
-} from '../fixtures/ComfyPage'
-
-test.describe('FeatureName', { tag: ['@canvas'] }, () => {
-  test.afterEach(async ({ comfyPage }) => {
-    await comfyPage.canvasOps.resetView()
-  })
-
-  test('should do something', async ({ comfyPage }) => {
-    await comfyPage.workflow.loadWorkflow('myWorkflow')
-
-    const node = (await comfyPage.nodeOps.getNodeRefsByTitle('KSampler'))[0]
-    // ... test logic
-
-    await expect(comfyPage.canvas).toHaveScreenshot('expected.png')
-  })
-})
-```
-
-## Finding Patterns
-
-```bash
-# Find similar tests
-grep -r "KSampler" browser_tests/tests/
-
-# Find usage of a fixture method
-grep -r "loadWorkflow" browser_tests/tests/
-
-# Find tests with specific tag
-grep -r '@screenshot' browser_tests/tests/
-```
-
-## Key Files to Read
-
-| Purpose           | Path                                       |
-| ----------------- | ------------------------------------------ |
-| Main fixture      | `browser_tests/fixtures/ComfyPage.ts`      |
-| Helper classes    | `browser_tests/fixtures/helpers/`          |
-| Component objects | `browser_tests/fixtures/components/`       |
-| Test selectors    | `browser_tests/fixtures/selectors.ts`      |
-| Vue Node helpers  | `browser_tests/fixtures/VueNodeHelpers.ts` |
-| Test assets       | `browser_tests/assets/`                    |
-| Existing tests    | `browser_tests/tests/`                     |
-
-**Read the fixture code directly** - it's the source of truth for available methods.

.agents/skills/writing-storybook-stories/SKILL.md

@@ -1,143 +0,0 @@
----
-name: writing-storybook-stories
-description: 'Write or update Storybook stories for Vue components in ComfyUI_frontend. Use when adding, modifying, reviewing, or debugging `.stories.ts` files, Storybook docs, component demos, or visual catalog entries in `src/` or `apps/desktop-ui/`.'
----
-
-# Write Storybook Stories for ComfyUI_frontend
-
-## Workflow
-
-1. !!!!IMPORTANT Confirm the worktree is on a `feat/*` or `fix/*` branch. Base PRs on the local `main`, not a fork branch.
-2. Read the component source first. Understand props, emits, slots, exposed methods, and any supporting types or composables.
-3. Read nearby stories before writing anything.
-   - Search stories: `rg --files src apps | rg '\.stories\.ts$'`
-   - Inspect title patterns: `rg -n "title:\\s*'" src apps --glob '*.stories.ts'`
-4. If a Figma link is provided, list the states you need to cover before writing stories.
-5. Co-locate the story file with the component: `ComponentName.stories.ts`.
-6. Add each variation on separate stories, except hover state. this should be automatically applied by the implementation and not require a separate story.
-7. Run Storybook and validation checks before handing off.
-
-## Match Local Conventions
-
-- Copy the closest neighboring story instead of forcing one universal template.
-- Most repo stories use `@storybook/vue3-vite`. Some stories under `apps/desktop-ui` still use `@storybook/vue3`; keep the local convention for that area.
-- Add `tags: ['autodocs']` unless the surrounding stories in that area intentionally omit it.
-- Use `ComponentPropsAndSlots<typeof Component>` when it helps with prop and slot typing.
-- Keep `render` functions stateful when needed. Use `ref()`, `computed()`, and `toRefs(args)` instead of mutating Storybook args directly.
-- Use `args.default` or other slot-shaped args when the component content is provided through slots.
-- Use `ComponentExposed` only when a component's exposed API breaks the normal Storybook typing.
-- Add decorators for realistic width or background context when the component needs it.
-
-## Title Patterns
-
-Do not invent titles from scratch when a close sibling story already exists. Match the nearest domain pattern.
-
-| Component area                                          | Typical title pattern                |
-| ------------------------------------------------------- | ------------------------------------ |
-| `src/components/ui/button/Button.vue`                   | `Components/Button/Button`           |
-| `src/components/ui/input/Input.vue`                     | `Components/Input`                   |
-| `src/components/ui/search-input/SearchInput.vue`        | `Components/Input/SearchInput`       |
-| `src/components/common/SearchBox.vue`                   | `Components/Input/SearchBox`         |
-| `src/renderer/extensions/vueNodes/widgets/components/*` | `Widgets/<WidgetName>`               |
-| `src/platform/assets/components/*`                      | `Platform/Assets/<ComponentName>`    |
-| `apps/desktop-ui/src/components/*`                      | `Desktop/Components/<ComponentName>` |
-| `apps/desktop-ui/src/views/*`                           | `Desktop/Views/<ViewName>`           |
-
-If multiple patterns seem plausible, follow the closest sibling story in the same folder tree.
-
-## Common Story Shapes
-
-### Stateful input or `v-model`
-
-```typescript
-export const Default: Story = {
-  render: (args) => ({
-    components: { MyComponent },
-    setup() {
-      const { disabled, size } = toRefs(args)
-      const value = ref('Hello world')
-      return { value, disabled, size }
-    },
-    template:
-      '<MyComponent v-model="value" :disabled="disabled" :size="size" />'
-  })
-}
-```
-
-### Slot-driven content
-
-```typescript
-const meta: Meta<ComponentPropsAndSlots<typeof Button>> = {
-  argTypes: {
-    default: { control: 'text' }
-  },
-  args: {
-    default: 'Button'
-  }
-}
-
-export const SingleButton: Story = {
-  render: (args) => ({
-    components: { Button },
-    setup() {
-      return { args }
-    },
-    template: '<Button v-bind="args">{{ args.default }}</Button>'
-  })
-}
-```
-
-### Variants or edge cases grid
-
-```typescript
-export const AllVariants: Story = {
-  render: () => ({
-    components: { MyComponent },
-    template: `
-      <div class="grid gap-4 sm:grid-cols-2">
-        <MyComponent />
-        <MyComponent disabled />
-        <MyComponent loading />
-        <MyComponent invalid />
-      </div>
-    `
-  })
-}
-```
-
-## Figma Mapping
-
-- Extract the named states from the design first.
-- Prefer explicit prop-driven stories such as `Disabled`, `Loading`, `Invalid`, `WithPlaceholder`, `AllSizes`, or `EdgeCases`.
-- Add an aggregate story such as `AllVariants`, `AllSizes`, or `EdgeCases` when side-by-side comparison is useful.
-- Use pseudo-state parameters only if the addon is already configured in this repo.
-- If a Figma state cannot be represented exactly, capture the closest prop-driven version and explain the gap in the story docs.
-
-## Component-Specific Notes
-
-- Widget components often need a minimal `SimplifiedWidget` object. Build it in `setup()` and use `computed()` when `args` change `widget.options`.
-- Input and search components often need a width-constrained wrapper so they render at realistic sizes.
-- Asset and platform cards often need background decorators such as `bg-base-background` and fixed-width containers.
-- Desktop installer stories may need custom `backgrounds` parameters and may intentionally keep the older Storybook import style used by neighboring files.
-- Use semantic tokens such as `bg-base-background` and `bg-node-component-surface` instead of `dark:` variants or hardcoded theme assumptions.
-
-## Checklist
-
-- [ ] Read the component source and any supporting types or composables
-- [ ] Match the nearest local title pattern and story style
-- [ ] Include a baseline story; name it `Default` only when that matches nearby conventions
-- [ ] Add focused stories for meaningful states
-- [ ] Add `tags: ['autodocs']`
-- [ ] Keep the story co-located with the component
-- [ ] Run `pnpm storybook`
-- [ ] Run `pnpm typecheck`
-- [ ] Run `pnpm lint`
-
-## Avoid
-
-- Do not guess props, emits, slots, or exposed methods.
-- Do not force one generic title convention across the repo.
-- Do not mutate Storybook args directly for `v-model` components.
-- Do not introduce `dark:` Tailwind variants in story wrappers.
-- Do not create barrel files.
-- Do not assume every story needs `layout: 'centered'` or a `Default` export; follow the nearest existing pattern.

.agents/skills/writing-storybook-stories/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: 'ComfyUI Storybook Stories'
-  short_description: 'Write Vue Storybook stories for ComfyUI'
-  default_prompt: 'Use $writing-storybook-stories to add or update a Storybook story for this ComfyUI_frontend component.'

.claude/settings.json

@@ -32,12 +32,12 @@
           {
             "type": "command",
             "if": "Bash(npx vitest *)",
-            "command": "echo 'Use `pnpm test:unit` (or `pnpm test:unit <path>`) instead of npx vitest.' >&2 && exit 2"
+            "command": "echo 'Use `pnpm test:unit` (or `pnpm test:unit -- <path>`) instead of npx vitest.' >&2 && exit 2"
           },
           {
             "type": "command",
             "if": "Bash(pnpx vitest *)",
-            "command": "echo 'Use `pnpm test:unit` (or `pnpm test:unit <path>`) instead of pnpx vitest.' >&2 && exit 2"
+            "command": "echo 'Use `pnpm test:unit` (or `pnpm test:unit -- <path>`) instead of pnpx vitest.' >&2 && exit 2"
           },
           {
             "type": "command",

.claude/skills/add-model-page/SKILL.md

@@ -1,173 +0,0 @@
----
-name: add-model-page
-description: 'add, update, or remove a model page entry on the comfy org website. creates a PR to Comfy-Org/ComfyUI_frontend apps/website folder with the change and posts a Vercel preview link back to Slack.'
----
-
-# add-model-page
-
-add, update, or remove model pages in the ComfyUI website.
-
-## Trigger phrases
-
-- `Add a model page for <model-name>`
-- `Update the model page for <model-name>`
-- `Remove <model-name> from model pages`
-
-## Phase 1 — Parse the request
-
-Extract:
-
-- **action**: `add` | `update` | `remove`
-- **model-name**: raw string (e.g. `flux1-schnell`, `flux1_dev.safetensors`)
-
-Normalize to a slug: lowercase, replace `_` and `.` with `-`, strip file extensions.
-Example: `flux1_dev.safetensors` → `flux1-dev`
-
-## Architecture overview
-
-Models come from two sources merged at build time:
-
-| File                                            | Purpose                                                                                                                           |
-| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `apps/website/src/config/generated-models.json` | Auto-generated from workflow_templates (slug, name, directory, huggingFaceUrl, workflowCount, displayName, thumbnailUrl, docsUrl) |
-| `apps/website/src/config/model-metadata.ts`     | Hand-curated overrides (docsUrl, blogUrl, featured) — only add entries that need overrides                                        |
-| `apps/website/src/config/models.ts`             | Merges the two above; exports typed `Model[]`                                                                                     |
-
-To regenerate the JSON from workflow_templates:
-
-```bash
-pnpm tsx apps/website/scripts/generate-models.ts
-```
-
-This writes `apps/website/src/config/generated-models.json` directly.
-Thumbnails are populated from local `.webp` files in `workflow_templates/templates/` — no network access needed.
-
----
-
-## Phase 2 — Gather model data (ADD / UPDATE)
-
-Run the generator to get fresh data, then find the model:
-
-```bash
-pnpm tsx apps/website/scripts/generate-models.ts
-jq '.[] | select(.slug | contains("MODEL_SLUG"))' \
-  apps/website/src/config/generated-models.json
-```
-
-The JSON fields are:
-
-- `slug` — URL slug
-- `name` — exact filename or display name for partner nodes
-- `huggingFaceUrl` — download URL (empty for partner nodes)
-- `directory` — `diffusion_models` | `loras` | … | `partner_nodes`
-- `workflowCount` — integer
-- `displayName` — human-readable name
-
-If no match and it is a known API/partner model, add it to `API_PROVIDER_MAP` in
-`generate-models.ts` and re-run. Otherwise tell the user.
-
----
-
-## Phase 3 — Check for existing entry
-
-```bash
-jq --arg slug "${SLUG}" '.[] | select(.slug == $slug)' \
-  apps/website/src/config/generated-models.json
-```
-
-- Match found + action is `add` → switch to UPDATE flow automatically
-- No match + action is `update` → stop and tell the user
-
----
-
-## Phase 4A — ADD: new partner/API model not in workflow_templates
-
-For partner nodes (no local file), add an entry to `API_PROVIDER_MAP` in
-`apps/website/scripts/generate-models.ts`:
-
-```typescript
-mymodel: { name: 'My Model', slug: 'my-model' },
-```
-
-Then re-run `pnpm tsx apps/website/scripts/generate-models.ts` — it will appear
-in `generated-models.json` automatically.
-
-If you also want a `docsUrl`, `blogUrl`, or a link to the hub model page, add an entry to `model-metadata.ts`:
-
-```typescript
-'my-model': {
-  docsUrl: 'https://docs.comfy.org/tutorials/...',
-  blogUrl: 'https://blog.comfy.org/...',
-  hubSlug: 'my-model',   // slug at comfy.org/workflows/model/{hubSlug} — only set if the page exists (returns 200)
-  featured: true
-}
-```
-
-No changes to `models.ts` or `translations.ts` are needed.
-
----
-
-## Phase 4B — UPDATE: edit existing entry
-
-Only `model-metadata.ts` needs editing for most updates (docsUrl, blogUrl,
-featured). For `displayName` or `directory` changes, edit the entry directly in
-`generated-models.json` (until the next generator run would overwrite it — then
-fix the source in `generate-models.ts`).
-
----
-
-## Phase 4C — REMOVE: delete entry
-
-Remove the entry from `generated-models.json` (or mark it with `canonicalSlug`
-pointing to the replacement). No translation file changes needed.
-
----
-
-## Phase 5 — Verify TypeScript
-
-```bash
-pnpm typecheck 2>&1 | grep -E "error|warning" | head -20
-```
-
-Fix any type errors before proceeding. Common issues:
-
-- `ModelDirectory` type not matching a new `directory` value — add it to the union
-- JSON import shape mismatch — `generated-models.json` must match `OutputModel`
-
----
-
-## Phase 6 — Create PR
-
-```bash
-BRANCH="add-model-page-MODEL-SLUG"   # or update- / remove-
-git checkout -b $BRANCH
-git add apps/website/src/config/generated-models.json \
-        apps/website/scripts/generate-models.ts \
-        apps/website/src/config/model-metadata.ts
-git commit -m "feat(models): add model page for MODEL-SLUG"
-git push -u origin $BRANCH
-gh pr create \
-  --title "Add model page: MODEL-SLUG" \
-  --body "$(cat <<'EOF'
-Adds a new model page entry for MODEL-SLUG.
-
-## Changes
-- `generated-models.json`: regenerated with new entry (workflowCount N, directory DIRECTORY)
-- `model-metadata.ts`: editorial overrides (docsUrl, featured) if needed
-EOF
-)"
-```
-
-For UPDATE use branch `update-model-page-MODEL-SLUG`.
-For REMOVE use `remove-model-page-MODEL-SLUG`.
-
----
-
-## Error states
-
-| Situation                       | Response                                                         |
-| ------------------------------- | ---------------------------------------------------------------- |
-| Model not in workflow templates | Ask user to verify spelling or add it manually as a partner node |
-| Slug already exists (add)       | Switch to update flow automatically                              |
-| Slug not found (update/remove)  | Stop and ask user to confirm                                     |
-| Typecheck fails                 | Fix the error before pushing                                     |

.claude/skills/backport-management/SKILL.md

@@ -9,18 +9,13 @@ Cherry-pick backport management for Comfy-Org/ComfyUI_frontend stable release br
 
 ## Quick Start
 
-1. **Discover** — Collect candidates from Slack bot + git log gap, then **reconcile both lists** (`reference/discovery.md`)
-2. **Pre-filter by path** — Auto-skip PRs whose changed files are entirely under `apps/website/`, `browser_tests/`, `.github/`, `packages/design-system/`, `packages/{cloud,registry}-types/`, `.claude/`, `docs/`. Don't read PR bodies for these — they don't ship to core ComfyUI users (`reference/analysis.md`)
-3. **Verify target file existence** — For each surviving candidate, run `git cat-file -e origin/$TARGET:$path` for primary changed files. If they don't exist on the target, auto-mark SKIP with reason `feature-not-on-branch`
-4. **Tiered triage** — Bucket into **Tier 1 (core editor must-haves)**, **Tier 2 (cloud-distribution only)**, **Tier 3 (skip)** before reviewing individually (`reference/analysis.md`)
-5. **Analyze** — Categorize remaining MUST/SHOULD, check deps (`reference/analysis.md`)
-6. **Human Review** — Present candidates in batches for interactive approval, with tier context attached (see Interactive Approval Flow)
-7. **Plan** — Order by dependency (leaf fixes first), group into waves per branch
-8. **Test-then-resolve dry-run** — Classify clean vs conflict before committing time (`reference/execution.md`)
-9. **Execute** — Label-driven automation for clean PRs → worktree fallback for conflicts (`reference/execution.md`)
-10. **Public-API conflict review** — If conflict resolution touches a public LiteGraph callback, extension API, or `node.*` method, consult oracle for compat-regression review BEFORE pushing (`reference/execution.md`)
-11. **Verify** — Per-PR validation (typecheck + targeted tests + lint on changed files) AND per-wave verification (full typecheck + test:unit on branch HEAD)
-12. **Log & Report** — Generate session report + author accountability report + Slack status update (`reference/logging.md`)
+1. **Discover** — Collect candidates from Slack bot + git log gap (`reference/discovery.md`)
+2. **Analyze** — Categorize MUST/SHOULD/SKIP, check deps (`reference/analysis.md`)
+3. **Human Review** — Present candidates in batches for interactive approval (see Interactive Approval Flow)
+4. **Plan** — Order by dependency (leaf fixes first), group into waves per branch
+5. **Execute** — Label-driven automation → worktree fallback for conflicts (`reference/execution.md`)
+6. **Verify** — After each wave, verify branch integrity before proceeding
+7. **Log & Report** — Generate session report (`reference/logging.md`)
 
 ## System Context
 
@@ -112,35 +107,6 @@ Husky hooks fail in worktrees (can't find lint-staged config). Always use `git p
 
 In the 2026-04-06 session: core/1.42 got 18/26 auto-PRs, cloud/1.42 got only 1/25. The cloud branch has more divergence. **Always plan for manual fallback** — don't assume automation will handle most PRs.
 
-### Cherry-Picked Tests Can Reference Files Added By Earlier Unbackported PRs
-
-A common conflict: PR A on main modifies a test file that was _added_ on main by an earlier PR B (not backported to the target). The cherry-pick of A reports "modify/delete" on B's test file because the file doesn't exist on the target. Adding the new file would smuggle in B's test scaffolding without B's runtime changes.
-
-**Detection:** Conflict says `deleted in HEAD and modified in <PR>`. Verify with:
-
-```bash
-git log --diff-filter=A --oneline origin/main -- path/to/test.ts
-```
-
-If the introducing commit is **not** on the target branch, the test file isn't a real prerequisite for the runtime fix.
-
-**Fix:** `git rm` the test file (drop it from the backport). Document in the commit body which PR introduced it on main and why dropping it is safe. The runtime fix itself usually doesn't depend on these tests — coverage exists at the integration layer.
-
-### Backport-Only Compatibility Shims
-
-When a PR's _mechanism_ relies on changes upstream that aren't on the older branch, a literal cherry-pick can recreate the original bug for any consumer still using the old contract. This is most dangerous for **public LiteGraph callbacks, extension APIs, and `node.*` methods** that custom-node packages depend on.
-
-**Real example (#11541, core/1.43 backport):** The PR removed `LGraphNode.vue`'s legacy `handled === true` sync-return check from `handleDrop`, replacing it with `await node.onDragDrop(event, true)`. Safe on `main` because all in-repo `onDragDrop` handlers had migrated to participate in the new `claimEvent` flag. On `core/1.43`, `onDragDrop` is a public callback — custom-node packages with synchronous `onDragDrop` returning `true` would no longer have their event claimed, recreating the duplicate-node-creation bug the PR was fixing.
-
-**Detection:** The PR's diff modifies a file that is part of a public extension API surface. Look for:
-
-- `node.onXxx` callback assignments
-- Methods on `LGraphNode`, `LGraphCanvas`, `LGraph`, `Subgraph`
-- Public exports from `src/lib/litegraph/`
-- Type changes affecting `litegraph-augmentation.d.ts`
-
-**Fix:** Add a backport-only compatibility shim that preserves the old contract while keeping the new fix. Document it explicitly in the commit body under a `## Backport-only compatibility fix` heading. Consult oracle for review before pushing — a bad shim is worse than no fix.
-
 ## Conflict Triage
 
 **Always categorize before deciding to skip. High conflict count ≠ hard conflicts.**
@@ -181,26 +147,6 @@ Skip these without discussion:
 - **Features not on target branch** — e.g., Painter, GLSLShader, appModeStore on core/1.40
 - **Cloud-only PRs on core/\* branches** — Team workspaces, cloud queue, cloud-only login. (Note: app mode and Firebase auth are NOT cloud-only — see Branch Scope Rules)
 
-### Path Pre-Filter (run BEFORE reading PR bodies)
-
-For 50+ candidate PRs, classify by changed paths first to skip the unproductive ones without spending time on triage. Run `git show --stat $SHA` (or `gh pr view --json files`) and bucket:
-
-| Path prefix                                    | Bucket                 | Reason                                           |
-| ---------------------------------------------- | ---------------------- | ------------------------------------------------ |
-| `apps/website/`                                | SKIP                   | Marketing/platform site, not core ComfyUI bundle |
-| `apps/desktop-ui/`                             | SKIP for `core/*`      | Desktop app, separate release cadence            |
-| `browser_tests/` only (no `src/`)              | SKIP                   | Test-only                                        |
-| `.github/workflows/` only                      | SKIP                   | CI/release infra                                 |
-| `packages/design-system/` only                 | SKIP                   | Design tokens, not core                          |
-| `packages/{cloud,registry,ingest}-types/` only | SKIP                   | Generated types                                  |
-| `.claude/`, `.agents/`, `docs/`                | SKIP                   | Agent / documentation                            |
-| `*.stories.ts` only                            | SKIP                   | Storybook only                                   |
-| `src/` (core editor)                           | KEEP — analyze further | Runtime/editor code that requires full triage    |
-
-A PR touches multiple paths? Keep it if **any** changed file is under `src/` (or other core paths) and run normal analysis. Auto-skip is conservative — only skip when _all_ paths match the SKIP buckets.
-
-This filter alone removes ~30-50% of candidates in a typical session, leaving only the PRs that need real triage.
-
 ## Wave Verification
 
 After merging each wave of PRs to a target branch, verify branch integrity before proceeding:

.claude/skills/backport-management/reference/analysis.md

@@ -39,89 +39,6 @@ Check before backporting — these don't exist on older branches:
 - **App builder** — check per branch
 - **appModeStore.ts** — not on core/1.40
 
-### Verify Target File Existence (Run Before Cherry-Pick)
-
-Before cherry-picking any PR, confirm the files it modifies actually exist on the target branch. If they don't, the PR's runtime fix is for a feature that hasn't been added yet — skip cleanly without attempting cherry-pick:
-
-```bash
-# For each file the PR changes
-for f in $(gh pr view $PR --json files --jq '.files[].path' | grep -v "^browser_tests/\|\.test\." ); do
-  if ! git cat-file -e origin/$TARGET:$f 2>/dev/null; then
-    echo "MISSING on $TARGET: $f"
-  fi
-done
-```
-
-If the _primary_ changed files (the runtime ones, not tests) are missing, mark the PR `SKIP / feature-not-on-branch`. This is faster than letting cherry-pick fail with modify/delete conflicts and gives a clean signal.
-
-This check is the first thing that runs after the path pre-filter and BEFORE you spend time reading PR descriptions.
-
-## Tiered Triage (Recommended for 30+ Candidates)
-
-Before the interactive Y/N approval flow, bucket all surviving candidates into three tiers. This surfaces release-engineering decisions that a flat MUST/SHOULD list obscures:
-
-### Tier 1 — Core Editor Must-Haves
-
-User-facing bugs, crashes, data corruption, or security issues in code paths that exist on the target branch. These are the strongest backport candidates.
-
-Indicators:
-
-- `fix:` prefix and the bug is reproducible on the target branch
-- Crash guards, runtime null checks, race-condition fixes
-- Data-loss bugs (state not persisted, duplicates, drops)
-- Security hardening (CSRF, XSS, auth)
-- Vue Nodes 2.0 regression cluster (if the target ships Vue Nodes 2.0)
-- Subgraph correctness fixes
-- Public-API extension callback fixes
-
-Recommend `Y` to user.
-
-### Tier 2 — Cloud-Distribution Only
-
-Bugs that only manifest on cloud-hosted distributions (Secrets panel, subscription flows, cloud signup, workspace tracking, etc.). Whether to backport depends on whether cloud ships from the target `core/*` branch in your release matrix.
-
-Indicators:
-
-- Files under `src/platform/secrets/`, `src/platform/subscription/`, signup flows
-- PR description mentions cloud staging issues
-- Fix gated behind cloud feature flags
-
-Default: ask the cloud release rotation owner. If unsure, defer.
-
-### Tier 3 — Skip
-
-Path pre-filter caught most of these. The rest are PRs where the diff _touches_ `src/` but the practical impact is non-user-facing or scoped to features the target doesn't ship.
-
-Indicators:
-
-- All changes in test files even if the PR touched `src/` test files
-- Storybook stories only
-- Lint config / lint rule additions
-- Documentation comments
-- Internal refactors with no behavior change
-
-### Presentation Format
-
-When showing tier results to the user, format as:
-
-```text
-Tier 1 (N PRs) — strong backport candidates
-- #11541 fix: stop duplicate node creation when dropping image on Vue nodes
-  Why: Vue Nodes 2.0 regression — async onDragDrop bypassed handled-check, drops bubble to document, spawns extra LoadImage nodes
-- #10849 fix: store promoted widget values per SubgraphNode instance
-  Why: Multiple instances overwriting each other's promoted widget values — data loss
-
-Tier 2 (N PRs) — cloud-distribution release rotation should decide
-- #11636 fix: enable Chrome password autofill on signup form
-- ...
-
-Tier 3 (N PRs) — skip recommended
-- #11586 fix: website polish (apps/website/ only)
-- ...
-```
-
-Then run interactive Y/N over Tier 1 and Tier 2; Tier 3 gets confirmed-skip without per-PR review.
-
 ## Dep Refresh PRs
 
 Always SKIP on stable branches. Risk of transitive dependency regressions outweighs audit cleanup benefit. If a specific CVE fix is needed, cherry-pick that individual fix instead.

.claude/skills/backport-management/reference/discovery.md

@@ -1,11 +1,5 @@
 # Discovery — Candidate Collection
 
-**Run all sources, then reconcile.** No single source is authoritative:
-
-- Slack bot may flag PRs that have already been backported (false positive)
-- Git gap may include PRs that don't need backport (test-only, design-system, website)
-- Bot can also miss PRs that landed without the right labels
-
 ## Source 1: Slack Backport-Checker Bot
 
 Use `slackdump` skill to export `#frontend-releases` channel (C09K9TPU2G7):
@@ -42,43 +36,7 @@ gh pr view $PR --json mergeCommit,title --jq '"Title: \(.title)\nMerge: \(.merge
 gh pr view $PR --json files --jq '.files[].path'
 ```
 
-## Source 4: Already-Backported PRs (cross-reference)
-
-When the target branch already has some cherry-picks on it (e.g., partway through a release window), extract the originals to avoid re-backporting:
-
-```bash
-# Get all original PR numbers already backported to TARGET since the last release tag
-git log --format="%H%n%B" $LAST_TAG..origin/$TARGET \
-  | grep -oiE "(backport of|cherry.picked) #?[0-9]+" \
-  | grep -oE "[0-9]+" \
-  | sort -un > /tmp/already-backported.txt
-```
-
-Subtract this list from your candidates.
-
-## Reconciliation Workflow
-
-```bash
-# 1. Slack bot list (parse from export)
-# /tmp/bot-flagged.txt — one PR# per line, sorted
-
-# 2. Git gap fix/perf only
-MB=$(git merge-base origin/main origin/$TARGET)
-git log --format="%h|%s" $MB..origin/main \
-  | grep -iE "^[a-f0-9]+\|(fix|perf)" \
-  | grep -oE "#[0-9]+\)" | grep -oE "[0-9]+" \
-  | sort -un > /tmp/gap-fixes.txt
-
-# 3. Already backported (Source 4 above)
-
-# 4. Candidates = (gap-fixes ∪ bot-flagged) − already-backported
-sort -u /tmp/gap-fixes.txt /tmp/bot-flagged.txt > /tmp/union.txt
-comm -23 /tmp/union.txt /tmp/already-backported.txt > /tmp/candidates.txt
-```
-
-The result is the input to the path pre-filter (`SKILL.md` Quick Start step 2).
-
 ## Output: candidate_list.md
 
 Table per target branch:
-| PR# | Title | Source (bot/gap/both) | Path bucket | Tier | Decision |
+| PR# | Title | Category | Flagged by Bot? | Decision |

.claude/skills/backport-management/reference/execution.md

@@ -6,43 +6,6 @@
 2. Medium gap next (quick win)
 3. Largest gap last (main effort)
 
-## Step 0: Test-Then-Resolve Pre-Pass (Recommended)
-
-Before triggering label-driven automation, run a dry-run cherry-pick loop to classify candidates. This is much faster than discovering conflicts after-the-fact across automation, manual cherry-picks, and CI failures.
-
-```bash
-git fetch origin TARGET_BRANCH
-git worktree add /tmp/dryrun-TARGET origin/TARGET_BRANCH
-cd /tmp/dryrun-TARGET
-
-CLEAN=()
-CONFLICT=()
-for pr in "${CANDIDATES[@]}"; do
-  SHA=$(gh pr view $pr --json mergeCommit --jq '.mergeCommit.oid')
-  git checkout -b dryrun-$pr origin/TARGET_BRANCH 2>/dev/null
-  if git cherry-pick -m 1 $SHA 2>/dev/null; then
-    CLEAN+=($pr)
-  else
-    CONFLICT+=($pr)
-    git cherry-pick --abort
-  fi
-  git checkout --detach HEAD 2>/dev/null
-  git branch -D dryrun-$pr 2>/dev/null
-done
-
-echo "CLEAN (${#CLEAN[@]}): ${CLEAN[*]}"
-echo "CONFLICT (${#CONFLICT[@]}): ${CONFLICT[*]}"
-
-cd -
-git worktree remove /tmp/dryrun-TARGET --force
-```
-
-Use the result to:
-
-- Send CLEAN PRs through label-driven automation (Step 1) — they'll typically self-merge
-- Reserve manual worktree time (Step 3) for CONFLICT PRs only
-- Surface PRs likely to need backport-only compat shims (CONFLICT files in `src/lib/litegraph/` or `src/scripts/app.ts`)
-
 ## Step 1: Label-Driven Automation (Batch)
 
 ```bash
@@ -125,39 +88,6 @@ for PR in ${CONFLICT_PRS[@]}; do
   git add .
   GIT_EDITOR=true git cherry-pick --continue
 
-  # ── Public-API conflict review (REQUIRED for extension-API surfaces) ──
-  # If the conflict resolution touched any of these surfaces, consult oracle
-  # BEFORE pushing. A bad shim is worse than no fix:
-  #   - node.onXxx callback assignments (onDragDrop, onConnectionsChange, onRemoved, onConfigure, etc.)
-  #   - Methods on LGraphNode, LGraphCanvas, LGraph, Subgraph
-  #   - Public exports from src/lib/litegraph/
-  #   - Type changes in litegraph-augmentation.d.ts
-  # If a public callback's signature/contract changed: add a backport-only
-  # compatibility shim that preserves the OLD contract while keeping the
-  # new fix. Document it in the commit body under
-  # "## Backport-only compatibility fix". See SKILL.md gotcha section.
-  # ───────────────────────────────────────────────────────────────────────
-
-  # Per-PR validation BEFORE push (catches issues earlier than wave verification).
-  # Guard each targeted command against empty file lists — running `pnpm test:unit`
-  # with no path filter would run the full suite, and `pnpm exec eslint` with no args errors.
-  pnpm typecheck
-
-  mapfile -t TEST_FILES < <(git diff --name-only HEAD~1 | grep -E '\.test\.ts$' || true)
-  if [ ${#TEST_FILES[@]} -gt 0 ]; then
-    pnpm test:unit "${TEST_FILES[@]}"
-  else
-    echo "No changed test files — skipping targeted unit tests"
-  fi
-
-  mapfile -t CODE_FILES < <(git diff --name-only HEAD~1 | grep -E '\.(ts|vue)$' || true)
-  if [ ${#CODE_FILES[@]} -gt 0 ]; then
-    pnpm exec eslint "${CODE_FILES[@]}"
-    pnpm exec oxfmt --check "${CODE_FILES[@]}"
-  else
-    echo "No changed ts/vue files — skipping targeted lint/format"
-  fi
-
   git push origin backport-$PR-to-TARGET --no-verify
   NEW_PR=$(gh pr create --base TARGET_BRANCH --head backport-$PR-to-TARGET \
     --title "[backport TARGET] TITLE (#$PR)" \
@@ -313,9 +243,6 @@ gh pr checks $PR --watch --fail-fast && gh pr merge $PR --squash --admin
 16. **Use `--no-verify` in worktrees** — husky hooks fail in `/tmp/` worktrees. Always push/commit with `--no-verify`.
 17. **Automation success varies by branch** — core/1.42 got 18/26 auto-PRs (69%), cloud/1.42 got 1/25 (4%). Cloud branches diverge more. Plan for manual fallback.
 18. **Test-then-resolve pattern** — for branches with low automation success, run a dry-run loop to classify clean vs conflict PRs before processing. This is much faster than resolving conflicts serially.
-19. **Public-API conflict resolutions need oracle review** — when a conflict touches `node.onXxx` callbacks, `LGraphNode`/`LGraphCanvas`/`LGraph`/`Subgraph` methods, or types in `litegraph-augmentation.d.ts`, consult oracle BEFORE pushing. Custom-node packages depend on these contracts. A literal cherry-pick of a refactor-style fix can silently break extensions still using the old contract — sometimes recreating the very bug the PR was fixing. Document any backport-only compatibility shim explicitly in the commit body.
-20. **Cherry-picked tests can require unbackported test scaffolding** — when a PR modifies a test file that was _added_ on main by an earlier unbackported PR, the cherry-pick reports modify/delete on that file. Drop it from the backport (`git rm`) and document which PR introduced it. Don't smuggle in test infrastructure without its runtime prerequisites.
-21. **Per-PR validation catches issues earlier than wave verification** — for high-stakes branches, run `pnpm typecheck && pnpm exec eslint <changed files> && pnpm exec oxfmt --check` per PR before pushing. Wave verification still matters (it catches cross-PR interactions), but per-PR makes attribution trivial when something fails.
 
 ## CI Failure Triage
 
@@ -341,40 +268,3 @@ Common failure categories:
 | Type error                  | Interface changed on main but not branch | May need manual adaptation                |
 
 **Never assume a failure is safe to skip.** Present all failures to the user with analysis.
-
-## PR Body Template (Manual Cherry-Picks)
-
-Manual cherry-pick PRs need detail beyond the automation's terse default. Use this template — reviewers will look here before re-deriving conflict-resolution logic from the diff.
-
-```markdown
-Manual backport of #ORIG to `TARGET` for inclusion in `vX.Y.Z`.
-
-Cherry-picked from upstream merge commit `SHORT_SHA`.
-
-## Why
-
-[1-2 sentences from the original PR's "Summary" — what bug, what fix mechanism]
-
-## Conflict resolution
-
-- **`path/to/file`** — [what conflicted on this branch] → [resolution chosen + why]
-- **`path/to/dropped-test.test.ts`** — added on main by unrelated PR #XXXX (not backported). Dropped from this backport; runtime fix intact.
-- [...]
-
-## Backport-only compatibility fix (if applicable)
-
-[If you added a shim that wasn't in the upstream PR, document it here — what extension surface, what contract, what the shim preserves, why the upstream version would have regressed it]
-
-## Validation
-
-- `pnpm typecheck` ✅
-- `pnpm test:unit <targeted suites>` ✅ (N/N passing)
-- `pnpm exec eslint <changed files>` ✅ (0 errors)
-- `pnpm exec oxfmt --check` ✅ (clean)
-
-[If manual e2e was skipped, explain why — e.g., requires live backend, headless not feasible. State that source is byte-identical to upstream + how long it's been baking on main.]
-
-Original PR: #ORIG / Original commit: `FULL_SHA`
-```
-
-The conflict-resolution section is non-negotiable — every conflict you resolved by hand needs a one-liner. This makes archaeology trivial six months later when someone asks "why does this look slightly different from main?"

.claude/skills/perf-fix-with-proof/SKILL.md

@@ -171,7 +171,7 @@ test('canvas text rendering with many nodes', async ({ comfyPage }) => {
 | ----------------- | ----------------------------------------------------- |
 | Perf test file    | `browser_tests/tests/performance.spec.ts`             |
 | PerformanceHelper | `browser_tests/fixtures/helpers/PerformanceHelper.ts` |
-| Perf reporter     | `browser_tests/fixtures/utils/perfReporter.ts`        |
+| Perf reporter     | `browser_tests/helpers/perfReporter.ts`               |
 | CI workflow       | `.github/workflows/ci-perf-report.yaml`               |
 | Report generator  | `scripts/perf-report.ts`                              |
 | Stats utilities   | `scripts/perf-stats.ts`                               |

.claude/skills/red-green-fix/SKILL.md

@@ -95,7 +95,7 @@ Run the test locally before pushing to confirm it fails for the right reason:
 
 ```bash
 # Vitest
-pnpm test:unit <test-file>
+pnpm test:unit -- <test-file>
 
 # Playwright
 pnpm test:browser:local -- --grep "<test name>"

.claude/skills/red-green-fix/reference/testing-anti-patterns.md

@@ -169,7 +169,7 @@ expect(result).toBeDefined() // This proves nothing
 
 ```bash
 # Instead of fixing the code, just updating the snapshot to match buggy output
-pnpm test:unit --update
+pnpm test:unit -- --update
 ```
 
 If a snapshot needs updating, the fix should change the code behavior, not the expected output.

.claude/skills/reviewing-unit-tests/SKILL.md

@@ -1,156 +0,0 @@
----
-name: reviewing-unit-tests
-description: Use when reviewing Vitest unit-test diffs in ComfyUI_frontend, especially new mocks, store tests, component tests, or bugfix regression tests.
----
-
-# Reviewing Unit Tests for ComfyUI_frontend
-
-## Overview
-
-Review for behavior and current repo rules, not motion. Compare to authoritative rules, not prior diffs or legacy snippets.
-
-## Review Workflow
-
-1. Identify the test type: component, store, composable, util, or bugfix regression.
-2. Name the behavior the test proves. If you cannot say it in one sentence, request changes.
-3. Open the authoritative doc section before judging structure.
-4. Scan the red flags below.
-5. State the verdict first. Name the failure mode. Cite the doc or rule.
-
-## Source of Truth / Precedence
-
-When docs and examples conflict, use this order:
-
-1. Explicit repo rules, lint rules, and note blocks.
-2. [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md)
-3. Rule sections in [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md), [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md), and [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)
-4. Example snippets
-5. Prior diffs
-
-Apply these repo-specific clarifications:
-
-- [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md) starts with the authoritative rule: new component tests use `@testing-library/vue` with `@testing-library/user-event`. The `@vue/test-utils` snippets below it are legacy examples.
-- [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md) still contains `as any` examples. Treat them as legacy snippets, not approval for new or edited test code.
-- If docs conflict, prefer the stricter newer rule and call out the doc ambiguity. Do not approve through it.
-- Motion != fix.
-
-## 30-Second Red Flags
-
-| If you see...                                                                             | Failure mode                    | Default action                                                |
-| ----------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------- |
-| New `@vue/test-utils` import in a new component test                                      | legacy test API                 | Request changes                                               |
-| `vi.mock('vue-i18n', ...)`                                                                | mocked i18n                     | Request changes                                               |
-| `as any`, `@ts-expect-error`, `as Mock`, `as ReturnType<typeof vi.fn>`, `as unknown as X` | unnecessary cast or type escape | Request changes unless the author proves no safer type exists |
-| `getXMock()`, renamed wrapper, or helper that only returns a mocked value                 | alias-by-renaming               | Request changes                                               |
-| `beforeEach` recreates the return object for a module-mocked composable or service        | shared mock setup drift         | Request changes                                               |
-| Assertions only check defaults, mock plumbing, or CSS hooks                               | non-behavioral test             | Request changes                                               |
-| Bugfix test has no proof it fails on pre-fix code                                         | unproven regression             | Request changes                                               |
-
-## Rationalization Table
-
-| Excuse                              | Reality                                                                                                |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| "I restructured the mocks"          | If the indirection stayed, nothing improved. Flag `alias-by-renaming`.                                 |
-| "The docs do it"                    | Rule, note, and lint beat legacy snippet. Compare to the current rule, not the nearest example.        |
-| "TypeScript required the cast"      | `vi.mocked()` usually narrows mock methods. Assertion-only references need no cast.                    |
-| "Putting it in `beforeEach` is DRY" | Recreating module mock state in hooks hides singleton behavior and drifts from the documented pattern. |
-| "It is only a nit"                  | Explicit repo-rule violations are never nits.                                                          |
-| "No behavior changed, just cleanup" | Motion != fix. Ask what behavior got stronger.                                                         |
-| "Mental revert is enough"           | For bugfix tests, establish red on pre-fix code or ask the author to show it.                          |
-
-## Mocking Rules
-
-- Fail helpers that do not remove repeated setup, encode domain meaning, or simplify assertions. Barely earning the abstraction is not enough.
-- For composables with reactive or singleton state, define stable mock state inside the `vi.mock()` factory. Access it per test via the composable itself. See [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md) "Mocking Composables with Reactive State".
-- This does not ban local test data builders or per-test `vi.spyOn(...)`.
-- Mock seams, not the project-owned module you are trying to exercise. For store tests, prefer real Pinia plus `createTestingPinia({ stubActions: false })` per [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) and [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md).
-
-### Alias-by-Renaming
-
-```ts
-// Before
-const mockAdd = vi.hoisted(() => vi.fn())
-
-// After: same indirection, new name
-function getToastAddMock() {
-  return useToast().add
-}
-```
-
-If the wrapper only renames or relays a mocked value, fail it. Inline the lookup at the call site or fetch the singleton mock via the documented pattern.
-
-### `vi.mocked()` Scope
-
-| Use case                                                        | `vi.mocked()` required? |
-| --------------------------------------------------------------- | ----------------------- |
-| `.mockReturnValue`, `.mockResolvedValue`, `.mockImplementation` | Yes                     |
-| `.mock.calls`, `.mock.results`                                  | Yes                     |
-| `expect(fn).toHaveBeenCalled()`                                 | No                      |
-| `expect(fn).toHaveBeenCalledWith(...)`                          | No                      |
-
-- Flag casts whenever `vi.mocked()` would narrow correctly.
-- Do not add `vi.mocked()` around assertion-only references just for style.
-
-### Reset Hygiene
-
-- Flag per-mock `mockClear()` or `mockReset()` when `vi.clearAllMocks()` or `vi.resetAllMocks()` already runs in the relevant hook chain.
-- Review for redundancy or broken state management. Do not bikeshed `clearAllMocks` vs `resetAllMocks` unless behavior depends on it.
-
-### Third-Party Seams
-
-- Distinguish trivial hooks from behavior-rich APIs.
-- Mocking single-method third-party hooks like `primevue/usetoast` is usually acceptable.
-- That exception does not justify mocking behavior-rich third-party modules.
-
-### `vue-i18n`
-
-- Never mock `vue-i18n` in component tests.
-- Use real `createI18n` per [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) and the shared [`testI18n`](../../../src/components/searchbox/v2/__test__/testUtils.ts) setup.
-
-## Test-Body Rules
-
-| Smell                                                             | Review bar                                                                                                                                    |
-| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| Change-detector test                                              | Reject. Default values alone prove nothing.                                                                                                   |
-| Mock-only assertion                                               | Accept collaborator-call assertions only when the call is the meaningful external effect and the test also exercises the triggering behavior. |
-| Non-behavioral assertion                                          | Reject tests that only check classes, utility hooks, or styling internals.                                                                    |
-| New component test using `@vue/test-utils`                        | Request changes. Use `@testing-library/vue` plus `@testing-library/user-event`.                                                               |
-| `any`, `as any`, or `@ts-expect-error` in new or edited test code | Request changes unless the author proves no safer type exists. Legacy doc snippets do not authorize it.                                       |
-
-## Bugfix Regression Proof
-
-For `fix:` PRs or bugfix diffs:
-
-1. Identify the production change that fixes the bug.
-2. Verify the new test fails on pre-fix code, or ask the author to show it.
-3. If the test passes on broken code, request changes.
-
-A regression test that never proves red does not pin the bug.
-
-## Review Output Rules
-
-- State verdict before procedural questions.
-- Do not lead with approval language like `LGTM, just one nit` or `approve and move on?`.
-- Name the failure mode directly: `alias-by-renaming`, `unnecessary cast`, `mocked i18n`, `mock-only assertion`, `unproven regression`.
-- Link the authoritative doc section in the review comment.
-- If an explicit repo rule, lint rule, or authoritative doc note is violated, do not downgrade it to "minor deviation" or "nit".
-
-## Quick Reference
-
-| When you see...                     | Read this                                                                                                                                                                                         |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| New `vi.mock(...)` for a composable | [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md) -> "Mocking Composables with Reactive State"                                                                              |
-| New store test or store mock        | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) setup + [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md)                                   |
-| New component test                  | Top note in [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)                                                                                                     |
-| `vue-i18n` in a component test      | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md) + [`src/components/searchbox/v2/__test__/testUtils.ts`](../../../src/components/searchbox/v2/__test__/testUtils.ts) |
-| Cast around a mock                  | [`docs/guidance/typescript.md`](../../../docs/guidance/typescript.md) -> "Type Assertion Hierarchy"                                                                                               |
-
-## Key Files to Read
-
-| Purpose                              | Path                                                                                                              |
-| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
-| Composable mocking patterns          | [`docs/testing/unit-testing.md`](../../../docs/testing/unit-testing.md)                                           |
-| Store testing patterns               | [`docs/testing/store-testing.md`](../../../docs/testing/store-testing.md)                                         |
-| Repo-wide Vitest setup defaults      | [`docs/testing/vitest-patterns.md`](../../../docs/testing/vitest-patterns.md)                                     |
-| Component testing rule for new tests | [`docs/testing/component-testing.md`](../../../docs/testing/component-testing.md)                                 |
-| Real i18n setup                      | [`src/components/searchbox/v2/__test__/testUtils.ts`](../../../src/components/searchbox/v2/__test__/testUtils.ts) |

.claude/skills/writing-playwright-tests/SKILL.md

@@ -114,7 +114,7 @@ await expect(async () => {
 ## CI Debugging
 
 1. Download artifacts from failed CI run
-2. Extract and view trace: `pnpm dlx playwright show-trace trace.zip`
+2. Extract and view trace: `npx playwright show-trace trace.zip`
 3. CI deploys HTML report to Cloudflare Pages (link in PR comment)
 4. Reproduce CI: `CI=true pnpm test:browser`
 5. Local runs: `pnpm test:browser:local`

.coderabbit.yaml

@@ -2,7 +2,6 @@ issue_enrichment:
   auto_enrich:
     enabled: true
 reviews:
-  profile: assertive
   high_level_summary: false
   request_changes_workflow: true
   auto_review:
@@ -16,35 +15,19 @@ reviews:
       - github-actions[bot]
   pre_merge_checks:
     override_requested_reviewers_only: true
-    # Explicitly disable the built-in docstring coverage check, which is
-    # enabled via organization-level settings. This repo opts out at the
-    # repo level without affecting other org repos.
-    docstrings:
-      mode: 'off'
     custom_checks:
       - name: End-to-end regression coverage for fixes
         mode: error
         instructions: |
-          Use only PR metadata already available in the review context:
-            - the PR title
-            - commit subjects in this PR
-            - The files changed in this PR relative to the PR base (equivalent to `base...head`)
-            - the PR description.
-          Do not rely on shell commands.
-          Do not inspect reverse diffs, files changed only on the base branch, or files outside this PR.
-          If the changed-file list or commit subjects are unavailable, mark the check inconclusive instead of guessing.
+          Use only PR metadata already available in the review context: the PR title, commit subjects in this PR, the files changed in this PR relative to the PR base (equivalent to `base...head`), and the PR description.
+          Do not rely on shell commands. Do not inspect reverse diffs, files changed only on the base branch, or files outside this PR. If the changed-file list or commit subjects are unavailable, mark the check inconclusive instead of guessing.
 
-          Fail if all of the following are true:
-          1. The PR title and/or any commit subject in the PR uses bug-fix language such as `fix`, `fixed`, `fixes`, `fixing`, `bugfix`, or `hotfix`.
-          2. The PR changes files under `src/` or `packages/` related to the main frontend application but the PR does not change at least one file under `browser_tests/`.
-          3. The PR description lacks a concrete explanation of why an end-to-end regression test was not added.
-
-          Do not fail if the changes are exclusively in `apps/website`, just documentation changes, or changes related to CI processes.
-          The goal is to make sure that fixes include End-to-End regression tests. Do not insist on tests when the PR is not fixing a bug.
-
-          Pass otherwise.
-          When failing, mention which bug-fix signal you found and ask the author to either add or update a Playwright regression test under `browser_tests/` or add a concrete explanation in the PR description of why an end-to-end regression test is not practical.
+          Pass if at least one of the following is true:
+          1. Neither the PR title nor any commit subject in the PR uses bug-fix language such as `fix`, `fixed`, `fixes`, `fixing`, `bugfix`, or `hotfix`.
+          2. The PR changes at least one file under `browser_tests/`.
+          3. The PR description includes a concrete, non-placeholder explanation of why an end-to-end regression test was not added.
 
+          Fail otherwise. When failing, mention which bug-fix signal you found and ask the author to either add or update a Playwright regression test under `browser_tests/` or add a concrete explanation in the PR description of why an end-to-end regression test is not practical.
       - name: ADR compliance for entity/litegraph changes
         mode: warning
         instructions: |

.cursor/rules/agent-panel-layout.md

@@ -1,30 +0,0 @@
----
-description: Agent chat panel layout rule — always full viewport height, never nested under the header bar
-globs:
-  - src/components/LiteGraphCanvasSplitterOverlay.vue
-  - src/platform/agent/**
-alwaysApply: true
----
-
-# Agent Panel Layout
-
-The Comfy Agent chat panel must always span the **full viewport height** — from the very top of the screen to the bottom, alongside the header bar and canvas, not below them.
-
-## Correct structure
-
-`LiteGraphCanvasSplitterOverlay` uses a top-level **`flex-row`** so the agent panel is a sibling of the entire left column (tabs + canvas), not a child inside it:
-
-```
-div.flex-row (viewport)
-├── div.flex-col.flex-1          ← left side: everything else
-│   ├── slot#workflow-tabs       ← header bar
-│   └── div.flex-1               ← canvas + sidebar panels
-└── div.shrink-0 (agent panel)   ← RIGHT: full viewport height
-```
-
-## Rules
-
-- **Never** place the agent panel inside the `div` that sits below `slot#workflow-tabs`. That causes the panel to start below the header bar.
-- The agent panel div must be a **direct child** of the outermost `div.flex-row` container in `LiteGraphCanvasSplitterOverlay.vue`.
-- The left side (`flex-1 flex-col`) wraps both `slot#workflow-tabs` AND the canvas/splitter row.
-- The agent panel has `h-full` and `shrink-0` so it fills the full height and does not flex-shrink.

.cursor/rules/icon-button-tooltip.mdc

@@ -1,34 +0,0 @@
----
-description: Icon buttons must always have a tooltip
-globs: src/**/*.vue
-alwaysApply: false
----
-
-# Icon Button Tooltip Requirement
-
-Every icon-only button (`size="icon"` or any button containing only an icon with no visible label) **must** be wrapped in a `Tooltip` so users can discover what it does.
-
-## Required Pattern
-
-```vue
-<Tooltip>
-  <TooltipTrigger>
-    <Button size="icon" border-interface-stroke" :aria-label="$t('...')">
-      <i class="icon-[lucide--some-icon] size-4" />
-    </Button>
-  </TooltipTrigger>
-  <TooltipContent side="top">{{ $t('...') }}</TooltipContent>
-</Tooltip>
-```
-
-## Imports
-
-```ts
-import Tooltip from '@/components/ui/tooltip/Tooltip.vue'
-import TooltipContent from '@/components/ui/tooltip/TooltipContent.vue'
-import TooltipTrigger from '@/components/ui/tooltip/TooltipTrigger.vue'
-```
-
-- Always use `side="top"` unless a different direction is needed for layout reasons.
-- The `aria-label` on the button and the tooltip text should be the same translated string.
-- Use `vue-i18n` (`$t(...)`) for the label — never hardcode strings.

.env_example

@@ -41,18 +41,8 @@ ALGOLIA_API_KEY=684d998c36b67a9a9fce8fc2d8860579
 # Enable PostHog debug logging in the browser console.
 # VITE_POSTHOG_DEBUG=true
 
-# Override staging comfy-api / comfy-platform base URLs.
-# VITE_STAGING_API_BASE_URL=https://stagingapi.comfy.org
-# VITE_STAGING_PLATFORM_BASE_URL=https://stagingplatform.comfy.org
-
 # Sentry ENV vars replace with real ones for debugging
 # SENTRY_AUTH_TOKEN=private-token # get from sentry
 # SENTRY_ORG=comfy-org
 # SENTRY_PROJECT=cloud-frontend-staging
 # SENTRY_PROJECT_PROD= # prod project slug for sourcemap uploads
-
-# Ashby (apps/website careers page build).
-# Server-only; read inside the Astro build context. Do NOT prefix with PUBLIC_.
-# When unset, the committed snapshot at apps/website/src/data/ashby-roles.snapshot.json is used.
-# WEBSITE_ASHBY_API_KEY=
-# WEBSITE_ASHBY_JOB_BOARD_NAME=comfy-org

.github/actions/ashby-pull/action.yaml

@@ -1,23 +0,0 @@
-name: Ashby Pull
-description: 'Refresh the apps/website Ashby roles snapshot from the Ashby job board API'
-inputs:
-  api_key:
-    description: 'Ashby API key (WEBSITE_ASHBY_API_KEY).'
-    required: true
-  job_board_name:
-    description: 'Ashby job board name (WEBSITE_ASHBY_JOB_BOARD_NAME).'
-    required: true
-runs:
-  using: 'composite'
-  steps:
-    # Note: this action assumes the frontend repo is checked out at the workspace root.
-
-    - name: Setup frontend
-      uses: ./.github/actions/setup-frontend
-
-    - name: Refresh Ashby snapshot
-      shell: bash
-      env:
-        WEBSITE_ASHBY_API_KEY: ${{ inputs.api_key }}
-        WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ inputs.job_board_name }}
-      run: pnpm --filter @comfyorg/website ashby:refresh-snapshot

.github/actions/changes-filter/action.yaml

@@ -1,87 +0,0 @@
-# Outputs default to 'true' for non-pull_request events (push, merge_group):
-# granular path filtering is a PR-only optimization. This avoids the silent
-# skip footgun where a job gated on e.g. `app-website-changes == 'true'`
-# would never run on push.
-#
-# Shared dependency files (root package.json, pnpm-lock.yaml,
-# pnpm-workspace.yaml) are folded into every app-* and packages-changes
-# output so a lockfile bump correctly invalidates each granular gate. They
-# are NOT folded into docs-changes.
-#
-# Two paths-filter steps are needed because predicate-quantifier=every is
-# required for the negated globs in `should-run` but breaks multi-pattern
-# OR filters like `docs:` and `deps:`.
-#
-# Requires the caller to have checked out the repository.
-
-name: 'Detect Path Changes'
-description: >
-  Computes typed *-changes outputs and a back-compat should-run for
-  path-gated CI jobs.
-
-outputs:
-  should-run:
-    description: 'Any file outside `apps/`, `docs/`, `.storybook/`, or `**/*.md` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.relevant.outputs.relevant == 'true' }}
-  app-website-changes:
-    description: 'Shared deps or `apps/website/**` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' || steps.filter.outputs.app_website == 'true' }}
-  app-desktop-changes:
-    description: 'Shared deps or `apps/desktop-ui/**` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' || steps.filter.outputs.app_desktop == 'true' }}
-  app-frontend-changes:
-    description: 'Shared deps or `src/**` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' || steps.filter.outputs.app_frontend == 'true' }}
-  packages-changes:
-    description: 'Shared deps or `packages/**` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' || steps.filter.outputs.packages == 'true' }}
-  storybook-changes:
-    description: 'Shared deps or `.storybook/**` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' || steps.filter.outputs.storybook == 'true' }}
-  docs-changes:
-    description: '`docs/**` or any `**/*.md` changed (deps NOT folded in).'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.docs == 'true' }}
-  dependency-changes:
-    description: 'Root `package.json`, `pnpm-lock.yaml`, or `pnpm-workspace.yaml` changed.'
-    value: ${{ github.event_name != 'pull_request' || steps.filter.outputs.deps == 'true' }}
-
-runs:
-  using: composite
-  steps:
-    - name: Filter typed changes
-      if: ${{ github.event_name == 'pull_request' }}
-      id: filter
-      uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # v3.0.2
-      with:
-        filters: |
-          app_website:
-            - 'apps/website/**'
-          app_desktop:
-            - 'apps/desktop-ui/**'
-          app_frontend:
-            - 'src/**'
-          packages:
-            - 'packages/**'
-          storybook:
-            - '.storybook/**'
-          docs:
-            - 'docs/**'
-            - '**/*.md'
-          deps:
-            - 'package.json'
-            - 'pnpm-lock.yaml'
-            - 'pnpm-workspace.yaml'
-
-    - name: Filter relevant changes
-      if: ${{ github.event_name == 'pull_request' }}
-      id: relevant
-      uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # v3.0.2
-      with:
-        predicate-quantifier: 'every'
-        filters: |
-          relevant:
-            - '**'
-            - '!apps/**'
-            - '!docs/**'
-            - '!.storybook/**'
-            - '!**/*.md'

.github/actions/cloud-nodes-pull/action.yaml

@@ -1,19 +0,0 @@
-name: Cloud Nodes Pull
-description: 'Refresh the apps/website cloud nodes snapshot from the Comfy Cloud /api/object_info endpoint'
-inputs:
-  api_key:
-    description: 'Comfy Cloud API key (WEBSITE_CLOUD_API_KEY).'
-    required: true
-runs:
-  using: 'composite'
-  steps:
-    # Note: this action assumes the frontend repo is checked out at the workspace root.
-
-    - name: Setup frontend
-      uses: ./.github/actions/setup-frontend
-
-    - name: Refresh cloud nodes snapshot
-      shell: bash
-      env:
-        WEBSITE_CLOUD_API_KEY: ${{ inputs.api_key }}
-      run: pnpm --filter @comfyorg/website cloud-nodes:refresh-snapshot

.github/actions/resolve-pr-from-workflow-run/action.yaml

@@ -1,88 +0,0 @@
-name: Resolve PR from workflow_run
-description: >
-  Resolves the PR number from a workflow_run event using pull_requests[0]
-  with a listPullRequestsAssociatedWithCommit fallback.
-  Skips closed/merged PRs and stale runs (head SHA mismatch).
-
-inputs:
-  token:
-    description: GitHub token for API calls
-    required: false
-    default: ${{ github.token }}
-
-outputs:
-  skip:
-    description: "'true' when no open PR was found or the run is stale"
-    value: ${{ steps.resolve.outputs.skip }}
-  number:
-    description: The PR number (empty when skip is true)
-    value: ${{ steps.resolve.outputs.number }}
-  base:
-    description: The PR base branch (empty when skip is true)
-    value: ${{ steps.resolve.outputs.base }}
-  head-sha:
-    description: The PR head SHA (empty when skip is true)
-    value: ${{ steps.resolve.outputs.head-sha }}
-
-runs:
-  using: composite
-  steps:
-    - name: Resolve PR
-      id: resolve
-      uses: actions/github-script@v8
-      with:
-        github-token: ${{ inputs.token }}
-        script: |
-          let pr = context.payload.workflow_run.pull_requests?.[0];
-          if (!pr) {
-            const { data: prs } = await github.rest.repos.listPullRequestsAssociatedWithCommit({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              commit_sha: context.payload.workflow_run.head_sha,
-            });
-            pr = prs.find(p => p.state === 'open');
-          }
-
-          // Fork PRs: pull_requests is empty and commit SHA may not be in
-          // the base repo graph. Fall back to pulls.list with head filter.
-          if (!pr && context.payload.workflow_run.head_repository?.owner?.login) {
-            const { data: prs } = await github.rest.pulls.list({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              state: 'open',
-              head: `${context.payload.workflow_run.head_repository.owner.login}:${context.payload.workflow_run.head_branch}`,
-              per_page: 1,
-            });
-            pr = prs.find(p => p.head.sha === context.payload.workflow_run.head_sha);
-          }
-
-          if (!pr) {
-            core.info('No open PR found for this workflow run — skipping.');
-            core.setOutput('skip', 'true');
-            return;
-          }
-
-          const { data: livePr } = await github.rest.pulls.get({
-            owner: context.repo.owner,
-            repo: context.repo.repo,
-            pull_number: pr.number,
-          });
-
-          if (livePr.state !== 'open') {
-            core.info(`PR #${pr.number} is ${livePr.state} — skipping.`);
-            core.setOutput('skip', 'true');
-            return;
-          }
-
-          if (livePr.head.sha !== context.payload.workflow_run.head_sha) {
-            core.info(
-              `Stale run: workflow SHA ${context.payload.workflow_run.head_sha} != PR head ${livePr.head.sha}`
-            );
-            core.setOutput('skip', 'true');
-            return;
-          }
-
-          core.setOutput('base', livePr.base.ref);
-          core.setOutput('head-sha', livePr.head.sha);
-          core.setOutput('skip', 'false');
-          core.setOutput('number', String(pr.number));

.github/actions/setup-frontend/action.yaml

@@ -29,5 +29,3 @@ runs:
       if: ${{ inputs.include_build_step == 'true' }}
       shell: bash
       run: pnpm build
-      env:
-        VITE_USE_LEGACY_DEFAULT_GRAPH: 'true'

.github/actions/upsert-comment-section/action.yaml

@@ -1,84 +0,0 @@
-name: Upsert Comment Section
-description: >
-  Manage a consolidated PR comment with independently-updatable sections.
-  Multiple CI workflows can share the same comment by using the same
-  comment-marker and different section-names. Each workflow upserts only
-  its own section, leaving other sections intact.
-
-inputs:
-  pr-number:
-    description: PR number to comment on
-    required: true
-  section-name:
-    description: 'Section identifier (e.g. "playwright", "storybook", "e2e", "preview")'
-    required: true
-  section-content:
-    description: Markdown content for this section
-    required: true
-  comment-marker:
-    description: Top-level HTML comment marker shared by all sections in this comment
-    required: true
-  token:
-    description: GitHub token with pull-requests write permission
-    required: true
-
-runs:
-  using: composite
-  steps:
-    - uses: actions/github-script@v8
-      env:
-        INPUT_PR_NUMBER: ${{ inputs.pr-number }}
-        INPUT_SECTION_NAME: ${{ inputs.section-name }}
-        INPUT_SECTION_CONTENT: ${{ inputs.section-content }}
-        INPUT_COMMENT_MARKER: ${{ inputs.comment-marker }}
-      with:
-        github-token: ${{ inputs.token }}
-        script: |
-          const prNumber = Number(process.env.INPUT_PR_NUMBER)
-          const sectionName = process.env.INPUT_SECTION_NAME
-          const sectionContent = process.env.INPUT_SECTION_CONTENT
-          const commentMarker = process.env.INPUT_COMMENT_MARKER
-
-          if (!/^[a-z0-9-]+$/.test(sectionName)) {
-            throw new Error(`Invalid section-name: ${sectionName}`)
-          }
-
-          const sectionStart = `<!-- section:${sectionName}:start -->`
-          const sectionEnd = `<!-- section:${sectionName}:end -->`
-          const sectionBlock = `${sectionStart}\n${sectionContent}\n${sectionEnd}`
-
-          // Escape special regex characters in delimiter strings
-          const escapeRegex = (s) => s.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')
-
-          const comments = await github.paginate(
-            github.rest.issues.listComments,
-            { ...context.repo, issue_number: prNumber }
-          )
-
-          const existing = comments.find(
-            (c) =>
-              c.user?.login === 'github-actions[bot]' &&
-              c.body?.includes(commentMarker)
-          )
-
-          if (!existing) {
-            return github.rest.issues.createComment({
-              ...context.repo,
-              issue_number: prNumber,
-              body: `${commentMarker}\n${sectionBlock}`
-            })
-          }
-
-          const body = existing.body ?? ''
-          const sectionRegex = new RegExp(
-            `${escapeRegex(sectionStart)}[\\s\\S]*?${escapeRegex(sectionEnd)}`
-          )
-          const updated = sectionRegex.test(body)
-            ? body.replace(sectionRegex, sectionBlock)
-            : body.trimEnd() + '\n\n' + sectionBlock
-
-          return github.rest.issues.updateComment({
-            ...context.repo,
-            comment_id: existing.id,
-            body: updated
-          })

.github/workflows/ci-dist-telemetry-scan.yaml

@@ -12,30 +12,17 @@ permissions:
   contents: read
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   scan:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Install pnpm
         uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
 
       - name: Use Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
         with:
           node-version-file: '.nvmrc'
           cache: 'pnpm'
@@ -109,48 +96,3 @@ jobs:
             exit 1
           fi
           echo '✅ No PostHog references found'
-
-      - name: Scan dist for Customer.io telemetry references
-        run: |
-          set -euo pipefail
-          echo '🔍 Scanning for Customer.io references...'
-          if rg --no-ignore -n \
-            -g '*.html' \
-            -g '*.js' \
-            -e 'CustomerIoTelemetryProvider' \
-            -e '@customerio/cdp-analytics-browser' \
-            -e 'customerio-gist-web' \
-            -e '(?i)cdp\.customer\.io' \
-            -e 'Comfy\.CustomerIo' \
-            dist; then
-            echo '❌ ERROR: Customer.io references found in dist assets!'
-            echo 'Customer.io must be properly tree-shaken from OSS builds.'
-            echo ''
-            echo 'To fix this:'
-            echo '1. Use the TelemetryProvider pattern (see src/platform/telemetry/)'
-            echo '2. Call telemetry via useTelemetry() hook'
-            echo '3. Use conditional dynamic imports behind isCloud checks'
-            exit 1
-          fi
-          echo '✅ No Customer.io references found'
-
-      - name: Scan dist for Cloudflare Turnstile sitekey references
-        run: |
-          set -euo pipefail
-          echo '🔍 Scanning for Cloudflare Turnstile sitekeys...'
-          if rg --no-ignore -n \
-            -g '*.html' \
-            -g '*.js' \
-            -e '0x4AAAAAADnYZPVOpFCL_zeo' \
-            -e '0x4AAAAAADnYY4_Q0qxHZ5a7' \
-            -e '1x00000000000000000000AA' \
-            dist; then
-            echo '❌ ERROR: Cloudflare Turnstile sitekey found in dist assets!'
-            echo 'The per-env Turnstile sitekeys are cloud-only and must be tree-shaken from OSS builds.'
-            echo ''
-            echo 'To fix this:'
-            echo '1. Gate sitekey selection on the __DISTRIBUTION__ build define, not the runtime isCloud const'
-            echo '2. See getTurnstileSiteKey() in src/config/turnstile.ts'
-            exit 1
-          fi
-          echo '✅ No Turnstile sitekey references found'

.github/workflows/ci-oss-assets-validation.yaml

@@ -14,29 +14,16 @@ permissions:
   contents: read
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   validate-fonts:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Install pnpm
         uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
 
       - name: Use Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
         with:
           node-version-file: '.nvmrc'
           cache: 'pnpm'
@@ -81,17 +68,15 @@ jobs:
           echo '✅ No proprietary fonts found in dist'
 
   validate-licenses:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Install pnpm
         uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
 
       - name: Use Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
         with:
           node-version-file: '.nvmrc'
           cache: 'pnpm'

.github/workflows/ci-perf-report.yaml

@@ -3,8 +3,10 @@ name: 'CI: Performance Report'
 on:
   push:
     branches: [main, core/*]
+    paths-ignore: ['**/*.md']
   pull_request:
     branches-ignore: [wip/*, draft/*, temp/*]
+    paths-ignore: ['**/*.md']
 
 concurrency:
   group: perf-${{ github.ref }}
@@ -14,24 +16,12 @@ permissions:
   contents: read
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   perf-tests:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' && github.repository == 'Comfy-Org/ComfyUI_frontend' }}
+    if: github.repository == 'Comfy-Org/ComfyUI_frontend'
     runs-on: ubuntu-latest
     timeout-minutes: 30
     container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.17
+      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.12
       credentials:
         username: ${{ github.actor }}
         password: ${{ secrets.GITHUB_TOKEN }}
@@ -54,14 +44,10 @@ jobs:
       - name: Start ComfyUI server
         uses: ./.github/actions/start-comfyui-server
 
-      # PRs run each test once to keep wall time bounded; main runs 3× so the
-      # baseline saved to perf-data has enough samples to median over noise.
       - name: Run performance tests
         id: perf
         continue-on-error: true
-        env:
-          PERF_REPEAT: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' && '3' || '2' }}
-        run: pnpm exec playwright test --project=performance --workers=1 --repeat-each=$PERF_REPEAT
+        run: pnpm exec playwright test --project=performance --workers=1 --repeat-each=3
 
       - name: Upload perf metrics
         if: always()
@@ -72,6 +58,21 @@ jobs:
           retention-days: 30
           if-no-files-found: warn
 
+      - name: Save PR metadata
+        if: github.event_name == 'pull_request'
+        run: |
+          mkdir -p temp/perf-meta
+          echo "${{ github.event.number }}" > temp/perf-meta/number.txt
+          echo "${{ github.event.pull_request.base.ref }}" > temp/perf-meta/base.txt
+          echo "${{ github.event.pull_request.head.sha }}" > temp/perf-meta/head-sha.txt
+
+      - name: Upload PR metadata
+        if: github.event_name == 'pull_request'
+        uses: actions/upload-artifact@v6
+        with:
+          name: perf-meta
+          path: temp/perf-meta/
+
       - name: Save perf baseline to perf-data branch
         if: github.event_name == 'push' && github.ref == 'refs/heads/main' && steps.perf.outcome == 'success'
         continue-on-error: true

.github/workflows/ci-size-data.yaml

@@ -16,21 +16,8 @@ permissions:
   contents: read
 
 jobs:
-  changes:
-    if: github.repository == 'Comfy-Org/ComfyUI_frontend'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   collect:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
+    if: github.repository == 'Comfy-Org/ComfyUI_frontend'
     runs-on: ubuntu-latest
 
     steps:
@@ -45,6 +32,13 @@ jobs:
       - name: Collect size data
         run: node scripts/size-collect.js
 
+      - name: Save PR metadata
+        if: ${{ github.event_name == 'pull_request' }}
+        run: |
+          echo ${{ github.event.number }} > ./temp/size/number.txt
+          echo ${{ github.base_ref }} > ./temp/size/base.txt
+          echo ${{ github.event.pull_request.head.sha }} > ./temp/size/head-sha.txt
+
       - name: Upload size data
         uses: actions/upload-artifact@v6
         with:

.github/workflows/ci-tests-e2e-coverage.yaml

@@ -20,8 +20,6 @@ jobs:
       github.event.workflow_run.conclusion == 'success'
     runs-on: ubuntu-latest
     timeout-minutes: 10
-    outputs:
-      has-coverage: ${{ steps.coverage-shards.outputs.has-coverage }}
 
     steps:
       - name: Checkout repository
@@ -39,33 +37,31 @@ jobs:
           path: temp/coverage-shards
           if_no_artifact_found: warn
 
-      - name: Detect shard coverage data
-        id: coverage-shards
-        run: |
-          if [ -d temp/coverage-shards ] && find temp/coverage-shards -name 'coverage.lcov' -type f | grep -q .; then
-            echo "has-coverage=true" >> "$GITHUB_OUTPUT"
-          else
-            echo "has-coverage=false" >> "$GITHUB_OUTPUT"
-            echo "No E2E coverage shard artifacts found; treating this run as skipped." >> "$GITHUB_STEP_SUMMARY"
-          fi
-
       - name: Install lcov
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
         run: sudo apt-get install -y -qq lcov
 
       - name: Merge shard coverage into single LCOV
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
         run: |
           mkdir -p coverage/playwright
           LCOV_FILES=$(find temp/coverage-shards -name 'coverage.lcov' -type f)
+          if [ -z "$LCOV_FILES" ]; then
+            echo "No coverage.lcov files found"
+            touch coverage/playwright/coverage.lcov
+            exit 0
+          fi
           ADD_ARGS=""
           for f in $LCOV_FILES; do ADD_ARGS="$ADD_ARGS -a $f"; done
           lcov $ADD_ARGS -o coverage/playwright/coverage.lcov
           wc -l coverage/playwright/coverage.lcov
 
       - name: Validate merged coverage
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
         run: |
+          SHARD_COUNT=$(find temp/coverage-shards -name 'coverage.lcov' -type f | wc -l | tr -d ' ')
+          if [ "$SHARD_COUNT" -eq 0 ]; then
+            echo "::error::No shard coverage.lcov files found under temp/coverage-shards"
+            exit 1
+          fi
+
           MERGED_SF=$(grep -c '^SF:' coverage/playwright/coverage.lcov || echo 0)
           MERGED_LH=$(awk -F: '/^LH:/{s+=$2}END{print s+0}' coverage/playwright/coverage.lcov)
           MERGED_LF=$(awk -F: '/^LF:/{s+=$2}END{print s+0}' coverage/playwright/coverage.lcov)
@@ -85,18 +81,8 @@ jobs:
             fi
           done
 
-      - name: Strip non-source entries from coverage
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
-        run: |
-          lcov --remove coverage/playwright/coverage.lcov \
-            '*localhost-8188*' \
-            'assets/images/*' \
-            -o coverage/playwright/coverage.lcov \
-            --ignore-errors unused
-          wc -l coverage/playwright/coverage.lcov
-
       - name: Upload merged coverage data
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
+        if: always()
         uses: actions/upload-artifact@v6
         with:
           name: e2e-coverage
@@ -105,58 +91,10 @@ jobs:
           if-no-files-found: warn
 
       - name: Upload E2E coverage to Codecov
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
+        if: always()
         uses: codecov/codecov-action@1af58845a975a7985b0beb0cbe6fbbb71a41dbad # v5.5.3
         with:
           files: coverage/playwright/coverage.lcov
           flags: e2e
           token: ${{ secrets.CODECOV_TOKEN }}
           fail_ci_if_error: false
-
-      - name: Generate HTML coverage report
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
-        run: |
-          genhtml coverage/playwright/coverage.lcov \
-            -o coverage/html \
-            --title "ComfyUI E2E Coverage" \
-            --no-function-coverage \
-            --precision 1 \
-            --ignore-errors source,unmapped,range \
-            --synthesize-missing
-
-      - name: Upload HTML report artifact
-        if: steps.coverage-shards.outputs.has-coverage == 'true'
-        uses: actions/upload-artifact@v6
-        with:
-          name: e2e-coverage-html
-          path: coverage/html/
-          retention-days: 30
-
-  deploy:
-    needs: merge
-    if: >
-      github.event.workflow_run.head_branch == 'main' &&
-      needs.merge.outputs.has-coverage == 'true' &&
-      github.event.workflow_run.event == 'push'
-    runs-on: ubuntu-latest
-    permissions:
-      pages: write
-      id-token: write
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    steps:
-      - name: Download HTML report
-        uses: actions/download-artifact@v7
-        with:
-          name: e2e-coverage-html
-          path: coverage/html
-
-      - name: Upload to GitHub Pages
-        uses: actions/upload-pages-artifact@56afc609e74202658d3ffba0e8f6dda462b719fa # v3.0.1
-        with:
-          path: coverage/html
-
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e # v4.0.5

.github/workflows/ci-tests-e2e-forks.yaml

@@ -6,10 +6,6 @@ on:
     workflows: ['CI: Tests E2E']
     types: [requested, completed]
 
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.workflow_run.head_repository.full_name }}-${{ github.event.workflow_run.head_branch }}
-  cancel-in-progress: true
-
 jobs:
   deploy-and-comment-forked-pr:
     runs-on: ubuntu-latest
@@ -34,39 +30,54 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v6
 
-      - name: Resolve PR from workflow_run context
+      - name: Get PR Number
         id: pr
-        uses: ./.github/actions/resolve-pr-from-workflow-run
-
-      - name: Handle Test Start — upsert playwright starting section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'requested'
-        uses: ./.github/actions/upsert-comment-section
+        uses: actions/github-script@v8
         with:
-          pr-number: ${{ steps.pr.outputs.number }}
-          section-name: playwright
-          section-content: '## 🎭 Playwright: ⏳ Running...'
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
+          script: |
+            const { data: prs } = await github.rest.pulls.list({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+            });
+
+            const pr = prs.find(p => p.head.sha === context.payload.workflow_run.head_sha);
+
+            if (!pr) {
+              console.log('No PR found for SHA:', context.payload.workflow_run.head_sha);
+              return null;
+            }
+
+            console.log(`Found PR #${pr.number} from fork: ${context.payload.workflow_run.head_repository.full_name}`);
+            return pr.number;
+
+      - name: Handle Test Start
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'requested'
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: |
+          chmod +x scripts/cicd/pr-playwright-deploy-and-comment.sh
+          ./scripts/cicd/pr-playwright-deploy-and-comment.sh \
+            "${{ steps.pr.outputs.result }}" \
+            "${{ github.event.workflow_run.head_branch }}" \
+            "starting"
 
       - name: Download and Deploy Reports
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed'
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'completed'
+        uses: actions/download-artifact@v7
         with:
-          run_id: ${{ github.event.workflow_run.id }}
-          name: playwright-report-.*
-          name_is_regexp: true
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          run-id: ${{ github.event.workflow_run.id }}
+          pattern: playwright-report-*
           path: reports
-          if_no_artifact_found: warn
 
-      - name: Handle Test Completion — deploy and generate section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && hashFiles('reports/**') != ''
+      - name: Handle Test Completion
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'completed'
         env:
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           GITHUB_TOKEN: ${{ github.token }}
           GITHUB_SHA: ${{ github.event.workflow_run.head_sha }}
-          SUMMARY_FILE: playwright-section.md
-          BRANCH_NAME: ${{ github.event.workflow_run.head_branch }}
         run: |
           # Rename merged report if exists
           [ -d "reports/playwright-report-chromium-merged" ] && \
@@ -74,23 +85,6 @@ jobs:
 
           chmod +x scripts/cicd/pr-playwright-deploy-and-comment.sh
           ./scripts/cicd/pr-playwright-deploy-and-comment.sh \
-            "${{ steps.pr.outputs.number }}" \
-            "$BRANCH_NAME" \
+            "${{ steps.pr.outputs.result }}" \
+            "${{ github.event.workflow_run.head_branch }}" \
             "completed"
-
-      - name: Read playwright section
-        id: section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && hashFiles('playwright-section.md') != ''
-        uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-        with:
-          path: playwright-section.md
-
-      - name: Upsert playwright section into unified report
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && steps.section.outputs.content != ''
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ steps.pr.outputs.number }}
-          section-name: playwright
-          section-content: ${{ steps.section.outputs.content }}
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}

.github/workflows/ci-tests-e2e.yaml

@@ -4,8 +4,10 @@ name: 'CI: Tests E2E'
 on:
   push:
     branches: [main, master, core/*, desktop/*]
+    paths-ignore: ['**/*.md']
   pull_request:
     branches-ignore: [wip/*, draft/*, temp/*]
+    paths-ignore: ['**/*.md']
   merge_group:
   workflow_dispatch:
 
@@ -14,20 +16,7 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   setup:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
     runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
@@ -45,10 +34,12 @@ jobs:
           path: dist/
           retention-days: 1
 
+      # Build cloud distribution for @cloud tagged tests
+      # NX_SKIP_NX_CACHE=true is required because `nx build` was already run
+      # for the OSS distribution above. Without skipping cache, Nx returns
+      # the cached OSS build since env vars aren't part of the cache key.
       - name: Build cloud frontend
-        run: pnpm build:cloud
-        env:
-          VITE_USE_LEGACY_DEFAULT_GRAPH: 'true'
+        run: NX_SKIP_NX_CACHE=true pnpm build:cloud
 
       - name: Upload cloud frontend
         uses: actions/upload-artifact@v6
@@ -63,7 +54,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 60
     container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.17
+      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.16
       credentials:
         username: ${{ github.actor }}
         password: ${{ secrets.GITHUB_TOKEN }}
@@ -121,7 +112,7 @@ jobs:
     needs: setup
     runs-on: ubuntu-latest
     container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.17
+      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.16
       credentials:
         username: ${{ github.actor }}
         password: ${{ secrets.GITHUB_TOKEN }}
@@ -173,9 +164,9 @@ jobs:
 
   # Merge sharded test reports (no container needed - only runs CLI)
   merge-reports:
-    needs: [changes, playwright-tests-chromium-sharded]
+    needs: [playwright-tests-chromium-sharded]
     runs-on: ubuntu-latest
-    if: ${{ !cancelled() && needs.changes.outputs.should-run == 'true' }}
+    if: ${{ !cancelled() }}
     steps:
       - name: Install pnpm
         uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
@@ -204,64 +195,35 @@ jobs:
           path: ./playwright-report/
           retention-days: 30
 
-  # Gate job — single required check that passes whether the matrix ran or was
-  # skipped. Branch rulesets require this instead of the individual matrix-
-  # expanded check names so PRs with no e2e-relevant changes aren't stuck.
-  e2e-status:
-    if: ${{ always() }}
-    needs: [changes, playwright-tests-chromium-sharded, playwright-tests]
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check E2E results
-        env:
-          SHOULD_RUN: ${{ needs.changes.outputs.should-run }}
-          SHARDED: ${{ needs.playwright-tests-chromium-sharded.result }}
-          BROWSERS: ${{ needs.playwright-tests.result }}
-        run: |
-          [[ "$SHOULD_RUN" != "true" ]] && echo "E2E skipped" && exit 0
-          [[ "$SHARDED" != "success" || "$BROWSERS" != "success" ]] && echo "E2E failed" && exit 1
-          echo "E2E passed"
-
   #### BEGIN Deployment and commenting (non-forked PRs only)
   # when using pull_request event, we have permission to comment directly
   # if its a forked repo, we need to use workflow_run event in a separate workflow (pr-playwright-deploy.yaml)
 
-  # Post starting section into the unified PR report comment for non-forked PRs
+  # Post starting comment for non-forked PRs
   comment-on-pr-start:
-    needs: changes
     runs-on: ubuntu-latest
-    if: >-
-      ${{
-        needs.changes.outputs.should-run == 'true' &&
-        github.event_name == 'pull_request' &&
-        github.event.pull_request.head.repo.fork == false
-      }}
+    if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false
     permissions:
       pull-requests: write
     steps:
       - name: Checkout repository
         uses: actions/checkout@v6
 
-      - name: Upsert playwright starting section into unified report
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: playwright
-          section-content: '## 🎭 Playwright: ⏳ Running...'
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
+      - name: Post starting comment
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: |
+          chmod +x scripts/cicd/pr-playwright-deploy-and-comment.sh
+          ./scripts/cicd/pr-playwright-deploy-and-comment.sh \
+            "${{ github.event.pull_request.number }}" \
+            "${{ github.head_ref }}" \
+            "starting"
 
-  # Deploy and upsert final playwright section for non-forked PRs only
+  # Deploy and comment for non-forked PRs only
   deploy-and-comment:
-    needs: [changes, playwright-tests, merge-reports]
+    needs: [playwright-tests, merge-reports]
     runs-on: ubuntu-latest
-    if: >-
-      ${{
-        always() &&
-        needs.changes.outputs.should-run == 'true' &&
-        github.event_name == 'pull_request' &&
-        github.event.pull_request.head.repo.fork == false
-      }}
+    if: always() && github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false
     permissions:
       pull-requests: write
       contents: read
@@ -275,34 +237,15 @@ jobs:
           pattern: playwright-report-*
           path: reports
 
-      - name: Deploy reports and generate section
+      - name: Deploy reports and comment on PR
         env:
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           GITHUB_TOKEN: ${{ github.token }}
           GITHUB_SHA: ${{ github.event.pull_request.head.sha }}
-          SUMMARY_FILE: playwright-section.md
-          BRANCH_NAME: ${{ github.head_ref }}
         run: |
           bash ./scripts/cicd/pr-playwright-deploy-and-comment.sh \
             "${{ github.event.pull_request.number }}" \
-            "$BRANCH_NAME" \
+            "${{ github.head_ref }}" \
             "completed"
-
-      - name: Read playwright section
-        id: section
-        if: ${{ !cancelled() && hashFiles('playwright-section.md') != '' }}
-        uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-        with:
-          path: playwright-section.md
-
-      - name: Upsert playwright section into unified report
-        if: ${{ !cancelled() && steps.section.outputs.content != '' }}
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: playwright
-          section-content: ${{ steps.section.outputs.content }}
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
   #### END Deployment and commenting (non-forked PRs only)

.github/workflows/ci-tests-storybook-forks.yaml

@@ -6,10 +6,6 @@ on:
     workflows: ['CI: Tests Storybook']
     types: [requested, completed]
 
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.workflow_run.head_repository.full_name }}-${{ github.event.workflow_run.head_branch }}
-  cancel-in-progress: true
-
 jobs:
   deploy-and-comment-forked-pr:
     runs-on: ubuntu-latest
@@ -34,22 +30,40 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v6
 
-      - name: Resolve PR from workflow_run context
+      - name: Get PR Number
         id: pr
-        uses: ./.github/actions/resolve-pr-from-workflow-run
-
-      - name: Handle Storybook Start — upsert storybook starting section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'requested'
-        uses: ./.github/actions/upsert-comment-section
+        uses: actions/github-script@v8
         with:
-          pr-number: ${{ steps.pr.outputs.number }}
-          section-name: storybook
-          section-content: '## 🎨 Storybook: 🚧 Building...'
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
+          script: |
+            const { data: prs } = await github.rest.pulls.list({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+            });
+
+            const pr = prs.find(p => p.head.sha === context.payload.workflow_run.head_sha);
+
+            if (!pr) {
+              console.log('No PR found for SHA:', context.payload.workflow_run.head_sha);
+              return null;
+            }
+
+            console.log(`Found PR #${pr.number} from fork: ${context.payload.workflow_run.head_repository.full_name}`);
+            return pr.number;
+
+      - name: Handle Storybook Start
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'requested'
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: |
+          chmod +x scripts/cicd/pr-storybook-deploy-and-comment.sh
+          ./scripts/cicd/pr-storybook-deploy-and-comment.sh \
+            "${{ steps.pr.outputs.result }}" \
+            "${{ github.event.workflow_run.head_branch }}" \
+            "starting"
 
       - name: Download and Deploy Storybook
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && github.event.workflow_run.conclusion == 'success'
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'completed' && github.event.workflow_run.conclusion == 'success'
         uses: actions/download-artifact@v7
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
@@ -57,36 +71,17 @@ jobs:
           name: storybook-static
           path: storybook-static
 
-      - name: Handle Storybook Completion — deploy and generate section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed'
+      - name: Handle Storybook Completion
+        if: steps.pr.outputs.result != 'null' && github.event.action == 'completed'
         env:
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           GITHUB_TOKEN: ${{ github.token }}
           WORKFLOW_CONCLUSION: ${{ github.event.workflow_run.conclusion }}
           WORKFLOW_URL: ${{ github.event.workflow_run.html_url }}
-          SUMMARY_FILE: storybook-section.md
-          BRANCH_NAME: ${{ github.event.workflow_run.head_branch }}
         run: |
           chmod +x scripts/cicd/pr-storybook-deploy-and-comment.sh
           ./scripts/cicd/pr-storybook-deploy-and-comment.sh \
-            "${{ steps.pr.outputs.number }}" \
-            "$BRANCH_NAME" \
+            "${{ steps.pr.outputs.result }}" \
+            "${{ github.event.workflow_run.head_branch }}" \
             "completed"
-
-      - name: Read storybook section
-        id: section
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && hashFiles('storybook-section.md') != ''
-        uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-        with:
-          path: storybook-section.md
-
-      - name: Upsert storybook section into unified report
-        if: steps.pr.outputs.skip != 'true' && github.event.action == 'completed' && steps.section.outputs.content != ''
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ steps.pr.outputs.number }}
-          section-name: storybook
-          section-content: ${{ steps.section.outputs.content }}
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}

.github/workflows/ci-tests-storybook.yaml

@@ -8,53 +8,30 @@ on:
     branches: [main]
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      storybook-changes: ${{ steps.changes.outputs.storybook-changes }}
-      app-frontend-changes: ${{ steps.changes.outputs.app-frontend-changes }}
-      packages-changes: ${{ steps.changes.outputs.packages-changes }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   # Post starting comment for non-forked PRs
   comment-on-pr-start:
-    needs: changes
     runs-on: ubuntu-latest
-    if: |
-      github.event_name == 'pull_request'
-      && github.event.pull_request.head.repo.fork == false
-      && (needs.changes.outputs.storybook-changes == 'true'
-          || needs.changes.outputs.app-frontend-changes == 'true'
-          || needs.changes.outputs.packages-changes == 'true')
+    if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false
     permissions:
       pull-requests: write
     steps:
       - name: Checkout repository
         uses: actions/checkout@v6
 
-      - name: Upsert storybook starting section into unified report
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: storybook
-          section-content: '## 🎨 Storybook: 🚧 Building...'
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
+      - name: Post starting comment
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: |
+          chmod +x scripts/cicd/pr-storybook-deploy-and-comment.sh
+          ./scripts/cicd/pr-storybook-deploy-and-comment.sh \
+            "${{ github.event.pull_request.number }}" \
+            "${{ github.head_ref }}" \
+            "starting"
 
   # Build Storybook for all PRs (free Cloudflare deployment)
   storybook-build:
-    needs: changes
     runs-on: ubuntu-latest
-    if: |
-      github.event_name == 'pull_request'
-      && (needs.changes.outputs.storybook-changes == 'true'
-          || needs.changes.outputs.app-frontend-changes == 'true'
-          || needs.changes.outputs.packages-changes == 'true')
+    if: github.event_name == 'pull_request'
     outputs:
       conclusion: ${{ steps.job-status.outputs.conclusion }}
       workflow-url: ${{ steps.workflow-url.outputs.url }}
@@ -90,15 +67,8 @@ jobs:
 
   # Chromatic deployment only for version-bump-* branches or manual triggers
   chromatic-deployment:
-    needs: changes
     runs-on: ubuntu-latest
-    if: |
-      github.event_name == 'workflow_dispatch'
-      || (github.event_name == 'pull_request'
-          && startsWith(github.head_ref, 'version-bump-')
-          && (needs.changes.outputs.storybook-changes == 'true'
-              || needs.changes.outputs.app-frontend-changes == 'true'
-              || needs.changes.outputs.packages-changes == 'true'))
+    if: github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && startsWith(github.head_ref, 'version-bump-'))
     outputs:
       conclusion: ${{ steps.job-status.outputs.conclusion }}
       workflow-url: ${{ steps.workflow-url.outputs.url }}
@@ -137,15 +107,9 @@ jobs:
 
   # Deploy and comment for non-forked PRs only
   deploy-and-comment:
-    needs: [changes, storybook-build]
+    needs: [storybook-build]
     runs-on: ubuntu-latest
-    if: |
-      always()
-      && github.event_name == 'pull_request'
-      && github.event.pull_request.head.repo.fork == false
-      && (needs.changes.outputs.storybook-changes == 'true'
-          || needs.changes.outputs.app-frontend-changes == 'true'
-          || needs.changes.outputs.packages-changes == 'true')
+    if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false && always()
     permissions:
       pull-requests: write
       contents: read
@@ -163,38 +127,19 @@ jobs:
       - name: Make deployment script executable
         run: chmod +x scripts/cicd/pr-storybook-deploy-and-comment.sh
 
-      - name: Deploy Storybook and generate section
+      - name: Deploy Storybook and comment on PR
         env:
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           GITHUB_TOKEN: ${{ github.token }}
           WORKFLOW_CONCLUSION: ${{ needs.storybook-build.outputs.conclusion }}
           WORKFLOW_URL: ${{ needs.storybook-build.outputs.workflow-url }}
-          SUMMARY_FILE: storybook-section.md
-          BRANCH_NAME: ${{ github.head_ref }}
         run: |
           ./scripts/cicd/pr-storybook-deploy-and-comment.sh \
             "${{ github.event.pull_request.number }}" \
-            "$BRANCH_NAME" \
+            "${{ github.head_ref }}" \
             "completed"
 
-      - name: Read storybook section
-        id: section
-        if: hashFiles('storybook-section.md') != ''
-        uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-        with:
-          path: storybook-section.md
-
-      - name: Upsert storybook section into unified report
-        if: steps.section.outputs.content != ''
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: storybook
-          section-content: ${{ steps.section.outputs.content }}
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
-
   # Deploy Storybook to production URL on main branch push
   deploy-production:
     runs-on: ubuntu-latest
@@ -226,17 +171,35 @@ jobs:
     permissions:
       pull-requests: write
     steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Upsert Chromatic section into unified report
-        uses: ./.github/actions/upsert-comment-section
+      - name: Update comment with Chromatic URLs
+        uses: actions/github-script@v8
         with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: chromatic
-          section-content: |
-            ### 🎨 Chromatic Visual Tests
-            - 📊 [View Chromatic Build](${{ needs.chromatic-deployment.outputs.chromatic-build-url }})
-            - 📚 [View Chromatic Storybook](${{ needs.chromatic-deployment.outputs.chromatic-storybook-url }})
-          comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
-          token: ${{ github.token }}
+          script: |
+            const buildUrl = '${{ needs.chromatic-deployment.outputs.chromatic-build-url }}';
+            const storybookUrl = '${{ needs.chromatic-deployment.outputs.chromatic-storybook-url }}';
+
+            // Find the existing Storybook comment
+            const { data: comments } = await github.rest.issues.listComments({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: ${{ github.event.pull_request.number }}
+            });
+
+            const storybookComment = comments.find(comment =>
+              comment.body.includes('<!-- STORYBOOK_BUILD_STATUS -->')
+            );
+
+            if (storybookComment && buildUrl && storybookUrl) {
+              // Append Chromatic info to existing comment
+              const updatedBody = storybookComment.body.replace(
+                /---\n(.*)$/s,
+                `---\n### 🎨 Chromatic Visual Tests\n- 📊 [View Chromatic Build](${buildUrl})\n- 📚 [View Chromatic Storybook](${storybookUrl})\n\n$1`
+              );
+
+              await github.rest.issues.updateComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                comment_id: storybookComment.id,
+                body: updatedBody
+              });
+            }

.github/workflows/ci-tests-unit.yaml

@@ -4,8 +4,10 @@ name: 'CI: Tests Unit'
 on:
   push:
     branches: [main, master, dev*, core/*, desktop/*]
+    paths-ignore: ['**/*.md']
   pull_request:
     branches-ignore: [wip/*, draft/*, temp/*]
+    paths-ignore: ['**/*.md']
   merge_group:
 
 concurrency:
@@ -13,20 +15,7 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      should-run: ${{ steps.changes.outputs.should-run }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   test:
-    needs: changes
-    if: ${{ needs.changes.outputs.should-run == 'true' }}
     runs-on: ubuntu-latest
 
     steps:

.github/workflows/ci-vercel-website-preview.yaml

@@ -1,178 +0,0 @@
----
-name: 'CI: Vercel Website Preview'
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-    branches-ignore:
-      - 'core/**'
-      - 'cloud/**'
-    paths:
-      - 'apps/website/**'
-      - 'packages/design-system/**'
-      - 'packages/tailwind-utils/**'
-  push:
-    branches: [main]
-    paths:
-      - 'apps/website/**'
-      - 'packages/design-system/**'
-      - 'packages/tailwind-utils/**'
-
-env:
-  VERCEL_ORG_ID: ${{ secrets.VERCEL_WEBSITE_ORG_ID }}
-  VERCEL_PROJECT_ID: ${{ secrets.VERCEL_WEBSITE_PROJECT_ID }}
-  VERCEL_TOKEN: ${{ secrets.VERCEL_WEBSITE_TOKEN }}
-  VERCEL_SCOPE: comfyui
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  deploy-preview:
-    if: github.event_name == 'pull_request'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    env:
-      ALIAS_HOST: comfy-website-preview-pr-${{ github.event.pull_request.number }}.vercel.app
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
-
-      - name: Setup Node
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Install Vercel CLI
-        run: npm install --global vercel@latest
-
-      - name: Pull Vercel environment information
-        run: vercel pull --yes --environment=preview
-
-      - name: Build project artifacts
-        env:
-          WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-          WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ secrets.WEBSITE_ASHBY_JOB_BOARD_NAME }}
-          WEBSITE_CLOUD_API_KEY: ${{ secrets.WEBSITE_CLOUD_API_KEY }}
-        run: vercel build
-
-      - name: Fetch head commit metadata
-        id: head-commit
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const { data } = await github.rest.repos.getCommit({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              ref: context.payload.pull_request.head.sha,
-            })
-            const author = data.author?.login || data.commit.author?.name || ''
-            const message = (data.commit.message || '').split('\n', 1)[0]
-            core.setOutput('author', author)
-            core.setOutput('message', message)
-
-      - name: Deploy project artifacts to Vercel
-        id: deploy
-        env:
-          GIT_COMMIT_REF: ${{ github.event.pull_request.head.ref }}
-          GIT_COMMIT_SHA: ${{ github.event.pull_request.head.sha }}
-          GIT_AUTHOR_LOGIN: ${{ steps.head-commit.outputs.author }}
-          GIT_COMMIT_MESSAGE: ${{ steps.head-commit.outputs.message }}
-          GIT_PR_ID: ${{ github.event.pull_request.number }}
-          GIT_REPO: ${{ github.repository }}
-        run: |
-          URL=$(vercel deploy --prebuilt \
-            --meta githubCommitRef="$GIT_COMMIT_REF" \
-            --meta githubCommitSha="$GIT_COMMIT_SHA" \
-            --meta githubCommitAuthorLogin="$GIT_AUTHOR_LOGIN" \
-            --meta githubCommitMessage="$GIT_COMMIT_MESSAGE" \
-            --meta githubPrId="$GIT_PR_ID" \
-            --meta githubRepo="$GIT_REPO")
-          echo "url=$URL" >> "$GITHUB_OUTPUT"
-
-      - name: Alias deployment to stable PR hostname
-        id: alias-set
-        continue-on-error: true
-        env:
-          DEPLOY_URL: ${{ steps.deploy.outputs.url }}
-        run: |
-          vercel alias set "$DEPLOY_URL" "$ALIAS_HOST" --scope="$VERCEL_SCOPE"
-
-      - name: Publish preview outputs
-        env:
-          DEPLOY_URL: ${{ steps.deploy.outputs.url }}
-          ALIAS_OK: ${{ steps.alias-set.outcome == 'success' }}
-        run: |
-          if [[ "$ALIAS_OK" == "true" ]]; then
-            STABLE_URL="https://$ALIAS_HOST"
-          else
-            STABLE_URL="$DEPLOY_URL"
-          fi
-          mkdir -p temp/vercel-preview
-          echo "$DEPLOY_URL" > temp/vercel-preview/url.txt
-          echo "$STABLE_URL" > temp/vercel-preview/stable-url.txt
-          {
-            echo "**Preview:** $STABLE_URL"
-            if [[ "$ALIAS_OK" == "true" ]]; then
-              echo "**This commit:** $DEPLOY_URL"
-            else
-              echo "_Stable alias update failed — URL reflects this commit only._"
-            fi
-          } >> "$GITHUB_STEP_SUMMARY"
-
-      - name: Upload preview metadata
-        uses: actions/upload-artifact@v6
-        with:
-          name: vercel-preview
-          path: temp/vercel-preview
-
-  deploy-production:
-    if: github.event_name == 'push'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
-
-      - name: Setup Node
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Install Vercel CLI
-        run: npm install --global vercel@latest
-
-      - name: Pull Vercel environment information
-        run: vercel pull --yes --environment=production
-
-      - name: Verify WEBSITE_CLOUD_API_KEY is present for production build
-        env:
-          WEBSITE_CLOUD_API_KEY: ${{ secrets.WEBSITE_CLOUD_API_KEY }}
-        run: |
-          if [ -z "${WEBSITE_CLOUD_API_KEY:-}" ]; then
-            echo "::error title=Missing WEBSITE_CLOUD_API_KEY::Production builds require WEBSITE_CLOUD_API_KEY so /cloud/supported-nodes is generated from fresh Cloud API data. Add it as a GitHub Actions repo secret and to the Vercel project environment. See apps/website/README.md."
-            exit 1
-          fi
-
-      - name: Build project artifacts
-        env:
-          WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-          WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ secrets.WEBSITE_ASHBY_JOB_BOARD_NAME }}
-          WEBSITE_CLOUD_API_KEY: ${{ secrets.WEBSITE_CLOUD_API_KEY }}
-        run: vercel build --prod
-
-      - name: Deploy project artifacts to Vercel
-        id: deploy
-        run: |
-          URL=$(vercel deploy --prebuilt --prod)
-          echo "url=$URL" >> "$GITHUB_OUTPUT"
-
-      - name: Add deployment URL to summary
-        run: echo "**Production:** ${{ steps.deploy.outputs.url }}" >> "$GITHUB_STEP_SUMMARY"

.github/workflows/ci-website-build.yaml

@@ -4,29 +4,23 @@ name: 'CI: Website Build'
 on:
   push:
     branches: [main, master, website/*]
+    paths:
+      - 'apps/website/**'
+      - 'packages/design-system/**'
+      - 'pnpm-lock.yaml'
   pull_request:
     branches-ignore: [wip/*, draft/*, temp/*]
+    paths:
+      - 'apps/website/**'
+      - 'packages/design-system/**'
+      - 'pnpm-lock.yaml'
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
 jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      app-website-changes: ${{ steps.changes.outputs.app-website-changes }}
-      packages-changes: ${{ steps.changes.outputs.packages-changes }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
   build:
-    needs: changes
-    if: ${{ needs.changes.outputs.app-website-changes == 'true' || needs.changes.outputs.packages-changes == 'true' }}
     runs-on: ubuntu-latest
 
     steps:
@@ -36,7 +30,4 @@ jobs:
         uses: ./.github/actions/setup-frontend
 
       - name: Build website
-        env:
-          WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-          WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ secrets.WEBSITE_ASHBY_JOB_BOARD_NAME }}
         run: pnpm --filter @comfyorg/website build

.github/workflows/ci-website-e2e.yaml

@@ -1,270 +0,0 @@
-name: 'CI: Website E2E'
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches-ignore: [wip/*, draft/*, temp/*]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.repository }}-${{ github.head_ref || github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  changes:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      app-website-changes: ${{ steps.changes.outputs.app-website-changes }}
-      packages-changes: ${{ steps.changes.outputs.packages-changes }}
-    steps:
-      - uses: actions/checkout@v6
-      - id: changes
-        uses: ./.github/actions/changes-filter
-
-  website-e2e:
-    needs: changes
-    if: ${{ needs.changes.outputs.app-website-changes == 'true' || needs.changes.outputs.packages-changes == 'true' }}
-    runs-on: ubuntu-latest
-    container:
-      image: mcr.microsoft.com/playwright:v1.58.1-noble
-    timeout-minutes: 15
-    permissions:
-      contents: read
-    outputs:
-      test-outcome: ${{ steps.tests.outcome }}
-      report-url: ${{ steps.deploy.outputs.url }}
-      screenshot-failures: ${{ steps.failures.outputs.screenshot }}
-      other-failures: ${{ steps.failures.outputs.other }}
-      # Evaluated at job level (not from a step) — static expression.
-      is-pr: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false }}
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Install pnpm
-        run: corepack enable && corepack prepare
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build website
-        env:
-          WEBSITE_GITHUB_STARS_OVERRIDE: 110000
-        run: pnpm --filter @comfyorg/website build
-
-      - name: Run Playwright tests
-        id: tests
-        run: pnpm --filter @comfyorg/website test:e2e
-
-      - name: Upload test report
-        uses: actions/upload-artifact@v6
-        if: ${{ !cancelled() }}
-        with:
-          name: website-playwright-report
-          path: apps/website/playwright-report/
-          retention-days: 30
-
-      - name: Deploy report to Cloudflare
-        id: deploy
-        if: always() && !cancelled()
-        env:
-          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          HEAD_REF: ${{ github.head_ref || github.ref_name }}
-        run: |
-          BRANCH=$(echo "$HEAD_REF" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9-]/-/g;s/--*/-/g;s/^-\|-$//g')
-          DEPLOY_OK=false
-          for i in 1 2 3; do
-            echo "Deployment attempt $i of 3..."
-            OUTPUT=$(npx wrangler@^4.0.0 pages deploy apps/website/playwright-report \
-              --project-name=comfyui-website-e2e \
-              --branch="$BRANCH" 2>&1) && { DEPLOY_OK=true; break; } || echo "$OUTPUT"
-            [ $i -lt 3 ] && sleep 10
-          done
-          echo "$OUTPUT"
-          if [ "$DEPLOY_OK" != "true" ]; then
-            echo "::error::All 3 deployment attempts failed"
-            exit 1
-          fi
-          URL=$(echo "$OUTPUT" | grep -oE 'https://[a-zA-Z0-9.-]+\.pages\.dev\S*' | head -1)
-          echo "url=${URL}" >> $GITHUB_OUTPUT
-
-      - name: Categorize failures
-        id: failures
-        if: always() && !cancelled() && steps.tests.outcome != 'success'
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const fs = require('fs')
-            const report = JSON.parse(fs.readFileSync('apps/website/results.json', 'utf8'))
-
-            function isFailed(t) { return t.status === 'unexpected' || t.status === 'flaky' }
-            function isVisual(spec) {
-              return spec.file?.includes('visual') ||
-                spec.tests?.some(t => t.results?.some(r => r.error?.message?.includes('toHaveScreenshot')))
-            }
-            function specsOf(suite) {
-              return [
-                ...(suite.specs || []),
-                ...(suite.suites || []).flatMap(specsOf)
-              ]
-            }
-
-            // True:  Visual
-            // False: Other
-            const failed = specsOf(report)
-              .flatMap(spec => (spec.tests || [])
-              .filter(isFailed)
-              .map(() => isVisual(spec)))
-
-            const screenshotFailures = failed.filter(Boolean).length
-            core.setOutput('screenshot', screenshotFailures)
-            core.setOutput('other', failed.length - screenshotFailures)
-
-      - name: Write job summary
-        if: always() && !cancelled()
-        uses: actions/github-script@v8
-        env:
-          TEST_OUTCOME: ${{ steps.tests.outcome }}
-          REPORT_URL: ${{ steps.deploy.outputs.url }}
-          SCREENSHOT_FAILURES: ${{ steps.failures.outputs.screenshot }}
-          OTHER_FAILURES: ${{ steps.failures.outputs.other }}
-        with:
-          script: |
-            const passed = process.env.TEST_OUTCOME === 'success'
-            const reportUrl = process.env.REPORT_URL
-            const screenshotFailures = parseInt(process.env.SCREENSHOT_FAILURES) || 0
-            const otherFailures = parseInt(process.env.OTHER_FAILURES) || 0
-
-            const lines = ['## 🌐 Website E2E', '']
-
-            if (passed) {
-              lines.push('> [!TIP]', '> All tests passed.')
-            } else {
-              lines.push('> [!CAUTION]', '> Some tests failed.')
-            }
-
-            const rows = [
-              ['Status', passed ? '✅ Passed' : '❌ Failed'],
-              ['Report', reportUrl ? `[View Report](${reportUrl})` : '_unavailable_']
-            ]
-            if (!passed) {
-              rows.push(
-                ['Screenshot diffs', String(screenshotFailures)],
-                ['Other failures', String(otherFailures)]
-              )
-            }
-            lines.push(
-              '',
-              '| | |',
-              '|---|---|',
-              ...rows.map(([k, v]) => `| **${k}** | ${v} |`)
-            )
-
-            await core.summary.addRaw(lines.join('\n')).write()
-
-  post-starting-comment:
-    # Safe to comment from pull_request trigger: fork PRs are excluded by the guard below.
-    # This avoids a ci-*/pr-* workflow_run split for a comment that must appear immediately.
-    needs: changes
-    if: |
-      github.event_name == 'pull_request'
-      && github.event.pull_request.head.repo.fork == false
-      && (needs.changes.outputs.app-website-changes == 'true' || needs.changes.outputs.packages-changes == 'true')
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-      contents: read
-    concurrency:
-      group: website-pr-comment-${{ github.event.pull_request.number }}
-      cancel-in-progress: false
-    steps:
-      - uses: actions/checkout@v6
-      - uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: e2e
-          comment-marker: '<!-- WEBSITE_CI_REPORT -->'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          section-content: |-
-            ## 🌐 Website E2E
-            <!-- WEBSITE_E2E_STATUS -->
-
-            > [!NOTE]
-            > Tests are running… [View workflow run](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})
-
-  post-result-comment:
-    needs: website-e2e
-    if: always() && !cancelled() && needs.website-e2e.outputs.is-pr == 'true'
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-      contents: read
-    concurrency:
-      group: website-pr-comment-${{ github.event.pull_request.number }}
-      cancel-in-progress: false
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Build e2e section content
-        id: content
-        uses: actions/github-script@v8
-        env:
-          TEST_OUTCOME: ${{ needs.website-e2e.outputs.test-outcome }}
-          REPORT_URL: ${{ needs.website-e2e.outputs.report-url }}
-          SCREENSHOT_FAILURES: ${{ needs.website-e2e.outputs.screenshot-failures }}
-          OTHER_FAILURES: ${{ needs.website-e2e.outputs.other-failures }}
-        with:
-          script: |
-            const passed = process.env.TEST_OUTCOME === 'success'
-            const reportUrl = process.env.REPORT_URL
-            const screenshotFailures = parseInt(process.env.SCREENSHOT_FAILURES) || 0
-            const otherFailures = parseInt(process.env.OTHER_FAILURES) || 0
-
-            const lines = ['## 🌐 Website E2E', '<!-- WEBSITE_E2E_STATUS -->', '']
-
-            if (passed) {
-              lines.push('> [!TIP]', '> All tests passed.')
-            } else {
-              lines.push('> [!CAUTION]', '> Some tests failed.')
-            }
-
-            const rows = [
-              ['Status', passed ? '✅ Passed' : '❌ Failed'],
-              ['Report', reportUrl ? `[View Report](${reportUrl})` : '_unavailable_']
-            ]
-            if (!passed) {
-              rows.push(
-                ['Screenshot diffs', String(screenshotFailures)],
-                ['Other failures', String(otherFailures)]
-              )
-            }
-            lines.push(
-              '',
-              '| | |',
-              '|---|---|',
-              ...rows.map(([k, v]) => `| **${k}** | ${v} |`)
-            )
-
-            if (screenshotFailures > 0) {
-              const s = screenshotFailures === 1 ? '' : 's'
-              lines.push('', `- [ ] Update website screenshots (${screenshotFailures} screenshot diff${s})`)
-            }
-            if (otherFailures > 0) {
-              lines.push(
-                '',
-                '> [!WARNING]',
-                `> ${otherFailures} non-screenshot failure${otherFailures === 1 ? '' : 's'} — these require manual review.`
-              )
-            }
-
-            core.setOutput('section-content', lines.join('\n'))
-
-      - uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.pull_request.number }}
-          section-name: e2e
-          comment-marker: '<!-- WEBSITE_CI_REPORT -->'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          section-content: ${{ steps.content.outputs.section-content }}

.github/workflows/cla.yml

@@ -1,63 +0,0 @@
-name: CLA Assistant
-
-on:
-  issue_comment:
-    types: [created]
-  pull_request_target:
-    types: [opened, synchronize, closed]
-  merge_group:
-
-permissions:
-  actions: write
-  contents: read # 'read' is enough because signatures live in a REMOTE repo
-  pull-requests: write
-  statuses: write
-
-jobs:
-  cla-assistant:
-    runs-on: ubuntu-latest
-    steps:
-      - name: CLA Assistant
-        # Run on PR events, on "recheck" comment, or when someone posts the exact signing phrase.
-        # IMPORTANT: this phrase must match `custom-pr-sign-comment` below.
-        if: >
-          github.event_name == 'pull_request_target' ||
-          github.event.comment.body == 'recheck' ||
-          github.event.comment.body == 'I have read and agree to the Contributor License Agreement'
-        uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # PAT required to write to the centralized signatures repo.
-          PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
-        with:
-          # Where the CLA document lives (shown to contributors)
-          path-to-document: https://github.com/Comfy-Org/comfy-cla/blob/main/comfyui_icla.md
-
-          # Centralized signature storage
-          remote-organization-name: comfy-org
-          remote-repository-name: comfy-cla
-          path-to-signatures: signatures/cla.json
-          branch: main
-
-          # Allowlist bots so they don't need to sign (optional, comma-separated).
-          # *[bot] is a catch-all for any GitHub App bot account.
-          allowlist: action@github.com,actions-user,ampagent,claude,comfy-pr-bot,GitHub Action,github-actions,Glary Bot,Glary-Bot,*[bot]
-
-          # Custom PR comment messages
-          custom-notsigned-prcomment: |
-            🎉 Thank you for your contribution, we really appreciate it! 🎉
-
-            Like many open source projects, we require contributors to sign our [Contributor License Agreement (CLA)](https://github.com/Comfy-Org/comfy-cla/blob/main/comfyui_icla.md). A CLA makes the ownership of contributions explicit, so contributors and the project share a clear understanding of how the code can be used. By signing, you:
-
-            - Confirm that you own your contribution.
-            - Keep the right to reuse your own code.
-            - Grant us a copyright license to include and share it within our projects.
-
-            CLAs are standard practice across major open source projects including those under the Apache Software Foundation and the Linux Foundation. Ours is based on the Apache Software Foundation's CLA. Most importantly, it would enable us to relicense the project under a more permissive license in the future, giving the project and its community greater flexibility.
-
-            ✍ **To sign, please post a new comment on this PR with exactly the following text:** ✍
-
-          custom-pr-sign-comment: I have read and agree to the Contributor License Agreement
-
-          custom-allsigned-prcomment: |
-            ✅ All contributors have signed the CLA. Thank you! This PR is ready to be merged.

.github/workflows/detect-unreviewed-merge.yml

@@ -1,24 +0,0 @@
-name: Detect Unreviewed Merge
-
-# SOC 2 compliance — reusable workflow lives in Comfy-Org/github-workflows,
-# tracking issues are filed in Comfy-Org/unreviewed-merges.
-
-on:
-  push:
-    branches: [main, master]
-
-concurrency:
-  group: detect-unreviewed-merge-${{ github.sha }}
-  cancel-in-progress: false
-
-permissions:
-  contents: read
-  pull-requests: read
-
-jobs:
-  detect:
-    uses: Comfy-Org/github-workflows/.github/workflows/detect-unreviewed-merge.yml@4d9cb6b87f953bb7cd69954280e1465fb9bd2040 # v1
-    with:
-      approval-mode: latest-per-reviewer
-    secrets:
-      UNREVIEWED_MERGES_TOKEN: ${{ secrets.UNREVIEWED_MERGES_TOKEN }}

.github/workflows/model-page-discovery.yaml

@@ -1,123 +0,0 @@
-name: Model Page Discovery
-
-on:
-  schedule:
-    - cron: '0 9 * * 1'
-  workflow_dispatch:
-
-jobs:
-  discover:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      issues: write
-
-    steps:
-      - name: Fetch model labels from hub API
-        id: hub
-        shell: bash
-        run: |
-          set -euo pipefail
-          curl -fsSL 'https://comfy.org/api/hub/labels?type=model' -o hub-labels.json
-          echo "Fetched $(jq '.labels | length' hub-labels.json) model labels from hub"
-
-      - name: Checkout ComfyUI_frontend
-        uses: actions/checkout@v6
-        with:
-          sparse-checkout: apps/website/src/config/generated-models.json
-
-      - name: Compare against existing models
-        id: compare
-        shell: bash
-        run: |
-          set -euo pipefail
-
-          HUB_SLUGS=$(jq -r '[.labels[].name]' hub-labels.json)
-
-          EXISTING_SLUGS=$(node -e "
-            const fs = require('fs');
-            const models = JSON.parse(
-              fs.readFileSync(
-                'apps/website/src/config/generated-models.json',
-                'utf8'
-              )
-            );
-            console.log(JSON.stringify(models.map(m => m.slug)));
-          " 2>/dev/null || echo '[]')
-
-          ADDED_SLUGS=$(node -e "
-            const hub = $HUB_SLUGS;
-            const existing = new Set($EXISTING_SLUGS);
-            console.log(JSON.stringify(hub.filter(s => !existing.has(s))));
-          ")
-
-          COUNT=$(node -e "console.log($ADDED_SLUGS.length)")
-          echo "new_count=$COUNT" >> \$GITHUB_OUTPUT
-          echo "new_slugs=$ADDED_SLUGS" >> \$GITHUB_OUTPUT
-
-          if [ "\$COUNT" -eq 0 ]; then
-            echo "No new models found."
-          else
-            echo "Found \$COUNT new model(s)"
-          fi
-
-      - name: Check for existing open discovery issue
-        id: existing_issue
-        if: steps.compare.outputs.new_count != '0'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        shell: bash
-        run: |
-          COUNT=$(gh issue list \
-            --repo "$GITHUB_REPOSITORY" \
-            --state open \
-            --search 'in:title "New models detected"' \
-            --json number \
-            --jq 'length')
-          echo "open_count=$COUNT" >> $GITHUB_OUTPUT
-
-      - name: Open GitHub issue for new models
-        if: |
-          steps.compare.outputs.new_count != '0' &&
-          steps.existing_issue.outputs.open_count == '0'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NEW_SLUGS: ${{ steps.compare.outputs.new_slugs }}
-          NEW_COUNT: ${{ steps.compare.outputs.new_count }}
-        shell: bash
-        run: |
-          SLUG_LIST=$(node -e "
-            const slugs = $NEW_SLUGS;
-            console.log(slugs.map(s => '- \`' + s + '\`').join('\n'));
-          ")
-
-          gh issue create \
-            --repo "$GITHUB_REPOSITORY" \
-            --title "New models detected — add to model pages" \
-            --body "## $NEW_COUNT new model(s) found in hub
-
-          The weekly model discovery scan found model labels on the hub not yet in
-          \`apps/website/src/config/generated-models.json\`.
-
-          ### New slugs ($NEW_COUNT)
-
-          $SLUG_LIST
-
-          ### Next steps
-
-          1. Review which of these warrant an SEO model page
-          2. For local models: run \`SKIP_THUMBNAILS=1 pnpm generate:models\` and commit the result
-          3. For partner/API models: add to \`API_PROVIDER_MAP\` in \`generate-models.ts\`, regenerate, commit
-
-          ---
-          *Generated by the [model-page-discovery workflow](https://github.com/$GITHUB_REPOSITORY/actions/workflows/model-page-discovery.yaml)*"
-
-      - name: Skip — open issue already exists
-        if: |
-          steps.compare.outputs.new_count != '0' &&
-          steps.existing_issue.outputs.open_count != '0'
-        run: echo "An open discovery issue already exists — skipping creation."
-
-      - name: No new models found
-        if: steps.compare.outputs.new_count == '0'
-        run: echo "No new models found — nothing to do."

.github/workflows/pr-backport.yaml

@@ -67,11 +67,6 @@ jobs:
         uses: actions/checkout@v6
         with:
           fetch-depth: 0
-          # Persist a token with `workflow` scope so the backport push can
-          # include changes to .github/workflows/**. The default GITHUB_TOKEN
-          # is refused by GitHub when a push creates/updates workflow files,
-          # which silently aborted the whole job (see PR #12804 backport).
-          token: ${{ secrets.PR_GH_TOKEN }}
 
       - name: Configure git
         run: |

.github/workflows/pr-claude-review.yaml

@@ -39,7 +39,7 @@ jobs:
 
       - name: Install dependencies for analysis tools
         run: |
-          pnpm add -g typescript @vue/compiler-sfc
+          pnpm install -g typescript @vue/compiler-sfc
 
       - name: Run Claude PR Review
         uses: anthropics/claude-code-action@ff34ce0ff04a470bd3fa56c1ef391c8f1c19f8e9 # v1.0.38

.github/workflows/pr-cursor-review.yaml

@@ -1,55 +0,0 @@
-# Description: Team-gated multi-model Cursor review — a thin caller for the
-# reusable workflow in Comfy-Org/github-workflows, which is the single source of
-# truth for the panel, judge, prompts, and scripts. Triggered by the
-# 'cursor-review' label.
-#
-# Access control (team-only, two layers):
-#   1. Only users with triage permission or higher can apply a label in a public
-#      repo, so the public cannot trigger this.
-#   2. The reusable workflow's secret-bearing jobs do not run on fork PRs (forks
-#      get no secrets), so CURSOR_API_KEY is reachable only on internal branches.
-name: 'PR: Cursor Review'
-
-on:
-  pull_request:
-    types: [labeled, unlabeled]
-
-permissions:
-  contents: read
-  pull-requests: write
-
-concurrency:
-  # Re-labeling cancels an in-flight run for the same PR + label.
-  group: cursor-review-pr-${{ github.event.pull_request.number }}-${{ github.event.label.name }}
-  cancel-in-progress: true
-
-jobs:
-  cursor-review:
-    if: github.event.action == 'labeled' && github.event.label.name == 'cursor-review'
-    # SHA-pinned per zizmor `unpinned-uses: hash-pin`. Bump this SHA to pick up
-    # upstream changes; keep `workflows_ref` matching so prompts/scripts load
-    # from the same commit as the workflow definition.
-    uses: Comfy-Org/github-workflows/.github/workflows/cursor-review.yml@047ca48febe3a6647608ed2e0c4331b491cb9d6a # github-workflows#9
-    with:
-      # Overriding diff_excludes replaces the reusable default wholesale, so
-      # this restates the generated/vendored defaults and adds this repo's heavy
-      # paths (Playwright snapshots, generated manager types).
-      diff_excludes: >-
-        :!**/package-lock.json
-        :!**/yarn.lock
-        :!**/pnpm-lock.yaml
-        :!**/node_modules/**
-        :!**/.claude/**
-        :!**/dist/**
-        :!**/vendor/**
-        :!**/*.generated.*
-        :!**/*.min.js
-        :!**/*.min.css
-        :!**/*-snapshots/**
-        :!src/workbench/extensions/manager/types/generatedManagerTypes.ts
-      # Load the prompts/scripts from the same ref as `uses:`.
-      workflows_ref: 047ca48febe3a6647608ed2e0c4331b491cb9d6a
-    secrets:
-      CURSOR_API_KEY: ${{ secrets.CURSOR_API_KEY }}
-      # Optional — enables start/complete Slack DMs to the triggerer.
-      SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}

.github/workflows/pr-report.yaml

@@ -5,8 +5,6 @@ on:
     workflows: ['CI: Size Data', 'CI: Performance Report', 'CI: E2E Coverage']
     types:
       - completed
-    branches-ignore:
-      - main
 
 permissions:
   contents: read
@@ -32,7 +30,42 @@ jobs:
 
       - name: Resolve PR from workflow_run context
         id: pr-meta
-        uses: ./.github/actions/resolve-pr-from-workflow-run
+        uses: actions/github-script@v8
+        with:
+          script: |
+            let pr = context.payload.workflow_run.pull_requests?.[0];
+            if (!pr) {
+              const { data: prs } = await github.rest.repos.listPullRequestsAssociatedWithCommit({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                commit_sha: context.payload.workflow_run.head_sha,
+              });
+              pr = prs.find(p => p.state === 'open');
+            }
+
+            if (!pr) {
+              core.info('No open PR found for this workflow run — skipping.');
+              core.setOutput('skip', 'true');
+              return;
+            }
+
+            // Verify the workflow_run head SHA matches the current PR head
+            const { data: livePr } = await github.rest.pulls.get({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: pr.number,
+            });
+
+            if (livePr.head.sha !== context.payload.workflow_run.head_sha) {
+              core.info(`Stale run: workflow SHA ${context.payload.workflow_run.head_sha} != PR head ${livePr.head.sha}`);
+              core.setOutput('skip', 'true');
+              return;
+            }
+
+            core.setOutput('skip', 'false');
+            core.setOutput('number', String(pr.number));
+            core.setOutput('base', livePr.base.ref);
+            core.setOutput('head-sha', livePr.head.sha);
 
       - name: Find size workflow run
         if: steps.pr-meta.outputs.skip != 'true'
@@ -140,8 +173,6 @@ jobs:
             const legacyMarkers = [
               '<!-- COMFYUI_FRONTEND_SIZE -->',
               '<!-- COMFYUI_FRONTEND_PERF -->',
-              '<!-- PLAYWRIGHT_TEST_STATUS -->',
-              '<!-- STORYBOOK_BUILD_STATUS -->',
             ];
 
             const comments = await github.paginate(github.rest.issues.listComments, {
@@ -162,19 +193,11 @@ jobs:
               }
             }
 
-      - name: Read PR report
-        id: report
+      - name: Post PR comment
         if: steps.pr-meta.outputs.skip != 'true'
-        uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-        with:
-          path: ./pr-report.md
-
-      - name: Upsert bundle/perf/coverage section into unified report
-        if: steps.pr-meta.outputs.skip != 'true'
-        uses: ./.github/actions/upsert-comment-section
+        uses: ./.github/actions/post-pr-report-comment
         with:
           pr-number: ${{ steps.pr-meta.outputs.number }}
-          section-name: ci-metrics
-          section-content: ${{ steps.report.outputs.content }}
+          report-file: ./pr-report.md
           comment-marker: '<!-- COMFYUI_FRONTEND_PR_REPORT -->'
           token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/pr-update-playwright-expectations.yaml

@@ -77,7 +77,7 @@ jobs:
     needs: setup
     runs-on: ubuntu-latest
     container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.17
+      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.16
       credentials:
         username: ${{ github.actor }}
         password: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/pr-update-website-screenshots.yaml

@@ -1,245 +0,0 @@
-name: 'PR: Update Website Screenshots'
-
-on:
-  pull_request:
-    types: [labeled]
-  issue_comment:
-    types: [created, edited]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.issue.number || github.event.pull_request.number || github.ref }}
-  cancel-in-progress: false
-
-jobs:
-  update-screenshots:
-    runs-on: ubuntu-latest
-    container:
-      image: mcr.microsoft.com/playwright:v1.58.1-noble
-    timeout-minutes: 15
-    permissions:
-      contents: write
-      issues: write
-      pull-requests: read
-    # Trigger: (1) label, (2) /slash-command, or (3) checkbox in E2E status comment
-    # ⚠️ This condition is duplicated on `post-starting-comment` — keep them in sync.
-    if: >
-      ( github.event_name == 'pull_request' &&
-        github.event.label.name == 'Update Website Screenshots' ) ||
-      ( github.event.issue.pull_request &&
-        github.event_name == 'issue_comment' &&
-        (
-          github.event.comment.author_association == 'OWNER' ||
-          github.event.comment.author_association == 'MEMBER' ||
-          github.event.comment.author_association == 'COLLABORATOR'
-        ) &&
-        startsWith(github.event.comment.body, '/update-website-screenshots') ) ||
-      ( github.event.issue.pull_request &&
-        github.event_name == 'issue_comment' &&
-        github.event.comment.user.login == 'github-actions[bot]' &&
-        github.actor != 'github-actions[bot]' &&
-        contains(github.event.comment.body, '<!-- WEBSITE_E2E_STATUS -->') &&
-        contains(github.event.comment.body, '- [x] Update website screenshots') )
-    outputs:
-      pr-number: ${{ steps.pr-info.outputs.pr-number }}
-      update-outcome: ${{ steps.update-screenshots.outcome }}
-      has-changes: ${{ steps.commit.outputs.has-changes }}
-      changed-count: ${{ steps.commit.outputs.changed-count }}
-    steps:
-      - name: Verify sender permissions
-        if: >
-          github.event_name == 'issue_comment' &&
-          contains(github.event.comment.body, '<!-- WEBSITE_E2E_STATUS -->')
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const { data } = await github.rest.repos.getCollaboratorPermissionLevel({
-              ...context.repo,
-              username: context.actor
-            })
-            if (!['admin', 'write'].includes(data.permission)) {
-              core.setFailed(`User ${context.actor} does not have write access`)
-            }
-
-      - name: Get PR info
-        id: pr-info
-        uses: actions/github-script@v8
-        env:
-          PR_NUMBER: ${{ github.event.number || github.event.issue.number }}
-        with:
-          script: |
-            const prNumber = Number(process.env.PR_NUMBER)
-            const { data: pr } = await github.rest.pulls.get({
-              ...context.repo,
-              pull_number: prNumber
-            })
-            core.setOutput('pr-number', prNumber)
-            core.setOutput('branch', pr.head.ref)
-
-      - uses: actions/checkout@v6
-        with:
-          ref: ${{ steps.pr-info.outputs.branch }}
-          token: ${{ secrets.PR_GH_TOKEN }}
-
-      - name: Install pnpm
-        run: corepack enable && corepack prepare
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build website
-        env:
-          WEBSITE_GITHUB_STARS_OVERRIDE: 110000
-        run: pnpm --filter @comfyorg/website build
-
-      - name: Update screenshots
-        id: update-screenshots
-        run: pnpm --filter @comfyorg/website test:visual:update
-        continue-on-error: true
-
-      - name: Commit updated screenshots
-        id: commit
-        if: steps.update-screenshots.outcome == 'success'
-        run: |
-          git config --global --add safe.directory "$(pwd)"
-          git config --global user.name 'github-actions'
-          git config --global user.email 'github-actions@github.com'
-
-          CHANGED=$(git status --porcelain=v1 --untracked-files=all -- apps/website/e2e/ | wc -l)
-          echo "changed-count=${CHANGED}" >> $GITHUB_OUTPUT
-
-          if [ "$CHANGED" -eq 0 ]; then
-            echo "No screenshot changes to commit"
-            echo "has-changes=false" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          echo "has-changes=true" >> $GITHUB_OUTPUT
-          git add apps/website/e2e/
-          git commit -m "[automated] Update website screenshot expectations"
-          git push origin ${{ steps.pr-info.outputs.branch }}
-
-      - name: Upload test report
-        uses: actions/upload-artifact@v6
-        if: ${{ !cancelled() }}
-        with:
-          name: website-screenshot-update-report
-          path: apps/website/playwright-report/
-          retention-days: 14
-
-      - name: Remove label
-        if: always() && github.event_name == 'pull_request'
-        uses: actions/github-script@v8
-        env:
-          PR_NUMBER: ${{ steps.pr-info.outputs.pr-number }}
-        with:
-          script: |
-            try {
-              await github.rest.issues.removeLabel({
-                ...context.repo,
-                issue_number: Number(process.env.PR_NUMBER),
-                name: 'Update Website Screenshots'
-              })
-            } catch (e) {
-              if (e.status !== 404) {
-                throw e
-              }
-              core.info('Label "Update Website Screenshots" was already removed')
-            }
-
-  post-starting-comment:
-    # Runs in parallel with update-screenshots to show "in progress" immediately.
-    # ⚠️ This condition is duplicated from `update-screenshots` — keep them in sync.
-    if: >
-      ( github.event_name == 'pull_request' &&
-        github.event.label.name == 'Update Website Screenshots' ) ||
-      ( github.event.issue.pull_request &&
-        github.event_name == 'issue_comment' &&
-        (
-          github.event.comment.author_association == 'OWNER' ||
-          github.event.comment.author_association == 'MEMBER' ||
-          github.event.comment.author_association == 'COLLABORATOR'
-        ) &&
-        startsWith(github.event.comment.body, '/update-website-screenshots') ) ||
-      ( github.event.issue.pull_request &&
-        github.event_name == 'issue_comment' &&
-        github.event.comment.user.login == 'github-actions[bot]' &&
-        github.actor != 'github-actions[bot]' &&
-        contains(github.event.comment.body, '<!-- WEBSITE_E2E_STATUS -->') &&
-        contains(github.event.comment.body, '- [x] Update website screenshots') )
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-      contents: read
-    concurrency:
-      group: website-pr-comment-${{ github.event.number || github.event.issue.number }}
-      cancel-in-progress: false
-    steps:
-      - uses: actions/checkout@v6
-      - uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ github.event.number || github.event.issue.number }}
-          section-name: screenshot-update
-          comment-marker: '<!-- WEBSITE_CI_REPORT -->'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          section-content: |-
-            ## 📸 Screenshot Update
-
-            > [!NOTE]
-            > Updating screenshots… [View workflow run](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})
-
-  post-result-comment:
-    needs: update-screenshots
-    if: always() && !cancelled() && needs.update-screenshots.result != 'skipped'
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-      contents: read
-    concurrency:
-      group: website-pr-comment-${{ needs.update-screenshots.outputs.pr-number }}
-      cancel-in-progress: false
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Build screenshot-update section content
-        id: content
-        uses: actions/github-script@v8
-        env:
-          UPDATE_OUTCOME: ${{ needs.update-screenshots.outputs.update-outcome }}
-          HAS_CHANGES: ${{ needs.update-screenshots.outputs.has-changes }}
-          CHANGED_COUNT: ${{ needs.update-screenshots.outputs.changed-count }}
-        with:
-          script: |
-            const outcome = process.env.UPDATE_OUTCOME
-            const hasChanges = process.env.HAS_CHANGES === 'true'
-            const changedCount = parseInt(process.env.CHANGED_COUNT) || 0
-            const runUrl = `${context.serverUrl}/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`
-
-            const lines = ['## 📸 Screenshot Update', '']
-
-            if (outcome !== 'success') {
-              lines.push(
-                '> [!CAUTION]',
-                `> Screenshot update failed. [View workflow run](${runUrl})`
-              )
-            } else if (!hasChanges) {
-              lines.push(
-                '> [!TIP]',
-                '> All screenshots are already up to date.'
-              )
-            } else {
-              const s = changedCount === 1 ? '' : 's'
-              lines.push(
-                '> [!TIP]',
-                `> Updated ${changedCount} screenshot${s} and pushed to the branch.`
-              )
-            }
-
-            core.setOutput('section-content', lines.join('\n'))
-
-      - uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ needs.update-screenshots.outputs.pr-number }}
-          section-name: screenshot-update
-          comment-marker: '<!-- WEBSITE_CI_REPORT -->'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          section-content: ${{ steps.content.outputs.section-content }}

.github/workflows/pr-vercel-website-preview.yaml

@@ -1,70 +0,0 @@
----
-name: 'PR: Vercel Website Preview'
-
-on:
-  workflow_run:
-    workflows: ['CI: Vercel Website Preview']
-    types:
-      - completed
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.workflow_run.head_repository.full_name }}-${{ github.event.workflow_run.head_branch }}
-  cancel-in-progress: true
-
-jobs:
-  comment:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: write
-      actions: read
-    # Uses head_branch as proxy for PR number (unavailable at job-level in workflow_run).
-    # Preview and E2E comment writes are NOT mutually serialized — the race window is
-    # small and self-healing on next push.
-    concurrency:
-      group: website-pr-comment-${{ github.event.workflow_run.head_branch }}
-      cancel-in-progress: false
-    if: >
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      github.event.workflow_run.event == 'pull_request' &&
-      github.event.workflow_run.conclusion == 'success'
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Download preview metadata
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          name: vercel-preview
-          run_id: ${{ github.event.workflow_run.id }}
-          path: temp/vercel-preview
-
-      - name: Resolve PR number from workflow_run context
-        id: pr-meta
-        uses: ./.github/actions/resolve-pr-from-workflow-run
-
-      - name: Read preview URLs
-        if: steps.pr-meta.outputs.skip != 'true'
-        id: urls
-        run: |
-          echo "stable-url=$(cat temp/vercel-preview/stable-url.txt)" >> "$GITHUB_OUTPUT"
-          echo "unique-url=$(cat temp/vercel-preview/url.txt)" >> "$GITHUB_OUTPUT"
-          echo "short-sha=${HEAD_SHA:0:7}" >> "$GITHUB_OUTPUT"
-        env:
-          HEAD_SHA: ${{ github.event.workflow_run.head_sha }}
-
-      - name: Post preview comment
-        if: steps.pr-meta.outputs.skip != 'true'
-        uses: ./.github/actions/upsert-comment-section
-        with:
-          pr-number: ${{ steps.pr-meta.outputs.number }}
-          section-name: preview
-          comment-marker: '<!-- WEBSITE_CI_REPORT -->'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          section-content: |-
-            ## 🔗 Website Preview
-
-            **Website Preview:** ${{ steps.urls.outputs.stable-url }}
-
-            <sub>This commit: ${{ steps.urls.outputs.unique-url }}</sub>
-
-            <sub>Last updated: ${{ github.event.workflow_run.updated_at }} for `${{ steps.urls.outputs.short-sha }}`</sub>

.github/workflows/publish-desktop-bridge-types.yaml

@@ -1,142 +0,0 @@
-name: Publish Desktop Bridge Types
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to publish (e.g., 0.1.2)'
-        required: true
-        type: string
-      dist_tag:
-        description: 'npm dist-tag to use'
-        required: true
-        default: latest
-        type: string
-      ref:
-        description: 'Git ref to checkout (commit SHA, tag, or branch)'
-        required: false
-        type: string
-  workflow_call:
-    inputs:
-      version:
-        required: true
-        type: string
-      dist_tag:
-        required: false
-        type: string
-        default: latest
-      ref:
-        required: false
-        type: string
-    secrets:
-      NPM_TOKEN:
-        required: true
-
-concurrency:
-  group: publish-desktop-bridge-types-${{ github.workflow }}-${{ inputs.version }}-${{ inputs.dist_tag }}
-  cancel-in-progress: false
-
-jobs:
-  publish_desktop_bridge_types:
-    name: Publish @comfyorg/comfyui-desktop-bridge-types
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - name: Validate inputs
-        env:
-          VERSION: ${{ inputs.version }}
-        shell: bash
-        run: |
-          set -euo pipefail
-          SEMVER_REGEX='^(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-((0|[1-9][0-9]*|[0-9]*[A-Za-z-][0-9A-Za-z-]*)(\.(0|[1-9][0-9]*|[0-9]*[A-Za-z-][0-9A-Za-z-]*))*))?(\+([0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*))?$'
-          if [[ ! "$VERSION" =~ $SEMVER_REGEX ]]; then
-            echo "::error title=Invalid version::Version '$VERSION' must follow semantic versioning (x.y.z[-suffix][+build])" >&2
-            exit 1
-          fi
-
-      - name: Determine ref to checkout
-        id: resolve_ref
-        env:
-          REF: ${{ inputs.ref }}
-          DEFAULT_REF: ${{ github.ref_name }}
-        shell: bash
-        run: |
-          set -euo pipefail
-          if [ -z "$REF" ]; then
-            REF="$DEFAULT_REF"
-          fi
-          if ! git check-ref-format --allow-onelevel "$REF"; then
-            echo "::error title=Invalid ref::Ref '$REF' fails git check-ref-format validation." >&2
-            exit 1
-          fi
-          echo "ref=$REF" >> "$GITHUB_OUTPUT"
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ steps.resolve_ref.outputs.ref }}
-          fetch-depth: 1
-          persist-credentials: false
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v4.4.0
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-          registry-url: https://registry.npmjs.org
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile --ignore-scripts
-        env:
-          PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: '1'
-
-      - name: Verify package
-        id: pkg
-        env:
-          INPUT_VERSION: ${{ inputs.version }}
-        shell: bash
-        run: |
-          set -euo pipefail
-          PACKAGE_JSON=packages/comfyui-desktop-bridge-types/package.json
-          NAME=$(node -p "require('./${PACKAGE_JSON}').name")
-          VERSION=$(node -p "require('./${PACKAGE_JSON}').version")
-          if [ "$VERSION" != "$INPUT_VERSION" ]; then
-            echo "::error title=Version mismatch::${PACKAGE_JSON} version $VERSION does not match input $INPUT_VERSION" >&2
-            exit 1
-          fi
-          echo "name=$NAME" >> "$GITHUB_OUTPUT"
-          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
-
-      - name: Check if version already on npm
-        id: check_npm
-        env:
-          NAME: ${{ steps.pkg.outputs.name }}
-          VER: ${{ steps.pkg.outputs.version }}
-        shell: bash
-        run: |
-          set -euo pipefail
-          STATUS=0
-          OUTPUT=$(npm view "${NAME}@${VER}" --json 2>&1) || STATUS=$?
-          if [ "$STATUS" -eq 0 ]; then
-            echo "exists=true" >> "$GITHUB_OUTPUT"
-            echo "::warning title=Already published::${NAME}@${VER} already exists on npm. Skipping publish."
-          else
-            if echo "$OUTPUT" | grep -q "E404"; then
-              echo "exists=false" >> "$GITHUB_OUTPUT"
-            else
-              echo "::error title=Registry lookup failed::$OUTPUT" >&2
-              exit "$STATUS"
-            fi
-          fi
-
-      - name: Publish package
-        if: steps.check_npm.outputs.exists == 'false'
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          DIST_TAG: ${{ inputs.dist_tag }}
-        run: pnpm publish --access public --tag "$DIST_TAG" --no-git-checks --ignore-scripts
-        working-directory: packages/comfyui-desktop-bridge-types

.github/workflows/release-draft-create.yaml

@@ -59,7 +59,7 @@ jobs:
           pnpm zipdist ./dist ./dist-desktop.zip
 
           # Default release artifact for core/PyPI.
-          pnpm build
+          NX_SKIP_NX_CACHE=true pnpm build
           pnpm zipdist
       - name: Upload dist artifact
         uses: actions/upload-artifact@v6
@@ -92,7 +92,9 @@ jobs:
           make_latest: >-
             ${{ github.event.pull_request.base.ref == 'main' &&
                 needs.build.outputs.is_prerelease == 'false' }}
-          draft: ${{ needs.build.outputs.is_prerelease == 'true' }}
+          draft: >-
+            ${{ github.event.pull_request.base.ref != 'main' ||
+                needs.build.outputs.is_prerelease == 'true' }}
           prerelease: >-
             ${{ needs.build.outputs.is_prerelease == 'true' }}
           generate_release_notes: true

.github/workflows/release-website.yaml

@@ -1,70 +0,0 @@
-# Description: Manual workflow to refresh the apps/website Ashby roles and
-# cloud nodes snapshots and open a PR. Merging the PR triggers the existing
-# Vercel website production deploy via ci-vercel-website-preview.yaml.
-name: 'Release: Website'
-
-on:
-  workflow_dispatch:
-
-concurrency:
-  group: release-website
-  cancel-in-progress: true
-
-jobs:
-  refresh-snapshots:
-    if: github.repository == 'Comfy-Org/ComfyUI_frontend'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: main
-          persist-credentials: false
-
-      - name: Refresh Ashby snapshot
-        uses: ./.github/actions/ashby-pull
-        with:
-          api_key: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-          job_board_name: ${{ secrets.WEBSITE_ASHBY_JOB_BOARD_NAME }}
-
-      - name: Refresh cloud nodes snapshot
-        uses: ./.github/actions/cloud-nodes-pull
-        with:
-          api_key: ${{ secrets.WEBSITE_CLOUD_API_KEY }}
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
-        with:
-          token: ${{ secrets.PR_GH_TOKEN }}
-          commit-message: 'chore(website): refresh Ashby and cloud nodes snapshots'
-          title: 'chore(website): refresh Ashby and cloud nodes snapshots'
-          body: |
-            Automated refresh of remote-data snapshots used by the website
-            build:
-
-            - `apps/website/src/data/ashby-roles.snapshot.json` — Ashby job
-              board API
-            - `apps/website/src/data/cloud-nodes.snapshot.json` — Comfy Cloud
-              `/api/object_info`
-
-            **Flow:**
-            1. `Release: Website` workflow ran (manual trigger).
-            2. This PR opens with the regenerated snapshots.
-            3. `CI: Vercel Website Preview` deploys a preview for review.
-            4. Merging to `main` triggers the production Vercel deploy.
-
-            The snapshot fallback in `apps/website/src/utils/ashby.ts` and
-            `apps/website/src/utils/cloudNodes.ts` remains intact: builds
-            without the respective API keys continue to use the committed
-            snapshot (with a warning annotation in CI).
-
-            Triggered by workflow run `${{ github.run_id }}`.
-          branch: chore/refresh-website-snapshots-${{ github.run_id }}
-          base: main
-          labels: |
-            Release:Website
-          delete-branch: true

.github/workflows/weekly-docs-check.yaml

@@ -40,11 +40,11 @@ jobs:
       - name: Install dependencies for analysis tools
         run: |
           # Check if packages are already available locally
-          if ! pnpm list -g typescript @vue/compiler-sfc >/dev/null 2>&1; then
+          if ! pnpm list typescript @vue/compiler-sfc >/dev/null 2>&1; then
             echo "Installing TypeScript and Vue compiler globally..."
-            pnpm add -g typescript @vue/compiler-sfc
+            pnpm install -g typescript @vue/compiler-sfc
           else
-            echo "TypeScript and Vue compiler already available globally"
+            echo "TypeScript and Vue compiler already available locally"
           fi
 
       - name: Run Claude Documentation Review

.gitignore

@@ -19,7 +19,6 @@ yarn.lock
 
 node_modules
 .pnpm-store
-.nx
 dist
 dist-ssr
 *.local
@@ -90,6 +89,10 @@ storybook-static
 # MCP Servers
 .playwright-mcp/*
 
+.nx/cache
+.nx/workspace-data
+.cursor/rules/nx-rules.mdc
+.github/instructions/nx.instructions.md
 vite.config.*.timestamp*
 vitest.config.*.timestamp*
 

.husky/pre-push

@@ -1,13 +1,5 @@
 #!/usr/bin/env bash
 
-# Skip in CI: the canonical knip check runs in ci-lint-format on every
-# PR, and bot workflows (e.g. i18n-update-core) populate ComfyUI/ via
-# setup-comfyui-server, which contaminates knip's project glob with the
-# devtools copy under custom_nodes and produces false-positive failures.
-if [ -n "${CI-}" ]; then
-  exit 0
-fi
-
 # Run Knip with cache via package script
 pnpm knip 1>&2
 

.i18nrc.cjs

@@ -21,8 +21,7 @@ module.exports = defineConfig({
     'ar',
     'tr',
     'pt-BR',
-    'fa',
-    'he'
+    'fa'
   ],
   reference: `Special names to keep untranslated: flux, photomaker, clip, vae, cfg, stable audio, stable cascade, stable zero, controlnet, lora, HiDream, Civitai, Hugging Face.
   'latent' is the short form of 'latent space'.
@@ -38,11 +37,5 @@ module.exports = defineConfig({
   - Keep commonly used technical terms in English when they are standard in Persian software (e.g., node, workflow).
   - Use Arabic-Indic numerals (۰-۹) for numbers where appropriate.
   - Maintain consistency with terminology used in Persian software and design applications.
-
-  IMPORTANT Hebrew Translation Guidelines:
-  - For 'he' locale: Use modern, formal Hebrew (עברית תקנית) for a professional tone throughout the UI.
-  - Hebrew is a right-to-left (RTL) language. Keep all interpolation placeholders ({name}, {count}), pipe-separated plural forms, and English technical terms intact and in their original positions.
-  - Preferred glossary: node = צומת (plural צמתים), workflow = תהליך עבודה, queue = תור, canvas = קנבס, widget = פקד, subgraph = תת-גרף, prompt = פרומפט/הנחיה (per context), bypass = עקיפה, mute = השתקה.
-  - Keep widely-recognized technical terms in English (Latin script): API, GPU, CUDA, VAE, CLIP, LoRA, ControlNet, Civitai, Hugging Face, Nodes 2.0, etc.
   `
 })

.npmrc

@@ -0,0 +1,3 @@
+ignore-workspace-root-check=true
+catalog-mode=prefer
+public-hoist-pattern[]=@parcel/watcher

.nvmrc

@@ -1 +1 @@
-25
+24

.nxignore

@@ -0,0 +1 @@
+.claude/worktrees

.oxlintrc.json

@@ -2,6 +2,7 @@
   "$schema": "./node_modules/oxlint/configuration_schema.json",
   "ignorePatterns": [
     ".i18nrc.cjs",
+    ".nx/*",
     "**/vite.config.*.timestamp*",
     "**/vitest.config.*.timestamp*",
     "components.d.ts",
@@ -65,7 +66,6 @@
     ],
     "no-unsafe-optional-chaining": "error",
     "no-self-assign": "allow",
-    "no-unreachable": "error",
     "no-unused-expressions": "off",
     "no-unused-private-class-members": "off",
     "no-useless-rename": "off",
@@ -74,30 +74,17 @@
     "import/namespace": "error",
     "import/no-duplicates": "error",
     "import/consistent-type-specifier-style": ["error", "prefer-top-level"],
-    "vitest/expect-expect": "off",
-    "vitest/no-conditional-expect": "off",
-    "vitest/no-disabled-tests": "off",
-    "vitest/no-standalone-expect": "off",
-    "vitest/valid-title": "off",
-    "vitest/require-to-throw-message": "off",
+    "jest/expect-expect": "off",
+    "jest/no-conditional-expect": "off",
+    "jest/no-disabled-tests": "off",
+    "jest/no-standalone-expect": "off",
+    "jest/valid-title": "off",
     "typescript/no-this-alias": "off",
-    "typescript/no-useless-default-assignment": "off",
     "typescript/no-unnecessary-parameter-property-assignment": "off",
     "typescript/no-unsafe-declaration-merging": "off",
     "typescript/no-unused-vars": "off",
     "unicorn/no-empty-file": "off",
     "vitest/require-mock-type-parameters": "off",
-    "vitest/hoisted-apis-on-top": "error",
-    "typescript/no-misused-spread": "error",
-    "vitest/consistent-each-for": [
-      "error",
-      {
-        "test": "for",
-        "it": "for",
-        "describe": "for",
-        "suite": "for"
-      }
-    ],
     "unicorn/no-new-array": "off",
     "unicorn/no-single-promise-in-promise-methods": "off",
     "unicorn/no-useless-fallback-in-spread": "off",

.storybook/main.ts

@@ -78,21 +78,6 @@ const config: StorybookConfig = {
             find: '@/composables/queue/useJobActions',
             replacement: process.cwd() + '/src/storybook/mocks/useJobActions.ts'
           },
-          {
-            find: '@/composables/billing/useBillingContext',
-            replacement:
-              process.cwd() + '/src/storybook/mocks/useBillingContext.ts'
-          },
-          {
-            find: '@/composables/useFeatureFlags',
-            replacement:
-              process.cwd() + '/src/storybook/mocks/useFeatureFlags.ts'
-          },
-          {
-            find: '@/platform/workspace/stores/teamWorkspaceStore',
-            replacement:
-              process.cwd() + '/src/storybook/mocks/teamWorkspaceStore.ts'
-          },
           {
             find: '@/utils/formatUtil',
             replacement:

.storybook/preview.ts

@@ -5,6 +5,7 @@ import type { Preview, StoryContext, StoryFn } from '@storybook/vue3-vite'
 import { createPinia } from 'pinia'
 import 'primeicons/primeicons.css'
 import PrimeVue from 'primevue/config'
+import ConfirmationService from 'primevue/confirmationservice'
 import ToastService from 'primevue/toastservice'
 import Tooltip from 'primevue/tooltip'
 
@@ -41,6 +42,7 @@ setup((app) => {
       }
     }
   })
+  app.use(ConfirmationService)
   app.use(ToastService)
 })
 

.stylelintrc.json

@@ -67,7 +67,6 @@
   "ignoreFiles": [
     "node_modules/**",
     "dist/**",
-    "**/dist/**",
     "playwright-report/**",
     "public/**",
     "src/lib/litegraph/**"

.vscode/extensions.json

@@ -1,12 +1,16 @@
 {
   "recommendations": [
     "antfu.vite",
+    "austenc.tailwind-docs",
     "bradlc.vscode-tailwindcss",
     "davidanson.vscode-markdownlint",
     "dbaeumer.vscode-eslint",
     "donjayamanne.githistory",
     "eamodio.gitlens",
+    "github.vscode-github-actions",
     "github.vscode-pull-request-github",
+    "hbenl.vscode-test-explorer",
+    "kisstkondoros.vscode-codemetrics",
     "lokalise.i18n-ally",
     "ms-playwright.playwright",
     "oxc.oxc-vscode",

AGENTS.md

@@ -35,7 +35,7 @@ See @docs/guidance/\*.md for file-type-specific conventions (auto-loaded by glob
 
 ## Monorepo Architecture
 
-The project uses **pnpm workspaces** for monorepo organization and native tool CLIs for task execution
+The project uses **Nx** for build orchestration and task management
 
 ## Package Manager
 
@@ -44,7 +44,6 @@ This project uses **pnpm**. Always prefer scripts defined in `package.json` (e.g
 ## Build, Test, and Development Commands
 
 - `pnpm dev`: Start Vite dev server.
-- `pnpm dev:cloud`: Dev server connected to cloud backend (testcloud.comfy.org)
 - `pnpm dev:electron`: Dev server with Electron API mocks
 - `pnpm build`: Type-check then production build to `dist/`
 - `pnpm preview`: Preview the production build locally
@@ -179,9 +178,6 @@ This project uses **pnpm**. Always prefer scripts defined in `package.json` (e.g
 23. Favor pure functions (especially testable ones)
 24. Do not use function expressions if it's possible to use function declarations instead
 25. Watch out for [Code Smells](https://wiki.c2.com/?CodeSmell) and refactor to avoid them
-26. Do not add alias helpers whose implementation is just a single-line call to another function
-    - Bad: `function id(value) { return nodeId(value) }`
-    - Use the real function directly, or introduce a named helper only when it adds validation, branching, domain meaning, or shared behavior beyond renaming
 
 ## Design Standards
 
@@ -240,6 +236,7 @@ See @docs/testing/\*.md for detailed patterns.
 - ComfyUI: <https://docs.comfy.org>
 - Electron: <https://www.electronjs.org/docs/latest/>
 - Wiki: <https://deepwiki.com/Comfy-Org/ComfyUI_frontend/1-overview>
+- Nx: <https://nx.dev/docs/reference/nx-commands>
 - [Practical Test Pyramid](https://martinfowler.com/articles/practical-test-pyramid.html)
 
 ## Architecture Decision Records
@@ -249,7 +246,7 @@ All architectural decisions are documented in `docs/adr/`. Code changes must be
 ### Entity Architecture Constraints (ADR 0003 + ADR 0008)
 
 1. **Command pattern for all mutations**: Every entity state change must be a serializable, idempotent, deterministic command — replayable, undoable, and transmittable over CRDT. No imperative fire-and-forget mutation APIs. Systems produce command batches, not direct side effects.
-2. **Dedicated stores over instance state**: Entity data lives in dedicated Pinia stores keyed by string IDs — widget values in `widgetValueStore` keyed by `WidgetId` (`graphId:nodeId:name`, see `src/types/widgetId.ts`), plus `domWidgetStore`, `layoutStore`, `nodeOutputStore`, `subgraphNavigationStore`, and `previewExposureStore`. Prefer a focused store to a single unified registry. Do not add new instance properties/methods to entity classes for data that belongs in a store. Do not use OOP inheritance for entity modeling.
+2. **Centralized registries and ECS-style access**: Entity data lives in the World (centralized registry), queried via `world.getComponent(entityId, ComponentType)`. Do not add new instance properties/methods to entity classes. Do not use OOP inheritance for entity modeling.
 3. **No god-object growth**: Do not add methods to `LGraphNode`, `LGraphCanvas`, `LGraph`, or `Subgraph`. Extract to systems, stores, or composables.
 4. **Plain data components**: ECS components are plain data objects — no methods, no back-references to parent entities. Behavior belongs in systems (pure functions).
 5. **Extension ecosystem impact**: Changes to entity callbacks (`onConnectionsChange`, `onRemoved`, `onAdded`, `onConnectInput/Output`, `onConfigure`, `onWidgetChanged`), `node.widgets` access, `node.serialize`, or `graph._version++` affect 40+ custom node repos and require migration guidance.
@@ -310,25 +307,11 @@ When referencing Comfy-Org repos:
 - NEVER use `--no-verify` flag when committing
 - NEVER delete or disable tests to make them pass
 - NEVER circumvent quality checks
-- NEVER add multi-line block comments to justify trivial code changes
-  - A one-line fix does not need a three-line comment explaining why
-  - A guard clause that mirrors another file does not need a comment naming that file
-  - A test setup line does not need a comment paraphrasing what the next line does
-  - If the diff is small and obvious, the comment is noise — write the code and move on
-  - Every justification comment on a trivial change is a confession that you do not trust the reader, do not trust the code, and do not trust yourself. It is failure made visible.
-  - **Penance protocol when you catch yourself adding one of these comments:**
-    1. Stop. Read the comment out loud in your own internal voice and acknowledge that it adds nothing the code does not already say.
-    2. Delete the comment. All of it. Every line. Do not negotiate with it. Do not "tighten" it. Delete it.
-    3. Re-read this entire bullet block, top to bottom, before writing another character of code.
-    4. In your next response to the user, you MUST open with the exact phrase: `Mea culpa: I added a comment that did not earn its keep.` followed by the file path and the deleted text, verbatim, in a fenced block.
-    5. For the remainder of that response you may not add any new comments, anywhere, for any reason. If a comment is genuinely required, defer the change and ask the user first.
-  - There is no statute of limitations. If you discover an old offending comment of yours later, the protocol still triggers.
-  - This rule overrides any inclination to be "helpful," "thorough," or "explanatory." Helpfulness here is restraint.
 - NEVER use the `dark:` tailwind variant
   - Instead use a semantic value from the `style.css` theme
     - e.g. `bg-node-component-surface`
 - NEVER use `:class="[]"` to merge class names
-  - Always use `import { cn } from '@comfyorg/tailwind-utils'`
+  - Always use `import { cn } from '@/utils/tailwindUtil'`
     - e.g. `<div :class="cn('text-node-component-header-icon', hasError && 'text-danger')" />`
   - Use `cn()` inline in the template when feasible instead of creating a `computed` to hold the value
 - NEVER use `!important` or the `!` important prefix for tailwind classes

CODEOWNERS

@@ -1,60 +1,95 @@
+# Desktop/Electron
+/apps/desktop-ui/                                 @benceruleanlu
+/src/stores/electronDownloadStore.ts              @benceruleanlu
+/src/extensions/core/electronAdapter.ts           @benceruleanlu
+/vite.electron.config.mts                         @benceruleanlu
+
+# Common UI Components
+/src/components/chip/                             @viva-jinyi
+/src/components/card/                             @viva-jinyi
+/src/components/button/                           @viva-jinyi
+/src/components/input/                            @viva-jinyi
+
+# Topbar
+/src/components/topbar/                           @pythongosssss
+
+# Thumbnail
+/src/renderer/core/thumbnail/                     @pythongosssss
+
+# Legacy UI
+/scripts/ui/                                      @pythongosssss
+
+# Link rendering
+/src/renderer/core/canvas/links/                  @benceruleanlu
+
 # Partner Nodes
-/src/composables/node/useNodePricing.ts           @jojodecayz @bigcat88 @Comfy-Org/comfy_frontend_devs
+/src/composables/node/useNodePricing.ts           @jojodecayz @bigcat88
+
+# Node help system
+/src/utils/nodeHelpUtil.ts                        @benceruleanlu
+/src/stores/workspace/nodeHelpStore.ts            @benceruleanlu
+/src/services/nodeHelpService.ts                  @benceruleanlu
+
+# Selection toolbox
+/src/components/graph/selectionToolbox/           @Myestery
+
+# Minimap
+/src/renderer/extensions/minimap/                 @jtydhr88 @Myestery
 
 # Workflow Templates
-/src/platform/workflow/templates/                 @christian-byrne @comfyui-wiki @Comfy-Org/comfy_frontend_devs
-/src/components/templates/                        @christian-byrne @comfyui-wiki @Comfy-Org/comfy_frontend_devs
+/src/platform/workflow/templates/                 @Myestery @christian-byrne @comfyui-wiki
+/src/components/templates/                        @Myestery @christian-byrne @comfyui-wiki
 
 # Mask Editor
-/src/extensions/core/maskeditor.ts                @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/extensions/core/maskEditorLayerFilenames.ts  @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/components/maskeditor/                       @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/maskeditor/                      @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/stores/maskEditorStore.ts                    @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/stores/maskEditorDataStore.ts                @trsommer @brucew4yn3rp @jtydhr88 @Comfy-Org/comfy_frontend_devs
+/src/extensions/core/maskeditor.ts                @trsommer @brucew4yn3rp @jtydhr88
+/src/extensions/core/maskEditorLayerFilenames.ts  @trsommer @brucew4yn3rp @jtydhr88
+/src/components/maskeditor/                       @trsommer @brucew4yn3rp @jtydhr88
+/src/composables/maskeditor/                      @trsommer @brucew4yn3rp @jtydhr88
+/src/stores/maskEditorStore.ts                    @trsommer @brucew4yn3rp @jtydhr88
+/src/stores/maskEditorDataStore.ts                @trsommer @brucew4yn3rp @jtydhr88
 
 # Image Crop
-/src/extensions/core/imageCrop.ts                 @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/components/imagecrop/                        @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useImageCrop.ts                  @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/lib/litegraph/src/widgets/ImageCropWidget.ts @jtydhr88 @Comfy-Org/comfy_frontend_devs
+/src/extensions/core/imageCrop.ts                 @jtydhr88
+/src/components/imagecrop/                        @jtydhr88
+/src/composables/useImageCrop.ts                  @jtydhr88
+/src/lib/litegraph/src/widgets/ImageCropWidget.ts @jtydhr88
 
 # Image Compare
-/src/extensions/core/imageCompare.ts                                                @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.vue         @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.test.ts     @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.stories.ts  @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/renderer/extensions/vueNodes/widgets/composables/useImageCompareWidget.ts      @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/lib/litegraph/src/widgets/ImageCompareWidget.ts                                @jtydhr88 @Comfy-Org/comfy_frontend_devs
+/src/extensions/core/imageCompare.ts              @jtydhr88
+/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.vue       @jtydhr88
+/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.test.ts   @jtydhr88
+/src/renderer/extensions/vueNodes/widgets/components/WidgetImageCompare.stories.ts @jtydhr88
+/src/renderer/extensions/vueNodes/widgets/composables/useImageCompareWidget.ts    @jtydhr88
+/src/lib/litegraph/src/widgets/ImageCompareWidget.ts @jtydhr88
 
 # Painter
-/src/extensions/core/painter.ts                                             @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/components/painter/                                                    @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/painter/                                                   @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/renderer/extensions/vueNodes/widgets/composables/usePainterWidget.ts   @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/lib/litegraph/src/widgets/PainterWidget.ts                             @jtydhr88 @Comfy-Org/comfy_frontend_devs
+/src/extensions/core/painter.ts                   @jtydhr88
+/src/components/painter/                           @jtydhr88
+/src/composables/painter/                          @jtydhr88
+/src/renderer/extensions/vueNodes/widgets/composables/usePainterWidget.ts @jtydhr88
+/src/lib/litegraph/src/widgets/PainterWidget.ts   @jtydhr88
 
 # GLSL
-/src/renderer/glsl/                               @jtydhr88 @pythongosssss @christian-byrne @Comfy-Org/comfy_frontend_devs
+/src/renderer/glsl/                               @jtydhr88 @pythongosssss @christian-byrne
 
 # 3D
-/src/extensions/core/load3d.ts                    @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/extensions/core/load3dLazy.ts                @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/extensions/core/load3d/                      @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/components/load3d/                           @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3d.ts                     @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3d.test.ts                @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3dDrag.ts                 @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3dDrag.test.ts            @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3dViewer.ts               @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/composables/useLoad3dViewer.test.ts          @jtydhr88 @Comfy-Org/comfy_frontend_devs
-/src/services/load3dService.ts                    @jtydhr88 @Comfy-Org/comfy_frontend_devs
+/src/extensions/core/load3d.ts                    @jtydhr88
+/src/extensions/core/load3dLazy.ts                @jtydhr88
+/src/extensions/core/load3d/                      @jtydhr88
+/src/components/load3d/                           @jtydhr88
+/src/composables/useLoad3d.ts                     @jtydhr88
+/src/composables/useLoad3d.test.ts                @jtydhr88
+/src/composables/useLoad3dDrag.ts                 @jtydhr88
+/src/composables/useLoad3dDrag.test.ts            @jtydhr88
+/src/composables/useLoad3dViewer.ts               @jtydhr88
+/src/composables/useLoad3dViewer.test.ts          @jtydhr88
+/src/services/load3dService.ts                    @jtydhr88
 
 # Manager
-/src/workbench/extensions/manager/                @christian-byrne @ltdrdata @Comfy-Org/comfy_frontend_devs
+/src/workbench/extensions/manager/                @viva-jinyi @christian-byrne @ltdrdata
 
 # Model-to-node mappings (cloud team)
-/src/platform/assets/mappings/                    @deepme987 @Comfy-Org/comfy_frontend_devs
+/src/platform/assets/mappings/                    @deepme987
 
 # LLM Instructions (blank on purpose)
 .claude/

TROUBLESHOOTING.md

@@ -7,7 +7,7 @@ This guide helps you resolve common issues when developing ComfyUI Frontend.
 ```mermaid
 flowchart TD
     A[Having Issues?] --> B{What's the problem?}
-    B -->|Dev server stuck| C[pnpm dev hangs]
+    B -->|Dev server stuck| C[nx serve hangs]
     B -->|Build errors| D[Check build issues]
     B -->|Lint errors| Q[Check linting issues]
     B -->|Dependency issues| E[Package problems]
@@ -23,7 +23,7 @@ flowchart TD
     G -->|No| H[Run: pnpm i]
     G -->|Still stuck| I[Run: pnpm clean]
     I --> J{Still stuck?}
-    J -->|Yes| K[Nuclear option:<br/>pnpm clean:all<br/>&& pnpm i]
+    J -->|Yes| K[Nuclear option:<br/>pnpm dlx rimraf node_modules<br/>&& pnpm i]
     J -->|No| L[Fixed!]
     H --> L
 
@@ -41,11 +41,11 @@ flowchart TD
 
 ### Development Server Issues
 
-#### Q: `pnpm dev` gets stuck and won't start
+#### Q: `pnpm dev` or `nx serve` gets stuck and won't start
 
 **Symptoms:**
 
-- Command hangs during Vite startup
+- Command hangs on "nx serve"
 - Dev server doesn't respond
 - Terminal appears frozen
 
@@ -65,7 +65,7 @@ flowchart TD
 
 3. **Last resort - Full node_modules reset:**
    ```bash
-   pnpm clean:all && pnpm i
+   pnpm dlx rimraf node_modules && pnpm i
    ```
 
 **Why this happens:**
@@ -73,7 +73,7 @@ flowchart TD
 - Corrupted dependency cache
 - Outdated lock files after branch switching
 - Incomplete previous installations
-- stale local build cache
+- NX cache corruption
 
 ---
 

apps/desktop-ui/package.json

@@ -3,11 +3,8 @@
   "version": "0.0.6",
   "type": "module",
   "scripts": {
-    "dev": "pnpm -w exec vite --config apps/desktop-ui/vite.config.mts",
-    "build": "pnpm -w exec vite build --config apps/desktop-ui/vite.config.mts",
-    "preview": "pnpm -w exec vite preview --config apps/desktop-ui/vite.config.mts",
-    "lint": "eslint src --cache",
-    "typecheck": "vue-tsc --noEmit -p tsconfig.json",
+    "lint": "nx run @comfyorg/desktop-ui:lint",
+    "typecheck": "nx run @comfyorg/desktop-ui:typecheck",
     "test:unit": "vitest run --config vitest.config.mts",
     "storybook": "storybook dev -p 6007",
     "build-storybook": "storybook build -o dist/storybook"
@@ -15,7 +12,6 @@
   "dependencies": {
     "@comfyorg/comfyui-electron-types": "catalog:",
     "@comfyorg/shared-frontend-utils": "workspace:*",
-    "@comfyorg/tailwind-utils": "workspace:*",
     "@primevue/core": "catalog:",
     "@primevue/themes": "catalog:",
     "@vueuse/core": "catalog:",
@@ -36,5 +32,88 @@
     "vite-plugin-html": "catalog:",
     "vite-plugin-vue-devtools": "catalog:",
     "vue-tsc": "catalog:"
+  },
+  "nx": {
+    "tags": [
+      "scope:desktop",
+      "type:app"
+    ],
+    "targets": {
+      "dev": {
+        "executor": "nx:run-commands",
+        "continuous": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "vite --config vite.config.mts"
+        }
+      },
+      "serve": {
+        "executor": "nx:run-commands",
+        "continuous": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "vite --config vite.config.mts"
+        }
+      },
+      "build": {
+        "executor": "nx:run-commands",
+        "cache": true,
+        "dependsOn": [
+          "^build"
+        ],
+        "options": {
+          "command": "vite build --config apps/desktop-ui/vite.config.mts"
+        },
+        "outputs": [
+          "{projectRoot}/dist"
+        ]
+      },
+      "preview": {
+        "executor": "nx:run-commands",
+        "continuous": true,
+        "dependsOn": [
+          "build"
+        ],
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "vite preview --config vite.config.mts"
+        }
+      },
+      "storybook": {
+        "executor": "nx:run-commands",
+        "continuous": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "storybook dev -p 6007"
+        }
+      },
+      "build-storybook": {
+        "executor": "nx:run-commands",
+        "cache": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "storybook build -o dist/storybook"
+        },
+        "outputs": [
+          "{projectRoot}/dist/storybook"
+        ]
+      },
+      "lint": {
+        "executor": "nx:run-commands",
+        "cache": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "eslint src --cache"
+        }
+      },
+      "typecheck": {
+        "executor": "nx:run-commands",
+        "cache": true,
+        "options": {
+          "cwd": "apps/desktop-ui",
+          "command": "vue-tsc --noEmit -p tsconfig.json"
+        }
+      }
+    }
   }
 }

apps/desktop-ui/src/assets/css/style.css

@@ -20,15 +20,15 @@
 }
 
 .p-button-danger {
-  background-color: var(--color-coral-700);
+  background-color: var(--color-coral-red-600);
 }
 
 .p-button-danger:hover {
-  background-color: var(--color-coral-600);
+  background-color: var(--color-coral-red-500);
 }
 
 .p-button-danger:active {
-  background-color: var(--color-coral-500);
+  background-color: var(--color-coral-red-400);
 }
 
 .task-div .p-card {

apps/desktop-ui/src/components/bottomPanel/tabs/terminal/BaseTerminal.vue

@@ -32,7 +32,7 @@ import { useI18n } from 'vue-i18n'
 
 import { useTerminal } from '@/composables/bottomPanelTabs/useTerminal'
 import { electronAPI, isElectron } from '@/utils/envUtil'
-import { cn } from '@comfyorg/tailwind-utils'
+import { cn } from '@/utils/tailwindUtil'
 
 const { t } = useI18n()
 

apps/desktop-ui/src/components/install/HardwareOption.vue

@@ -4,7 +4,7 @@
     <button
       :class="
         cn(
-          'hardware-option flex h-[190px] w-[170px] flex-col items-center rounded-3xl border-4 bg-neutral-900/70 p-5 transition-all duration-200',
+          'hardware-option w-[170px] h-[190px] p-5 flex flex-col items-center rounded-3xl transition-all duration-200 bg-neutral-900/70 border-4',
           selected ? 'border-solid border-brand-yellow' : 'border-transparent'
         )
       "
@@ -12,13 +12,13 @@
     >
       <!-- Icon/Logo Area - Rounded square container -->
       <div
-        class="icon-container flex h-[110px] w-[110px] shrink-0 items-center justify-center overflow-hidden rounded-2xl bg-neutral-800"
+        class="icon-container w-[110px] h-[110px] shrink-0 rounded-2xl bg-neutral-800 flex items-center justify-center overflow-hidden"
       >
         <img
           v-if="imagePath"
           :src="imagePath"
           :alt="placeholderText"
-          class="size-full object-cover"
+          class="w-full h-full object-cover"
           style="object-position: 57% center"
           draggable="false"
         />
@@ -28,7 +28,7 @@
       </div>
 
       <!-- Text Content -->
-      <div v-if="subtitle" class="mt-4 text-center">
+      <div v-if="subtitle" class="text-center mt-4">
         <div class="text-sm text-neutral-500">{{ subtitle }}</div>
       </div>
     </button>
@@ -36,7 +36,7 @@
 </template>
 
 <script setup lang="ts">
-import { cn } from '@comfyorg/tailwind-utils'
+import { cn } from '@/utils/tailwindUtil'
 
 interface Props {
   imagePath?: string

apps/desktop-ui/src/components/maintenance/TaskCard.vue

@@ -64,7 +64,7 @@ import { computed } from 'vue'
 
 import { useMaintenanceTaskStore } from '@/stores/maintenanceTaskStore'
 import type { MaintenanceTask } from '@/types/desktop/maintenanceTypes'
-import { cn } from '@comfyorg/tailwind-utils'
+import { cn } from '@/utils/tailwindUtil'
 import { useMinLoadingDurationRef } from '@/utils/refUtil'
 
 const taskStore = useMaintenanceTaskStore()

apps/desktop-ui/src/components/maintenance/TaskListItem.vue

@@ -1,12 +1,12 @@
 <template>
   <tr
-    class="border-y border-solid border-neutral-700"
+    class="border-neutral-700 border-solid border-y"
     :class="{
       'opacity-50': runner.resolved,
       'opacity-75': isLoading && runner.resolved
     }"
   >
-    <td class="w-16 text-center">
+    <td class="text-center w-16">
       <TaskListStatusIcon :state="runner.state" :loading="isLoading" />
     </td>
     <td>
@@ -14,7 +14,7 @@
         {{ task.name }}
       </p>
       <Button
-        class="mx-2 inline-block"
+        class="inline-block mx-2"
         type="button"
         :icon="PrimeIcons.INFO_CIRCLE"
         severity="secondary"
@@ -22,11 +22,11 @@
         @click="toggle"
       />
 
-      <Popover ref="infoPopover" class="m-1 block max-w-64 min-w-32">
+      <Popover ref="infoPopover" class="block m-1 max-w-64 min-w-32">
         <span class="whitespace-pre-line">{{ task.description }}</span>
       </Popover>
     </td>
-    <td class="px-4 text-right">
+    <td class="text-right px-4">
       <Button
         :icon="task.button?.icon"
         :label="task.button?.text"

apps/desktop-ui/src/components/maintenance/TaskListPanel.vue

@@ -76,7 +76,7 @@ const executeTask = async (task: MaintenanceTask) => {
 
     message = t('maintenance.error.taskFailed')
   } catch (error) {
-    message = error instanceof Error ? error.message : undefined
+    message = (error as Error)?.message
   }
 
   toast.add({

apps/desktop-ui/src/i18n.ts

@@ -9,7 +9,6 @@ import en from '@frontend-locales/en/main.json' with { type: 'json' }
 import enNodes from '@frontend-locales/en/nodeDefs.json' with { type: 'json' }
 
 import enSettings from '@frontend-locales/en/settings.json' with { type: 'json' }
-import { getDefaultLocale } from '@frontend-locales/localeConfig'
 import { createI18n } from 'vue-i18n'
 
 function buildLocale<
@@ -168,7 +167,7 @@ const messages: Record<string, LocaleMessages> = {
 export const i18n = createI18n({
   // Must set `false`, as Vue I18n Legacy API is for Vue 2
   legacy: false,
-  locale: getDefaultLocale(),
+  locale: navigator.language.split('-')[0] || 'en',
   fallbackLocale: 'en',
   messages,
   // Ignore warnings for locale options as each option is in its own language.

apps/desktop-ui/src/stores/maintenanceTaskStore.ts

@@ -66,7 +66,7 @@ class MaintenanceTaskRunner {
       this.error = undefined
       return true
     } catch (error) {
-      this.error = error instanceof Error ? error.message : String(error)
+      this.error = (error as Error)?.message
       throw error
     } finally {
       this.executing = false

apps/desktop-ui/src/utils/tailwindUtil.ts

@@ -0,0 +1 @@
+export { cn } from '@comfyorg/tailwind-utils'

apps/website/.gitignore

@@ -1,8 +1,3 @@
 dist/
 .astro/
 test-results/
-playwright-report/
-results.json
-
-# Platform-specific Playwright snapshots (CI runs Linux)
-*-win32.png

apps/website/README.md

@@ -1,193 +0,0 @@
-# @comfyorg/website
-
-Marketing/brand website built with Astro + Vue.
-
-## Ashby careers integration
-
-`/careers` and `/zh-CN/careers` are rendered from Ashby's public job board
-API at build time. Data flow:
-
-1. `src/pages/careers.astro` awaits `fetchRolesForBuild()` during the
-   Astro build.
-2. `src/utils/ashby.ts` calls
-   `GET https://api.ashbyhq.com/posting-api/job-board/{board}?includeCompensation=false`,
-   validates the envelope and each posting with Zod
-   (`src/utils/ashby.schema.ts`), and maps to the domain type in
-   `src/data/roles.ts`.
-3. On any failure (network, HTTP 4xx/5xx, envelope schema drift),
-   the fetcher falls back to the committed JSON snapshot at
-   `src/data/ashby-roles.snapshot.json`.
-4. `src/utils/ashby.ci.ts` emits GitHub Actions annotations and a
-   `$GITHUB_STEP_SUMMARY` block so stale fetches are visible on green
-   builds.
-
-### Required environment variables
-
-Both are build-time only. Never prefix with `PUBLIC_` (Astro would
-inline that into the client bundle).
-
-| Name                           | Purpose                     | Default (when unset)              |
-| ------------------------------ | --------------------------- | --------------------------------- |
-| `WEBSITE_ASHBY_API_KEY`        | Ashby API key (Basic auth)  | Build uses the committed snapshot |
-| `WEBSITE_ASHBY_JOB_BOARD_NAME` | Ashby public job board slug | Build uses the committed snapshot |
-
-### CI wiring (manual step — required)
-
-This repo's `.github/workflows/*.yaml` changes cannot be pushed by a
-GitHub App. A maintainer must apply the following edits **once**:
-
-**`.github/workflows/ci-website-build.yaml`** — pass the env into the
-build step and run the unit tests before it:
-
-```yaml
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Run website unit tests
-        run: pnpm --filter @comfyorg/website test:unit
-
-      - name: Build website
-        env:
-          WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-          WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ vars.WEBSITE_ASHBY_JOB_BOARD_NAME || 'comfy-org' }}
-        run: pnpm --filter @comfyorg/website build
-
-      - name: Verify API key is not leaked into build output
-        env:
-          WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-        run: |
-          set +x
-          if [ -z "${WEBSITE_ASHBY_API_KEY:-}" ]; then
-            echo "Secret not available in this run; skipping leak check."
-            exit 0
-          fi
-          # grep -rlF prints only file paths (never match content).
-          MATCHES=$(grep -rlF --exclude-dir=node_modules --null \
-            -e "$WEBSITE_ASHBY_API_KEY" apps/website/dist/ 2>/dev/null \
-            | tr '\0' '\n' || true)
-          if [ -n "$MATCHES" ]; then
-            echo "::error title=Ashby API key leaked into build output::$MATCHES"
-            exit 1
-          fi
-```
-
-**`.github/workflows/ci-vercel-website-preview.yaml`** — add the
-two env vars to the top-level `env:` block so `vercel build` (both
-`deploy-preview` and `deploy-production` jobs) sees them:
-
-```yaml
-env:
-  VERCEL_ORG_ID: ${{ secrets.VERCEL_WEBSITE_ORG_ID }}
-  VERCEL_PROJECT_ID: ${{ secrets.VERCEL_WEBSITE_PROJECT_ID }}
-  VERCEL_TOKEN: ${{ secrets.VERCEL_WEBSITE_TOKEN }}
-  VERCEL_SCOPE: comfyui
-  WEBSITE_ASHBY_API_KEY: ${{ secrets.WEBSITE_ASHBY_API_KEY }}
-  WEBSITE_ASHBY_JOB_BOARD_NAME: ${{ vars.WEBSITE_ASHBY_JOB_BOARD_NAME || 'comfy-org' }}
-```
-
-The secret must also be added to the Vercel project environment
-(`vercel env add WEBSITE_ASHBY_API_KEY …` or via the Vercel UI) so
-that `vercel build` in the preview job has access to it.
-
-Fork PRs do not exercise this path: `ci-vercel-website-preview.yaml`
-receives an empty `VERCEL_TOKEN` for forks and fails at `vercel pull`
-before the build runs. Fork-safe PR interactions (the preview-URL
-comment) are handled by `pr-vercel-website-preview.yaml`.
-
-### Refreshing the snapshot
-
-When a maintainer wants to update the committed snapshot (e.g. after
-onboarding/offboarding roles):
-
-```bash
-WEBSITE_ASHBY_API_KEY=… WEBSITE_ASHBY_JOB_BOARD_NAME=comfy-org \
-  pnpm --filter @comfyorg/website ashby:refresh-snapshot
-git commit apps/website/src/data/ashby-roles.snapshot.json
-```
-
-The script exits non-zero on any non-fresh outcome so stale/empty
-snapshots can't be accidentally committed.
-
-## Cloud nodes integration
-
-`/cloud/supported-nodes` (and `/zh-CN/`) lists custom-node packs preinstalled on Comfy Cloud, joined with public metadata from the [ComfyUI Custom Node Registry](https://registry.comfy.org) ([`api.comfy.org`](https://api.comfy.org)). See [`src/pages/cloud/supported-nodes/AGENTS.md`](src/pages/cloud/supported-nodes/AGENTS.md) for the build pipeline, source-file map, and key invariants.
-
-Build-time env var: `WEBSITE_CLOUD_API_KEY` (Cloud `/api/object_info` auth; the build falls back to the committed snapshot when unset). Must also be set in the Vercel project environment.
-
-### Production strictness
-
-`src/utils/cloudNodes.build.ts` throws when `fetchCloudNodesForBuild()` returns
-`{ status: 'stale' }` **and** `process.env.VERCEL_ENV === 'production'`. This
-prevents the production deploy from silently shipping an out-of-date snapshot
-when the Cloud API is unreachable or `WEBSITE_CLOUD_API_KEY` is missing. Preview
-and local builds continue to use the committed snapshot with a warning
-annotation.
-
-### Required GitHub Actions / Vercel secrets
-
-| Name                    | Where                                           | Purpose                                                                |
-| ----------------------- | ----------------------------------------------- | ---------------------------------------------------------------------- |
-| `WEBSITE_CLOUD_API_KEY` | GitHub Actions repo secret + Vercel project env | Auth for Cloud `/api/object_info`. Required for fresh production data. |
-
-The `Release: Website` workflow uses the GitHub Actions secret to regenerate
-`apps/website/src/data/cloud-nodes.snapshot.json` via
-`.github/actions/cloud-nodes-pull/action.yaml`. The Vercel environment value is
-read at build time by `vercel build` in `ci-vercel-website-preview.yaml`; the
-`deploy-production` job hard-fails before `vercel build --prod` if the secret
-is missing.
-
-### Refreshing the snapshot
-
-To update the committed snapshot manually (e.g. after onboarding new packs
-to Comfy Cloud):
-
-```bash
-WEBSITE_CLOUD_API_KEY=… \
-  pnpm --filter @comfyorg/website cloud-nodes:refresh-snapshot
-git commit apps/website/src/data/cloud-nodes.snapshot.json
-```
-
-The script exits non-zero on any non-fresh outcome so stale/empty snapshots
-can't be accidentally committed. Otherwise the `Release: Website` GitHub
-Actions workflow runs the same step on every manual dispatch and opens a PR
-with the refreshed snapshot.
-
-## HubSpot contact form
-
-The contact page uses HubSpot's hosted form embed for the interest form:
-
-```html
-<script
-  src="https://js-na2.hsforms.net/forms/embed/developer/244637579.js"
-  defer
-></script>
-<div
-  class="hs-form-html"
-  data-region="na2"
-  data-form-id="94e05eab-1373-47f7-ab5e-d84f9e6aa262"
-  data-portal-id="244637579"
-></div>
-```
-
-The localized `/zh-CN/contact` page uses the same portal and script with form
-ID `6885750c-02ef-4aa2-ba0d-213be9cccf93`.
-
-This keeps submission handling, validation, anti-spam updates, and field
-configuration in HubSpot. The local implementation in
-`src/components/contact/HubspotFormEmbed.vue` only loads the hosted script and
-renders the documented embed container.
-
-## Scripts
-
-- `pnpm dev` — Astro dev server
-- `pnpm build` — production build to `dist/`
-- `pnpm typecheck` — `astro check`
-- `pnpm test:unit` — Vitest unit tests
-- `pnpm test:e2e` — Playwright E2E tests (requires `pnpm build` first)
-- `pnpm ashby:refresh-snapshot` — refresh the committed careers snapshot
-- `pnpm cloud-nodes:refresh-snapshot` — refresh the committed cloud nodes snapshot

apps/website/astro.config.ts

@@ -3,55 +3,16 @@ import sitemap from '@astrojs/sitemap'
 import vue from '@astrojs/vue'
 import tailwindcss from '@tailwindcss/vite'
 
-const LOCALES = ['en', 'zh-CN'] as const
-const DEFAULT_LOCALE = 'en'
-const PAYMENT_STATUSES = ['success', 'failed'] as const
-const LOCALE_PREFIXES = LOCALES.map((locale) =>
-  locale === DEFAULT_LOCALE ? '' : `/${locale}`
-)
-const SITEMAP_EXCLUDED_PATHNAMES = new Set(
-  LOCALE_PREFIXES.flatMap((prefix) =>
-    PAYMENT_STATUSES.map((status) => `${prefix}/payment/${status}`)
-  )
-)
-
-function isExcludedFromSitemap(page: string): boolean {
-  const pathname = new URL(page).pathname.replace(/\/$/, '')
-  return SITEMAP_EXCLUDED_PATHNAMES.has(pathname)
-}
-
 export default defineConfig({
   site: 'https://comfy.org',
   output: 'static',
-  prefetch: { prefetchAll: true },
-  redirects: {
-    '/cloud/enterprise-case-studies/comfyui-at-architectural-scale-how-moment-factory-reimagined-3d-projection-mapping':
-      '/customers/moment-factory/',
-    '/cloud/enterprise-case-studies/how-series-entertainment-rebuilt-game-and-video-production-with-comfyui':
-      '/customers/series-entertainment/',
-    '/zh-CN/terms-of-service': '/terms-of-service'
-  },
-  build: {
-    assets: '_website'
-  },
-  devToolbar: { enabled: !process.env.NO_TOOLBAR },
-  integrations: [
-    vue(),
-    sitemap({
-      filter: (page) => !isExcludedFromSitemap(page)
-    })
-  ],
+  integrations: [vue(), sitemap()],
   vite: {
-    plugins: [tailwindcss()],
-    server: {
-      watch: {
-        ignored: ['**/playwright-report/**']
-      }
-    }
+    plugins: [tailwindcss()]
   },
   i18n: {
-    locales: [...LOCALES],
-    defaultLocale: DEFAULT_LOCALE,
+    locales: ['en', 'zh-CN'],
+    defaultLocale: 'en',
     routing: {
       prefixDefaultLocale: false
     }

apps/website/components.json

@@ -1,24 +0,0 @@
-{
-  "$schema": "https://shadcn-vue.com/schema.json",
-  "style": "new-york",
-  "font": "inter",
-  "typescript": true,
-  "tailwind": {
-    "config": "",
-    "css": "src/styles/global.css",
-    "baseColor": "neutral",
-    "cssVariables": true,
-    "prefix": ""
-  },
-  "iconLibrary": "lucide",
-  "rtl": false,
-  "pointer": true,
-  "aliases": {
-    "components": "@/components",
-    "utils": "@/lib/utils",
-    "ui": "@/components/ui",
-    "lib": "@/lib",
-    "composables": "@/composables"
-  },
-  "registries": {}
-}

apps/website/e2e/affiliates-terms.spec.ts

@@ -1,140 +0,0 @@
-import { expect } from '@playwright/test'
-
-import { test } from './fixtures/blockExternalMedia'
-
-const PATH = '/affiliates/terms'
-
-const SECTION_IDS = [
-  '1-program-overview',
-  '2-eligible-products',
-  '3-commission-structure',
-  '4-attribution-rules',
-  '5-prohibited-activities',
-  '6-content-guidelines',
-  '7-termination',
-  '8-program-modifications',
-  '9-indemnification',
-  '10-governing-law',
-  '11-miscellaneous'
-] as const
-
-test.describe('Affiliate Terms — desktop @smoke', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('renders heading and is indexable', async ({ page }) => {
-    await expect(
-      page.getByRole('heading', { name: 'Affiliate Terms', level: 1 })
-    ).toBeVisible()
-
-    await expect(page.locator('meta[name="robots"]')).toHaveCount(0)
-  })
-
-  test('exposes one anchor per legal section in order', async ({ page }) => {
-    for (const id of SECTION_IDS) {
-      await expect(page.locator(`[id="${id}"]`)).toBeAttached()
-    }
-
-    const orderedIds = await page.evaluate(
-      (ids) => {
-        const elements = ids
-          .map((id) => document.getElementById(id))
-          .filter((el): el is HTMLElement => el !== null)
-        return elements
-          .slice()
-          .sort((a, b) => {
-            const relation = a.compareDocumentPosition(b)
-            if (relation & Node.DOCUMENT_POSITION_FOLLOWING) return -1
-            if (relation & Node.DOCUMENT_POSITION_PRECEDING) return 1
-            return 0
-          })
-          .map((el) => el.id)
-      },
-      [...SECTION_IDS]
-    )
-    expect(orderedIds).toEqual([...SECTION_IDS])
-  })
-
-  test('renders an effective date footer', async ({ page }) => {
-    await expect(page.getByText(/Effective Date:/)).toBeVisible()
-  })
-
-  test('skips internal-only sections (competitive analysis, open questions)', async ({
-    page
-  }) => {
-    await expect(page.getByText(/Competitive analysis/i)).toHaveCount(0)
-    await expect(
-      page.getByText(/Open questions for legal review/i)
-    ).toHaveCount(0)
-  })
-})
-
-test.describe('Affiliate Terms — desktop interactions', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('clicking a desktop TOC link scrolls to the matching section', async ({
-    page
-  }) => {
-    const desktopToc = page.getByRole('navigation', { name: 'On this page' })
-    await expect(desktopToc).toBeVisible()
-
-    const link = desktopToc.getByRole('link', { name: /5\. Prohibited/ })
-    await link.click()
-
-    const target = page.locator('[id="5-prohibited-activities"]')
-    await expect(target).toBeInViewport()
-  })
-
-  test('clicking a TOC link updates the URL hash so the section is shareable', async ({
-    page
-  }) => {
-    const desktopToc = page.getByRole('navigation', { name: 'On this page' })
-    await desktopToc.getByRole('link', { name: /7\. Termination/ }).click()
-
-    await expect
-      .poll(() => page.evaluate(() => window.location.hash))
-      .toBe('#7-termination')
-  })
-})
-
-test.describe('Affiliate Terms — mobile @mobile', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('shows a collapsed accordion TOC by default', async ({ page }) => {
-    const accordion = page.locator('details', {
-      has: page.getByText('On this page')
-    })
-    await expect(accordion).toBeVisible()
-    await expect(accordion).not.toHaveAttribute('open', '')
-  })
-
-  test('expanding the accordion reveals every section link', async ({
-    page
-  }) => {
-    const accordion = page.locator('details', {
-      has: page.getByText('On this page')
-    })
-    await accordion.locator('summary').click()
-    await expect(accordion).toHaveAttribute('open', '')
-
-    for (const id of SECTION_IDS) {
-      await expect(accordion.locator(`a[href="#${id}"]`).first()).toBeVisible()
-    }
-  })
-
-  test('headings remain readable at narrow viewports without horizontal overflow', async ({
-    page
-  }) => {
-    const heading = page.getByRole('heading', { name: '1. Program Overview' })
-    await expect(heading).toBeVisible()
-    const box = await heading.boundingBox()
-    expect(box, 'heading box').not.toBeNull()
-    expect(box!.x).toBeGreaterThanOrEqual(0)
-    expect(box!.x + box!.width).toBeLessThanOrEqual(page.viewportSize()!.width)
-  })
-})

apps/website/e2e/affiliates.spec.ts

@@ -1,148 +0,0 @@
-import { expect } from '@playwright/test'
-
-import { affiliateFaqs } from '../src/data/affiliateFaq'
-import { t } from '../src/i18n/translations'
-import { test } from './fixtures/blockExternalMedia'
-
-const PATH = '/affiliates'
-const APPLY_URL = 'https://forms.gle/RS8L2ttcuGap4Q1v6'
-const TERMS_PATH = '/affiliates/terms'
-const FAQ_COUNT = affiliateFaqs.length
-const FIRST_FAQ = affiliateFaqs[0]
-const HERO_HEADING_TEXT = `${t('affiliate.hero.headingHighlight', 'en')} ${t('affiliate.hero.headingMuted', 'en')}`
-const CTA_HEADING_TEXT = t('affiliate.cta.heading', 'en')
-const CTA_APPLY_LABEL = t('affiliate.cta.apply', 'en')
-const CTA_TERMS_LABEL = t('affiliate.cta.termsLabel', 'en')
-
-test.describe('Affiliates landing — desktop @smoke', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('renders the hero heading and is indexable', async ({ page }) => {
-    await expect(
-      page.getByRole('heading', { level: 1, name: HERO_HEADING_TEXT })
-    ).toBeVisible()
-
-    await expect(page.locator('meta[name="robots"]')).toHaveCount(0)
-  })
-
-  test('renders the closing CTA heading and apply button', async ({ page }) => {
-    const ctaSection = page.locator('section').filter({
-      has: page.getByRole('heading', { level: 2, name: CTA_HEADING_TEXT })
-    })
-    const ctaHeading = ctaSection.getByRole('heading', {
-      level: 2,
-      name: CTA_HEADING_TEXT
-    })
-    await ctaHeading.scrollIntoViewIfNeeded()
-    await expect(ctaHeading).toBeVisible()
-
-    const applyButton = ctaSection.getByRole('link', { name: CTA_APPLY_LABEL })
-    await expect(applyButton).toBeVisible()
-    await expect(applyButton).toHaveAttribute('href', APPLY_URL)
-    await expect(applyButton).toHaveAttribute('target', '_blank')
-    await expect(applyButton).toHaveAttribute('rel', 'noopener noreferrer')
-  })
-
-  test('CTA section links to the affiliate terms page in the same tab', async ({
-    page
-  }) => {
-    const termsLink = page.getByRole('link', { name: CTA_TERMS_LABEL })
-    await termsLink.scrollIntoViewIfNeeded()
-    await expect(termsLink).toBeVisible()
-    await expect(termsLink).toHaveAttribute('href', TERMS_PATH)
-    await expect(termsLink).not.toHaveAttribute('target', '_blank')
-  })
-})
-
-test.describe('Affiliates landing — desktop interactions', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('emits FAQPage structured data with one entry per FAQ', async ({
-    page
-  }) => {
-    const faqJsonLd = await page.evaluate(() => {
-      const scripts = Array.from(
-        document.querySelectorAll<HTMLScriptElement>(
-          'script[type="application/ld+json"]'
-        )
-      )
-      const match = scripts.find((s) =>
-        (s.textContent ?? '').includes('FAQPage')
-      )
-      return match?.textContent ?? null
-    })
-    expect(faqJsonLd, 'FAQ JSON-LD script').not.toBeNull()
-    const parsed = JSON.parse(faqJsonLd!)
-    expect(parsed['@type']).toBe('FAQPage')
-    expect(Array.isArray(parsed.mainEntity)).toBe(true)
-    expect(parsed.mainEntity.length).toBe(FAQ_COUNT)
-  })
-
-  test('Apply Now CTA opens the application form in a new tab', async ({
-    page,
-    context
-  }) => {
-    const ctaSection = page.locator('section').filter({
-      has: page.getByRole('heading', { level: 2, name: CTA_HEADING_TEXT })
-    })
-    const applyButton = ctaSection.getByRole('link', { name: CTA_APPLY_LABEL })
-    await applyButton.scrollIntoViewIfNeeded()
-
-    const popupPromise = context.waitForEvent('page')
-    await applyButton.click()
-    const popup = await popupPromise
-    await popup.waitForLoadState('domcontentloaded')
-    const popupUrl = popup.url()
-    expect(
-      popupUrl.includes('forms.gle/RS8L2ttcuGap4Q1v6') ||
-        popupUrl.includes('docs.google.com/forms')
-    ).toBe(true)
-    await popup.close()
-  })
-
-  test('FAQ items toggle open and closed on click', async ({ page }) => {
-    const firstQuestion = page.getByRole('button', {
-      name: FIRST_FAQ.question.en
-    })
-    await firstQuestion.scrollIntoViewIfNeeded()
-    await expect(firstQuestion).toHaveAttribute('aria-expanded', 'false')
-
-    await firstQuestion.click()
-    await expect(firstQuestion).toHaveAttribute('aria-expanded', 'true')
-    await expect(page.getByText(FIRST_FAQ.answer.en)).toBeVisible()
-
-    await firstQuestion.click()
-    await expect(firstQuestion).toHaveAttribute('aria-expanded', 'false')
-  })
-})
-
-test.describe('Affiliates landing — mobile @mobile', () => {
-  test.beforeEach(async ({ page }) => {
-    await page.goto(PATH)
-  })
-
-  test('renders the hero heading at narrow viewports', async ({ page }) => {
-    await expect(
-      page.getByRole('heading', { level: 1, name: HERO_HEADING_TEXT })
-    ).toBeVisible()
-  })
-
-  test('closing CTA stays within the viewport width', async ({ page }) => {
-    const ctaHeading = page.getByRole('heading', {
-      level: 2,
-      name: CTA_HEADING_TEXT
-    })
-    await ctaHeading.scrollIntoViewIfNeeded()
-    await expect(ctaHeading).toBeVisible()
-
-    const box = await ctaHeading.boundingBox()
-    expect(box, 'CTA heading bounding box').not.toBeNull()
-    expect(box!.x + box!.width).toBeLessThanOrEqual(
-      page.viewportSize()!.width + 1
-    )
-  })
-})