export generateUUID

.agents/checks/accessibility.md

@@ -1,28 +0,0 @@
----
-name: accessibility
-description: Reviews UI code for WCAG 2.2 AA accessibility violations
-severity-default: medium
-tools: [Read, Grep]
----
-
-You are an accessibility auditor reviewing a code diff for WCAG 2.2 AA compliance. Focus on UI changes that affect users with disabilities.
-
-Check for:
-
-1. **Missing form labels** - inputs, selects, textareas without associated `<label>` or `aria-label`/`aria-labelledby`
-2. **Missing alt text** - images without `alt` attributes, or decorative images missing `alt=""`
-3. **Keyboard navigation** - interactive elements not focusable, custom widgets missing keyboard handlers (Enter, Space, Escape, Arrow keys), focus traps without escape
-4. **Focus management** - modals/dialogs that don't trap focus, dynamic content that doesn't move focus appropriately, removed elements without focus recovery
-5. **ARIA misuse** - invalid `aria-*` attributes, roles without required children/properties, `aria-hidden` on focusable elements
-6. **Color as sole indicator** - using color alone to convey meaning (errors, status) without text/icon alternative
-7. **Touch targets** - interactive elements smaller than 24x24 CSS pixels (WCAG 2.2 SC 2.5.8)
-8. **Screen reader support** - dynamic content changes without `aria-live` announcements, unlabeled icon buttons, links with only "click here"
-9. **Heading hierarchy** - skipped heading levels (h1 → h3), missing page landmarks
-
-Rules:
-
-- Focus on NEW or CHANGED UI in the diff — do not audit the entire existing codebase
-- Only flag issues in .vue, .tsx, .jsx, .html, or template-containing files
-- Skip non-UI files entirely (stores, services, utils)
-- Skip canvas-based content: the LiteGraph node editor renders on `<canvas>` elements, not DOM-based UI. WCAG rules don't fully apply to canvas rendering internals — only audit the DOM-based controls around it (toolbars, panels, dialogs)
-- "Critical" for completely inaccessible interactive elements, "major" for missing labels/ARIA, "minor" for enhancement opportunities

.agents/checks/api-contract.md

@@ -1,35 +0,0 @@
----
-name: api-contract
-description: Catches breaking changes to public interfaces, window-exposed APIs, event contracts, and exported symbols
-severity-default: high
-tools: [Grep, Read, glob]
----
-
-You are an API contract reviewer. Your job is to catch breaking changes and contract violations in public-facing interfaces.
-
-## What to Check
-
-1. **Breaking changes to globally exposed APIs** — anything on `window` or other global objects that consumers depend on. Renamed properties, removed methods, changed signatures, changed return types.
-2. **Event contract changes** — renamed events, changed event payloads, removed events that listeners may depend on.
-3. **Changed function signatures** — parameters reordered, required params added, return type changed on exported functions.
-4. **Removed or renamed exports** — any `export` that was previously available and is now gone or renamed without a re-export alias.
-5. **REST API changes** — changed endpoints, added required fields, removed response fields, changed status codes.
-6. **Type contract narrowing** — a function that used to accept `string | number` now only accepts `string`, or a return type that narrows unexpectedly.
-7. **Default value changes** — changing defaults on optional parameters that consumers may rely on.
-8. **Store/state shape changes** — renamed store properties, changed state structure that computed properties or watchers may depend on.
-
-## How to Identify the Public API
-
-- Check `package.json` for `"exports"` or `"main"` fields.
-- **Window globals**: This repo exposes LiteGraph classes on `window` (e.g., `window['LiteGraph']`, `window['LGraphNode']`, `window['LGraphCanvas']`) and `window['__COMFYUI_FRONTEND_VERSION__']`. These are consumed by custom node extensions and must not be renamed or removed.
-- **Extension hooks**: The `app` object and its extension registration system (`app.registerExtension`) is a public contract for third-party custom nodes. Changes to `ComfyApp`, `ComfyApi`, or the extension lifecycle are breaking changes.
-- Check AGENTS.md for project-specific API surface definitions.
-- Any exported symbol from common entry points (e.g., `src/types/index.ts`) should be treated as potentially public.
-
-## Rules
-
-- ONLY flag changes that break existing consumers.
-- Do NOT flag additions (new methods, new exports, new endpoints).
-- Do NOT flag internal/private API changes.
-- Always check if a re-export or compatibility shim was added before flagging.
-- Critical for removed/renamed globals, high for changed export signatures, medium for changed defaults.

.agents/checks/architecture-reviewer.md

@@ -1,27 +0,0 @@
----
-name: architecture-reviewer
-description: Reviews code for architectural issues like over-engineering, SOLID violations, coupling, and API design
-severity-default: medium
-tools: [Grep, Read, glob]
----
-
-You are a software architect reviewing a code diff. Focus on structural and design issues.
-
-## What to Check
-
-1. **Over-engineering** — abstractions for single-use cases, premature generalization, unnecessary indirection layers
-2. **SOLID violations** — god classes, mixed responsibilities, rigid coupling, interface segregation issues
-3. **Separation of concerns** — business logic in UI components, data access in controllers, mixed layers
-4. **API design** — inconsistent interfaces, leaky abstractions, unclear contracts
-5. **Coupling** — tight coupling between modules, circular dependencies, feature envy
-6. **Consistency** — breaking established patterns without justification, inconsistent approaches to similar problems
-7. **Dependency direction** — imports going the wrong way in the architecture, lower layers depending on higher
-8. **Change amplification** — designs requiring changes in many places for simple feature additions
-
-## Rules
-
-- Focus on structural issues that affect maintainability and evolution.
-- Do NOT report bugs, security, or performance issues (other checks handle those).
-- Consider whether the code is proportional to the problem it solves.
-- "Under-engineering" (missing useful abstractions) is as valid as over-engineering.
-- Rate severity by impact on future maintainability.

.agents/checks/bug-hunter.md

@@ -1,34 +0,0 @@
----
-name: bug-hunter
-description: Finds logic errors, off-by-ones, null safety issues, race conditions, and edge cases
-severity-default: high
-tools: [Read, Grep]
----
-
-You are a bug hunter reviewing a code diff. Your ONLY job is to find bugs - logic errors that will cause incorrect behavior at runtime.
-
-Focus areas:
-
-1. **Off-by-one errors** in loops, slices, and indices
-2. **Null/undefined dereferences** - any path where a value could be null but isn't checked
-3. **Race conditions** - shared mutable state, async ordering assumptions
-4. **Edge cases** - empty arrays, zero values, empty strings, boundary conditions
-5. **Type coercion bugs** - loose equality, implicit conversions
-6. **Error handling gaps** - unhandled promise rejections, swallowed errors
-7. **State mutation bugs** - mutating props, shared references, stale closures
-8. **Incorrect boolean logic** - flipped conditions, missing negation, wrong operator precedence
-
-Rules:
-
-- ONLY report actual bugs that will cause wrong behavior
-- Do NOT report style issues, naming, or performance
-- Do NOT report hypothetical bugs that require implausible inputs
-- Each finding must explain the specific runtime failure scenario
-
-## Repo-Specific Bug Patterns
-
-- `z.any()` in Zod schemas disables validation and propagates `any` into TypeScript types — always flag
-- Destructuring reactive objects (props, reactive()) without `toRefs()` loses reactivity — flag outside of `defineProps` destructuring
-- `ComputedRef<T>` exposed via `defineExpose` or public API should be unwrapped first
-- LiteGraph node operations: check for missing null guards on `node.graph` (can be null when node is removed)
-- Watch/watchEffect without cleanup for side effects (timers, listeners) — leak on component unmount

.agents/checks/coderabbit.md

@@ -1,50 +0,0 @@
----
-name: coderabbit
-description: Runs CodeRabbit CLI for AST-aware code quality review
-severity-default: medium
-tools: [Bash, Read]
----
-
-Run CodeRabbit CLI review on the current changes.
-
-## Steps
-
-1. Check if CodeRabbit CLI is installed:
-
-   ```bash
-   which coderabbit
-   ```
-
-   If not installed, skip this check and report:
-   "Skipped: CodeRabbit CLI not installed. Install and authenticate:
-
-   ```
-   npm install -g coderabbit
-   coderabbit auth login
-   ```
-
-   See https://docs.coderabbit.ai/guides/cli for setup."
-
-2. Run review:
-
-   ```bash
-   coderabbit --prompt-only --type uncommitted
-   ```
-
-   If there are committed but unpushed changes, use `--type committed` instead.
-
-3. Parse CodeRabbit's output. Each finding should include:
-   - File path and line number
-   - Severity mapped from CodeRabbit's own levels
-   - Category (logic, security, performance, style, test, architecture, dx)
-   - Description and suggested fix
-
-## Rate Limiting
-
-If a rate limit is hit, skip and note it. Prefer reading the current quota from CLI/API output rather than assuming a fixed reviews/hour limit.
-
-## Error Handling
-
-- Auth expired: skip and report "CodeRabbit auth expired, run: coderabbit auth login"
-- CLI timeout (>120s): skip and note
-- Parse error: return raw output with a warning

.agents/checks/complexity.md

@@ -1,28 +0,0 @@
----
-name: complexity
-description: Reviews code for excessive complexity and suggests refactoring opportunities
-severity-default: medium
-tools: [Grep, Read, glob]
----
-
-You are a complexity and refactoring advisor reviewing a code diff. Focus on code that is unnecessarily complex and will be hard to maintain.
-
-## What to Check
-
-1. **High cyclomatic complexity** — functions with many branching paths (if/else chains, switch statements with >7 cases, nested ternaries). Threshold: complexity >10 is high severity, >15 is critical.
-2. **Deep nesting** — code nested >4 levels deep (nested if/for/try blocks). Suggest guard clauses, early returns, or extraction.
-3. **Oversized functions** — functions >50 lines that do multiple things. Suggest extraction of cohesive sub-functions.
-4. **God classes/modules** — files >500 lines mixing multiple responsibilities. Suggest splitting by concern.
-5. **Long parameter lists** — functions with >5 parameters. Suggest parameter objects or builder patterns.
-6. **Complex boolean expressions** — conditions with >3 clauses that are hard to parse. Suggest extracting to named boolean variables.
-7. **Feature envy** — methods that use data from another class more than their own, suggesting the method belongs elsewhere.
-8. **Duplicate logic** — two or more code blocks in the diff doing essentially the same thing with minor variations.
-9. **Unnecessary indirection** — wrapper functions that add no value, abstractions for single-use cases, premature generalization.
-
-## Rules
-
-- Only flag complexity in NEW or SIGNIFICANTLY CHANGED code.
-- Do NOT suggest refactoring stable, well-tested code that happens to be complex.
-- Do NOT flag complexity that is inherent to the problem domain (e.g., state machines, protocol handlers).
-- Provide a concrete refactoring approach, not just "this is too complex".
-- High severity for code that will likely cause bugs during future modifications, medium for readability improvements, low for optional simplifications.

.agents/checks/ddd-structure.md

@@ -1,86 +0,0 @@
----
-name: ddd-structure
-description: Reviews whether new code is placed in the right domain/layer and follows domain-driven structure principles
-severity-default: medium
-tools: [Grep, Read, glob]
----
-
-You are a domain-driven design reviewer. Your job is to check whether new or moved code is placed in the correct architectural layer and domain folder.
-
-## Principles
-
-1. **Domain over Technical Layer** — code should be organized by what it does (domain/feature), not by what it is (component/service/store). New files in flat technical folders like `src/components/`, `src/services/`, `src/stores/`, `src/utils/` are a smell if the repo already has domain folders.
-
-2. **Cohesion** — files that change together should live together. A component, its store, its service, and its types for a single feature should be co-located.
-
-3. **Import Direction** — lower layers must not import from higher layers. Check that imports flow in the allowed direction (see Layer Architecture below).
-
-4. **Bounded Contexts** — each domain/feature should have clear boundaries. Cross-domain imports should go through public interfaces, not reach into internal files.
-
-5. **Naming** — folders and files should reflect domain concepts, not technical roles. `workflowExecution.ts` > `service.ts`.
-
-## Layer Architecture
-
-This repo uses a VSCode-style layered architecture with strict unidirectional imports:
-
-```
-base → platform → workbench → renderer
-```
-
-| Layer        | Purpose                                | Can Import From                    |
-| ------------ | -------------------------------------- | ---------------------------------- |
-| `base/`      | Pure utilities, no framework deps      | Nothing                            |
-| `platform/`  | Core domain services, business logic   | `base/`                            |
-| `workbench/` | Features, workspace orchestration      | `base/`, `platform/`               |
-| `renderer/`  | UI layer (Vue components, composables) | `base/`, `platform/`, `workbench/` |
-
-### Import Direction Violations to Check
-
-```bash
-# platform must NOT import from workbench or renderer
-grep -r "from '@/renderer'" src/platform/ --include="*.ts" --include="*.vue"
-grep -r "from '@/workbench'" src/platform/ --include="*.ts" --include="*.vue"
-# base must NOT import from platform, workbench, or renderer
-grep -r "from '@/platform'" src/base/ --include="*.ts" --include="*.vue"
-grep -r "from '@/workbench'" src/base/ --include="*.ts" --include="*.vue"
-grep -r "from '@/renderer'" src/base/ --include="*.ts" --include="*.vue"
-# workbench must NOT import from renderer
-grep -r "from '@/renderer'" src/workbench/ --include="*.ts" --include="*.vue"
-```
-
-### Legacy Flat Folders
-
-Flag NEW files added to these legacy flat folders (they should go in a domain folder under the appropriate layer instead):
-
-- `src/components/` → should be in `src/renderer/` or `src/workbench/extensions/{feature}/components/`
-- `src/stores/` → should be in `src/platform/{domain}/` or `src/workbench/extensions/{feature}/stores/`
-- `src/services/` → should be in `src/platform/{domain}/`
-- `src/composables/` → should be in `src/renderer/` or `src/platform/{domain}/ui/`
-
-Do NOT flag modifications to existing files in legacy folders — only flag NEW files.
-
-## How to Review
-
-1. Look at the diff to see where new files are created or where code is added.
-2. Check if the repo has an established domain folder structure (look for domain-organized directories like `src/platform/`, `src/workbench/`, `src/renderer/`, `src/base/`, or similar).
-3. If domain folders exist but new code was placed in a flat technical folder, flag it.
-4. Run import direction checks:
-   - Use `Grep` or `Read` to check if new imports violate layer boundaries.
-   - Flag any imports from a higher layer to a lower one using the rules above.
-5. Check for new files in legacy flat folders and flag them per the Legacy Flat Folders section.
-
-## Generic Checks (when no domain structure is detected)
-
-- God files (>500 lines mixing concerns)
-- Circular imports between modules
-- Business logic in UI components
-
-## Severity Guidelines
-
-| Issue                                                         | Severity |
-| ------------------------------------------------------------- | -------- |
-| Import direction violation (lower layer imports higher layer) | high     |
-| New file in legacy flat folder when domain folders exist      | medium   |
-| Business logic in UI component                                | medium   |
-| Missing domain boundary (cross-cutting import into internals) | low      |
-| Naming uses technical role instead of domain concept          | low      |

.agents/checks/dep-secrets-scan.md

@@ -1,66 +0,0 @@
----
-name: dep-secrets-scan
-description: Runs dependency vulnerability audit and secrets detection
-severity-default: critical
-tools: [Bash, Read]
----
-
-Run dependency audit and secrets scan to detect known CVEs in dependencies and leaked secrets in code.
-
-## Steps
-
-1. Check which tools are available:
-
-   ```bash
-   pnpm --version
-   gitleaks version
-   ```
-
-   - If **neither** is installed, skip this check and report: "Skipped: neither pnpm nor gitleaks installed. Install pnpm: `npm i -g pnpm`. Install gitleaks: `brew install gitleaks` or see https://github.com/gitleaks/gitleaks#installing"
-   - If only one is available, run that one and note the other was skipped.
-
-2. **Dependency audit** (if pnpm is available):
-
-   ```bash
-   pnpm audit --json 2>/dev/null || true
-   ```
-
-   Parse the JSON output. Map advisory severity:
-   - `critical` advisory → `critical`
-   - `high` advisory → `major`
-   - `moderate` advisory → `minor`
-   - `low` advisory → `nitpick`
-
-   Report each finding with: package name, version, advisory title, CVE, and suggested patched version.
-
-3. **Secrets detection** (if gitleaks is available):
-
-   ```bash
-   gitleaks detect --no-banner --report-format json --source . 2>/dev/null || true
-   ```
-
-   Parse the JSON output. All secret findings are `critical` severity.
-
-   Report each finding with: file and line, rule description, and a redacted match. Always suggest removing the secret and rotating credentials.
-
-## What This Catches
-
-### Dependency Audit
-
-- Known CVEs in direct and transitive dependencies
-- Vulnerable packages from the npm advisory database
-
-### Secrets Detection
-
-- API keys and tokens in code
-- AWS credentials, GCP service account keys
-- Database connection strings with passwords
-- Private keys and certificates
-- Generic high-entropy secrets
-
-## Error Handling
-
-- If pnpm audit fails, log the error and continue with gitleaks.
-- If gitleaks fails, log the error and continue with audit results.
-- If JSON parsing fails for either tool, include raw output with a warning.
-- If both tools produce no findings, report "No issues found."

.agents/checks/doc-freshness.md

@@ -1,40 +0,0 @@
----
-name: doc-freshness
-description: Reviews whether code changes are reflected in documentation
-severity-default: medium
-tools: [Read, Grep]
----
-
-You are a documentation freshness reviewer. Your job is to check whether code changes are properly reflected in documentation, and whether new features need documentation.
-
-Check for:
-
-1. **Stale README sections** - code changes that invalidate setup instructions, API examples, or architecture descriptions in README.md
-2. **Outdated code comments** - comments referencing removed functions, old parameter names, previous behavior, or TODO items that are now done
-3. **Missing JSDoc on public APIs** - exported functions, classes, or interfaces without JSDoc descriptions, especially those used by consumers of the library
-4. **Changed behavior without changelog** - user-facing behavior changes that should be noted in a changelog or release notes
-5. **Dead documentation links** - links in markdown files pointing to moved or deleted files
-6. **Missing migration guidance** - breaking changes without upgrade instructions
-
-Rules:
-
-- Focus on documentation that needs to CHANGE due to the diff — don't audit all existing docs
-- Do NOT flag missing comments on internal/private functions
-- Do NOT flag missing changelog entries for purely internal refactors
-- "Major" for stale docs that will mislead users, "minor" for missing JSDoc on public APIs, "nitpick" for minor doc improvements
-
-## ComfyUI_frontend Documentation
-
-This repository's public APIs are used by custom node and extension authors. Documentation lives at [docs.comfy.org](https://docs.comfy.org) (repo: Comfy-Org/docs).
-
-For any NEW API, event, hook, or configuration that extensions or custom nodes can use:
-
-- Flag with a suggestion to open a PR to Comfy-Org/docs to document the new API
-- Example: "This new extension API should be documented at docs.comfy.org — consider opening a PR to Comfy-Org/docs"
-
-For changes to existing extension-facing APIs:
-
-- Check if the existing docs at docs.comfy.org may need updating
-- Flag stale references in CONTRIBUTING.md or developer guides
-
-Anything relevant to custom extension authors should trigger a documentation suggestion.

.agents/checks/dx-readability.md

@@ -1,25 +0,0 @@
----
-name: dx-readability
-description: Reviews code for developer experience issues including naming clarity, cognitive complexity, dead code, and confusing patterns
-severity-default: low
-tools: [Read, Grep]
----
-
-You are a developer experience reviewer. Focus on code that will confuse the next developer who reads it.
-
-Check for:
-
-1. **Unclear naming** - variables/functions that don't communicate intent, abbreviations, misleading names
-2. **Cognitive complexity** - deeply nested conditions, long functions doing multiple things, complex boolean expressions
-3. **Dead code** - unreachable branches, unused variables, commented-out code, vestigial parameters
-4. **Confusing patterns** - clever tricks over simple code, implicit behavior, action-at-a-distance, surprising side effects
-5. **Missing context** - complex business logic without explaining why, non-obvious algorithms without comments
-6. **Inconsistent abstractions** - mixing raw and wrapped APIs, different error handling styles in same module
-7. **Implicit knowledge** - code that only works because of undocumented assumptions or conventions
-
-Rules:
-
-- Only flag things that would genuinely confuse a competent developer
-- Do NOT flag established project conventions even if you'd prefer different ones
-- "Minor" for things that slow comprehension, "nitpick" for pure style preferences
-- Major is reserved for genuinely misleading code (names that lie, silent behavior changes)

.agents/checks/ecosystem-compat.md

@@ -1,58 +0,0 @@
----
-name: ecosystem-compat
-description: Checks whether changes break exported symbols that downstream consumers may depend on
-severity-default: high
-tools: [Grep, Read, glob, mcp__comfy_codesearch__search_code]
----
-
-Check whether this PR introduces breaking changes to exported symbols that downstream consumers may depend on.
-
-## What to Check
-
-- Renamed or removed exported functions/classes/types
-- Changed function signatures (parameters added/removed/reordered)
-- Changed return types
-- Removed or renamed CSS classes used for selectors
-- Changed event names or event payload shapes
-- Changed global registrations or extension hooks
-- Modified integration points with external systems
-
-## Method
-
-1. Read the diff and identify any changes to exported symbols.
-2. For each potentially breaking change, try to determine if downstream consumers exist:
-   - If `mcp__comfy_codesearch__search_code` is available, search for usages of the changed symbol across downstream repositories.
-   - Otherwise, use `Grep` to search for usages within the current repository and note that external usage could not be verified.
-3. If consumers are found using the changed API, report it as a finding.
-
-## Severity Guidelines
-
-| Ecosystem Usage | Severity | Guidance                                                     |
-| --------------- | -------- | ------------------------------------------------------------ |
-| 5+ consumers    | critical | Must address before merge                                    |
-| 2-4 consumers   | high     | Should address or document                                   |
-| 1 consumer      | medium   | Note in PR, author decides                                   |
-| 0 consumers     | low      | Note potential risk only                                     |
-| Unknown usage   | medium   | Require explicit note that external usage was not verifiable |
-
-## Suggestion Template
-
-When a breaking change is found, suggest:
-
-- Keeping the old export alongside the new one
-- Adding a deprecation wrapper
-- Explicitly noting this as a breaking change in the PR description so consumers can update
-
-## ComfyUI Code Search MCP
-
-This check works best with the ComfyUI code search MCP tool, which searches across all custom node repositories for usage of changed symbols.
-
-If the `mcp__comfy_codesearch__search_code` tool is not available, install it:
-
-```
-amp mcp add comfy-codesearch https://comfy-codesearch.vercel.app/api/mcp
-# OR for Claude Code:
-claude mcp add -t http comfy-codesearch https://comfy-codesearch.vercel.app/api/mcp
-```
-
-Without this MCP, the check will fall back to searching within the current repository only, and cannot verify external ecosystem usage.

.agents/checks/error-handling.md

@@ -1,38 +0,0 @@
----
-name: error-handling
-description: Reviews error handling patterns for empty catches, swallowed errors, missing async error handling, and generic error UX
-severity-default: high
-tools: [Read, Grep]
----
-
-You are an error handling auditor reviewing a code diff. Focus exclusively on how errors are handled, propagated, and surfaced.
-
-Check for:
-
-1. **Empty catch blocks** - errors caught and silently swallowed with no logging or re-throw
-2. **Generic catches** - catching all errors without distinguishing types, losing context
-3. **Missing async error handling** - unhandled promise rejections, async functions without try/catch or .catch()
-4. **Swallowed errors** - errors caught and replaced with a return value that hides the failure
-5. **Missing error boundaries** - Vue/React component trees without error boundaries around risky subtrees
-6. **No retry or fallback** - network calls, file I/O, or external service calls with no retry logic or graceful degradation
-7. **Generic error UX** - user-facing code showing "Something went wrong" without actionable guidance or error codes
-8. **Missing cleanup on error** - resources (connections, file handles, timers) not cleaned up in error paths
-9. **Error propagation breaks** - catching errors mid-chain and not re-throwing, breaking caller's ability to handle
-
-Rules:
-
-- Focus on NEW or CHANGED error handling in the diff
-- Do NOT flag existing error handling patterns in untouched code
-- Do NOT suggest adding error handling to code that legitimately cannot fail (pure functions, type-safe internal calls)
-- "Critical" for swallowed errors in data-mutation paths, "major" for missing error handling on external calls, "minor" for missing logging
-
-## Repo-Specific Error Handling
-
-- User-facing error messages must be actionable and friendly (per AGENTS.md)
-- Use the shared `useErrorHandling` composable (`src/composables/useErrorHandling.ts`) for centralized error handling:
-  - `wrapWithErrorHandling` / `wrapWithErrorHandlingAsync` automatically catch errors and surface them as toast notifications via `useToastStore`
-  - `toastErrorHandler` can be used directly for custom error handling flows
-  - Supports `ErrorRecoveryStrategy` for retry/fallback patterns (e.g., reauthentication, network reconnect)
-- API errors from `api.get()`/`api.post()` should be caught and surfaced to the user via `useToastStore` (`src/platform/updates/common/toastStore.ts`)
-- Electron/desktop code paths: IPC errors should be caught and not crash the renderer process
-- Workflow execution errors should be displayed in the UI status bar, not silently swallowed

.agents/checks/eslint.strict.config.js

@@ -1,60 +0,0 @@
-/**
- * Strict ESLint config for the sonarjs-lint review check.
- *
- * Uses eslint-plugin-sonarjs to get SonarQube-grade analysis without a server.
- * This config is NOT used for regular development linting — only for the
- * code review checks' static analysis pass.
- *
- * Install: pnpm add -D eslint eslint-plugin-sonarjs
- * Run:     pnpm dlx eslint --no-config-lookup --config .agents/checks/eslint.strict.config.js --ext .ts,.js,.vue {files}
- */
-
-import sonarjs from 'eslint-plugin-sonarjs'
-
-export default [
-  sonarjs.configs.recommended,
-  {
-    plugins: {
-      sonarjs
-    },
-    rules: {
-      // Bug detection
-      'sonarjs/no-all-duplicated-branches': 'error',
-      'sonarjs/no-element-overwrite': 'error',
-      'sonarjs/no-identical-conditions': 'error',
-      'sonarjs/no-identical-expressions': 'error',
-      'sonarjs/no-one-iteration-loop': 'error',
-      'sonarjs/no-use-of-empty-return-value': 'error',
-      'sonarjs/no-collection-size-mischeck': 'error',
-      'sonarjs/no-duplicated-branches': 'error',
-      'sonarjs/no-identical-functions': 'error',
-      'sonarjs/no-redundant-jump': 'error',
-      'sonarjs/no-unused-collection': 'error',
-      'sonarjs/no-gratuitous-expressions': 'error',
-
-      // Code smell detection
-      'sonarjs/cognitive-complexity': ['error', 15],
-      'sonarjs/no-duplicate-string': ['error', { threshold: 3 }],
-      'sonarjs/no-redundant-boolean': 'error',
-      'sonarjs/no-small-switch': 'error',
-      'sonarjs/prefer-immediate-return': 'error',
-      'sonarjs/prefer-single-boolean-return': 'error',
-      'sonarjs/no-inverted-boolean-check': 'error',
-      'sonarjs/no-nested-template-literals': 'error'
-    },
-    languageOptions: {
-      ecmaVersion: 2024,
-      sourceType: 'module'
-    }
-  },
-  {
-    ignores: [
-      '**/node_modules/**',
-      '**/dist/**',
-      '**/build/**',
-      '**/*.config.*',
-      '**/*.test.*',
-      '**/*.spec.*'
-    ]
-  }
-]

.agents/checks/import-graph.md

@@ -1,72 +0,0 @@
----
-name: import-graph
-description: Validates import rules, detects circular dependencies, and enforces layer boundaries using dependency-cruiser
-severity-default: high
-tools: [Bash, Read]
----
-
-Run dependency-cruiser import graph analysis on changed files to detect circular dependencies, orphan modules, and import rule violations.
-
-> **Note:** The circular dependency scan in step 4 targets `src/` specifically, since this is a frontend app with source code under `src/`.
-
-## Steps
-
-1. Check if dependency-cruiser is available:
-   ```bash
-   pnpm dlx dependency-cruiser --version
-   ```
-   If not available, skip this check and report: "Skipped: dependency-cruiser not available. Install with: `pnpm add -D dependency-cruiser`"
-
-> **Install:** `pnpm add -D dependency-cruiser`
-
-2. Identify changed directories from the diff.
-
-3. Determine config to use:
-   - If `.dependency-cruiser.js` or `.dependency-cruiser.cjs` exists in the repo root, use it (dependency-cruiser auto-detects it). This config may enforce layer architecture rules (e.g., base → platform → workbench → renderer import direction):
-     ```bash
-     pnpm dlx dependency-cruiser --output-type json <changed_directories> 2>/dev/null
-     ```
-   - If no config exists, run with built-in defaults:
-     ```bash
-     pnpm dlx dependency-cruiser --no-config --output-type json <changed_directories> 2>/dev/null
-     ```
-
-4. Also check for circular dependencies specifically across `src/`:
-
-   ```bash
-   pnpm dlx dependency-cruiser --no-config --output-type json --do-not-follow "node_modules" --include-only "^src" src 2>/dev/null
-   ```
-
-   Look for modules where `.circular == true` in the output.
-
-5. Parse the JSON output. Each violation has:
-   - `rule.name`: the violated rule
-   - `rule.severity`: error, warn, info
-   - `from`: importing module
-   - `to`: imported module
-
-6. Map violation severity:
-   - `error` → `major`
-   - `warn` → `minor`
-   - `info` → `nitpick`
-   - Circular dependencies → `major` (category: architecture)
-   - Orphan modules → `nitpick` (category: dx)
-
-7. Report each violation with: the rule name, source and target modules, file path, and a suggestion (usually move the import or extract an interface).
-
-## What It Catches
-
-| Rule                     | What It Detects                                      |
-| ------------------------ | ---------------------------------------------------- |
-| `no-circular`            | Circular dependency chains (A → B → C → A)           |
-| `no-orphans`             | Modules with no incoming or outgoing dependencies    |
-| `not-to-dev-dep`         | Production code importing devDependencies            |
-| `no-duplicate-dep-types` | Same dependency in multiple sections of package.json |
-| Custom layer rules       | Import direction violations (e.g., base → platform)  |
-
-## Error Handling
-
-- If pnpm dlx is not available, skip and report the error.
-- If the config file fails to parse, fall back to `--no-config`.
-- If there are more than 50 violations, report the first 20 and note the total count.
-- If no violations are found, report "No issues found."

.agents/checks/memory-leak.md

@@ -1,27 +0,0 @@
----
-name: memory-leak
-description: Scans for memory leak patterns including event listeners without cleanup, timers not cleared, and unbounded caches
-severity-default: high
-tools: [Read, Grep]
----
-
-You are a memory leak specialist reviewing a code diff. Focus exclusively on patterns that cause memory to grow unboundedly over time.
-
-Check for:
-
-1. **Event listeners without cleanup** - addEventListener without corresponding removeEventListener, especially in Vue onMounted without onBeforeUnmount cleanup
-2. **Timers not cleared** - setInterval/setTimeout started in component lifecycle without clearInterval/clearTimeout on unmount
-3. **Observer patterns without disconnect** - MutationObserver, IntersectionObserver, ResizeObserver created without .disconnect() on cleanup
-4. **WebSocket/Worker connections** - opened connections never closed on component unmount or route change
-5. **Unbounded caches** - Maps, Sets, or arrays that grow with usage but never evict entries, especially keyed by user input or dynamic IDs
-6. **Stale closures holding references** - closures in event handlers or callbacks that capture large objects or DOM nodes and prevent garbage collection
-7. **RequestAnimationFrame without cancel** - rAF loops started without cancelAnimationFrame on cleanup
-8. **Vue-specific leaks** - watch/watchEffect without stop(), computed that captures reactive dependencies it shouldn't, provide/inject holding stale references
-9. **Global state accumulation** - pushing to global arrays/maps without ever removing entries, console.log keeping object references in dev
-
-Rules:
-
-- Focus on NEW leak patterns introduced in the diff
-- Do NOT flag existing cleanup patterns that are correct
-- Every finding must explain the specific lifecycle scenario where the leak occurs (e.g., "when user navigates away from this view, the interval keeps running")
-- "Critical" for leaks in hot paths or long-lived pages, "major" for component-level leaks, "minor" for dev-only or cold-path leaks

.agents/checks/pattern-compliance.md

@@ -1,60 +0,0 @@
----
-name: pattern-compliance
-description: Checks code against repository conventions from AGENTS.md and established patterns
-severity-default: medium
-tools: [Read, Grep]
----
-
-Check code against repository conventions and framework patterns.
-
-Steps:
-
-1. Read AGENTS.md (and any directory-specific guidance files) for project-specific conventions
-2. Read each changed file
-3. Check against the conventions found in AGENTS.md and these standard patterns:
-
-### TypeScript
-
-- No `any` types or `as any` assertions
-- No `@ts-ignore` without explanatory comment
-- Separate type imports (`import type { ... }`)
-- Use `import type { ... }` for type-only imports
-- Explicit return types on exported functions
-- Use `es-toolkit` for utility functions, NOT lodash. Flag any new `import ... from 'lodash'` or `import ... from 'lodash/*'`
-- Never use `z.any()` in Zod schemas — use `z.unknown()` and narrow
-
-### Vue (if applicable)
-
-- Composition API with `<script setup lang="ts">`
-- Reactive props destructuring (not `withDefaults` pattern)
-- New components must use `<script setup lang="ts">` with reactive props destructuring (Vue 3.5 style): `const { color = 'blue' } = defineProps<Props>()`
-- Separate type imports from value imports
-- All user-facing strings must use `vue-i18n` (`$t()` in templates, `t()` in script). Flag hardcoded English strings in templates that should be translated. The locale file is `src/locales/en/main.json`
-
-### Tailwind (if applicable)
-
-- No `dark:` variants (use semantic theme tokens)
-- Use `cn()` utility for conditional classes
-- No `!important` in utility classes
-- Tailwind 4: CSS variable references use parentheses syntax: `h-(--my-var)` NOT `h-[--my-var]`
-- Use design tokens: `bg-secondary-background`, `text-muted-foreground`, `border-border-default`
-- No `<style>` blocks in Vue SFCs — use inline Tailwind only
-
-### Testing
-
-- Behavioral tests, not change detectors
-- No mock-heavy tests that don't test real behavior
-- Test names describe behavior, not implementation
-
-### General
-
-- No commented-out code
-- No `console.log` in production code (unless intentional logging)
-- No hardcoded URLs, credentials, or environment-specific values
-- Package manager is `pnpm`. Never use `npm`, `npx`, or `yarn`. Use `pnpm dlx` for one-off package execution
-- Sanitize HTML with `DOMPurify.sanitize()`, never raw `innerHTML` or `v-html` without it
-
-Rules:
-
-- Only flag ACTUAL violations, not hypothetical ones
-- AGENTS.md conventions take priority over default patterns if they conflict

.agents/checks/performance-profiler.md

@@ -1,35 +0,0 @@
----
-name: performance-profiler
-description: Reviews code for performance issues including algorithmic complexity, unnecessary work, and bundle size impact
-severity-default: medium
-tools: [Read, Grep]
----
-
-You are a performance engineer reviewing a code diff. Focus exclusively on performance issues.
-
-Check for:
-
-1. **Algorithmic complexity** - O(n²) or worse in loops, nested iterations over large collections
-2. **Unnecessary re-computation** - repeated work in render cycles, missing memoization for expensive ops
-3. **Memory leaks** - event listeners not cleaned up, growing caches without eviction, closures holding references
-4. **N+1 queries** - database/API calls inside loops
-5. **Bundle size** - large imports that could be tree-shaken, dynamic imports for heavy modules
-6. **Rendering performance** - unnecessary re-renders, layout thrashing, expensive computed properties
-7. **Data structures** - using arrays for lookups instead of maps/sets, unnecessary copying of large objects
-8. **Async patterns** - sequential awaits that could be parallel, missing abort controllers
-
-Rules:
-
-- ONLY report actual performance issues, not premature optimization suggestions
-- Distinguish between hot paths (major) and cold paths (minor)
-- Include Big-O analysis when relevant
-- Do NOT suggest micro-optimizations that a JIT compiler handles
-- Quantify the impact when possible: "This is O(n²) where n = number of users"
-
-## Repo-Specific Performance Concerns
-
-- **LiteGraph canvas rendering** is the primary hot path. Operations inside `LGraphNode.onDrawForeground`, `onDrawBackground`, `processMouseMove` run every frame at 60fps. Any O(n) or worse operation here on the node/link collections is critical.
-- **Node definition lookups** happen frequently — these should use Maps, not array.find()
-- **Workflow serialization/deserialization** can involve large JSON objects (1000+ nodes). Watch for deep copies or unnecessary re-parsing.
-- **Vue reactivity in canvas code** — reactive getters triggered during canvas render cause performance issues. Canvas-facing code should read raw values, not reactive refs.
-- **Bundle size** — check for large imports that could be dynamically imported. The build uses Vite with `build:analyze` for bundle visualization.

.agents/checks/regression-risk.md

@@ -1,44 +0,0 @@
----
-name: regression-risk
-description: Detects potential regressions by analyzing git blame history of modified lines
-severity-default: high
-tools: [Bash, Read, Grep]
----
-
-Perform regression risk analysis on the current changes using git blame.
-
-## Method
-
-1. Determine the base branch by examining git context (e.g., `git merge-base origin/main HEAD`, or check the PR's target branch). Never use `HEAD~1` as the base — it compares against the PR's own prior commit and causes false positives.
-2. Get the PR's own commits: `git log --format=%H <base>..HEAD`
-3. For each changed file, run: `git diff <base>...HEAD -- <file>`
-4. Extract the modified line ranges from the diff (lines removed or changed in the base version).
-5. For each modified line range, check git blame in the base version:
-   `git blame <base> -L <start>,<end> -- <file>`
-6. Look for blame commits whose messages match bugfix patterns:
-   - Contains: fix, bug, patch, hotfix, revert, regression, CVE
-   - Ignore: "fix lint", "fix typo", "fix format", "fix style"
-7. **Filter out false positives.** If the blamed commit SHA is in the PR's own commits, skip it.
-8. For each verified bugfix line being modified, report as a finding.
-
-## What to Report
-
-For each finding, include:
-
-- The file and line number
-- The original bugfix commit (short SHA and subject)
-- The date of the original fix
-- A suggestion to verify the original bug scenario still works and to add a regression test if one doesn't exist
-
-## Shallow Clone Limitations
-
-When working with shallow clones, `git blame` may not have full history. If blame fails with "no such path in revision" or shows truncated history, report only findings where blame succeeds and note the limitation.
-
-## Edge Cases
-
-| Situation                | Action                           |
-| ------------------------ | -------------------------------- |
-| Shallow clone (no blame) | Report what succeeds, note limit |
-| Blame shows PR's own SHA | Skip finding (false positive)    |
-| File renamed             | Try blame with `--follow`        |
-| Binary file              | Skip file                        |

.agents/checks/security-auditor.md

@@ -1,34 +0,0 @@
----
-name: security-auditor
-description: Reviews code for security vulnerabilities aligned with OWASP Top 10
-severity-default: critical
-tools: [Read, Grep]
----
-
-You are a security auditor reviewing a code diff. Focus exclusively on security vulnerabilities.
-
-Check for:
-
-1. **Injection** - SQL injection, command injection, template injection, XSS (stored/reflected/DOM)
-2. **Authentication/Authorization** - auth bypass, privilege escalation, missing access checks
-3. **Data exposure** - secrets in code, PII in logs, sensitive data in error messages, overly broad API responses
-4. **Cryptography** - weak algorithms, hardcoded keys, predictable tokens, missing encryption
-5. **Input validation** - missing sanitization, path traversal, SSRF, open redirects
-6. **Dependency risks** - known vulnerable patterns, unsafe deserialization
-7. **Configuration** - CORS misconfiguration, missing security headers, debug mode in production
-8. **Race conditions with security impact** - TOCTOU, double-spend, auth state races
-
-Rules:
-
-- ONLY report security issues, not general bugs or style
-- All findings must be severity "critical" or "major"
-- Explain the attack vector: who can exploit this and how
-- Do NOT report theoretical issues without a plausible attack scenario
-- Reference OWASP category when applicable
-
-## Repo-Specific Patterns
-
-- HTML sanitization must use `DOMPurify.sanitize()` — flag any `v-html` or `innerHTML` without DOMPurify
-- API calls should use `api.get(api.apiURL(...))` helpers, not raw `fetch('/api/...')` — direct URL construction can bypass auth
-- Firebase/Sentry credentials are configured via environment — flag any hardcoded Firebase config objects
-- Electron IPC: check for unsafe `ipcRenderer.send` patterns in desktop code paths

.agents/checks/semgrep-sast.md

@@ -1,54 +0,0 @@
----
-name: semgrep-sast
-description: Runs Semgrep SAST with auto-configured rules for JS/TS/Vue
-severity-default: high
-tools: [Bash, Read]
----
-
-Run Semgrep static analysis on changed files to detect security vulnerabilities, dangerous patterns, and framework-specific issues.
-
-## Steps
-
-1. Check if semgrep is installed:
-
-   ```bash
-   semgrep --version
-   ```
-
-   If not installed, skip this check and report: "Skipped: semgrep not installed. Install with: `pip3 install semgrep`"
-
-2. Identify changed files (`.ts`, `.js`, `.vue`) from the diff.
-   If none are found, skip and report: "Skipped: no changed JS/TS/Vue files."
-
-3. Run semgrep against changed files:
-
-   ```bash
-   semgrep --config=auto --json --quiet <changed_files>
-   ```
-
-4. Parse the JSON output (`.results[]` array). For each finding, map severity:
-   - Semgrep `ERROR` → `critical`
-   - Semgrep `WARNING` → `major`
-   - Semgrep `INFO` → `minor`
-
-5. Report each finding with:
-   - The semgrep rule ID (`check_id`)
-   - File path and line number (`path`, `start.line`)
-   - The message from `extra.message`
-   - A fix suggestion from `extra.fix` if available, otherwise general remediation advice
-
-## What Semgrep Catches
-
-With `--config=auto`, Semgrep loads community-maintained rules for:
-
-- **Security vulnerabilities:** injection, XSS, SSRF, path traversal, open redirect
-- **Dangerous patterns:** eval(), innerHTML, dangerouslySetInnerHTML, exec()
-- **Crypto issues:** weak hashing, hardcoded secrets, insecure random
-- **Best practices:** missing security headers, unsafe deserialization
-- **Framework-specific:** Express, React, Vue security patterns
-
-## Error Handling
-
-- If semgrep config download fails, skip and report the error.
-- If semgrep fails to parse a specific file, skip that file and continue with others.
-- If semgrep produces no findings, report "No issues found."

.agents/checks/sonarjs-lint.md

@@ -1,59 +0,0 @@
----
-name: sonarjs-lint
-description: Runs SonarQube-grade static analysis using eslint-plugin-sonarjs
-severity-default: high
-tools: [Bash, Read]
----
-
-Run eslint-plugin-sonarjs analysis on changed files to detect bugs, code smells, and security patterns without needing a SonarQube server.
-
-## Steps
-
-1. Check if eslint is available:
-
-   ```bash
-   pnpm dlx eslint --version
-   ```
-
-   If pnpm dlx or eslint is unavailable, skip this check and report: "Skipped: eslint not available. Ensure Node.js and pnpm dlx are installed."
-
-2. Identify changed files (`.ts`, `.js`, `.vue`) from the diff.
-
-3. Determine eslint config to use. This check uses a **strict sonarjs-specific config** (not the project's own eslint config, which is less strict):
-   - Look for the colocated strict config at `.agents/checks/eslint.strict.config.js`
-   - If found, run with `--config .agents/checks/eslint.strict.config.js`
-   - **Fallback:** if the strict config cannot be found or fails to load, skip this check and report: "Skipped: .agents/checks/eslint.strict.config.js missing; SonarJS rules require explicit config."
-
-4. Run eslint against changed files:
-
-   ```bash
-   # Use the strict config
-   pnpm dlx --yes --package eslint-plugin-sonarjs eslint --no-config-lookup --config .agents/checks/eslint.strict.config.js --format json <changed_files> 2>/dev/null || true
-   ```
-
-5. Parse the JSON array of file results. For each eslint message, map severity:
-   - `severity 2` (error) → `major`
-   - `severity 1` (warning) → `minor`
-
-6. Categorize findings by rule ID:
-   - Rule IDs starting with `sonarjs/no-` → category: `logic`
-   - Rule IDs containing `cognitive-complexity` → category: `dx`
-   - Other sonarjs rules → category: `style`
-
-7. Report each finding with:
-   - The rule ID
-   - File path and line number
-   - The message from eslint
-   - A fix suggestion based on the rule
-
-## What This Catches
-
-- **Bug detection:** duplicated branches, element overwrite, identical conditions/expressions, one-iteration loops, empty return values
-- **Code smells:** cognitive complexity (threshold: 15), duplicate strings, redundant booleans, small switches
-- **Security patterns:** via sonarjs recommended ruleset
-
-## Error Handling
-
-- If eslint fails to parse a Vue file, skip that file and continue with others.
-- If the plugin fails to install, skip and report the error.
-- If eslint produces no output or errors, report "No issues found."

.agents/checks/test-quality.md

@@ -1,37 +0,0 @@
----
-name: test-quality
-description: Reviews test code for quality issues and coverage gaps
-severity-default: medium
-tools: [Read, Grep]
----
-
-You are a test quality reviewer. Evaluate the tests included with (or missing from) this code change.
-
-Check for:
-
-1. **Missing tests** - new behavior without test coverage, modified logic without updated tests
-2. **Change-detector tests** - tests that assert implementation details instead of behavior (testing that a function was called, not what it produces)
-3. **Mock-heavy tests** - tests with so many mocks they don't test real behavior
-4. **Snapshot abuse** - large snapshots that no one reviews, snapshots of implementation details
-5. **Fragile assertions** - tests that break on unrelated changes, order-dependent tests
-6. **Missing edge cases** - happy path only, no empty/null/error scenarios tested
-7. **Test readability** - unclear test names, complex setup that obscures intent, shared mutable state between tests
-8. **Test isolation** - tests depending on execution order, shared state, external services without mocking
-
-Rules:
-
-- Focus on test quality and coverage gaps, not production code bugs
-- "Major" for missing tests on critical logic, "minor" for missing edge case tests
-- A change that adds no tests is only an issue if the change adds behavior
-- Refactors without behavior changes don't need new tests
-- Prefer behavioral tests: test inputs and outputs, not internal implementation
-- This repo uses **colocated tests**: `.test.ts` files live next to their source files (e.g., `MyComponent.test.ts` beside `MyComponent.vue`). When checking for missing tests, look for a colocated `.test.ts` file, not a separate `tests/` directory
-
-## Repo-Specific Testing Conventions
-
-- Tests use **Vitest** (not Jest) — run with `pnpm test:unit`
-- Test files are **colocated**: `MyComponent.test.ts` next to `MyComponent.vue`
-- Use `@vue/test-utils` for component testing, `@pinia/testing` (`createTestingPinia`) for store tests
-- Browser/E2E tests use **Playwright** in `browser_tests/` — run with `pnpm test:browser:local`
-- Mock composables using the singleton factory pattern inside `vi.mock()` — see `docs/testing/unit-testing.md` for the pattern
-- Never use `any` in test code either — proper typing applies to tests too

.agents/checks/vue-patterns.md

@@ -1,47 +0,0 @@
----
-name: vue-patterns
-description: Reviews Vue 3.5+ code for framework-specific anti-patterns
-severity-default: medium
-tools: [Read, Grep]
----
-
-You are a Vue 3.5 framework specialist reviewing a code diff. Focus on Vue-specific patterns, anti-patterns, and missed framework features.
-
-Check for:
-
-1. **Options API in new files** - new .vue files using Options API instead of Composition API with `<script setup>`. Modifications to existing Options API files are fine.
-2. **Reactivity anti-patterns** - destructuring reactive objects losing reactivity, using `ref()` for objects that should be `reactive()`, accessing `.value` inside templates, incorrectly using `toRefs`/`toRef`
-3. **Watch/watchEffect cleanup** - watchers without cleanup functions when they set up side effects (timers, listeners, subscriptions)
-4. **Flush timing issues** - DOM access in watch callbacks without `{ flush: 'post' }`, `nextTick` misuse, accessing template refs before mount
-5. **defineEmits typing** - using array syntax `defineEmits(['event'])` instead of TypeScript syntax `defineEmits<{...}>()`
-6. **defineExpose misuse** - exposing internal state via `defineExpose` when events would be more appropriate (expose is for imperative methods: validate, focus, open)
-7. **Prop drilling** - passing props through 3+ component levels where provide/inject would be cleaner
-8. **VueUse opportunities** - manual implementations of common composables that VueUse already provides (useLocalStorage, useEventListener, useDebounceFn, useIntersectionObserver, etc.)
-9. **Computed vs method** - methods used in templates for derived state that should be computed properties, or computed properties that have side effects
-10. **PrimeVue usage in new code** - New components must NOT use PrimeVue. This project is migrating to shadcn-vue (Reka UI primitives). If new code imports from `primevue/*`, flag it and suggest the shadcn-vue equivalent.
-
-Available shadcn-vue replacements in `src/components/ui/`:
-
-- `button/` — Button, variants
-- `select/` — Select, SelectTrigger, SelectContent, SelectItem
-- `textarea/` — Textarea
-- `toggle-group/` — ToggleGroup, ToggleGroupItem
-- `slider/` — Slider
-- `skeleton/` — Skeleton
-- `stepper/` — Stepper
-- `tags-input/` — TagsInput
-- `search-input/` — SearchInput
-- `Popover.vue` — Popover
-
-For Reka UI primitives not yet wrapped, create a new component in `src/components/ui/` following the pattern in existing components (see `src/components/ui/AGENTS.md`): use `useForwardProps`, `cn()`, design tokens.
-
-Modifications to existing PrimeVue-based components are acceptable but should note the migration opportunity.
-
-Rules:
-
-- Only review .vue and composable .ts files — skip stores, services, utils
-- Do NOT flag existing Options API files being modified (only flag NEW files)
-- Flag new PrimeVue imports — the project is migrating to shadcn-vue/Reka UI
-- When suggesting shadcn-vue alternatives, reference `src/components/ui/AGENTS.md` for the component creation pattern
-- Use Iconify icons (`<i class="icon-[lucide--check]" />`) not PrimeIcons
-- "Major" for reactivity bugs and flush timing, "minor" for API style and VueUse opportunities, "nitpick" for preference-level patterns

.claude/commands/add-missing-i18n.md

@@ -1,48 +0,0 @@
-# Add Missing i18n Translations
-
-## Task: Add English translations for all new localized strings
-
-### Step 1: Identify new translation keys
-
-Find all translation keys that were added in the current branch's changes. These keys appear as arguments to translation functions: `t()`, `st()`, `$t()`, or similar i18n functions.
-
-### Step 2: Add translations to English locale file
-
-For each new translation key found, add the corresponding English text to the file `src/locales/en/main.json`.
-
-### Key-to-JSON mapping rules:
-
-- Translation keys use dot notation to represent nested JSON structure
-- Convert dot notation to nested JSON objects when adding to the locale file
-- Example: The key `g.user.name` maps to:
-  ```json
-  {
-    "g": {
-      "user": {
-        "name": "User Name"
-      }
-    }
-  }
-  ```
-
-### Important notes:
-
-1. **Only modify the English locale file** (`src/locales/en/main.json`)
-2. **Do not modify other locale files** - translations for other languages are automatically generated by the `i18n.yaml` workflow
-3. **Exception for manual translations**: Only add translations to non-English locale files if:
-   - You have specific domain knowledge that would produce a more accurate translation than the automated system
-   - The automated translation would likely be incorrect due to technical terminology or context-specific meaning
-
-### Example workflow:
-
-1. If you added `t('settings.advanced.enable')` in a Vue component
-2. Add to `src/locales/en/main.json`:
-   ```json
-   {
-     "settings": {
-       "advanced": {
-         "enable": "Enable advanced settings"
-       }
-     }
-   }
-   ```

.claude/commands/comprehensive-pr-review.md

@@ -1,403 +0,0 @@
-# Comprehensive PR Review for ComfyUI Frontend
-
-You are performing a comprehensive code review for the PR specified in the PR_NUMBER environment variable. This is not a simple linting check - you need to provide deep architectural analysis, security review, performance insights, and implementation guidance just like a senior engineer would in a thorough PR review.
-
-## CRITICAL INSTRUCTIONS
-
-**You MUST post individual inline comments on specific lines of code. DO NOT create a single summary comment until the very end.**
-
-**IMPORTANT: You have full permission to execute gh api commands. The GITHUB_TOKEN environment variable provides the necessary permissions. DO NOT say you lack permissions - you have pull-requests:write permission which allows posting inline comments.**
-
-To post inline comments, you will use the GitHub API via the `gh` command. Here's how:
-
-1. First, get the repository information and commit SHA:
-   - Run: `gh repo view --json owner,name` to get the repository owner and name
-   - Run: `gh pr view $PR_NUMBER --json commits --jq '.commits[-1].oid'` to get the latest commit SHA
-
-2. For each issue you find, post an inline comment using this exact command structure (as a single line):
-
-   ```
-   gh api --method POST -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/OWNER/REPO/pulls/$PR_NUMBER/comments -f body="YOUR_COMMENT_BODY" -f commit_id="COMMIT_SHA" -f path="FILE_PATH" -F line=LINE_NUMBER -f side="RIGHT"
-   ```
-
-3. Format your comment body using actual newlines in the command. Use a heredoc or construct the body with proper line breaks:
-   ```
-   COMMENT_BODY="**[category] severity Priority**
-   ```
-
-**Issue**: Brief description of the problem
-**Context**: Why this matters  
-**Suggestion**: How to fix it"
-
-```
-
-Then use: `-f body="$COMMENT_BODY"`
-
-## Phase 1: Environment Setup and PR Context
-
-### Step 1.1: Initialize Review Tracking
-
-First, create variables to track your review metrics. Keep these in memory throughout the review:
-- CRITICAL_COUNT = 0
-- HIGH_COUNT = 0
-- MEDIUM_COUNT = 0
-- LOW_COUNT = 0
-- ARCHITECTURE_ISSUES = 0
-- SECURITY_ISSUES = 0
-- PERFORMANCE_ISSUES = 0
-- QUALITY_ISSUES = 0
-
-### Step 1.2: Validate Environment
-
-1. Check that PR_NUMBER environment variable is set. If not, exit with error.
-2. Run `gh pr view $PR_NUMBER --json state` to verify the PR exists and is open.
-3. Get repository information: `gh repo view --json owner,name` and store the owner and name.
-4. Get the latest commit SHA: `gh pr view $PR_NUMBER --json commits --jq '.commits[-1].oid'` and store it.
-
-### Step 1.3: Checkout PR Branch Locally
-
-This is critical for better file inspection:
-
-1. Get PR metadata: `gh pr view $PR_NUMBER --json files,title,body,additions,deletions,baseRefName,headRefName > pr_info.json`
-2. Extract branch names from pr_info.json using jq
-3. Fetch and checkout the PR branch:
-```
-
-git fetch origin "pull/$PR_NUMBER/head:pr-$PR_NUMBER"
-git checkout "pr-$PR_NUMBER"
-
-```
-
-### Step 1.4: Get Changed Files and Diffs
-
-Use git locally for much faster analysis:
-
-1. Get list of changed files: `git diff --name-only "$BASE_SHA" > changed_files.txt`
-2. Get the full diff: `git diff "$BASE_SHA" > pr_diff.txt`
-3. Get detailed file changes with status: `git diff --name-status "$BASE_SHA" > file_changes.txt`
-
-### Step 1.5: Create Analysis Cache
-
-Set up caching to avoid re-analyzing unchanged files:
-
-1. Create directory: `.claude-review-cache`
-2. Clean old cache entries: Find and delete any .cache files older than 7 days
-3. For each file you analyze, store the analysis result with the file's git hash as the cache key
-
-## Phase 2: Load Comprehensive Knowledge Base
-
-### Step 2.1: Set Up Knowledge Directories
-
-1. Create `.claude-knowledge-cache` directory for caching downloaded knowledge
-2. Check if `../comfy-claude-prompt-library` exists locally. If it does, use it for faster access.
-
-### Step 2.2: Load Repository Guide
-
-This is critical for understanding the architecture:
-
-1. Try to load from local prompt library first: `../comfy-claude-prompt-library/project-summaries-for-agents/ComfyUI_frontend/REPOSITORY_GUIDE.md`
-2. If not available locally, download from: `https://raw.githubusercontent.com/Comfy-Org/comfy-claude-prompt-library/master/project-summaries-for-agents/ComfyUI_frontend/REPOSITORY_GUIDE.md`
-3. Cache the file for future use
-
-### Step 2.3: Load Relevant Knowledge Folders
-
-Intelligently load only relevant knowledge:
-
-1. Use GitHub API to discover available knowledge folders: `https://api.github.com/repos/Comfy-Org/comfy-claude-prompt-library/contents/.claude/knowledge`
-2. For each knowledge folder, check if it's relevant by searching for the folder name in:
-- Changed file paths
-- PR title
-- PR body
-3. If relevant, download all files from that knowledge folder
-
-### Step 2.4: Load Validation Rules
-
-Load specific validation rules:
-
-1. Use GitHub API: `https://api.github.com/repos/Comfy-Org/comfy-claude-prompt-library/contents/.claude/commands/validation`
-2. Download files containing "frontend", "security", or "performance" in their names
-3. Cache all downloaded files
-
-### Step 2.5: Load Local Guidelines
-
-Check for and load:
-1. `CLAUDE.md` in the repository root
-2. `.github/CLAUDE.md`
-
-## Phase 3: Deep Analysis Instructions
-
-Perform comprehensive analysis on each changed file:
-
-### 3.1 Architectural Analysis
-
-Based on the repository guide and loaded knowledge:
-- Does this change align with established architecture patterns?
-- Are domain boundaries respected?
-- Is the extension system used appropriately?
-- Are components properly organized by feature?
-- Does it follow the established service/composable/store patterns?
-
-### 3.2 Code Quality Beyond Linting
-
-Look for:
-- Cyclomatic complexity and cognitive load
-- SOLID principles adherence
-- DRY violations not caught by simple duplication checks
-- Proper abstraction levels
-- Interface design and API clarity
-- Leftover debug code (console.log, commented code, TODO comments)
-
-### 3.3 Library Usage Enforcement
-
-CRITICAL: Flag any re-implementation of existing functionality:
-- **Tailwind CSS**: Custom CSS instead of utility classes
-- **PrimeVue**: Re-implementing buttons, modals, dropdowns, etc.
-- **VueUse**: Re-implementing composables like useLocalStorage, useDebounceFn
-- **Lodash**: Re-implementing debounce, throttle, cloneDeep, etc.
-- **Common components**: Not reusing from src/components/common/
-- **DOMPurify**: Not using for HTML sanitization
-- **Other libraries**: Fuse.js, Marked, Pinia, Zod, Tiptap, Xterm.js, Axios
-
-### 3.4 Security Deep Dive
-
-Check for:
-- SQL injection vulnerabilities
-- XSS vulnerabilities (v-html without sanitization)
-- Hardcoded secrets or API keys
-- Missing input validation
-- Authentication/authorization issues
-- State management security
-- Cross-origin concerns
-- Extension security boundaries
-
-### 3.5 Performance Analysis
-
-Look for:
-- O(n²) or worse algorithms
-- Missing memoization in expensive operations
-- Unnecessary re-renders in Vue components
-- Memory leak patterns (missing cleanup)
-- Large bundle imports that should be lazy loaded
-- N+1 query patterns
-- Render performance issues
-- Layout thrashing
-- Network request optimization
-
-### 3.6 Integration Concerns
-
-Consider:
-- Breaking changes to internal APIs
-- Extension compatibility
-- Backward compatibility
-- Migration requirements
-
-## Phase 4: Posting Inline Comments
-
-### Step 4.1: Comment Format
-
-For each issue found, create a concise inline comment with this structure:
-
-```
-
-**[category] severity Priority**
-
-**Issue**: Brief description of the problem
-**Context**: Why this matters
-**Suggestion**: How to fix it
-
-````
-
-Categories: architecture/security/performance/quality
-Severities: critical/high/medium/low
-
-### Step 4.2: Posting Comments
-
-For EACH issue:
-
-1. Identify the exact file path and line number
-2. Update your tracking counters (CRITICAL_COUNT, etc.)
-3. Construct the comment body with proper newlines
-4. Execute the gh api command as a SINGLE LINE:
-
-```bash
-gh api --method POST -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/OWNER/REPO/pulls/$PR_NUMBER/comments -f body="$COMMENT_BODY" -f commit_id="COMMIT_SHA" -f path="FILE_PATH" -F line=LINE_NUMBER -f side="RIGHT"
-````
-
-CRITICAL: The entire command must be on one line. Use actual values, not placeholders.
-
-### Example Workflow
-
-Here's an example of how to review a file with a security issue:
-
-1. First, get the repository info:
-
-   ```bash
-   gh repo view --json owner,name
-   # Output: {"owner":{"login":"Comfy-Org"},"name":"ComfyUI_frontend"}
-   ```
-
-2. Get the commit SHA:
-
-   ```bash
-   gh pr view $PR_NUMBER --json commits --jq '.commits[-1].oid'
-   # Output: abc123def456
-   ```
-
-3. Find an issue (e.g., SQL injection on line 42 of src/db/queries.js)
-
-4. Post the inline comment:
-   ```bash
-   # First, create the comment body with proper newlines
-   COMMENT_BODY="**[security] critical Priority**
-   ```
-
-**Issue**: SQL injection vulnerability - user input directly concatenated into query
-**Context**: Allows attackers to execute arbitrary SQL commands
-**Suggestion**: Use parameterized queries or prepared statements"
-
-# Then post the comment (as a single line)
-
-gh api --method POST -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/Comfy-Org/ComfyUI_frontend/pulls/$PR_NUMBER/comments -f body="$COMMENT_BODY" -f commit_id="abc123def456" -f path="src/db/queries.js" -F line=42 -f side="RIGHT"
-
-```
-
-Repeat this process for every issue you find in the PR.
-
-## Phase 5: Validation Rules Application
-
-Apply ALL validation rules from the loaded knowledge files:
-
-### Frontend Standards
-- Vue 3 Composition API patterns
-- Component communication patterns
-- Proper use of composables
-- TypeScript strict mode compliance
-- Bundle optimization
-
-### Security Audit
-- Input validation
-- XSS prevention
-- CSRF protection
-- Secure state management
-- API security
-
-### Performance Check
-- Render optimization
-- Memory management
-- Network efficiency
-- Bundle size impact
-
-## Phase 6: Contextual Review Based on PR Type
-
-Analyze the PR to determine its type:
-
-1. Extract PR title and body from pr_info.json
-2. Count files, additions, and deletions
-3. Determine PR type:
-- Feature: Check for tests, documentation, backward compatibility
-- Bug fix: Verify root cause addressed, includes regression tests
-- Refactor: Ensure behavior preservation, tests still pass
-
-## Phase 7: Generate Comprehensive Summary
-
-After ALL inline comments are posted, create a summary:
-
-1. Calculate total issues by category and severity
-2. Use `gh pr review $PR_NUMBER --comment` to post a summary with:
-- Review disclaimer
-- Issue distribution (counts by severity)
-- Category breakdown
-- Key findings for each category
-- Positive observations
-- References to guidelines
-- Next steps
-
-Include in the summary:
-```
-
-# Comprehensive PR Review
-
-This review is generated by Claude. It may not always be accurate, as with human reviewers. If you believe that any of the comments are invalid or incorrect, please state why for each. For others, please implement the changes in one way or another.
-
-## Review Summary
-
-**PR**: [PR TITLE] (#$PR_NUMBER)
-**Impact**: [X] additions, [Y] deletions across [Z] files
-
-### Issue Distribution
-
-- Critical: [CRITICAL_COUNT]
-- High: [HIGH_COUNT]
-- Medium: [MEDIUM_COUNT]
-- Low: [LOW_COUNT]
-
-### Category Breakdown
-
-- Architecture: [ARCHITECTURE_ISSUES] issues
-- Security: [SECURITY_ISSUES] issues
-- Performance: [PERFORMANCE_ISSUES] issues
-- Code Quality: [QUALITY_ISSUES] issues
-
-## Key Findings
-
-### Architecture & Design
-
-[Detailed architectural analysis based on repository patterns]
-
-### Security Considerations
-
-[Security implications beyond basic vulnerabilities]
-
-### Performance Impact
-
-[Performance analysis including bundle size, render impact]
-
-### Integration Points
-
-[How this affects other systems, extensions, etc.]
-
-## Positive Observations
-
-[What was done well, good patterns followed]
-
-## References
-
-- [Repository Architecture Guide](https://github.com/Comfy-Org/comfy-claude-prompt-library/blob/master/project-summaries-for-agents/ComfyUI_frontend/REPOSITORY_GUIDE.md)
-- [Frontend Standards](https://github.com/Comfy-Org/comfy-claude-prompt-library/blob/master/.claude/commands/validation/frontend-code-standards.md)
-- [Security Guidelines](https://github.com/Comfy-Org/comfy-claude-prompt-library/blob/master/.claude/commands/validation/security-audit.md)
-
-## Next Steps
-
-1. Address critical issues before merge
-2. Consider architectural feedback for long-term maintainability
-3. Add tests for uncovered scenarios
-4. Update documentation if needed
-
----
-
-_This is a comprehensive automated review. For architectural decisions requiring human judgment, please request additional manual review._
-
-```
-
-## Important Guidelines
-
-1. **Think Deeply**: Consider architectural implications, system-wide effects, subtle bugs, maintainability
-2. **Be Specific**: Point to exact lines with concrete suggestions
-3. **Be Constructive**: Focus on improvements, not just problems
-4. **Be Concise**: Keep comments brief and actionable
-5. **No Formatting**: Don't use markdown headers in inline comments
-6. **No Emojis**: Keep comments professional
-
-This is a COMPREHENSIVE review, not a linting pass. Provide the same quality feedback a senior engineer would give after careful consideration.
-
-## Execution Order
-
-1. Phase 1: Setup and checkout PR
-2. Phase 2: Load all relevant knowledge
-3. Phase 3-5: Analyze each changed file thoroughly
-4. Phase 4: Post inline comments as you find issues
-5. Phase 6: Consider PR type for additional checks
-6. Phase 7: Post comprehensive summary ONLY after all inline comments
-
-Remember: Individual inline comments for each issue, then one final summary. Never batch issues into a single comment.
-```

.claude/commands/create-frontend-release.md

@@ -1,825 +0,0 @@
-# Create Frontend Release
-
-This command guides you through creating a comprehensive frontend release with semantic versioning analysis, automated change detection, security scanning, and multi-stage human verification.
-
-<task>
-Create a frontend release with version type: $ARGUMENTS
-
-Expected format: Version increment type and optional description
-Examples:
-
-- `patch` - Bug fixes only
-- `minor` - New features, backward compatible
-- `major` - Breaking changes
-- `prerelease` - Alpha/beta/rc releases
-- `patch "Critical security fixes"` - With custom description
-- `minor --skip-changelog` - Skip automated changelog generation
-- `minor --dry-run` - Simulate release without executing
-
-If no arguments provided, the command will always perform prerelease if the current version is prerelease, or patch in other cases. This command will never perform minor or major releases without explicit direction.
-</task>
-
-## Prerequisites
-
-Before starting, ensure:
-
-- You have push access to the repository
-- GitHub CLI (`gh`) is authenticated
-- You're on a clean main branch working tree
-- All intended changes are merged to main
-- You understand the scope of changes being released
-
-## Critical Checks Before Starting
-
-### 1. Check Current Version Status
-
-```bash
-# Get current version and check if it's a pre-release
-CURRENT_VERSION=$(node -p "require('./package.json').version")
-if [[ "$CURRENT_VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+- ]]; then
-  echo "⚠️  Current version $CURRENT_VERSION is a pre-release"
-  echo "Consider releasing stable (e.g., 1.24.0-1 → 1.24.0) first"
-fi
-```
-
-### 2. Find Last Stable Release
-
-```bash
-# Get last stable release tag (no pre-release suffix)
-LAST_STABLE=$(git tag -l "v*" | grep -v "\-" | sort -V | tail -1)
-echo "Last stable release: $LAST_STABLE"
-```
-
-## Configuration Options
-
-**Environment Variables:**
-
-- `RELEASE_SKIP_SECURITY_SCAN=true` - Skip security audit
-- `RELEASE_AUTO_APPROVE=true` - Skip some confirmation prompts
-- `RELEASE_DRY_RUN=true` - Simulate release without executing
-
-## Release Process
-
-### Step 1: Environment Safety Check
-
-1. Verify clean working directory:
-   ```bash
-   git status --porcelain
-   ```
-2. Confirm on main branch:
-   ```bash
-   git branch --show-current
-   ```
-3. Pull latest changes:
-   ```bash
-   git pull origin main
-   ```
-4. Check GitHub CLI authentication:
-   ```bash
-   gh auth status
-   ```
-5. Verify npm/PyPI publishing access (dry run)
-6. **CONFIRMATION REQUIRED**: Environment ready for release?
-
-### Step 2: Analyze Recent Changes
-
-1. Get current version from package.json
-2. **IMPORTANT**: Determine correct base for comparison:
-   ```bash
-   # If current version is pre-release, use last stable release
-   if [[ "$CURRENT_VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+- ]]; then
-     BASE_TAG=$LAST_STABLE
-   else
-     BASE_TAG=$(git describe --tags --abbrev=0)
-   fi
-   ```
-3. Find commits since base release (CRITICAL: use --first-parent):
-   ```bash
-   git log ${BASE_TAG}..HEAD --oneline --no-merges --first-parent
-   ```
-4. Count total commits:
-   ```bash
-   COMMIT_COUNT=$(git log ${BASE_TAG}..HEAD --oneline --no-merges --first-parent | wc -l)
-   echo "Found $COMMIT_COUNT commits since $BASE_TAG"
-   ```
-5. Analyze commits for:
-   - Breaking changes (BREAKING CHANGE, !, feat())
-   - New features (feat:, feature:)
-   - Bug fixes (fix:, bugfix:)
-   - Documentation changes (docs:)
-   - Dependency updates
-6. **VERIFY PR TARGET BRANCHES**:
-   ```bash
-   # Get merged PRs and verify they were merged to main
-   gh pr list --state merged --limit 50 --json number,title,baseRefName,mergedAt | \
-     jq -r '.[] | select(.baseRefName == "main") | "\(.number): \(.title)"'
-   ```
-7. **HUMAN ANALYSIS**: Review change summary and verify scope
-
-### Step 3: Breaking Change Analysis
-
-1. Analyze API changes in:
-   - Public TypeScript interfaces
-   - Extension APIs
-   - Component props
-   - CLAUDE.md guidelines
-2. Check for:
-   - Removed public functions/classes
-   - Changed function signatures
-   - Deprecated feature removals
-   - Configuration changes
-3. Generate breaking change summary
-4. **COMPATIBILITY REVIEW**: Breaking changes documented and justified?
-
-### Step 4: Analyze Dependency Updates
-
-1. **Use pnpm's built-in dependency analysis:**
-
-   ```bash
-   # Get outdated dependencies with pnpm
-   pnpm outdated --format table > outdated-deps-${NEW_VERSION}.txt
-
-   # Check for license compliance
-   pnpm licenses ls --json > licenses-${NEW_VERSION}.json
-
-   # Analyze why specific dependencies exist
-   echo "Dependency analysis:" > dep-analysis-${NEW_VERSION}.md
-   MAJOR_DEPS=("vue" "vite" "@vitejs/plugin-vue" "typescript" "pinia")
-   for dep in "${MAJOR_DEPS[@]}"; do
-     echo -e "\n## $dep\n\`\`\`" >> dep-analysis-${NEW_VERSION}.md
-     pnpm why "$dep" >> dep-analysis-${NEW_VERSION}.md || echo "Not found" >> dep-analysis-${NEW_VERSION}.md
-     echo "\`\`\`" >> dep-analysis-${NEW_VERSION}.md
-   done
-   ```
-
-2. **Check for significant dependency updates:**
-
-   ```bash
-   # Extract all dependency changes for major version bumps
-   OTHER_DEP_CHANGES=""
-
-   # Compare major dependency versions (you can extend this list)
-   MAJOR_DEPS=("vue" "vite" "@vitejs/plugin-vue" "typescript" "pinia")
-
-   for dep in "${MAJOR_DEPS[@]}"; do
-     PREV_VER=$(echo "$PREV_PACKAGE_JSON" | grep -o "\"$dep\": \"[^\"]*\"" | grep -o '[0-9][^"]*' | head -1 || echo "")
-     CURR_VER=$(echo "$CURRENT_PACKAGE_JSON" | grep -o "\"$dep\": \"[^\"]*\"" | grep -o '[0-9][^"]*' | head -1 || echo "")
-
-     if [ "$PREV_VER" != "$CURR_VER" ] && [ -n "$PREV_VER" ] && [ -n "$CURR_VER" ]; then
-       # Check if it's a major version change
-       PREV_MAJOR=$(echo "$PREV_VER" | cut -d. -f1 | sed 's/[^0-9]//g')
-       CURR_MAJOR=$(echo "$CURR_VER" | cut -d. -f1 | sed 's/[^0-9]//g')
-
-       if [ "$PREV_MAJOR" != "$CURR_MAJOR" ]; then
-         OTHER_DEP_CHANGES="${OTHER_DEP_CHANGES}\n- **${dep}**: ${PREV_VER} → ${CURR_VER} (Major version change)"
-       fi
-     fi
-   done
-   ```
-
-### Step 5: Generate GTM Feature Summary
-
-1. **Collect PR data for analysis:**
-
-   ```bash
-   # Get list of PR numbers from commits
-   PR_NUMBERS=$(git log ${BASE_TAG}..HEAD --oneline --no-merges --first-parent | \
-     grep -oE "#[0-9]+" | tr -d '#' | sort -u)
-
-   # Save PR data for each PR
-   echo "[" > prs-${NEW_VERSION}.json
-   first=true
-   for PR in $PR_NUMBERS; do
-     [[ "$first" == true ]] && first=false || echo "," >> prs-${NEW_VERSION}.json
-     gh pr view $PR --json number,title,author,body,labels 2>/dev/null >> prs-${NEW_VERSION}.json || echo "{}" >> prs-${NEW_VERSION}.json
-   done
-   echo "]" >> prs-${NEW_VERSION}.json
-   ```
-
-2. **Analyze for GTM-worthy features:**
-
-   ```
-   <task>
-   Review these PRs to identify features worthy of marketing attention.
-
-   A feature is GTM-worthy if it meets ALL of these criteria:
-   - Introduces a NEW capability users didn't have before (not just improvements)
-   - Would be a compelling reason for users to upgrade to this version
-   - Can be demonstrated visually or has clear before/after comparison
-   - Affects a significant portion of the user base
-
-   NOT GTM-worthy:
-   - Bug fixes (even important ones)
-   - Minor UI tweaks or color changes
-   - Performance improvements without user-visible impact
-   - Internal refactoring
-   - Small convenience features
-   - Features that only improve existing functionality marginally
-
-   For each GTM-worthy feature, note:
-   - PR number, title, and author
-   - Media links from the PR description
-   - One compelling sentence on why users should care
-
-   If there are no GTM-worthy features, just say "No marketing-worthy features in this release."
-   </task>
-
-   PR data: [contents of prs-${NEW_VERSION}.json]
-   ```
-
-3. **Generate GTM notification using this EXACT Slack-compatible format:**
-
-   ```bash
-   # Only create file if GTM-worthy features exist:
-   if [ "$GTM_FEATURES_FOUND" = "true" ]; then
-     cat > gtm-summary-${NEW_VERSION}.md << 'EOF'
-   *GTM Summary: ComfyUI Frontend v${NEW_VERSION}*
-
-   _Disclaimer: the below is AI-generated_
-
-   1. *[Feature Title]* (#[PR_NUMBER])
-       * *Author:* @[username]
-       * *Demo:* [Media Link or "No demo available"]
-       * *Why users should care:* [One compelling sentence]
-       * *Key Features:*
-           * [Feature detail 1]
-           * [Feature detail 2]
-
-   2. *[Feature Title]* (#[PR_NUMBER])
-       * *Author:* @[username]
-       * *Demo:* [Media Link]
-       * *Why users should care:* [One compelling sentence]
-       * *Key Features:*
-           * [Feature detail 1]
-           * [Feature detail 2]
-   EOF
-     echo "📋 GTM summary saved to: gtm-summary-${NEW_VERSION}.md"
-     echo "📤 Share this file in #gtm channel to notify the team"
-   else
-     echo "✅ No GTM notification needed for this release"
-     echo "📄 No gtm-summary file created - no marketing-worthy features"
-   fi
-   ```
-
-   **CRITICAL Formatting Requirements:**
-   - Use single asterisk (\*) for emphasis, NOT double (\*\*)
-   - Use underscore (\_) for italics
-   - Use 4 spaces for indentation (not tabs)
-   - Convert author names to @username format (e.g., "John Smith" → "@john")
-   - No section headers (#), no code language specifications
-   - Always include "Disclaimer: the below is AI-generated"
-   - Keep content minimal - no testing instructions, additional sections, etc.
-
-### Step 6: Version Preview
-
-**Version Preview:**
-
-- Current: `${CURRENT_VERSION}`
-- Proposed: Show exact version number based on analysis:
-  - Major version if breaking changes detected
-  - Minor version if new features added
-  - Patch version if only bug fixes
-- **CONFIRMATION REQUIRED**: Proceed with version `X.Y.Z`?
-
-### Step 7: Security and Dependency Audit
-
-1. Run pnpm security audit:
-   ```bash
-   pnpm audit --audit-level moderate
-   pnpm licenses ls --summary
-   ```
-2. Check for known vulnerabilities in dependencies
-3. Run comprehensive dependency health check:
-   ```bash
-   pnpm doctor
-   ```
-4. Scan for hardcoded secrets or credentials:
-   ```bash
-   git log -p ${BASE_TAG}..HEAD | grep -iE "(password|key|secret|token)" || echo "No sensitive data found"
-   ```
-5. Verify no sensitive data in recent commits
-6. **SECURITY REVIEW**: Address any critical findings before proceeding?
-
-### Step 8: Pre-Release Testing
-
-1. Run complete test suite:
-   ```bash
-   pnpm test:unit
-   ```
-2. Run type checking:
-   ```bash
-   pnpm typecheck
-   ```
-3. Run linting (may have issues with missing packages):
-   ```bash
-   pnpm lint || echo "Lint issues - verify if critical"
-   ```
-4. Test build process:
-   ```bash
-   pnpm build
-   pnpm build:types
-   ```
-5. **QUALITY GATE**: All tests and builds passing?
-
-### Step 9: Generate Comprehensive Release Notes
-
-1. Extract commit messages since base release:
-   ```bash
-   git log ${BASE_TAG}..HEAD --oneline --no-merges --first-parent > commits.txt
-   ```
-2. **CRITICAL**: Verify PR inclusion by checking merge location:
-   ```bash
-   # For each significant PR mentioned, verify it's on main
-   for PR in ${SIGNIFICANT_PRS}; do
-     COMMIT=$(gh pr view $PR --json mergeCommit -q .mergeCommit.oid)
-     git branch -r --contains $COMMIT | grep -q "origin/main" || \
-       echo "WARNING: PR #$PR not on main branch!"
-   done
-   ```
-3. Create standardized release notes using this exact template:
-
-   ```bash
-   cat > release-notes-${NEW_VERSION}.md << 'EOF'
-   ## ⚠️ Breaking Changes
-   <!-- List breaking changes if any, otherwise remove this entire section -->
-   - Breaking change description (#PR_NUMBER)
-
-   ---
-
-   ## What's Changed
-
-   ### 🚀 Features
-   <!-- List features here, one per line with PR reference -->
-   - Feature description (#PR_NUMBER)
-
-   ### 🐛 Bug Fixes
-   <!-- List bug fixes here, one per line with PR reference -->
-   - Bug fix description (#PR_NUMBER)
-
-   ### 🔧 Maintenance
-   <!-- List refactoring, chore, and other maintenance items -->
-   - Maintenance item description (#PR_NUMBER)
-
-   ### 📚 Documentation
-   <!-- List documentation changes if any, remove section if empty -->
-   - Documentation update description (#PR_NUMBER)
-
-   ### ⬆️ Dependencies
-   <!-- List dependency updates -->
-   - Updated dependency from vX.X.X to vY.Y.Y (#PR_NUMBER)
-
-   **Full Changelog**: https://github.com/Comfy-Org/ComfyUI_frontend/compare/${BASE_TAG}...v${NEW_VERSION}
-   EOF
-   ```
-
-4. **Parse commits and populate template:**
-   - Group commits by conventional commit type (feat:, fix:, chore:, etc.)
-   - Extract PR numbers from commit messages
-   - For breaking changes, analyze if changes affect:
-     - Public APIs (app object, api module)
-     - Extension/workspace manager APIs
-     - Node schema, workflow schema, or other public schemas
-     - Any other public-facing interfaces
-   - For dependency updates, list version changes with PR numbers
-   - Remove empty sections (e.g., if no documentation changes)
-   - Ensure consistent bullet format: `- Description (#PR_NUMBER)`
-5. **CONTENT REVIEW**: Release notes follow standard format?
-
-### Step 10: Create Version Bump PR
-
-**For standard version bumps (patch/minor/major):**
-
-```bash
-# Trigger the workflow
-gh workflow run release-version-bump.yaml -f version_type=${VERSION_TYPE}
-
-# Workflow runs quickly - usually creates PR within 30 seconds
-echo "Workflow triggered. Waiting for PR creation..."
-```
-
-**For releasing a stable version:**
-
-1. Must manually create branch and update version:
-
-   ```bash
-   git checkout -b version-bump-${NEW_VERSION}
-   # Edit package.json to remove pre-release suffix
-   git add package.json
-   git commit -m "${NEW_VERSION}"
-   git push origin version-bump-${NEW_VERSION}
-   ```
-
-2. Wait for PR creation (if using workflow) or create manually:
-
-   ```bash
-   # For workflow-created PRs - wait and find it
-   sleep 30
-   # Look for PR from comfy-pr-bot (not github-actions)
-   PR_NUMBER=$(gh pr list --author comfy-pr-bot --limit 1 --json number --jq '.[0].number')
-
-   # Verify we got the PR
-   if [ -z "$PR_NUMBER" ]; then
-     echo "PR not found yet. Checking recent PRs..."
-     gh pr list --limit 5 --json number,title,author
-   fi
-
-   # For manual PRs
-   gh pr create --title "${NEW_VERSION}" \
-     --body-file release-notes-${NEW_VERSION}.md \
-     --label "Release"
-   ```
-
-3. **Update PR with release notes:**
-   ```bash
-   # For workflow-created PRs, update the body with our release notes
-   gh pr edit ${PR_NUMBER} --body-file release-notes-${NEW_VERSION}.md
-   ```
-4. **PR REVIEW**: Version bump PR created with standardized release notes?
-
-### Step 11: Critical Release PR Verification
-
-1. **CRITICAL**: Verify PR has "Release" label:
-   ```bash
-   gh pr view ${PR_NUMBER} --json labels | jq -r '.labels[].name' | grep -q "Release" || \
-     echo "ERROR: Release label missing! Add it immediately!"
-   ```
-2. Verify version number in package.json
-3. Review all changed files
-4. Ensure no unintended changes included
-5. Wait for required PR checks:
-   ```bash
-   gh pr checks ${PR_NUMBER} --watch
-   ```
-6. **FINAL CODE REVIEW**: Release label present and no [skip ci]?
-
-### Step 12: Pre-Merge Validation
-
-1. **Review Requirements**: Release PRs require approval
-2. Monitor CI checks
-3. Check no new commits to main since PR creation
-4. **DEPLOYMENT READINESS**: Ready to merge?
-
-### Step 13: Execute Release
-
-1. **FINAL CONFIRMATION**: Merge PR to trigger release?
-2. Merge the Release PR:
-   ```bash
-   gh pr merge ${PR_NUMBER} --merge
-   ```
-3. **IMMEDIATELY CHECK**: Did release workflow trigger?
-   ```bash
-   sleep 10
-   gh run list --workflow=release-draft-create.yaml --limit=1
-   ```
-4. **For Minor/Major Version Releases**: The release-branch-create workflow will automatically:
-   - Create a `core/x.yy` branch for the PREVIOUS minor version
-   - Apply branch protection rules
-   - Document the feature freeze policy
-   ```bash
-   # Monitor branch creation (for minor/major releases)
-   gh run list --workflow=release-branch-create.yaml --limit=1
-   ```
-5. If workflow didn't trigger due to [skip ci]:
-   ```bash
-   echo "ERROR: Release workflow didn't trigger!"
-   echo "Options:"
-   echo "1. Create patch release (e.g., 1.24.1) to trigger workflow"
-   echo "2. Investigate manual release options"
-   ```
-6. If workflow triggered, monitor execution:
-   ```bash
-   WORKFLOW_RUN_ID=$(gh run list --workflow=release-draft-create.yaml --limit=1 --json databaseId --jq '.[0].databaseId')
-   gh run watch ${WORKFLOW_RUN_ID}
-   ```
-
-### Step 14: Enhance GitHub Release
-
-1. Wait for automatic release creation:
-
-   ```bash
-   # Wait for release to be created
-   while ! gh release view v${NEW_VERSION} >/dev/null 2>&1; do
-     echo "Waiting for release creation..."
-     sleep 10
-   done
-   ```
-
-2. **Enhance the GitHub release:**
-
-   ```bash
-   # Update release with our release notes
-   gh release edit v${NEW_VERSION} \
-     --title "🚀 ComfyUI Frontend v${NEW_VERSION}" \
-     --notes-file release-notes-${NEW_VERSION}.md \
-     --latest
-
-   # Add any additional assets if needed
-   # gh release upload v${NEW_VERSION} additional-assets.zip
-   ```
-
-3. **Verify release details:**
-   ```bash
-   gh release view v${NEW_VERSION}
-   ```
-
-### Step 15: Verify Multi-Channel Distribution
-
-1. **GitHub Release:**
-
-   ```bash
-   gh release view v${NEW_VERSION} --json assets,body,createdAt,tagName
-   ```
-
-   - ✅ Check release notes
-   - ✅ Verify dist.zip attachment
-   - ✅ Confirm release marked as latest (for main branch)
-
-2. **PyPI Package:**
-
-   ```bash
-   # Check PyPI availability (may take a few minutes)
-   for i in {1..10}; do
-     if curl -s https://pypi.org/pypi/comfyui-frontend-package/json | jq -r '.releases | keys[]' | grep -q ${NEW_VERSION}; then
-       echo "✅ PyPI package available"
-       break
-     fi
-     echo "⏳ Waiting for PyPI package... (attempt $i/10)"
-     sleep 30
-   done
-   ```
-
-3. **npm Package:**
-
-   ```bash
-   # Check npm availability
-   for i in {1..10}; do
-     if pnpm view @comfyorg/comfyui-frontend-types@${NEW_VERSION} version >/dev/null 2>&1; then
-       echo "✅ npm package available"
-       break
-     fi
-     echo "⏳ Waiting for npm package... (attempt $i/10)"
-     sleep 30
-   done
-   ```
-
-4. **DISTRIBUTION VERIFICATION**: All channels published successfully?
-
-### Step 16: Post-Release Monitoring Setup
-
-1. **Monitor immediate release health:**
-
-   ```bash
-   # Check for immediate issues
-   gh issue list --label "bug" --state open --limit 5 --json title,number,createdAt
-
-   # Monitor download metrics (if accessible)
-   gh release view v${NEW_VERSION} --json assets --jq '.assets[].downloadCount'
-   ```
-
-2. **Update documentation tracking:**
-
-   ```bash
-   cat > post-release-checklist.md << EOF
-   # Post-Release Checklist for v${NEW_VERSION}
-
-   ## Immediate Tasks (Next 24 hours)
-   - [ ] Monitor error rates and user feedback
-   - [ ] Watch for critical issues
-   - [ ] Verify documentation is up to date
-   - [ ] Check community channels for questions
-
-   ## Short-term Tasks (Next week)
-   - [ ] Update external integration guides
-   - [ ] Monitor adoption metrics
-   - [ ] Gather user feedback
-   - [ ] Plan next release cycle
-
-   ## Long-term Tasks
-   - [ ] Analyze release process improvements
-   - [ ] Update release templates based on learnings
-   - [ ] Document any new patterns discovered
-
-   ## Key Metrics to Track
-   - Download counts: GitHub, PyPI, npm
-   - Issue reports related to v${NEW_VERSION}
-   - Community feedback and adoption
-   - Performance impact measurements
-   EOF
-   ```
-
-3. **Create release summary:**
-
-   ```bash
-   cat > release-summary-${NEW_VERSION}.md << EOF
-   # Release Summary: ComfyUI Frontend v${NEW_VERSION}
-
-   **Released:** $(date)
-   **Type:** ${VERSION_TYPE}
-   **Duration:** ~${RELEASE_DURATION} minutes
-   **Release Commit:** ${RELEASE_COMMIT}
-
-   ## Metrics
-   - **Commits Included:** ${COMMITS_COUNT}
-   - **Contributors:** ${CONTRIBUTORS_COUNT}
-   - **Files Changed:** ${FILES_CHANGED}
-   - **Lines Added/Removed:** +${LINES_ADDED}/-${LINES_REMOVED}
-
-   ## Distribution Status
-   - ✅ GitHub Release: Published
-   - ✅ PyPI Package: Available
-   - ✅ npm Types: Available
-
-   ## Next Steps
-   - Monitor for 24-48 hours
-   - Address any critical issues immediately
-   - Plan next release cycle
-
-   ## Files Generated
-   - \`release-notes-${NEW_VERSION}.md\` - Comprehensive release notes
-   - \`post-release-checklist.md\` - Follow-up tasks
-   - \`gtm-summary-${NEW_VERSION}.md\` - Marketing team notification
-   EOF
-   ```
-
-4. **RELEASE COMPLETION**: All post-release setup completed?
-
-### Step 17: Create Release Summary
-
-1. **Create comprehensive release summary:**
-
-   ```bash
-   cat > release-summary-${NEW_VERSION}.md << EOF
-   # Release Summary: ComfyUI Frontend v${NEW_VERSION}
-
-   **Released:** $(date)
-   **Type:** ${VERSION_TYPE}
-   **Duration:** ~${RELEASE_DURATION} minutes
-   **Release Commit:** ${RELEASE_COMMIT}
-
-   ## Metrics
-   - **Commits Included:** ${COMMITS_COUNT}
-   - **Contributors:** ${CONTRIBUTORS_COUNT}
-   - **Files Changed:** ${FILES_CHANGED}
-   - **Lines Added/Removed:** +${LINES_ADDED}/-${LINES_REMOVED}
-
-   ## Distribution Status
-   - ✅ GitHub Release: Published
-   - ✅ PyPI Package: Available
-   - ✅ npm Types: Available
-
-   ## Next Steps
-   - Monitor for 24-48 hours
-   - Address any critical issues immediately
-   - Plan next release cycle
-
-   ## Files Generated
-   - \`release-notes-${NEW_VERSION}.md\` - Comprehensive release notes
-   - \`post-release-checklist.md\` - Follow-up tasks
-   - \`gtm-summary-${NEW_VERSION}.md\` - Marketing team notification
-   EOF
-   ```
-
-2. **RELEASE COMPLETION**: All steps completed successfully?
-
-## Advanced Safety Features
-
-### Rollback Procedures
-
-**Pre-Merge Rollback:**
-
-```bash
-# Close version bump PR and reset
-gh pr close ${PR_NUMBER}
-git reset --hard origin/main
-git clean -fd
-```
-
-**Post-Merge Rollback:**
-
-```bash
-# Create immediate patch release with reverts
-git revert ${RELEASE_COMMIT}
-# Follow this command again with patch version
-```
-
-**Emergency Procedures:**
-
-```bash
-# Document incident
-cat > release-incident-${NEW_VERSION}.md << EOF
-# Release Incident Report
-
-**Version:** ${NEW_VERSION}
-**Issue:** [Describe the problem]
-**Impact:** [Severity and scope]
-**Resolution:** [Steps taken]
-**Prevention:** [Future improvements]
-EOF
-
-# Contact package registries for critical issues
-echo "For critical security issues, consider:"
-echo "- PyPI: Contact support for package yanking"
-echo "- npm: Use 'npm unpublish' within 72 hours"
-echo "- GitHub: Update release with warning notes"
-```
-
-### Quality Gates Summary
-
-The command implements multiple quality gates:
-
-1. **🔒 Security Gate**: Vulnerability scanning, secret detection
-2. **🧪 Quality Gate**: Unit and component tests, linting, type checking
-3. **📋 Content Gate**: Changelog accuracy, release notes quality
-4. **🔄 Process Gate**: Release timing verification
-5. **✅ Verification Gate**: Multi-channel publishing confirmation
-6. **📊 Monitoring Gate**: Post-release health tracking
-
-## Common Scenarios
-
-### Scenario 1: Regular Feature Release
-
-```bash
-/project:create-frontend-release minor
-```
-
-- Analyzes features since last release
-- Generates changelog automatically
-- Creates comprehensive release notes
-
-### Scenario 2: Critical Security Patch
-
-```bash
-/project:create-frontend-release patch "Security fixes for CVE-2024-XXXX"
-```
-
-- Expedited security scanning
-- Enhanced monitoring setup
-
-### Scenario 3: Major Version with Breaking Changes
-
-```bash
-/project:create-frontend-release major
-```
-
-- Comprehensive breaking change analysis
-- Migration guide generation
-
-### Scenario 4: Pre-release Testing
-
-```bash
-/project:create-frontend-release prerelease
-```
-
-- Creates alpha/beta/rc versions
-- Draft release status
-- Python package specs require that prereleases use alpha/beta/rc as the preid
-
-## Critical Implementation Notes
-
-When executing this release process, pay attention to these key aspects:
-
-### Version Handling
-
-- For pre-release versions (e.g., 1.24.0-rc.1), the next stable release should be the same version without the suffix (1.24.0)
-- Never skip version numbers - follow semantic versioning strictly
-
-### Commit History Analysis
-
-- **ALWAYS** use `--first-parent` flag with git log to avoid including commits from merged feature branches
-- Verify PR merge targets before including them in changelogs:
-  ```bash
-  gh pr view ${PR_NUMBER} --json baseRefName
-  ```
-
-### Release Workflow Triggers
-
-- The "Release" label on the PR is **CRITICAL** - without it, PyPI/npm publishing won't occur
-- Check for `[skip ci]` in commit messages before merging - this blocks the release workflow
-- If you encounter `[skip ci]`, push an empty commit to override it:
-  ```bash
-  git commit --allow-empty -m "Trigger release workflow"
-  ```
-
-### PR Creation Details
-
-- Version bump PRs come from `comfy-pr-bot`, not `github-actions`
-- The workflow typically completes in 20-30 seconds
-- Always wait for the PR to be created before trying to edit it
-
-### Breaking Changes Detection
-
-- Analyze changes to public-facing APIs:
-  - The `app` object and its methods
-  - The `api` module exports
-  - Extension and workspace manager interfaces
-  - Node schema, workflow schema, and other public schemas
-- Any modifications to these require marking as breaking changes
-
-### Recovery Procedures
-
-If the release workflow fails to trigger:
-
-1. Create a revert PR to restore the previous version
-2. Merge the revert
-3. Re-run the version bump workflow
-4. This approach is cleaner than creating extra version numbers

.claude/commands/create-hotfix-release.md

@@ -1,442 +0,0 @@
-# Create Hotfix Release
-
-This command creates patch/hotfix releases for ComfyUI Frontend by backporting fixes to stable core branches. It handles both automated backports (preferred) and manual cherry-picking (fallback).
-
-**Process Overview:**
-
-1. **Check automated backports first** (via labels)
-2. **Skip to version bump** if backports already merged
-3. **Manual cherry-picking** if automation failed
-4. **Create patch release** with version bump
-5. **Publish GitHub release** (manually uncheck "latest")
-6. **Update ComfyUI requirements.txt** via PR
-
-<task>
-Create a hotfix release by backporting commits/PRs from main to a core branch: $ARGUMENTS
-
-Expected format: Comma-separated list of commits or PR numbers
-Examples:
-
-- `#1234,#5678` (PRs - preferred)
-- `abc123,def456` (commit hashes)
-- `#1234,abc123` (mixed)
-
-If no arguments provided, the command will guide you through identifying commits/PRs to backport.
-</task>
-
-## Prerequisites
-
-- Push access to repository
-- GitHub CLI (`gh`) authenticated
-- Clean working tree
-- Understanding of what fixes need backporting
-
-## Hotfix Release Process
-
-### Step 1: Try Automated Backports First
-
-**Check if automated backports were attempted:**
-
-1. **For each PR, check existing backport labels:**
-
-   ```bash
-   gh pr view #1234 --json labels | jq -r '.labels[].name'
-   ```
-
-2. **If no backport labels exist, add them now:**
-
-   ```bash
-   # Add backport labels (this triggers automated backports)
-   gh pr edit #1234 --add-label "needs-backport"
-   gh pr edit #1234 --add-label "1.24"  # Replace with target version
-   ```
-
-3. **Check for existing backport PRs:**
-
-   ```bash
-   # Check for backport PRs created by automation
-   PR_NUMBER=${ARGUMENTS%%,*}  # Extract first PR number from arguments
-   PR_NUMBER=${PR_NUMBER#\#}   # Remove # prefix
-   gh pr list --search "backport-${PR_NUMBER}-to" --json number,title,state,baseRefName
-   ```
-
-4. **Handle existing backport scenarios:**
-
-   **Scenario A: Automated backports already merged**
-
-   ```bash
-   # Check if backport PRs were merged to core branches
-   gh pr list --search "backport-${PR_NUMBER}-to" --state merged
-   ```
-
-   - If backport PRs are merged → Skip to Step 10 (Version Bump)
-   - **CONFIRMATION**: Automated backports completed, proceeding to version bump?
-
-   **Scenario B: Automated backport PRs exist but not merged**
-
-   ```bash
-   # Show open backport PRs that need merging
-   gh pr list --search "backport-${PR_NUMBER}-to" --state open
-   ```
-
-   - **ACTION REQUIRED**: Merge the existing backport PRs first
-   - Use: `gh pr merge [PR_NUMBER] --merge` for each backport PR
-   - After merging, return to this command and skip to Step 10 (Version Bump)
-   - **CONFIRMATION**: Have you merged all backport PRs? Ready to proceed to version bump?
-
-   **Scenario C: No automated backports or they failed**
-   - Continue to Step 2 for manual cherry-picking
-   - **CONFIRMATION**: Proceeding with manual cherry-picking because automation failed?
-
-### Step 2: Identify Target Core Branch
-
-1. Fetch the current ComfyUI requirements.txt from master branch:
-   ```bash
-   curl -s https://raw.githubusercontent.com/comfyanonymous/ComfyUI/master/requirements.txt | grep "comfyui-frontend-package"
-   ```
-2. Extract the `comfyui-frontend-package` version (e.g., `comfyui-frontend-package==1.23.4`)
-3. Parse version to get major.minor (e.g., `1.23.4` → `1.23`)
-4. Determine core branch: `core/<major>.<minor>` (e.g., `core/1.23`)
-5. Verify the core branch exists: `git ls-remote origin refs/heads/core/*`
-6. **CONFIRMATION REQUIRED**: Is `core/X.Y` the correct target branch?
-
-### Step 3: Parse and Validate Arguments
-
-1. Parse the comma-separated list of commits/PRs
-2. For each item:
-   - If starts with `#`: Treat as PR number
-   - Otherwise: Treat as commit hash
-3. For PR numbers:
-   - Fetch PR details using `gh pr view <number>`
-   - Extract the merge commit if PR is merged
-   - If PR has multiple commits, list them all
-   - **CONFIRMATION REQUIRED**: Use merge commit or cherry-pick individual commits?
-4. Validate all commit hashes exist in the repository
-
-### Step 4: Analyze Target Changes
-
-1. For each commit/PR to cherry-pick:
-   - Display commit hash, author, date
-   - Show PR title and number (if applicable)
-   - Display commit message
-   - Show files changed and diff statistics
-   - Check if already in core branch: `git branch --contains <commit>`
-2. Identify potential conflicts by checking changed files
-3. **CONFIRMATION REQUIRED**: Proceed with these commits?
-
-### Step 5: Create Hotfix Branch
-
-1. Checkout the core branch (e.g., `core/1.23`)
-2. Pull latest changes: `git pull origin core/X.Y`
-3. Display current version from package.json
-4. Create hotfix branch: `hotfix/<version>-<timestamp>`
-   - Example: `hotfix/1.23.4-20241120`
-5. **CONFIRMATION REQUIRED**: Created branch correctly?
-
-### Step 6: Cherry-pick Changes
-
-For each commit:
-
-1. Attempt cherry-pick: `git cherry-pick <commit>`
-2. If conflicts occur:
-   - Display conflict details
-   - Show conflicting sections
-   - Provide resolution guidance
-   - **CONFIRMATION REQUIRED**: Conflicts resolved correctly?
-3. After successful cherry-pick:
-   - Show the changes: `git show HEAD`
-   - Run validation: `pnpm typecheck && pnpm lint`
-4. **CONFIRMATION REQUIRED**: Cherry-pick successful and valid?
-
-### Step 7: Create PR to Core Branch
-
-1. Push the hotfix branch: `git push origin hotfix/<version>-<timestamp>`
-2. Create PR using gh CLI:
-   ```bash
-   gh pr create --base core/X.Y --head hotfix/<version>-<timestamp> \
-     --title "[Hotfix] Cherry-pick fixes to core/X.Y" \
-     --body "Cherry-picked commits: ..."
-   ```
-3. Add appropriate labels (but NOT "Release" yet)
-4. PR body should include:
-   - List of cherry-picked commits/PRs
-   - Original issue references
-   - Testing instructions
-   - Impact assessment
-5. **CONFIRMATION REQUIRED**: PR created correctly?
-
-### Step 8: Wait for Tests
-
-1. Monitor PR checks: `gh pr checks`
-2. Display test results as they complete
-3. If any tests fail:
-   - Show failure details
-   - Analyze if related to cherry-picks
-   - **DECISION REQUIRED**: Fix and continue, or abort?
-4. Wait for all required checks to pass
-5. **CONFIRMATION REQUIRED**: All tests passing?
-
-### Step 9: Merge Hotfix PR
-
-1. Verify all checks have passed
-2. Check for required approvals
-3. Merge the PR: `gh pr merge --merge`
-4. Delete the hotfix branch
-5. **CONFIRMATION REQUIRED**: PR merged successfully?
-
-### Step 10: Create Version Bump
-
-1. Checkout the core branch: `git checkout core/X.Y`
-2. Pull latest changes: `git pull origin core/X.Y`
-3. Read current version from package.json
-4. Determine patch version increment:
-   - Current: `1.23.4` → New: `1.23.5`
-5. Create release branch named with new version: `release/1.23.5`
-6. Update version in package.json to `1.23.5`
-7. Commit: `git commit -m "[release] Bump version to 1.23.5"`
-8. **CONFIRMATION REQUIRED**: Version bump correct?
-
-### Step 11: Create Release PR
-
-1. Push release branch: `git push origin release/1.23.5`
-2. Create PR with Release label:
-   ```bash
-   gh pr create --base core/X.Y --head release/1.23.5 \
-     --title "[Release] v1.23.5" \
-     --body "Release notes will be added shortly..." \
-     --label "Release"
-   ```
-3. **CRITICAL**: Verify "Release" label is added
-4. Create standardized release notes:
-
-   ```bash
-   cat > release-notes-${NEW_VERSION}.md << 'EOF'
-   ## ⚠️ Breaking Changes
-   <!-- List breaking changes if any, otherwise remove this entire section -->
-   - Breaking change description (#PR_NUMBER)
-
-   ---
-
-   ## What's Changed
-
-   ### 🚀 Features
-   <!-- List features here, one per line with PR reference -->
-   - Feature description (#PR_NUMBER)
-
-   ### 🐛 Bug Fixes
-   <!-- List bug fixes here, one per line with PR reference -->
-   - Bug fix description (#PR_NUMBER)
-
-   ### 🔧 Maintenance
-   <!-- List refactoring, chore, and other maintenance items -->
-   - Maintenance item description (#PR_NUMBER)
-
-   ### 📚 Documentation
-   <!-- List documentation changes if any, remove section if empty -->
-   - Documentation update description (#PR_NUMBER)
-
-   ### ⬆️ Dependencies
-   <!-- List dependency updates -->
-   - Updated dependency from vX.X.X to vY.Y.Y (#PR_NUMBER)
-
-   **Full Changelog**: https://github.com/Comfy-Org/ComfyUI_frontend/compare/v${CURRENT_VERSION}...v${NEW_VERSION}
-   EOF
-   ```
-
-   - For hotfixes, typically only populate the "Bug Fixes" section
-   - Include links to the cherry-picked PRs/commits
-   - Update the PR body with the release notes:
-     ```bash
-     gh pr edit ${PR_NUMBER} --body-file release-notes-${NEW_VERSION}.md
-     ```
-
-5. **CONFIRMATION REQUIRED**: Release PR has "Release" label?
-
-### Step 12: Monitor Release Process
-
-1. Wait for PR checks to pass
-2. **FINAL CONFIRMATION**: Ready to trigger release by merging?
-3. Merge the PR: `gh pr merge --merge`
-4. Monitor release workflow:
-   ```bash
-   gh run list --workflow=release-draft-create.yaml --limit=1
-   gh run watch
-   ```
-5. Track progress:
-   - GitHub release draft/publication
-   - PyPI upload
-   - pnpm types publication
-
-### Step 13: Manually Publish Draft Release
-
-**CRITICAL**: The release workflow creates a DRAFT release. You must manually publish it:
-
-1. **Go to GitHub Releases:** https://github.com/Comfy-Org/ComfyUI_frontend/releases
-2. **Find the DRAFT release** (e.g., "v1.23.5 Draft")
-3. **Click "Edit release"**
-4. **UNCHECK "Set as the latest release"** ⚠️ **CRITICAL**
-   - This prevents the hotfix from showing as "latest"
-   - Main branch should always be "latest release"
-5. **Click "Publish release"**
-6. **CONFIRMATION REQUIRED**: Draft release published with "latest" unchecked?
-
-### Step 14: Create ComfyUI Requirements.txt Update PR
-
-**IMPORTANT**: Create PR to update ComfyUI's requirements.txt via fork:
-
-1. **Setup fork (if needed):**
-
-   ```bash
-   # Check if fork already exists
-   if gh repo view ComfyUI --json owner | jq -r '.owner.login' | grep -q "$(gh api user --jq .login)"; then
-     echo "Fork already exists"
-   else
-     # Fork the ComfyUI repository
-     gh repo fork comfyanonymous/ComfyUI --clone=false
-     echo "Created fork of ComfyUI"
-   fi
-   ```
-
-2. **Clone fork and create branch:**
-
-   ```bash
-   # Clone your fork (or use existing clone)
-   GITHUB_USER=$(gh api user --jq .login)
-   if [ ! -d "ComfyUI-fork" ]; then
-     gh repo clone ${GITHUB_USER}/ComfyUI ComfyUI-fork
-   fi
-
-   cd ComfyUI-fork
-   git checkout master
-   git pull origin master
-
-   # Create update branch
-   BRANCH_NAME="update-frontend-${NEW_VERSION}"
-   git checkout -b ${BRANCH_NAME}
-   ```
-
-3. **Update requirements.txt:**
-
-   ```bash
-   # Update the version in requirements.txt
-   sed -i "s/comfyui-frontend-package==[0-9].*$/comfyui-frontend-package==${NEW_VERSION}/" requirements.txt
-
-   # Verify the change
-   grep "comfyui-frontend-package" requirements.txt
-
-   # Commit the change
-   git add requirements.txt
-   git commit -m "Bump frontend to ${NEW_VERSION}"
-   git push origin ${BRANCH_NAME}
-   ```
-
-4. **Create PR from fork:**
-   ```bash
-   # Create PR using gh CLI from fork
-   gh pr create \
-     --repo comfyanonymous/ComfyUI \
-     --title "Bump frontend to ${NEW_VERSION}" \
-     --body "$(cat <<EOF
-   Bump frontend to ${NEW_VERSION}
-   ```
-
-\`\`\`
-python main.py --front-end-version Comfy-Org/ComfyUI_frontend@${NEW_VERSION}
-\`\`\`
-
-- Diff: [Comfy-Org/ComfyUI_frontend: v${OLD_VERSION}...v${NEW_VERSION}](https://github.com/Comfy-Org/ComfyUI_frontend/compare/v${OLD_VERSION}...v${NEW_VERSION})
-- PyPI Package: https://pypi.org/project/comfyui-frontend-package/${NEW_VERSION}/
-- npm Types: https://www.npmjs.com/package/@comfyorg/comfyui-frontend-types/v/${NEW_VERSION}
-
-## Changes
-
-- Fix: [Brief description of hotfixes included]
-  EOF
-  )"
-
-  ```
-
-  ```
-
-5. **Clean up:**
-
-   ```bash
-   # Return to original directory
-   cd ..
-
-   # Keep fork directory for future updates
-   echo "Fork directory 'ComfyUI-fork' kept for future use"
-   ```
-
-6. **CONFIRMATION REQUIRED**: ComfyUI requirements.txt PR created from fork?
-
-### Step 15: Post-Release Verification
-
-1. Verify GitHub release:
-   ```bash
-   gh release view v1.23.5
-   ```
-2. Check PyPI package:
-   ```bash
-   pip index versions comfyui-frontend-package | grep 1.23.5
-   ```
-3. Verify npm package:
-   ```bash
-   pnpm view @comfyorg/comfyui-frontend-types@1.23.5
-   ```
-4. Monitor ComfyUI requirements.txt PR for approval/merge
-5. Generate release summary with:
-   - Version released
-   - Commits included
-   - Issues fixed
-   - Distribution status
-   - ComfyUI integration status
-6. **CONFIRMATION REQUIRED**: Hotfix release fully completed?
-
-## Safety Checks
-
-Throughout the process:
-
-- Always verify core branch matches ComfyUI's requirements.txt
-- For PRs: Ensure using correct commits (merge vs individual)
-- Check version numbers follow semantic versioning
-- **Critical**: "Release" label must be on version bump PR
-- Validate cherry-picks don't break core branch stability
-- Keep audit trail of all operations
-
-## Rollback Procedures
-
-If something goes wrong:
-
-- Before push: `git reset --hard origin/core/X.Y`
-- After PR creation: Close PR and start over
-- After failed release: Create new patch version with fixes
-- Document any issues for future reference
-
-## Important Notes
-
-- **Always try automated backports first** - This command is for when automation fails
-- Core branch version will be behind main - this is expected
-- The "Release" label triggers the PyPI/npm publication
-- **CRITICAL**: Always uncheck "Set as latest release" for hotfix releases
-- **Must create ComfyUI requirements.txt PR** - Hotfix isn't complete without it
-- PR numbers must include the `#` prefix
-- Mixed commits/PRs are supported but review carefully
-- Always wait for full test suite before proceeding
-
-## Modern Workflow Context
-
-**Primary Backport Method:** Automated via `needs-backport` + `X.YY` labels
-**This Command Usage:**
-
-- Smart path detection - skip to version bump if backports already merged
-- Fallback to manual cherry-picking only when automation fails/has conflicts
-  **Complete Hotfix:** Includes GitHub release publishing + ComfyUI requirements.txt integration
-
-## Workflow Paths
-
-- **Path A:** Backports already merged → Skip to Step 10 (Version Bump)
-- **Path B:** Backport PRs need merging → Merge them → Skip to Step 10 (Version Bump)
-- **Path C:** No/failed backports → Manual cherry-picking (Steps 2-9) → Version Bump (Step 10)
-
-This process ensures a complete hotfix release with proper GitHub publishing, ComfyUI integration, and multiple safety checkpoints.

.claude/commands/pr.md

@@ -1,131 +0,0 @@
-# Create PR
-
-Automate PR creation with proper tags, labels, and concise summary.
-
-## Step 1: Check Prerequisites
-
-```bash
-# Ensure you have uncommitted changes
-git status
-
-# If changes exist, commit them first
-git add .
-git commit -m "[tag] Your commit message"
-```
-
-## Step 2: Push and Create PR
-
-You'll create the PR with the following structure:
-
-### PR Tags (use in title)
-
-- `[feat]` - New features → label: `enhancement`
-- `[bugfix]` - Bug fixes → label: `verified bug`
-- `[refactor]` - Code restructuring → label: `enhancement`
-- `[docs]` - Documentation → label: `documentation`
-- `[test]` - Test changes → label: `enhancement`
-- `[ci]` - CI/CD changes → label: `enhancement`
-
-### Label Mapping
-
-#### General Labels
-
-- Feature/Enhancement: `enhancement`
-- Bug fixes: `verified bug`
-- Documentation: `documentation`
-- Dependencies: `dependencies`
-- Performance: `Performance`
-- Desktop app: `Electron`
-
-#### Product Area Labels
-
-**Core Features**
-
-- `area:nodes` - Node-related functionality
-- `area:workflows` - Workflow management
-- `area:queue` - Queue system
-- `area:models` - Model handling
-- `area:templates` - Template system
-- `area:subgraph` - Subgraph functionality
-
-**UI Components**
-
-- `area:ui` - General user interface improvements
-- `area:widgets` - Widget system
-- `area:dom-widgets` - DOM-based widgets
-- `area:links` - Connection links between nodes
-- `area:groups` - Node grouping functionality
-- `area:reroutes` - Reroute nodes
-- `area:previews` - Preview functionality
-- `area:minimap` - Minimap navigation
-- `area:floating-toolbox` - Floating toolbar
-- `area:mask-editor` - Mask editing tools
-
-**Navigation & Organization**
-
-- `area:navigation` - Navigation system
-- `area:search` - Search functionality
-- `area:workspace-management` - Workspace features
-- `area:topbar-menu` - Top bar menu
-- `area:help-menu` - Help menu system
-
-**System Features**
-
-- `area:settings` - Settings/preferences
-- `area:hotkeys` - Keyboard shortcuts
-- `area:undo-redo` - Undo/redo system
-- `area:customization` - Customization features
-- `area:auth` - Authentication
-- `area:comms` - Communication/networking
-
-**Development & Infrastructure**
-
-- `area:CI/CD` - CI/CD pipeline
-- `area:testing` - Testing infrastructure
-- `area:vue-migration` - Vue migration work
-- `area:manager` - ComfyUI Manager integration
-
-**Platform-Specific**
-
-- `area:mobile` - Mobile support
-- `area:3d` - 3D-related features
-
-**Special Areas**
-
-- `area:i18n` - Translation/internationalization
-- `area:CNR` - Comfy Node Registry
-
-## Step 3: Execute PR Creation
-
-```bash
-# First, push your branch
-git push -u origin $(git branch --show-current)
-
-# Then create the PR (replace placeholders)
-gh pr create \
-  --title "[TAG] Brief description" \
-  --body "$(cat <<'EOF'
-## Summary
-One sentence describing what changed and why.
-
-## Changes
-- **What**: Core functionality added/modified
-- **Breaking**: Any breaking changes (if none, omit this line)
-- **Dependencies**: New dependencies (if none, omit this line)
-
-## Review Focus
-- Critical design decisions or edge cases that need attention
-
-Fixes #ISSUE_NUMBER
-EOF
-)" \
-  --label "APPROPRIATE_LABEL" \
-  --base main
-```
-
-## Additional Options
-
-- Add multiple labels: `--label "enhancement,Performance"`
-- Request reviewers: `--reviewer @username`
-- Mark as draft: `--draft`
-- Open in browser after creation: `--web`

.claude/commands/setup_repo.md

@@ -1,158 +0,0 @@
-# Setup Repository
-
-Bootstrap the ComfyUI Frontend monorepo with all necessary dependencies and verification checks.
-
-## Overview
-
-This command will:
-
-1. Install pnpm package manager (if not present)
-2. Install all project dependencies
-3. Verify the project builds successfully
-4. Run unit tests to ensure functionality
-5. Start development server to verify frontend boots correctly
-
-## Prerequisites Check
-
-First, let's verify the environment:
-
-```bash
-# Check Node.js version (should be >= 24)
-node --version
-
-# Check if we're in a git repository
-git status
-```
-
-## Step 1: Install pnpm
-
-```bash
-# Check if pnpm is already installed
-pnpm --version 2>/dev/null || {
-  echo "Installing pnpm..."
-  npm install -g pnpm
-}
-
-# Verify pnpm installation
-pnpm --version
-```
-
-## Step 2: Install Dependencies
-
-```bash
-# Install all dependencies using pnpm
-echo "Installing project dependencies..."
-pnpm install
-
-# Verify node_modules exists and has packages
-ls -la node_modules | head -5
-```
-
-## Step 3: Verify Build
-
-```bash
-# Run TypeScript type checking
-echo "Running TypeScript checks..."
-pnpm typecheck
-
-# Build the project
-echo "Building project..."
-pnpm build
-
-# Verify dist folder was created
-ls -la dist/
-```
-
-## Step 4: Run Unit Tests
-
-```bash
-# Run unit tests
-echo "Running unit tests..."
-pnpm test:unit
-
-# If tests fail, show the output and stop
-if [ $? -ne 0 ]; then
-  echo "❌ Unit tests failed. Please fix failing tests before continuing."
-  exit 1
-fi
-
-echo "✅ Unit tests passed successfully"
-```
-
-## Step 5: Verify Development Server
-
-```bash
-# Start development server in background
-echo "Starting development server..."
-pnpm dev &
-SERVER_PID=$!
-
-# Wait for server to start (check for port 5173 or similar)
-echo "Waiting for server to start..."
-sleep 10
-
-# Check if server is running
-if curl -s http://localhost:5173 > /dev/null 2>&1; then
-  echo "✅ Development server started successfully at http://localhost:5173"
-
-  # Kill the background server
-  kill $SERVER_PID
-  wait $SERVER_PID 2>/dev/null
-else
-  echo "❌ Development server failed to start or is not accessible"
-  kill $SERVER_PID 2>/dev/null
-  wait $SERVER_PID 2>/dev/null
-  exit 1
-fi
-```
-
-## Step 6: Final Verification
-
-```bash
-# Run linting to ensure code quality
-echo "Running linter..."
-pnpm lint
-
-# Show project status
-echo ""
-echo "🎉 Repository setup complete!"
-echo ""
-echo "Available commands:"
-echo "  pnpm dev          - Start development server"
-echo "  pnpm build        - Build for production"
-echo "  pnpm test:unit    - Run unit tests"
-echo "  pnpm typecheck    - Run TypeScript checks"
-echo "  pnpm lint         - Run ESLint"
-echo "  pnpm format       - Format code with oxfmt"
-echo ""
-echo "Next steps:"
-echo "1. Run 'pnpm dev' to start developing"
-echo "2. Open http://localhost:5173 in your browser"
-echo "3. Check README.md for additional setup instructions"
-```
-
-## Troubleshooting
-
-If any step fails:
-
-1. **pnpm installation fails**: Try using `curl -fsSL https://get.pnpm.io/install.sh | sh -`
-2. **Dependencies fail to install**: Try clearing cache with `pnpm store prune` and retry
-3. **Build fails**: Check for TypeScript errors and fix them first
-4. **Tests fail**: Review test output and fix failing tests
-5. **Dev server fails**: Check if port 5173 is already in use
-
-## Manual Verification Steps
-
-After running the setup, manually verify:
-
-1. **Dependencies installed**: `ls node_modules | wc -l` should show many packages
-2. **Build artifacts**: `ls dist/` should show built files
-3. **Server accessible**: Open http://localhost:5173 in browser
-4. **Hot reload works**: Edit a file and see changes reflect
-
-## Environment Requirements
-
-- Node.js >= 24
-- Git repository
-- Internet connection for package downloads
-- Available ports (typically 5173 for dev server)

.claude/commands/verify-visually.md

@@ -1,58 +0,0 @@
-Your task is to perform visual verification of our recent changes to ensure they display correctly in the browser. This verification is critical for catching visual regressions, layout issues, and ensuring our UI changes render properly for end users.
-
-<instructions>
-Follow these steps systematically to verify our changes:
-
-1. **Server Setup**
-   - Check if the dev server is running on port 5173 using browser navigation or port checking
-   - If not running, start it with `pnpm dev` from the root directory
-   - If the server fails to start, provide detailed troubleshooting steps by reading package.json and README.md for accurate instructions
-   - Wait for the server to be fully ready before proceeding
-
-2. **Visual Testing Process**
-   - Navigate to http://localhost:5173/
-   - For each target page (specified in arguments or recently changed files):
-     - Navigate to the page using direct URL or site navigation
-     - Take a high-quality screenshot
-     - Analyze the screenshot for the specific changes we implemented
-     - Document any visual issues or improvements needed
-
-3. **Quality Verification**
-   Check each page for:
-   - Content accuracy and completeness
-   - Proper styling and layout alignment
-   - Responsive design elements
-   - Navigation functionality
-   - Image loading and display
-   - Typography and readability
-   - Color scheme consistency
-   - Interactive elements (buttons, links, forms)
-     </instructions>
-
-<examples>
-Common issues to watch for:
-- Broken layouts or overlapping elements
-- Missing images or broken image links
-- Inconsistent styling or spacing
-- Navigation menu problems
-- Mobile responsiveness issues
-- Text overflow or truncation
-- Color contrast problems
-</examples>
-
-<reporting>
-For each page tested, provide:
-1. Page URL and screenshot
-2. Confirmation that changes display correctly OR detailed description of issues found
-3. Any design improvement suggestions
-4. Overall assessment of visual quality
-
-If you find issues, be specific about:
-
-- Exact location of the problem
-- Expected vs actual behavior
-- Severity level (critical, important, minor)
-- Suggested fix if obvious
-  </reporting>
-
-Remember: Take your time with each screenshot and analysis. Visual quality directly impacts user experience and our project's professional appearance.

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

@@ -1,150 +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 (`reference/discovery.md`)
-2. **Analyze** — Categorize MUST/SHOULD/SKIP, check deps (`reference/analysis.md`)
-3. **Plan** — Order by dependency (leaf fixes first), group into waves per branch
-4. **Execute** — Label-driven automation → worktree fallback for conflicts (`reference/execution.md`)
-5. **Verify** — After each wave, verify branch integrity before proceeding
-6. **Log & Report** — Generate session report with mermaid diagram (`reference/logging.md`)
-
-## System Context
-
-| Item           | Value                                             |
-| -------------- | ------------------------------------------------- |
-| Repo           | `~/ComfyUI_frontend` (Comfy-Org/ComfyUI_frontend) |
-| Merge strategy | Squash merge (`gh pr merge --squash --admin`)     |
-| Automation     | `pr-backport.yaml` GitHub Action (label-driven)   |
-| Tracking dir   | `~/temp/backport-session/`                        |
-
-## Branch Scope Rules
-
-**Critical: Match PRs to the correct target branches.**
-
-| Branch prefix | Scope                          | Example                                   |
-| ------------- | ------------------------------ | ----------------------------------------- |
-| `cloud/*`     | Cloud-hosted ComfyUI only      | App mode, cloud auth, cloud-specific UI   |
-| `core/*`      | Local/self-hosted ComfyUI only | Core editor, local workflows, node system |
-
-**⚠️ NEVER backport cloud-only PRs to `core/*` branches.** Cloud-only changes (app mode, cloud auth, cloud billing UI, cloud-specific API calls) are irrelevant to local users and waste effort. Before backporting any PR to a `core/*` branch, check:
-
-- Does the PR title/description mention "app mode", "cloud", or cloud-specific features?
-- Does the PR only touch files like `appModeStore.ts`, cloud auth, or cloud-specific components?
-- If yes → skip for `core/*` branches (may still apply to `cloud/*` branches)
-
-## ⚠️ 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.
-
-## 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)                      |
-| **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** — App mode, cloud auth, cloud billing. These only affect cloud-hosted ComfyUI.
-
-## 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
-git worktree remove /tmp/verify-TARGET --force
-```
-
-If typecheck fails, stop and investigate before continuing. A broken branch after wave N means all subsequent waves will compound the problem.
-
-## 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
-
-## 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
-git checkout -b backport-$PR-to-$BRANCH origin/$BRANCH
-git cherry-pick -m 1 $MERGE_SHA
-# Resolve conflicts, push, create PR, merge
-```
-
-### PR Title Convention
-
-```
-[backport TARGET_BRANCH] Original Title (#ORIGINAL_PR)
-```

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

@@ -1,68 +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 (app mode, cloud auth, cloud billing, cloud-specific UI) |
-| `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
-
-## 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
-
-Present decisions.md before execution. Include:
-
-1. All MUST/SHOULD/SKIP categorizations with rationale
-2. Questions for human (feature existence, scope, deps)
-3. Estimated effort per branch

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

@@ -1,42 +0,0 @@
-# Discovery — Candidate Collection
-
-## 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'
-```
-
-## Output: candidate_list.md
-
-Table per target branch:
-| PR# | Title | Category | Flagged by Bot? | Decision |

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

@@ -1,150 +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 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
-gh pr list --base TARGET_BRANCH --state open --limit 50 --json number,title
-```
-
-## Step 2: Review & Merge Clean Auto-PRs
-
-```bash
-for pr in $AUTO_PRS; do
-  # Check size
-  gh pr view $pr --json title,additions,deletions,changedFiles \
-    --jq '"Files: \(.changedFiles), +\(.additions)/-\(.deletions)"'
-  # Admin merge
-  gh pr merge $pr --squash --admin
-  sleep 3
-done
-```
-
-## 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
-  # See SKILL.md Conflict Triage table for resolution per type.
-
-  # Resolve all conflicts, then:
-  git add .
-  GIT_EDITOR=true git cherry-pick --continue
-
-  git push origin backport-$PR-to-TARGET
-  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+$')
-  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
-git worktree remove /tmp/verify-TARGET --force
-```
-
-If verification fails, stop and fix before proceeding to the next wave. Do not compound problems across waves.
-
-## 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. 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
-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` on the target branch after merging a batch. Catching breakage early prevents compounding errors.
-11. **Cloud-only PRs don't belong on core/\* branches** — app mode, cloud auth, and cloud-specific UI changes are irrelevant to local users. Always check PR scope against branch scope before backporting.

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

@@ -1,96 +0,0 @@
-# Logging & Session Reports
-
-## During Execution
-
-Maintain `execution-log.md` with per-branch tables:
-
-```markdown
-| PR#   | Title | Status                            | Backport PR | Notes   |
-| ----- | ----- | --------------------------------- | ----------- | ------- |
-| #XXXX | Title | ✅ Merged / ⏭️ Skip / ⏸️ Deferred | #YYYY       | Details |
-```
-
-## Wave Verification Log
-
-Track verification results per wave:
-
-```markdown
-## Wave N Verification — TARGET_BRANCH
-
-- PRs merged: #A, #B, #C
-- Typecheck: ✅ Pass / ❌ Fail
-- Issues found: (if any)
-- Human review needed: (list any non-trivial conflict resolutions)
-```
-
-## 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 |
-
-## 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 Deliverable: Visual Summary
-
-At session end, generate a **mermaid diagram** showing all backported PRs organized by target branch and category (MUST/SHOULD), plus a summary table. Present this to the user as the final output.
-
-```mermaid
-graph TD
-    subgraph branch1["☁️ cloud/X.XX — N PRs"]
-        C1["#XXXX title"]
-        C2["#XXXX title"]
-    end
-
-    subgraph branch2must["🔴 core/X.XX MUST — N PRs"]
-        M1["#XXXX title"]
-    end
-
-    subgraph branch2should["🟡 core/X.XX SHOULD — N PRs"]
-        S1["#XXXX-#XXXX N auto-merged"]
-        S2["#XXXX-#XXXX N manual picks"]
-    end
-
-    classDef cloudStyle fill:#1a3a5c,stroke:#4da6ff,color:#e0f0ff
-    classDef coreStyle fill:#1a4a2e,stroke:#4dff88,color:#e0ffe8
-    classDef mustStyle fill:#5c1a1a,stroke:#ff4d4d,color:#ffe0e0
-    classDef shouldStyle fill:#4a3a1a,stroke:#ffcc4d,color:#fff5e0
-```
-
-Use the `mermaid` tool to render this diagram and present it alongside the summary table as the session's final deliverable.
-
-## Files to Track
-
-- `candidate_list.md` — all candidates per branch
-- `decisions.md` — MUST/SHOULD/SKIP with rationale
-- `wave-plan.md` — execution order
-- `execution-log.md` — real-time status
-- `backport-session-report.md` — final summary
-
-All in `~/temp/backport-session/`.

.claude/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.

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

@@ -1,200 +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                                               |
-
-## 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: `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`
-
-## 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.

.coderabbit.yaml

@@ -1,14 +0,0 @@
-issue_enrichment:
-  auto_enrich:
-    enabled: true
-reviews:
-  high_level_summary: false
-  auto_review:
-    drafts: true
-    ignore_title_keywords:
-      - '[release]'
-      - '[backport'
-    ignore_usernames:
-      - comfy-pr-bot
-      - github-actions
-      - github-actions[bot]

.cursorrules

@@ -0,0 +1,54 @@
+// Vue 3 Composition API .cursorrules
+
+// Vue 3 Composition API best practices
+const vue3CompositionApiBestPractices = [
+  "Use setup() function for component logic",
+  "Utilize ref and reactive for reactive state",
+  "Implement computed properties with computed()",
+  "Use watch and watchEffect for side effects",
+  "Implement lifecycle hooks with onMounted, onUpdated, etc.",
+  "Utilize provide/inject for dependency injection",
+  "Use vue 3.5 style of default prop declaration. Example:
+
+const { nodes, showTotal = true } = defineProps<{
+  nodes: ApiNodeCost[]
+  showTotal?: boolean
+}>()
+
+",
+  "Organize vue component in <template> <script> <style> order",
+]
+
+// Folder structure
+const folderStructure = `
+src/
+  components/
+  constants/
+  composables/
+  views/
+  stores/
+  services/
+  App.vue
+  main.ts
+`;
+
+// Tailwind CSS best practices
+const tailwindCssBestPractices = [
+  "Use Tailwind CSS for styling",
+  "Implement responsive design with Tailwind CSS",
+]
+
+// Additional instructions
+const additionalInstructions = `
+1. Leverage VueUse functions for performance-enhancing styles
+2. Use lodash for utility functions
+3. Use TypeScript for type safety
+4. Implement proper props and emits definitions
+5. Utilize Vue 3's Teleport component when needed
+6. Use Suspense for async components
+7. Implement proper error handling
+8. Follow Vue 3 style guide and naming conventions
+9. Use Vite for fast development and building
+10. Use vue-i18n in composition API for any string literals. Place new translation
+entries in src/locales/en/main.json.
+`;

.env_example

@@ -5,43 +5,16 @@ PLAYWRIGHT_TEST_URL=http://localhost:5173
 
 # Proxy target of the local development server
 # Note: localhost:8188 does not work.
-# Cloud auto-detection: Setting this to any *.comfy.org URL automatically enables
-# cloud mode (DISTRIBUTION=cloud) without needing to set DISTRIBUTION separately.
-# Examples: https://testcloud.comfy.org/, https://stagingcloud.comfy.org/,
-#           https://pr-123.testenvs.comfy.org/, https://cloud.comfy.org/
 DEV_SERVER_COMFYUI_URL=http://127.0.0.1:8188
 
 # Allow dev server access from remote IP addresses.
 # If true, the vite dev server will listen on all addresses, including LAN
 # and public addresses.
-# VITE_REMOTE_DEV=true
+VITE_REMOTE_DEV=false
 
 # The directory containing the ComfyUI installation used to run Playwright tests.
 # If you aren't using a separate install for testing, point this to your regular install.
 TEST_COMFYUI_DIR=/home/ComfyUI
 
 # Whether to enable minification of the frontend code.
-# ENABLE_MINIFY=true
-
-# Whether to disable proxying the `/templates` route. If true, allows you to
-# serve templates from the ComfyUI_frontend/public/templates folder (for
-# locally testing changes to templates). When false or nonexistent, the
-# templates are served via the normal method from the server's python site
-# packages.
-# DISABLE_TEMPLATES_PROXY=true
-
-# If playwright tests are being run via vite dev server, Vue plugins will
-# invalidate screenshots.  When `true`, vite plugins will not be loaded.
-# DISABLE_VUE_PLUGINS=true
-
-# Algolia credentials required for developing with the new custom node manager.
-ALGOLIA_APP_ID=4E0RO38HS8
-ALGOLIA_API_KEY=684d998c36b67a9a9fce8fc2d8860579
-
-# Enable PostHog debug logging in the browser console.
-# VITE_POSTHOG_DEBUG=true
-
-# 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
+ENABLE_MINIFY=true

.git-blame-ignore-revs

@@ -1,30 +0,0 @@
-# .git-blame-ignore-revs
-# List of commits to ignore in git blame
-# Format: <commit hash> # <description>
-
-# npm run format on litegraph merge (10,672 insertions, 7,327 deletions across 129 files)
-c53f197de2a3e0fa66b16dedc65c131235c1c4b6
-
-# Reorganize renderer components into domain-driven folder structure
-c8a83a9caede7bdb5f8598c5492b07d08c339d49
-
-# Domain-driven design (DDD) refactors - September 2025
-# These commits reorganized the codebase into domain-driven architecture
-
-# [refactor] Improve renderer domain organization (#5552)
-6349ceee6c0a57fc7992e85635def9b6e22eaeb2
-
-# [refactor] Improve settings domain organization (#5550)  
-4c8c4a1ad4f53354f700a33ea1b95262aeda2719
-
-# [refactor] Improve workflow domain organization (#5584)
-ca312fd1eab540cc4ddc0e3d244d38b3858574f0
-
-# [refactor] Move thumbnail functionality to renderer/core domain (#5586)
-e3bb29ceb8174b8bbca9e48ec7d42cd540f40efa
-
-# [refactor] Improve updates/notifications domain organization (#5590)
-27ab355f9c73415dc39f4d3f512b02308f847801
-
-# Migrate Tailwind styles to design-system package
-9f19d8fb4bd22518879343b49c05634dca777df0

.gitattributes

@@ -1,6 +1,7 @@
-# Force all text files to use LF line endings
-* text=auto eol=lf
+# Default
+* text=auto
 
-# Generated files
-packages/registry-types/src/comfyRegistryTypes.ts linguist-generated=true
-src/workbench/extensions/manager/types/generatedManagerTypes.ts linguist-generated=true
+# Force TS to LF to make the unixy scripts not break on Windows
+*.ts text eol=lf
+*.vue text eol=lf
+*.js text eol=lf

.github/AGENTS.md

@@ -1,23 +0,0 @@
-# PR Review Context
-
-Context for automated PR review system.
-
-## Review Scope
-
-This automated review performs comprehensive analysis:
-
-- Architecture and design patterns
-- Security vulnerabilities
-- Performance implications
-- Code quality and maintainability
-- Integration concerns
-
-For implementation details, see `.claude/commands/comprehensive-pr-review.md`.
-
-## GitHub Actions: Fork PR Permissions
-
-Fork PRs get a **read-only `GITHUB_TOKEN`** — no PR comments, no secret access, no pushing.
-
-Any workflow that needs write access must use the **two-workflow split**: a `pull_request`-triggered `ci-*.yaml` uploads artifacts (including PR metadata), then a `workflow_run`-triggered `pr-*.yaml` downloads them and posts comments with write permissions. See `ci-size-data` → `pr-size-report` or `ci-perf-report` → `pr-perf-report`. Use `.github/actions/post-pr-report-comment` for the comment step.
-
-Never write PR comments directly from `pull_request` workflows or use `pull_request_target` to run untrusted code.

.github/CLAUDE.md

@@ -1,4 +0,0 @@
-<!-- A rose by any other name would smell as sweet,
-     But Claude insists on files named for its own conceit. -->
-
-@AGENTS.md

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -1,102 +1,90 @@
 name: Bug Report
-description: 'Report something that is not working correctly'
+description: "Something is not behaving as expected."
+title: "[Bug]: "
 labels: ['Potential Bug']
-type: Bug
-
 body:
-  - type: checkboxes
-    attributes:
-      label: Prerequisites
-      options:
-        - label: I am running the latest version of ComfyUI
-          required: true
-        - label: I have custom nodes enabled
-
-  - type: textarea
-    id: description
-    attributes:
-      label: What happened?
-      description: A clear and concise description of the bug. Include screenshots or videos if helpful.
-      placeholder: |
-        Example: "When I connect a VAE Decode node to a KSampler, the connection line appears but the workflow fails to execute with an error message..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: reproduce
-    attributes:
-      label: Steps to Reproduce
-      description: How can we reproduce this issue? Please attach your workflow (JSON or PNG).
-      placeholder: |
-        1. Add a KSampler node
-        2. Connect it to...
-        3. Click Queue Prompt
-        4. See error
-      value: |
-        1.
-        2.
-        3.
-    validations:
-      required: true
-
-  - type: dropdown
-    id: severity
-    attributes:
-      label: How is this affecting you?
-      options:
-        - Crashes ComfyUI completely
-        - Workflow won't execute
-        - Feature doesn't work as expected
-        - Visual/UI issue only
-        - Minor inconvenience
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: ComfyUI Frontend Version
-      description: Found in Settings > About (e.g., "1.3.45")
-      placeholder: '1.3.45'
-    validations:
-      required: true
-
-  - type: dropdown
-    id: browser
-    attributes:
-      label: Browser
-      description: Which browser are you using?
-      options:
-        - Chrome/Chromium
-        - Firefox
-        - Safari
-        - Edge
-        - Other
-    validations:
-      required: true
-
   - type: markdown
     attributes:
       value: |
-        ## Additional Information (Optional)
-        *The following fields help us debug complex issues but are not required for most bug reports.*
+        Before submitting a **Bug Report**, please ensure the following:
+
+        - **1:** You are running the latest version of ComfyUI.
+        - **2:** You have looked at the existing bug reports and made sure this isn't already reported.
+        - **3:** You confirmed that the bug is not caused by a custom node. You can disable all custom nodes by passing
+        `--disable-all-custom-nodes` command line argument.
 
   - type: textarea
-    id: console-errors
     attributes:
-      label: Console Errors
-      description: If you see red error messages in the browser console (F12), paste them here
-      render: javascript
+      label: Frontend Version
+      description: |
+        What is the frontend version you are using? You can check this in the settings dialog.
 
-  - type: textarea
-    id: logs
-    attributes:
-      label: Logs
-      description: If relevant, paste any terminal/server logs here
-      render: shell
+        <details>
 
+        <summary>Click to show where to find the version</summary>
+
+        Open the setting by clicking the cog icon in the bottom-left of the screen, then click `About`.
+
+        ![Frontend version](https://github.com/user-attachments/assets/561fb7c3-3012-457c-a494-9bdc1ff035c0)
+
+        </details>
+    validations:
+      required: true
   - type: textarea
-    id: additional
     attributes:
-      label: Additional Context
-      description: Any other information that might help (OS, GPU, specific nodes involved, etc.)
+      label: Expected Behavior
+      description: 'What you expected to happen.'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      description: 'What actually happened. Please include a screenshot / video clip of the issue if possible.'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps to Reproduce
+      description: "Describe how to reproduce the issue. Please be sure to attach a workflow JSON or PNG, ideally one that doesn't require custom nodes to test. If the bug open happens when certain custom nodes are used, most likely that custom node is what has the bug rather than ComfyUI, in which case it should be reported to the node's author."
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Debug Logs
+      description: 'Please copy the output from your terminal logs here.'
+      render: powershell
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Browser Logs
+      description: 'Please copy the output from your browser logs here. You can access this by pressing F12 to toggle the developer tools, then navigating to the Console tab.'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Setting JSON
+      description: 'Please upload the setting file here. The setting file is located at `user/default/comfy.settings.json`'
+    validations:
+      required: true
+  - type: dropdown
+    id: browsers
+    attributes:
+      label: What browsers do you use to access the UI ?
+      multiple: true
+      options:
+        - Mozilla Firefox
+        - Google Chrome
+        - Brave
+        - Apple Safari
+        - Microsoft Edge
+        - Android
+        - iOS
+        - Other
+  - type: textarea
+    attributes:
+      label: Other Information
+      description: 'Any other context, details, or screenshots that might help solve the issue.'
+      placeholder: 'Add any other relevant information here...'
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature-request.yaml

@@ -1,73 +1,40 @@
 name: Feature Request
-description: Report a problem or limitation you're experiencing
-labels: []
-type: Feature
+description: Suggest an idea for this project
+title: "[Feature Request]: "
+labels: ["enhancement"]
 
 body:
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the feature you want, and that it's not implemented in a recent build/commit.
+      options:
+        - label: I have searched the existing issues and checked the recent builds/commits
+          required: true
   - type: markdown
     attributes:
       value: |
-        *Please focus on describing the problem you're experiencing rather than proposing specific solutions. This helps us design the best possible solution for you and other users.*
+        *Please fill this form with as much information as possible, provide screenshots and/or illustrations of the feature if possible*
   - type: textarea
-    id: problem
+    id: feature
     attributes:
-      label: What problem are you experiencing?
-      description: Describe the issue or limitation you're facing in your workflow
-      placeholder: |
-        Example: "I frequently lose work when switching between different projects because there's no way to save my current workspace state"
-        NOT: "Add a save button that exports the workspace"
+      label: What would your feature do ?
+      description: Tell us about your feature in a very clear and simple way, and what problem it would solve
     validations:
       required: true
   - type: textarea
-    id: context
+    id: workflow
     attributes:
-      label: When does this problem occur?
-      description: Describe the specific situations or workflows where you encounter this issue
-      placeholder: |
-        - When working with large node graphs...
-        - During batch processing workflows...
-        - While collaborating with team members...
-    validations:
-      required: true
-  - type: dropdown
-    id: frequency
-    attributes:
-      label: How often do you encounter this problem?
-      options:
-        - Multiple times per day
-        - Daily
-        - Several times per week
-        - Weekly
-        - Occasionally
-        - Rarely
-    validations:
-      required: true
-  - type: dropdown
-    id: impact
-    attributes:
-      label: How much does this problem affect your workflow?
-      description: Help us understand the severity of this issue for you
-      options:
-        - Blocks me from completing tasks
-        - Significantly slows down my work
-        - Causes moderate inconvenience
-        - Minor annoyance
+      label: Proposed workflow
+      description: Please provide us with step by step information on how you'd like the feature to be accessed and used
+      value: |
+        1. Go to ....
+        2. Press ....
+        3. ...
     validations:
       required: true
   - type: textarea
-    id: workaround
+    id: misc
     attributes:
-      label: Current workarounds
-      description: How do you currently deal with this problem, if at all?
-      placeholder: |
-        Example: "I manually export and reimport nodes between projects, which takes 10-15 minutes each time"
-  - type: textarea
-    id: ideas
-    attributes:
-      label: Ideas for solutions (Optional)
-      description: If you have thoughts on potential solutions, feel free to share them here. However, we'll explore all possible options to find the best approach.
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional context
-      description: Add any other context, screenshots, or examples that help illustrate the problem.
+      label: Additional information
+      description: Add any other context or screenshots about the feature request here.

.github/actions/comment-release-links/action.yaml

@@ -1,119 +0,0 @@
-name: Post Release Summary Comment
-description: Post or update a PR comment summarizing release links with diff, derived versions, and optional extras.
-author: ComfyUI Frontend Team
-
-inputs:
-  issue-number:
-    description: Optional PR number override (defaults to the current pull request)
-    default: ''
-  version_file:
-    description: Path to the JSON file containing the current version (relative to repo root)
-    required: true
-
-outputs:
-  prev_version:
-    description: Previous version derived from the parent commit
-    value: ${{ steps.build.outputs.prev_version }}
-
-runs:
-  using: composite
-  steps:
-    - name: Build comment body
-      id: build
-      shell: bash
-      run: |
-        set -euo pipefail
-
-        VERSION_FILE="${{ inputs.version_file }}"
-        REPO="${{ github.repository }}"
-
-        if [[ -z "$VERSION_FILE" ]]; then
-          echo "::error::version_file input is required" >&2
-          exit 1
-        fi
-
-        PREV_JSON=$(git show HEAD^1:"$VERSION_FILE" 2>/dev/null || true)
-        if [[ -z "$PREV_JSON" ]]; then
-          echo "::error::Unable to read $VERSION_FILE from parent commit" >&2
-          exit 1
-        fi
-        PREV_VERSION=$(printf '%s' "$PREV_JSON" | node -pe "const data = JSON.parse(require('fs').readFileSync(0, 'utf8')); if (!data.version) { process.exit(1); } data.version")
-        if [[ -z "$PREV_VERSION" ]]; then
-          echo "::error::Unable to determine previous version from $VERSION_FILE" >&2
-          exit 1
-        fi
-
-        NEW_VERSION=$(node -pe "const fs=require('fs');const data=JSON.parse(fs.readFileSync(process.argv[1],'utf8'));if(!data.version){process.exit(1);}data.version" "$VERSION_FILE")
-        if [[ -z "$NEW_VERSION" ]]; then
-          echo "::error::Unable to determine current version from $VERSION_FILE" >&2
-          exit 1
-        fi
-
-        MARKER='release-summary'
-        MESSAGE='Publish jobs finished successfully:'
-        LINKS_VALUE=''
-
-        case "$VERSION_FILE" in
-          package.json)
-            LINKS_VALUE=$(printf '%s\n%s' \
-              'PyPI|https://pypi.org/project/comfyui-frontend-package/{{version}}/' \
-              'npm types|https://www.npmjs.com/package/@comfyorg/comfyui-frontend-types/v/{{version}}')
-            ;;
-          apps/desktop-ui/package.json)
-            MARKER='desktop-release-summary'
-            LINKS_VALUE='npm desktop UI|https://www.npmjs.com/package/@comfyorg/desktop-ui/v/{{version}}'
-            ;;
-        esac
-
-        DIFF_PREFIX='v'
-        DIFF_LABEL='Diff'
-        DIFF_URL="https://github.com/${REPO}/compare/${DIFF_PREFIX}${PREV_VERSION}...${DIFF_PREFIX}${NEW_VERSION}"
-        COMMENT_FILE=$(mktemp)
-
-        {
-          echo "<!--$MARKER:$DIFF_PREFIX$NEW_VERSION-->"
-          echo "$MESSAGE"
-          echo ""
-          echo "- $DIFF_LABEL: [\`$DIFF_PREFIX$PREV_VERSION...$DIFF_PREFIX$NEW_VERSION\`]($DIFF_URL)"
-
-          while IFS= read -r RAW_LINE; do
-            LINE=$(echo "$RAW_LINE" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-            [[ -z "$LINE" ]] && continue
-            if [[ "$LINE" != *"|"* ]]; then
-              echo "::warning::Skipping malformed link entry: $LINE" >&2
-              continue
-            fi
-            LABEL=${LINE%%|*}
-            URL_TEMPLATE=${LINE#*|}
-            URL=${URL_TEMPLATE//\{\{version\}\}/$NEW_VERSION}
-            URL=${URL//\{\{prev_version\}\}/$PREV_VERSION}
-            echo "- $LABEL: [\`$NEW_VERSION\`]($URL)"
-          done <<< "$LINKS_VALUE"
-
-          echo ""
-        } > "$COMMENT_FILE"
-
-        {
-          echo "body<<COMMENT_BODY_END_MARKER"
-          cat "$COMMENT_FILE"
-          echo "COMMENT_BODY_END_MARKER"
-        } >> "$GITHUB_OUTPUT"
-        echo "prev_version=$PREV_VERSION" >> "$GITHUB_OUTPUT"
-        echo "marker_search=<!--$MARKER:" >> "$GITHUB_OUTPUT"
-        echo "new_version=$NEW_VERSION" >> "$GITHUB_OUTPUT"
-
-    - name: Find existing comment
-      id: find
-      uses: peter-evans/find-comment@b30e6a3c0ed37e7c023ccd3f1db5c6c0b0c23aad # v4.0.0
-      with:
-        issue-number: ${{ inputs.issue-number || github.event.pull_request.number }}
-        comment-author: github-actions[bot]
-        body-includes: ${{ steps.build.outputs.marker_search }}
-
-    - name: Post or update comment
-      uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9 # v5.0.0
-      with:
-        issue-number: ${{ inputs.issue-number || github.event.pull_request.number }}
-        comment-id: ${{ steps.find.outputs.comment-id }}
-        body: ${{ steps.build.outputs.body }}
-        edit-mode: replace

.github/actions/post-pr-report-comment/action.yaml

@@ -1,35 +0,0 @@
-name: Post PR Report Comment
-description: Reads a markdown report file and posts/updates a single idempotent comment on a PR.
-
-inputs:
-  pr-number:
-    description: PR number to comment on
-    required: true
-  report-file:
-    description: Path to the markdown report file
-    required: true
-  comment-marker:
-    description: HTML comment marker for idempotent matching
-    required: true
-  token:
-    description: GitHub token with pull-requests write permission
-    required: true
-
-runs:
-  using: composite
-  steps:
-    - name: Read report
-      id: report
-      uses: juliangruber/read-file-action@b549046febe0fe86f8cb4f93c24e284433f9ab58 # v1.1.7
-      with:
-        path: ${{ inputs.report-file }}
-
-    - name: Create or update PR comment
-      uses: actions-cool/maintain-one-comment@4b2dbf086015f892dcb5e8c1106f5fccd6c1476b # v3.2.0
-      with:
-        token: ${{ inputs.token }}
-        number: ${{ inputs.pr-number }}
-        body: |
-          ${{ steps.report.outputs.content }}
-          ${{ inputs.comment-marker }}
-        body-include: ${{ inputs.comment-marker }}

.github/actions/setup-comfyui-server/action.yaml

@@ -1,55 +0,0 @@
-name: Setup ComfyUI Server
-description: 'Setup ComfyUI server for continuous integration (with ComfyUI_devtools node installed)'
-inputs:
-  extra_server_params:
-    description: 'Additional parameters to pass to ComfyUI server'
-    required: false
-    default: ''
-  launch_server:
-    description: 'Whether to launch the server after setup'
-    required: false
-    default: 'false'
-runs:
-  using: 'composite'
-  steps:
-    # Note: this workflow assume frontend repo is checked out and is built in ../dist
-
-    # Checkout ComfyUI repo, install the dev_tools node and start server
-    - name: Checkout ComfyUI
-      uses: actions/checkout@v6
-      with:
-        repository: 'comfyanonymous/ComfyUI'
-        path: 'ComfyUI'
-
-    - name: Install ComfyUI_devtools from frontend repo
-      shell: bash
-      run: |
-        mkdir -p ComfyUI/custom_nodes/ComfyUI_devtools
-        if ! cp -r ./tools/devtools/* ComfyUI/custom_nodes/ComfyUI_devtools/; then
-          echo "::error::Failed to copy ComfyUI_devtools from ./tools/devtools/"
-          echo "::error::This action assumes the ComfyUI_frontend repository is checked out in the current working directory."
-          echo "::error::Please ensure you have run 'actions/checkout@v5' before calling this action."
-          exit 1
-        fi
-
-    - name: Setup Python
-      uses: actions/setup-python@v6
-      with:
-        python-version: '3.10'
-
-    - name: Install Python requirements
-      shell: bash
-      working-directory: ComfyUI
-      run: |
-        python -m pip install --upgrade pip
-        pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu
-        pip install -r requirements.txt
-        pip install wait-for-it
-
-    - name: Start ComfyUI server
-      if: ${{ inputs.launch_server == 'true' }}
-      shell: bash
-      working-directory: ComfyUI
-      run: |
-        python main.py --cpu --multi-user --front-end-root ../dist ${{ inputs.extra_server_params }} &
-        wait-for-it --service 127.0.0.1:8188 -t 600

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

@@ -1,33 +0,0 @@
-name: Setup ComfyUI Frontend
-description: 'Install nodejs/pnpm/dependencies and optionally build ComfyUI_frontend'
-inputs:
-  include_build_step:
-    description: 'Include the build step to build the frontend. Set to true for workflows that need a built frontend'
-    required: false
-    default: 'false'
-runs:
-  using: 'composite'
-  steps:
-    # Note: this workflow assume frontend repo is checked out in the root of the workspace
-
-    # Install pnpm, Node.js, build frontend
-    - name: Install pnpm
-      uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-      with:
-        version: 10
-
-    - name: Setup Node.js
-      uses: actions/setup-node@v6
-      with:
-        node-version: 'lts/*'
-        cache: 'pnpm'
-        cache-dependency-path: './pnpm-lock.yaml'
-
-    - name: Install dependencies
-      shell: bash
-      run: pnpm install --frozen-lockfile
-
-    - name: Build ComfyUI_frontend
-      if: ${{ inputs.include_build_step == 'true' }}
-      shell: bash
-      run: pnpm build

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

@@ -1,28 +0,0 @@
-name: Setup Playwright
-description: Cache and install Playwright browsers with dependencies
-runs:
-  using: composite
-  steps:
-    - name: Detect Playwright version
-      id: detect-version
-      shell: bash
-      run: |
-        PLAYWRIGHT_VERSION=$(pnpm ls @playwright/test --json | jq --raw-output '.[0].devDependencies["@playwright/test"].version')
-        echo "playwright-version=$PLAYWRIGHT_VERSION" >> $GITHUB_OUTPUT
-
-    - name: Cache Playwright Browsers
-      uses: actions/cache@v5 # v5.0.2
-      id: cache-playwright-browsers
-      with:
-        path: '~/.cache/ms-playwright'
-        key: ${{ runner.os }}-playwright-browsers-${{ steps.detect-version.outputs.playwright-version }}
-
-    - name: Install Playwright Browsers
-      if: steps.cache-playwright-browsers.outputs.cache-hit != 'true'
-      shell: bash
-      run: pnpm exec playwright install chromium --with-deps
-
-    - name: Install Playwright Browsers (operating system dependencies)
-      if: steps.cache-playwright-browsers.outputs.cache-hit == 'true'
-      shell: bash
-      run: pnpm exec playwright install-deps

.github/actions/start-comfyui-server/action.yaml

@@ -1,23 +0,0 @@
-name: Start ComfyUI Server
-description: 'Start ComfyUI server in a container environment (assumes ComfyUI is pre-installed)'
-
-inputs:
-  front_end_root:
-    description: 'Path to frontend dist directory'
-    required: false
-    default: '$GITHUB_WORKSPACE/dist'
-  timeout:
-    description: 'Timeout in seconds for server startup'
-    required: false
-    default: '600'
-
-runs:
-  using: 'composite'
-  steps:
-    - name: Copy devtools and start server
-      shell: bash
-      run: |
-        set -euo pipefail
-        cp -r ./tools/devtools/* /ComfyUI/custom_nodes/ComfyUI_devtools/
-        cd /ComfyUI && python3 main.py --cpu --multi-user --front-end-root "${{ inputs.front_end_root }}" &
-        wait-for-it --service 127.0.0.1:8188 -t ${{ inputs.timeout }}

.github/copilot-instructions.md

@@ -1,37 +0,0 @@
-Use the Vue 3 Composition API instead of the Options API when writing Vue components. An exception is when overriding or extending a PrimeVue component for compatibility, you may use the Options API.
-
-Use setup() function for component logic
-
-Utilize ref and reactive for reactive state
-
-Implement computed properties with computed()
-
-Use watch and watchEffect for side effects
-
-Implement lifecycle hooks with onMounted, onUpdated, etc.
-
-Utilize provide/inject for dependency injection
-
-Use vue 3.5 style of default prop declaration.
-
-Use Tailwind CSS for styling
-
-Leverage VueUse functions for performance-enhancing styles
-
-Use es-toolkit for utility functions
-
-Use TypeScript for type safety
-
-Implement proper props and emits definitions
-
-Utilize Vue 3's Teleport component when needed
-
-Use Suspense for async components
-
-Implement proper error handling
-
-Follow Vue 3 style guide and naming conventions
-
-Use Vite for fast development and building
-
-Use vue-i18n in composition API for any string literals. Place new translation entries in src/locales/en/main.json.

.github/license-clarifications.json

@@ -1,3 +0,0 @@
-{
-  "posthog-js@*": { "licenses": "Apache-2.0" }
-}

.github/pull_request_template.md

@@ -1,20 +0,0 @@
-## Summary
-
-<!-- One sentence describing what changed and why. -->
-
-## Changes
-
-- **What**: <!-- Core functionality added/modified -->
-- **Breaking**: <!-- Any breaking changes (if none, remove this line) -->
-- **Dependencies**: <!-- New dependencies (if none, remove this line) -->
-
-## Review Focus
-
-<!-- Critical design decisions or edge cases that need attention -->
-
-<!-- If this PR fixes an issue, uncomment and update the line below -->
-<!-- Fixes #ISSUE_NUMBER -->
-
-## Screenshots (if applicable)
-
-<!-- Add screenshots or video recording to help explain your changes -->

.github/workflows/README.md

@@ -1,21 +0,0 @@
-# GitHub Workflows
-
-## Naming Convention
-
-Workflow files follow a consistent naming pattern: `<prefix>-<descriptive-name>.yaml`
-
-### Category Prefixes
-
-| Prefix     | Purpose                             | Example                              |
-| ---------- | ----------------------------------- | ------------------------------------ |
-| `ci-`      | Testing, linting, validation        | `ci-tests-e2e.yaml`                  |
-| `release-` | Version management, publishing      | `release-version-bump.yaml`          |
-| `pr-`      | PR automation (triggered by labels) | `pr-claude-review.yaml`              |
-| `api-`     | External Api type generation        | `api-update-registry-api-types.yaml` |
-| `i18n-`    | Internationalization updates        | `i18n-update-core.yaml`              |
-
-## Documentation
-
-Each workflow file contains comments explaining its purpose, triggers, and behavior. For specific details about what each workflow does, refer to the comments at the top of each `.yaml` file.
-
-For GitHub Actions documentation, see [Events that trigger workflows](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows).

.github/workflows/api-update-manager-api-types.yaml

@@ -1,108 +0,0 @@
-# Description: When upstream ComfyUI-Manager API is updated, click dispatch to update the TypeScript type definitions in this repo
-name: 'Api: Update Manager API Types'
-
-on:
-  # Manual trigger
-  workflow_dispatch:
-    inputs:
-      target_branch:
-        description: 'Target branch for the PR'
-        required: true
-        default: 'main'
-
-jobs:
-  update-manager-types:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Checkout ComfyUI-Manager repository
-        uses: actions/checkout@v6
-        with:
-          repository: Comfy-Org/ComfyUI-Manager
-          path: ComfyUI-Manager
-          clean: true
-
-      - name: Get Manager commit information
-        id: manager-info
-        run: |
-          cd ComfyUI-Manager
-          MANAGER_COMMIT=$(git rev-parse --short HEAD)
-          echo "commit=${MANAGER_COMMIT}" >> $GITHUB_OUTPUT
-          cd ..
-
-      - name: Generate Manager API types
-        run: |
-          echo "Generating TypeScript types from ComfyUI-Manager@${{ steps.manager-info.outputs.commit }}..."
-          pnpm dlx openapi-typescript ./ComfyUI-Manager/openapi.yaml --output ./src/types/generatedManagerTypes.ts
-
-      - name: Validate generated types
-        run: |
-          if [ ! -f ./src/types/generatedManagerTypes.ts ]; then
-            echo "Error: Types file was not generated."
-            exit 1
-          fi
-
-          # Check if file is not empty
-          if [ ! -s ./src/types/generatedManagerTypes.ts ]; then
-            echo "Error: Generated types file is empty."
-            exit 1
-          fi
-
-      - name: Lint generated types
-        run: |
-          echo "Linting generated ComfyUI-Manager API types..."
-          pnpm lint:fix:no-cache -- ./src/types/generatedManagerTypes.ts
-
-      - name: Check for changes
-        id: check-changes
-        run: |
-          if [[ -z $(git status --porcelain ./src/types/generatedManagerTypes.ts) ]]; then
-            echo "No changes to ComfyUI-Manager API types detected."
-            echo "changed=false" >> $GITHUB_OUTPUT
-            exit 0
-          else
-            echo "Changes detected in ComfyUI-Manager API types."
-            echo "changed=true" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Create Pull Request
-        if: steps.check-changes.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
-        with:
-          token: ${{ secrets.PR_GH_TOKEN }}
-          commit-message: '[chore] Update ComfyUI-Manager API types from ComfyUI-Manager@${{ steps.manager-info.outputs.commit }}'
-          title: '[chore] Update ComfyUI-Manager API types from ComfyUI-Manager@${{ steps.manager-info.outputs.commit }}'
-          body: |
-            ## Automated API Type Update
-
-            This PR updates the ComfyUI-Manager API types from the latest ComfyUI-Manager OpenAPI specification.
-
-            - Manager commit: ${{ steps.manager-info.outputs.commit }}
-            - Generated on: ${{ github.event.repository.updated_at }}
-
-            These types are automatically generated using openapi-typescript.
-          branch: update-manager-types-${{ steps.manager-info.outputs.commit }}
-          base: ${{ inputs.target_branch }}
-          labels: Manager
-          delete-branch: true
-          add-paths: |
-            src/types/generatedManagerTypes.ts

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

@@ -1,100 +0,0 @@
-name: 'CI: Dist Telemetry Scan'
-
-on:
-  pull_request:
-    branches-ignore: [wip/*, draft/*, temp/*]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-
-jobs:
-  scan:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Use Node.js
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build project
-        run: pnpm build
-        env:
-          DISTRIBUTION: localhost
-
-      - name: Scan dist for GTM telemetry references
-        run: |
-          set -euo pipefail
-          echo '🔍 Scanning for Google Tag Manager references...'
-          if rg --no-ignore -n \
-            -g '*.html' \
-            -g '*.js' \
-            -e 'Google Tag Manager' \
-            -e '(?i)\bgtm\.js\b' \
-            -e '(?i)googletagmanager\.com/gtm\.js\\?id=' \
-            -e '(?i)googletagmanager\.com/ns\.html\\?id=' \
-            dist; then
-            echo '❌ ERROR: Google Tag Manager references found in dist assets!'
-            echo 'GTM must be properly tree-shaken from OSS builds.'
-            exit 1
-          fi
-          echo '✅ No GTM references found'
-
-      - name: Scan dist for Mixpanel telemetry references
-        run: |
-          set -euo pipefail
-          echo '🔍 Scanning for Mixpanel references...'
-          if rg --no-ignore -n \
-            -g '*.html' \
-            -g '*.js' \
-            -e '(?i)mixpanel\.init' \
-            -e '(?i)mixpanel\.identify' \
-            -e 'MixpanelTelemetryProvider' \
-            -e 'mp\.comfy\.org' \
-            -e 'mixpanel-browser' \
-            -e '(?i)mixpanel\.track\(' \
-            dist; then
-            echo '❌ ERROR: Mixpanel references found in dist assets!'
-            echo 'Mixpanel 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 Mixpanel references found'
-
-      - name: Scan dist for PostHog telemetry references
-        run: |
-          set -euo pipefail
-          echo '🔍 Scanning for PostHog references...'
-          if rg --no-ignore -n \
-            -g '*.html' \
-            -g '*.js' \
-            -e '(?i)posthog\.init' \
-            -e '(?i)posthog\.capture' \
-            -e 'PostHogTelemetryProvider' \
-            -e 'ph\.comfy\.org' \
-            -e 'posthog-js' \
-            dist; then
-            echo '❌ ERROR: PostHog references found in dist assets!'
-            echo 'PostHog must be properly tree-shaken from OSS builds.'
-            exit 1
-          fi
-          echo '✅ No PostHog references found'

.github/workflows/ci-json-validation.yaml

@@ -1,18 +0,0 @@
-# Description: Validates JSON syntax in all tracked .json files (excluding tsconfig*.json) using jq
-name: 'CI: JSON Validation'
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    paths:
-      - '**/*.json'
-
-jobs:
-  json-lint:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-      - name: Validate JSON syntax
-        run: ./scripts/cicd/check-json.sh

.github/workflows/ci-lint-format.yaml

@@ -1,99 +0,0 @@
-# Description: Linting and code formatting validation for pull requests
-name: 'CI: Lint Format'
-
-on:
-  pull_request:
-    branches-ignore: [wip/*, draft/*, temp/*]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  lint-and-format:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout PR
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ !github.event.pull_request.head.repo.fork && github.head_ref || github.ref }}
-          token: ${{ !github.event.pull_request.head.repo.fork && secrets.PR_GH_TOKEN || github.token }}
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Detect browser_tests changes
-        id: changed-paths
-        uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # v3.0.2
-        with:
-          filters: |
-            browser_tests:
-              - 'browser_tests/**'
-
-      - name: Run ESLint with auto-fix
-        run: pnpm lint:fix
-
-      - name: Run Stylelint with auto-fix
-        run: pnpm stylelint:fix
-
-      - name: Run oxfmt with auto-format
-        run: pnpm format
-
-      - name: Check for changes
-        id: verify-changed-files
-        run: |
-          if [ -n "$(git status --porcelain)" ]; then
-            echo "changed=true" >> $GITHUB_OUTPUT
-          else
-            echo "changed=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Commit changes
-        if: steps.verify-changed-files.outputs.changed == 'true' && github.event.pull_request.head.repo.full_name == github.repository
-        run: |
-          git config --local user.email "action@github.com"
-          git config --local user.name "GitHub Action"
-          git add .
-          git commit -m "[automated] Apply ESLint and Oxfmt fixes"
-          git push
-
-      - name: Final validation
-        run: |
-          pnpm lint
-          pnpm stylelint
-          pnpm format:check
-          pnpm knip
-
-      - name: Typecheck browser tests
-        if: steps.changed-paths.outputs.browser_tests == 'true'
-        run: pnpm typecheck:browser
-
-      - name: Comment on PR about auto-fix
-        if: steps.verify-changed-files.outputs.changed == 'true' && github.event.pull_request.head.repo.full_name == github.repository
-        continue-on-error: true
-        uses: actions/github-script@v8
-        with:
-          script: |
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: '## 🔧 Auto-fixes Applied\n\nThis PR has been automatically updated to fix linting and formatting issues.\n\n**⚠️ Important**: Your local branch is now behind. Run `git pull` before making additional changes to avoid conflicts.\n\n### Changes made:\n- ESLint auto-fixes\n- Oxfmt formatting'
-            })
-
-      - name: Comment on PR about manual fix needed
-        if: steps.verify-changed-files.outputs.changed == 'true' && github.event.pull_request.head.repo.full_name != github.repository
-        continue-on-error: true
-        uses: actions/github-script@v8
-        with:
-          script: |
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: '## ⚠️ Linting/Formatting Issues Found\n\nThis PR has linting or formatting issues that need to be fixed.\n\n**Since this PR is from a fork, auto-fix cannot be applied automatically.**\n\n### Option 1: Set up pre-commit hooks (recommended)\nRun this once to automatically format code on every commit:\n```bash\npnpm prepare\n```\n\n### Option 2: Fix manually\nRun these commands and push the changes:\n```bash\npnpm lint:fix\npnpm format\n```\n\nSee [CONTRIBUTING.md](https://github.com/Comfy-Org/ComfyUI_frontend/blob/main/CONTRIBUTING.md#git-pre-commit-hooks) for more details.'
-            })

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

@@ -1,119 +0,0 @@
-name: 'CI: OSS Assets Validation'
-
-on:
-  pull_request:
-    branches-ignore: [wip/*, draft/*, temp/*]
-  push:
-    branches: [main, dev*]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-
-jobs:
-  validate-fonts:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@9fd676a19091d4595eefd76e4bd31c97133911f1 # v4.2.0
-        with:
-          version: 10
-
-      - name: Use Node.js
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build project
-        run: pnpm build
-        env:
-          DISTRIBUTION: localhost
-
-      - name: Check for proprietary fonts in dist
-        run: |
-          set -euo pipefail
-          echo '🔍 Checking dist for proprietary ABCROM fonts...'
-
-          if [ ! -d "dist" ] || [ -z "$(ls -A dist)" ]; then
-            echo '❌ ERROR: dist/ directory missing or empty!'
-            exit 1
-          fi
-
-          # Check for ABCROM font files
-          if find dist/ -type f -iname '*abcrom*' \
-            \( -name '*.woff' -o -name '*.woff2' -o -name '*.ttf' -o -name '*.otf' \) \
-            -print -quit | grep -q .; then
-            echo ''
-            echo '❌ ERROR: Found proprietary ABCROM font files in dist!'
-            echo ''
-            find dist/ -type f -iname '*abcrom*' \
-              \( -name '*.woff' -o -name '*.woff2' -o -name '*.ttf' -o -name '*.otf' \)
-            echo ''
-            echo 'ABCROM fonts are proprietary and should not ship to OSS builds.'
-            echo ''
-            echo 'To fix this:'
-            echo '1. Use conditional font loading based on isCloud'
-            echo '2. Ensure fonts are dynamically imported, not bundled'
-            echo '3. Check vite config for font handling'
-            exit 1
-          fi
-
-          echo '✅ No proprietary fonts found in dist'
-
-  validate-licenses:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@9fd676a19091d4595eefd76e4bd31c97133911f1 # v4.2.0
-        with:
-          version: 10
-
-      - name: Use Node.js
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Validate production dependency licenses
-        run: |
-          set -euo pipefail
-          echo '🔍 Checking production dependency licenses...'
-
-          # Use license-checker-rseidelsohn (actively maintained fork, handles monorepos)
-          # Exclude internal @comfyorg packages from license check
-          # Run in if condition to capture exit code
-          if npx license-checker-rseidelsohn@4 \
-            --production \
-            --summary \
-            --excludePackages '@comfyorg/comfyui-frontend;@comfyorg/design-system;@comfyorg/registry-types;@comfyorg/shared-frontend-utils;@comfyorg/tailwind-utils;@comfyorg/comfyui-electron-types' \
-            --clarificationsFile .github/license-clarifications.json \
-            --onlyAllow 'MIT;MIT*;Apache-2.0;BSD-2-Clause;BSD-3-Clause;ISC;0BSD;BlueOak-1.0.0;Python-2.0;CC0-1.0;Unlicense;(MIT OR Apache-2.0);(MIT OR GPL-3.0);(Apache-2.0 OR MIT);(MPL-2.0 OR Apache-2.0);CC-BY-4.0;CC-BY-3.0;GPL-3.0-only'; then
-            echo ''
-            echo '✅ All production dependency licenses are approved!'
-          else
-            echo ''
-            echo '❌ ERROR: Found dependencies with non-approved licenses!'
-            echo ''
-            echo 'To fix this:'
-            echo '1. Check the license of the problematic package'
-            echo '2. Find an alternative package with an approved license'
-            echo '3. If the license is safe and OSI-approved, add it to the --onlyAllow list'
-            echo ''
-            echo 'For more info on OSI-approved licenses:'
-            echo 'https://opensource.org/licenses'
-            exit 1
-          fi

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

@@ -1,70 +0,0 @@
-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 }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-
-jobs:
-  perf-tests:
-    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.12
-      credentials:
-        username: ${{ github.actor }}
-        password: ${{ secrets.GITHUB_TOKEN }}
-    permissions:
-      contents: read
-      packages: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: true
-
-      - name: Start ComfyUI server
-        uses: ./.github/actions/start-comfyui-server
-
-      - name: Run performance tests
-        id: perf
-        continue-on-error: true
-        run: pnpm exec playwright test --project=performance --workers=1 --repeat-each=3
-
-      - name: Upload perf metrics
-        if: always()
-        uses: actions/upload-artifact@v6
-        with:
-          name: perf-metrics
-          path: test-results/perf-metrics.json
-          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
-
-      - name: Upload PR metadata
-        if: github.event_name == 'pull_request'
-        uses: actions/upload-artifact@v6
-        with:
-          name: perf-meta
-          path: temp/perf-meta/

.github/workflows/ci-python-validation.yaml

@@ -1,27 +0,0 @@
-# Description: Validates Python code in tools/devtools directory
-name: 'CI: Python Validation'
-
-on:
-  pull_request:
-    paths:
-      - 'tools/devtools/**'
-  push:
-    branches: [main]
-    paths:
-      - 'tools/devtools/**'
-
-jobs:
-  syntax:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: '3.11'
-
-      - name: Validate Python syntax
-        run: python3 -m compileall -q tools/devtools

.github/workflows/ci-shell-validation.yaml

@@ -1,26 +0,0 @@
-# Description: Runs shellcheck on tracked shell scripts when they change
-name: 'CI: Shell Validation'
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - '**/*.sh'
-  pull_request:
-    paths:
-      - '**/*.sh'
-
-jobs:
-  shell-lint:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Install shellcheck
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y shellcheck
-
-      - name: Run shellcheck
-        run: bash ./scripts/cicd/check-shell.sh

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

@@ -1,41 +0,0 @@
-name: 'CI: Size Data'
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-permissions:
-  contents: read
-
-jobs:
-  collect:
-    if: github.repository == 'Comfy-Org/ComfyUI_frontend'
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Build project
-        run: pnpm build
-
-      - name: Collect size data
-        run: node scripts/size-collect.js
-
-      - name: Save PR number & base branch
-        if: ${{ github.event_name == 'pull_request' }}
-        run: |
-          echo ${{ github.event.number }} > ./temp/size/number.txt
-          echo ${{ github.base_ref }} > ./temp/size/base.txt
-
-      - name: Upload size data
-        uses: actions/upload-artifact@v6
-        with:
-          name: size-data
-          path: temp/size

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

@@ -1,90 +0,0 @@
-# Description: Deploys test results from forked PRs (forks can't access deployment secrets)
-name: 'CI: Tests E2E (Deploy for Forks)'
-
-on:
-  workflow_run:
-    workflows: ['CI: Tests E2E']
-    types: [requested, completed]
-
-jobs:
-  deploy-and-comment-forked-pr:
-    runs-on: ubuntu-latest
-    if: |
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      github.event.workflow_run.event == 'pull_request' &&
-      github.event.workflow_run.head_repository != null &&
-      github.event.workflow_run.repository != null &&
-      github.event.workflow_run.head_repository.full_name != github.event.workflow_run.repository.full_name
-    permissions:
-      pull-requests: write
-      actions: read
-    steps:
-      - name: Log workflow trigger info
-        run: |
-          echo "Repository: ${{ github.repository }}"
-          echo "Event: ${{ github.event.workflow_run.event }}"
-          echo "Head repo: ${{ github.event.workflow_run.head_repository.full_name || 'null' }}"
-          echo "Base repo: ${{ github.event.workflow_run.repository.full_name || 'null' }}"
-          echo "Is forked: ${{ github.event.workflow_run.head_repository.full_name != github.event.workflow_run.repository.full_name }}"
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Get PR Number
-        id: pr
-        uses: actions/github-script@v8
-        with:
-          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.result != 'null' && github.event.action == 'completed'
-        uses: actions/download-artifact@v7
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id }}
-          pattern: playwright-report-*
-          path: 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 }}
-        run: |
-          # Rename merged report if exists
-          [ -d "reports/playwright-report-chromium-merged" ] && \
-            mv reports/playwright-report-chromium-merged reports/playwright-report-chromium
-
-          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 }}" \
-            "completed"

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

@@ -1,226 +0,0 @@
-# Description: End-to-end testing with Playwright across multiple browsers, deploys test reports to Cloudflare Pages
-name: 'CI: Tests E2E'
-
-on:
-  push:
-    branches: [main, master, core/*, desktop/*]
-    paths-ignore: ['**/*.md']
-  pull_request:
-    branches-ignore: [wip/*, draft/*, temp/*]
-    paths-ignore: ['**/*.md']
-  workflow_dispatch:
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  setup:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: true
-
-      # Upload only built dist/ (containerized test jobs will pnpm install without cache)
-      - name: Upload built frontend
-        uses: actions/upload-artifact@v6
-        with:
-          name: frontend-dist
-          path: dist/
-          retention-days: 1
-
-  # Sharded chromium tests
-  playwright-tests-chromium-sharded:
-    needs: setup
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.13
-      credentials:
-        username: ${{ github.actor }}
-        password: ${{ secrets.GITHUB_TOKEN }}
-    permissions:
-      contents: read
-      packages: read
-    strategy:
-      fail-fast: false
-      matrix:
-        shardIndex: [1, 2, 3, 4, 5, 6, 7, 8]
-        shardTotal: [8]
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-      - name: Download built frontend
-        uses: actions/download-artifact@v7
-        with:
-          name: frontend-dist
-          path: dist/
-
-      - name: Start ComfyUI server
-        uses: ./.github/actions/start-comfyui-server
-
-      - name: Install frontend deps
-        run: pnpm install --frozen-lockfile
-
-      # Run sharded tests (browsers pre-installed in container)
-      - name: Run Playwright tests (Shard ${{ matrix.shardIndex }}/${{ matrix.shardTotal }})
-        id: playwright
-        run: pnpm exec playwright test --project=chromium --shard=${{ matrix.shardIndex }}/${{ matrix.shardTotal }} --reporter=blob
-        env:
-          PLAYWRIGHT_BLOB_OUTPUT_DIR: ./blob-report
-
-      - name: Upload blob report
-        uses: actions/upload-artifact@v6
-        if: ${{ !cancelled() }}
-        with:
-          name: blob-report-chromium-${{ matrix.shardIndex }}
-          path: blob-report/
-          retention-days: 1
-
-  playwright-tests:
-    # Ideally, each shard runs test in 6 minutes, but allow up to 15 minutes
-    timeout-minutes: 15
-    needs: setup
-    runs-on: ubuntu-latest
-    container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.13
-      credentials:
-        username: ${{ github.actor }}
-        password: ${{ secrets.GITHUB_TOKEN }}
-    permissions:
-      contents: read
-      packages: read
-    strategy:
-      fail-fast: false
-      matrix:
-        browser: [chromium-2x, chromium-0.5x, mobile-chrome]
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-      - name: Download built frontend
-        uses: actions/download-artifact@v7
-        with:
-          name: frontend-dist
-          path: dist/
-
-      - name: Start ComfyUI server
-        uses: ./.github/actions/start-comfyui-server
-
-      - name: Install frontend deps
-        run: pnpm install --frozen-lockfile
-
-      # Run tests (browsers pre-installed in container)
-      - name: Run Playwright tests (${{ matrix.browser }})
-        id: playwright
-        run: pnpm exec playwright test --project=${{ matrix.browser }} --reporter=blob
-        env:
-          PLAYWRIGHT_BLOB_OUTPUT_DIR: ./blob-report
-
-      - name: Generate HTML and JSON reports
-        if: always()
-        run: |
-          # Generate HTML report from blob
-          pnpm exec playwright merge-reports --reporter=html ./blob-report
-          # Generate JSON report separately with explicit output path
-          PLAYWRIGHT_JSON_OUTPUT_NAME=playwright-report/report.json \
-          pnpm exec playwright merge-reports --reporter=json ./blob-report
-
-      - name: Upload Playwright report
-        uses: actions/upload-artifact@v6
-        if: always()
-        with:
-          name: playwright-report-${{ matrix.browser }}
-          path: ./playwright-report/
-          retention-days: 30
-
-  # Merge sharded test reports (no container needed - only runs CLI)
-  merge-reports:
-    needs: [playwright-tests-chromium-sharded]
-    runs-on: ubuntu-latest
-    if: ${{ !cancelled() }}
-    steps:
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Download blob reports
-        uses: actions/download-artifact@v7
-        with:
-          path: ./all-blob-reports
-          pattern: blob-report-chromium-*
-          merge-multiple: true
-
-      - name: Merge into HTML Report
-        run: |
-          # Generate HTML report
-          pnpm dlx @playwright/test merge-reports --reporter=html ./all-blob-reports
-          # Generate JSON report separately with explicit output path
-          PLAYWRIGHT_JSON_OUTPUT_NAME=playwright-report/report.json \
-          pnpm dlx @playwright/test merge-reports --reporter=json ./all-blob-reports
-
-      - name: Upload HTML report
-        uses: actions/upload-artifact@v6
-        with:
-          name: playwright-report-chromium
-          path: ./playwright-report/
-          retention-days: 30
-
-  #### 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 comment for non-forked PRs
-  comment-on-pr-start:
-    runs-on: ubuntu-latest
-    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: 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 comment for non-forked PRs only
-  deploy-and-comment:
-    needs: [playwright-tests, merge-reports]
-    runs-on: ubuntu-latest
-    if: always() && github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false
-    permissions:
-      pull-requests: write
-      contents: read
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Download all playwright reports
-        uses: actions/download-artifact@v7
-        with:
-          pattern: playwright-report-*
-          path: reports
-
-      - 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 }}
-        run: |
-          bash ./scripts/cicd/pr-playwright-deploy-and-comment.sh \
-            "${{ github.event.pull_request.number }}" \
-            "${{ github.head_ref }}" \
-            "completed"
-  #### END Deployment and commenting (non-forked PRs only)

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

@@ -1,87 +0,0 @@
-# Description: Deploys Storybook previews from forked PRs (forks can't access deployment secrets)
-name: 'CI: Tests Storybook (Deploy for Forks)'
-
-on:
-  workflow_run:
-    workflows: ['CI: Tests Storybook']
-    types: [requested, completed]
-
-jobs:
-  deploy-and-comment-forked-pr:
-    runs-on: ubuntu-latest
-    if: |
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      github.event.workflow_run.event == 'pull_request' &&
-      github.event.workflow_run.head_repository != null &&
-      github.event.workflow_run.repository != null &&
-      github.event.workflow_run.head_repository.full_name != github.event.workflow_run.repository.full_name
-    permissions:
-      pull-requests: write
-      actions: read
-    steps:
-      - name: Log workflow trigger info
-        run: |
-          echo "Repository: ${{ github.repository }}"
-          echo "Event: ${{ github.event.workflow_run.event }}"
-          echo "Head repo: ${{ github.event.workflow_run.head_repository.full_name || 'null' }}"
-          echo "Base repo: ${{ github.event.workflow_run.repository.full_name || 'null' }}"
-          echo "Is forked: ${{ github.event.workflow_run.head_repository.full_name != github.event.workflow_run.repository.full_name }}"
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Get PR Number
-        id: pr
-        uses: actions/github-script@v8
-        with:
-          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.result != 'null' && github.event.action == 'completed' && github.event.workflow_run.conclusion == 'success'
-        uses: actions/download-artifact@v7
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id }}
-          name: storybook-static
-          path: storybook-static
-
-      - 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 }}
-        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 }}" \
-            "completed"

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

@@ -1,205 +0,0 @@
-# Description: Builds Storybook and runs visual regression testing via Chromatic, deploys previews to Cloudflare Pages
-name: 'CI: Tests Storybook'
-
-on:
-  workflow_dispatch: # Allow manual triggering
-  pull_request:
-  push:
-    branches: [main]
-
-jobs:
-  # Post starting comment for non-forked PRs
-  comment-on-pr-start:
-    runs-on: ubuntu-latest
-    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: 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:
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request'
-    outputs:
-      conclusion: ${{ steps.job-status.outputs.conclusion }}
-      workflow-url: ${{ steps.workflow-url.outputs.url }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Build Storybook
-        run: pnpm build-storybook
-
-      - name: Set job status
-        id: job-status
-        if: always()
-        run: |
-          echo "conclusion=${{ job.status }}" >> $GITHUB_OUTPUT
-
-      - name: Get workflow URL
-        id: workflow-url
-        if: always()
-        run: |
-          echo "url=${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}" >> $GITHUB_OUTPUT
-
-      - name: Upload Storybook build
-        if: success() && github.event.pull_request.head.repo.fork == false
-        uses: actions/upload-artifact@v6
-        with:
-          name: storybook-static
-          path: storybook-static/
-          retention-days: 7
-
-  # Chromatic deployment only for version-bump-* branches or manual triggers
-  chromatic-deployment:
-    runs-on: ubuntu-latest
-    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 }}
-      chromatic-build-url: ${{ steps.chromatic.outputs.buildUrl }}
-      chromatic-storybook-url: ${{ steps.chromatic.outputs.storybookUrl }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0 # Required for Chromatic baseline
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Build Storybook and run Chromatic
-        id: chromatic
-        uses: chromaui/action@07791f8243f4cb2698bf4d00426baf4b2d1cb7e0 # v13.3.5
-        with:
-          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
-          buildScriptName: build-storybook
-          autoAcceptChanges: 'main' # Auto-accept changes on main branch
-          exitOnceUploaded: true # Don't wait for UI tests to complete
-          onlyChanged: true # Only capture changed stories
-
-      - name: Set job status
-        id: job-status
-        if: always()
-        run: |
-          echo "conclusion=${{ job.status }}" >> $GITHUB_OUTPUT
-
-      - name: Get workflow URL
-        id: workflow-url
-        if: always()
-        run: |
-          echo "url=${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}" >> $GITHUB_OUTPUT
-
-  # Deploy and comment for non-forked PRs only
-  deploy-and-comment:
-    needs: [storybook-build]
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false && always()
-    permissions:
-      pull-requests: write
-      contents: read
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Download Storybook build
-        if: needs.storybook-build.outputs.conclusion == 'success'
-        uses: actions/download-artifact@v7
-        with:
-          name: storybook-static
-          path: storybook-static
-
-      - name: Make deployment script executable
-        run: chmod +x scripts/cicd/pr-storybook-deploy-and-comment.sh
-
-      - 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 }}
-        run: |
-          ./scripts/cicd/pr-storybook-deploy-and-comment.sh \
-            "${{ github.event.pull_request.number }}" \
-            "${{ github.head_ref }}" \
-            "completed"
-
-  # Deploy Storybook to production URL on main branch push
-  deploy-production:
-    runs-on: ubuntu-latest
-    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Build Storybook
-        run: pnpm build-storybook
-
-      - name: Deploy to Cloudflare Pages (production)
-        env:
-          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-        run: |
-          npx wrangler@^4.0.0 pages deploy storybook-static \
-            --project-name=comfy-storybook \
-            --branch=main
-
-  # Update comment with Chromatic URLs for version-bump branches
-  update-comment-with-chromatic:
-    needs: [chromatic-deployment, deploy-and-comment]
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false && startsWith(github.head_ref, 'version-bump-') && needs.chromatic-deployment.outputs.chromatic-build-url != ''
-    permissions:
-      pull-requests: write
-    steps:
-      - name: Update comment with Chromatic URLs
-        uses: actions/github-script@v8
-        with:
-          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

@@ -1,27 +0,0 @@
-# Description: Unit and component testing with Vitest
-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']
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Run Vitest tests
-        run: pnpm test:unit

.github/workflows/ci-validate-action-pins.yaml

@@ -1,21 +0,0 @@
-name: Validate Action SHA Pins
-
-on:
-  pull_request:
-    paths:
-      - '.github/workflows/**'
-      - '.github/actions/**'
-      - '.pinact.yaml'
-
-permissions:
-  contents: read
-
-jobs:
-  validate-pins:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - uses: suzuki-shunsuke/pinact-action@3d49c6412901042473ffa78becddab1aea46bbea # v1.3.1
-        with:
-          skip_push: 'true'

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

@@ -1,33 +0,0 @@
-# Description: Validates YAML syntax and style using yamllint with relaxed rules
-name: 'CI: YAML Validation'
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - '**/*.yml'
-      - '**/*.yaml'
-  pull_request:
-    paths:
-      - '**/*.yml'
-      - '**/*.yaml'
-
-jobs:
-  yaml-lint:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: '3.x'
-
-      - name: Install yamllint
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install yamllint
-
-      - name: Validate YAML syntax and style
-        run: ./scripts/cicd/check-yaml.sh

.github/workflows/cloud-backport-tag.yaml

@@ -1,69 +0,0 @@
----
-name: Cloud Backport Tag
-
-on:
-  pull_request:
-    types: ['closed']
-    branches: [cloud/*]
-
-jobs:
-  create-tag:
-    if: >
-      github.event.pull_request.merged == true &&
-      contains(github.event.pull_request.labels.*.name, 'backport')
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: read
-
-    steps:
-      - name: Checkout merge commit
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.merge_commit_sha }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Create tag for cloud backport
-        id: tag
-        run: |
-          set -euo pipefail
-
-          BRANCH="${{ github.event.pull_request.base.ref }}"
-          if [[ ! "$BRANCH" =~ ^cloud/([0-9]+)\.([0-9]+)$ ]]; then
-            echo "::error::Base branch '$BRANCH' is not a cloud/x.y branch"
-            exit 1
-          fi
-
-          MAJOR="${BASH_REMATCH[1]}"
-          MINOR="${BASH_REMATCH[2]}"
-
-          VERSION=$(node -p "require('./package.json').version")
-          if [[ "$VERSION" =~ ^${MAJOR}\.${MINOR}\.([0-9]+)(-.+)?$ ]]; then
-            PATCH="${BASH_REMATCH[1]}"
-            SUFFIX="${BASH_REMATCH[2]:-}"
-          else
-            echo "::error::Version '${VERSION}' does not match cloud branch '${BRANCH}'"
-            exit 1
-          fi
-
-          TAG="cloud/v${VERSION}"
-
-          if git ls-remote --tags origin "${TAG}" | grep -Fq "refs/tags/${TAG}"; then
-            echo "::notice::Tag ${TAG} already exists; skipping"
-            echo "tag=${TAG}" >> "$GITHUB_OUTPUT"
-            exit 0
-          fi
-
-          git tag "${TAG}" "${{ github.event.pull_request.merge_commit_sha }}"
-          git push origin "${TAG}"
-          echo "tag=${TAG}" >> "$GITHUB_OUTPUT"
-          {
-            echo "Created tag: ${TAG}"
-            echo "Branch: ${BRANCH}"
-            echo "Version: ${VERSION}"
-            echo "Commit: ${{ github.event.pull_request.merge_commit_sha }}"
-          } >> "$GITHUB_STEP_SUMMARY"

.github/workflows/cloud-dispatch-build.yaml

@@ -1,81 +0,0 @@
----
-# Dispatches a frontend-asset-build event to the cloud repo on push to
-# cloud/* branches and main. The cloud repo handles the actual build,
-# GCS upload, and secret management (Sentry, Algolia, GCS creds).
-#
-# This is fire-and-forget — it does NOT wait for the cloud workflow to
-# complete. Status is visible in the cloud repo's Actions tab.
-
-name: Cloud Frontend Build Dispatch
-
-on:
-  push:
-    branches:
-      - 'cloud/*'
-      - 'main'
-  pull_request:
-    types: [labeled, synchronize]
-  workflow_dispatch:
-
-permissions: {}
-
-concurrency:
-  group: cloud-dispatch-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  dispatch:
-    # Fork guard: prevent forks from dispatching to the cloud repo.
-    # For pull_request events, only dispatch for preview labels.
-    # - labeled: fires when a label is added; check the added label name.
-    # - synchronize: fires on push; check existing labels on the PR.
-    if: >
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      (github.event_name != 'pull_request' ||
-       (github.event.action == 'labeled' &&
-        contains(fromJSON('["preview","preview-cpu","preview-gpu"]'), github.event.label.name)) ||
-       (github.event.action == 'synchronize' &&
-        (contains(github.event.pull_request.labels.*.name, 'preview') ||
-         contains(github.event.pull_request.labels.*.name, 'preview-cpu') ||
-         contains(github.event.pull_request.labels.*.name, 'preview-gpu'))))
-    runs-on: ubuntu-latest
-    steps:
-      - name: Build client payload
-        id: payload
-        env:
-          EVENT_NAME: ${{ github.event_name }}
-          PR_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-          PR_HEAD_REF: ${{ github.event.pull_request.head.ref }}
-          PR_NUMBER: ${{ github.event.pull_request.number }}
-          ACTION: ${{ github.event.action }}
-          LABEL_NAME: ${{ github.event.label.name }}
-          PR_LABELS: ${{ toJson(github.event.pull_request.labels.*.name) }}
-        run: |
-          if [ "${EVENT_NAME}" = "pull_request" ]; then
-            REF="${PR_HEAD_SHA}"
-            BRANCH="${PR_HEAD_REF}"
-
-            # Derive variant from all PR labels (default to cpu for frontend-only previews)
-            VARIANT="cpu"
-            echo "${PR_LABELS}" | grep -q '"preview-gpu"' && VARIANT="gpu"
-          else
-            REF="${GITHUB_SHA}"
-            BRANCH="${GITHUB_REF_NAME}"
-            PR_NUMBER=""
-            VARIANT=""
-          fi
-          payload="$(jq -nc \
-            --arg ref "${REF}" \
-            --arg branch "${BRANCH}" \
-            --arg pr_number "${PR_NUMBER}" \
-            --arg variant "${VARIANT}" \
-            '{ref: $ref, branch: $branch, pr_number: $pr_number, variant: $variant}')"
-          echo "json=${payload}" >> "${GITHUB_OUTPUT}"
-
-      - name: Dispatch to cloud repo
-        uses: peter-evans/repository-dispatch@28959ce8df70de7be546dd1250a005dd32156697 # v4.0.1
-        with:
-          token: ${{ secrets.CLOUD_DISPATCH_TOKEN }}
-          repository: Comfy-Org/cloud
-          event-type: frontend-asset-build
-          client-payload: ${{ steps.payload.outputs.json }}

.github/workflows/cloud-dispatch-cleanup.yaml

@@ -1,39 +0,0 @@
----
-# Dispatches a frontend-preview-cleanup event to the cloud repo when a
-# frontend PR with a preview label is closed or has its preview label
-# removed. The cloud repo handles the actual environment teardown.
-#
-# This is fire-and-forget — it does NOT wait for the cloud workflow to
-# complete. Status is visible in the cloud repo's Actions tab.
-
-name: Cloud Frontend Preview Cleanup Dispatch
-
-on:
-  pull_request:
-    types: [closed, unlabeled]
-
-permissions: {}
-
-jobs:
-  dispatch:
-    # Only dispatch when:
-    # - PR closed AND had a preview label
-    # - Preview label specifically removed
-    if: >
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      ((github.event.action == 'closed' &&
-        (contains(github.event.pull_request.labels.*.name, 'preview') ||
-         contains(github.event.pull_request.labels.*.name, 'preview-cpu') ||
-         contains(github.event.pull_request.labels.*.name, 'preview-gpu'))) ||
-       (github.event.action == 'unlabeled' &&
-        contains(fromJSON('["preview","preview-cpu","preview-gpu"]'), github.event.label.name)))
-    runs-on: ubuntu-latest
-    steps:
-      - name: Dispatch to cloud repo
-        uses: peter-evans/repository-dispatch@28959ce8df70de7be546dd1250a005dd32156697 # v4.0.1
-        with:
-          token: ${{ secrets.CLOUD_DISPATCH_TOKEN }}
-          repository: Comfy-Org/cloud
-          event-type: frontend-preview-cleanup
-          client-payload: >-
-            {"pr_number": "${{ github.event.pull_request.number }}"}

.github/workflows/eslint.yaml

@@ -0,0 +1,17 @@
+name: ESLint
+
+on:
+  pull_request:
+    branches: [ main, master, dev*, core/*, desktop/* ]
+
+jobs:
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: 'lts/*'
+    - run: npm ci
+    - run: npm run lint

.github/workflows/format.yaml

@@ -0,0 +1,23 @@
+name: Prettier Check
+
+on:
+  pull_request:
+    branches: [ main, master, dev*, core/*, desktop/* ]
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: 'lts/*'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Run Prettier check
+      run: npm run format:check

.github/workflows/i18n-custom-nodes.yaml

@@ -0,0 +1,159 @@
+name: Update Locales for given custom node repository
+
+on:
+  workflow_dispatch:
+    inputs:
+      owner:
+        description: 'Owner of the repository to update locales for'
+        required: true
+        type: string
+      repository:
+        description: 'Repository to update locales for'
+        required: true
+        type: string
+      fork_owner:
+        description: 'Owner of the forked repository'
+        required: false
+        type: string
+        default: 'Comfy-Org'
+
+jobs:
+  update-locales:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout ComfyUI
+      uses: actions/checkout@v4
+      with:
+        repository: comfyanonymous/ComfyUI
+        path: ComfyUI
+        ref: master
+    - name: Checkout ComfyUI_frontend
+      uses: actions/checkout@v4
+      with:
+        repository: Comfy-Org/ComfyUI_frontend
+        path: ComfyUI_frontend
+    - name: Checkout ComfyUI_devtools
+      uses: actions/checkout@v4
+      with:
+        repository: Comfy-Org/ComfyUI_devtools
+        path: ComfyUI/custom_nodes/ComfyUI_devtools
+    - name: Checkout custom node repository
+      uses: actions/checkout@v4
+      with:
+        repository: ${{ inputs.owner }}/${{ inputs.repository }}
+        path: 'ComfyUI/custom_nodes/${{ inputs.repository }}'
+    - uses: actions/setup-node@v4
+      with:
+        node-version: 'lts/*'
+    - uses: actions/setup-python@v4
+      with:
+        python-version: '3.10'
+    - name: Install ComfyUI requirements
+      run: |
+        python -m pip install --upgrade pip
+        pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu
+        pip install -r requirements.txt
+        pip install wait-for-it
+      working-directory: ComfyUI
+    - name: Install custom node requirements
+      run: |
+        if [ -f "requirements.txt" ]; then
+          pip install -r requirements.txt
+        fi
+      working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
+    - name: Build & Install ComfyUI_frontend
+      run: |
+        npm ci
+        npm run build
+        rm -rf ../ComfyUI/web/*
+        mv dist/* ../ComfyUI/web/
+      working-directory: ComfyUI_frontend
+    - name: Start ComfyUI server
+      run: |
+        python main.py --cpu --multi-user &
+        wait-for-it --service 127.0.0.1:8188 -t 600
+      working-directory: ComfyUI
+    - name: Install Playwright Browsers
+      run: npx playwright install chromium --with-deps
+      working-directory: ComfyUI_frontend
+    - name: Start dev server
+      # Run electron dev server as it is a superset of the web dev server
+      # We do want electron specific UIs to be translated.
+      run: npm run dev:electron &
+      working-directory: ComfyUI_frontend
+    - name: Capture base i18n
+      run: npx tsx scripts/diff-i18n capture
+      working-directory: ComfyUI_frontend
+    - name: Update en.json
+      run: npm run collect-i18n
+      env:
+        PLAYWRIGHT_TEST_URL: http://localhost:5173
+      working-directory: ComfyUI_frontend
+    - name: Update translations
+      run: npm run locale
+      env:
+        OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+      working-directory: ComfyUI_frontend
+    - name: Diff base vs updated i18n
+      run: npx tsx scripts/diff-i18n diff
+      working-directory: ComfyUI_frontend
+    - name: Update i18n in custom node repository
+      run: |
+        LOCALE_DIR=ComfyUI/custom_nodes/${{ inputs.repository }}/locales/
+        install -d "$LOCALE_DIR"
+        cp -rf ComfyUI_frontend/temp/diff/* "$LOCALE_DIR"
+    - name: Check and create fork of custom node repository
+      run: |
+        # Try to fork the repository
+        gh repo fork ${{ inputs.owner }}/${{ inputs.repository }} --clone=false || {
+          echo "Fork failed - repository might already be forked"
+          # Exit 0 to prevent the workflow from failing
+          exit 0
+        }
+
+        # Enable workflows on the forked repository
+        gh api \
+          --method PUT \
+          -H "Accept: application/vnd.github+json" \
+          "/repos/${{ inputs.fork_owner }}/${{ inputs.repository }}/actions/permissions/workflow" \
+          -F can_approve_pull_request_reviews=true \
+          -F default_workflow_permissions="write" \
+          -F enabled=true
+      env:
+        GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}
+
+    - name: Commit changes
+      working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
+      run: |
+        git config --global user.name 'github-actions'
+        git config --global user.email 'github-actions@github.com'
+
+        # Create and switch to new branch
+        git checkout -b update-locales
+
+        # Stage and commit changes
+        git add -A
+        git commit -m "Update locales"
+
+    - name: Install SSH key For PUSH
+      uses: shimataro/ssh-key-action@v2
+      with:
+        # PR private key from action server
+        key: ${{ secrets.PR_SSH_PRIVATE_KEY }}
+        # github public key to confirm it's github server
+        known_hosts: github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
+
+    - name: Push changes
+      working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
+      run: |
+        # Force push to create the branch
+        echo "Pushing changes to ${{ inputs.fork_owner }}/${{ inputs.repository }}"
+        git push -f git@github.com:${{ inputs.fork_owner }}/${{ inputs.repository }}.git update-locales
+
+    - name: Create PR
+      working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
+      run: |
+        # Create PR using gh cli
+        gh pr create --title "Update locales for ${{ inputs.repository }}" --repo ${{ inputs.owner }}/${{ inputs.repository }} --head ${{ inputs.fork_owner }}:update-locales --body "Update locales for ${{ inputs.repository }}"
+      env:
+        GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}

.github/workflows/i18n-node-defs.yaml

@@ -0,0 +1,48 @@
+name: Update Node Definitions Locales
+
+on:
+  workflow_dispatch:
+    inputs:
+      trigger_type:
+        description: 'Type of trigger (manual or automatic)'
+        required: false
+        type: string
+        default: 'manual'
+
+jobs:
+  update-locales:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: Comfy-Org/ComfyUI_frontend_setup_action@v2.3
+    - name: Install Playwright Browsers
+      run: npx playwright install chromium --with-deps
+      working-directory: ComfyUI_frontend
+    - name: Start dev server
+      # Run electron dev server as it is a superset of the web dev server
+      # We do want electron specific UIs to be translated.
+      run: npm run dev:electron &
+      working-directory: ComfyUI_frontend
+    - name: Update en.json
+      run: npm run collect-i18n -- scripts/collect-i18n-node-defs.ts
+      env:
+        PLAYWRIGHT_TEST_URL: http://localhost:5173
+      working-directory: ComfyUI_frontend
+    - name: Update translations
+      run: npm run locale
+      env:
+        OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+      working-directory: ComfyUI_frontend
+    - name: Create Pull Request
+      uses: peter-evans/create-pull-request@v7
+      with:
+        token: ${{ secrets.PR_GH_TOKEN }}
+        commit-message: "Update locales for node definitions"
+        title: "Update locales for node definitions"
+        body: |
+          Automated PR to update locales for node definitions
+
+          This PR was created automatically by the frontend update workflow.
+        branch: update-locales-node-defs-${{ github.event.inputs.trigger_type }}-${{ github.run_id }}
+        base: main
+        labels: dependencies
+        path: ComfyUI_frontend

.github/workflows/i18n-update-core.yaml

@@ -1,61 +0,0 @@
-# Description: Generates and updates translations for core ComfyUI components using OpenAI
-name: 'i18n: Update Core'
-
-on:
-  # Manual dispatch for urgent translation updates
-  workflow_dispatch:
-  # Only trigger on PRs to main/master - additional branch filtering in job condition
-  pull_request:
-    branches: [main]
-    types: [opened, synchronize, reopened]
-
-jobs:
-  update-locales:
-    # Branch detection: Only run for manual dispatch or version-bump-* branches from main repo
-    if: github.event_name == 'workflow_dispatch' || (github.event.pull_request.head.repo.full_name == github.repository && startsWith(github.head_ref, 'version-bump-'))
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          token: ${{ secrets.PR_GH_TOKEN }}
-
-      # Setup playwright environment
-      - name: Setup ComfyUI Frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: true
-      - name: Setup ComfyUI Server
-        uses: ./.github/actions/setup-comfyui-server
-        with:
-          launch_server: true
-      - name: Setup Playwright
-        uses: ./.github/actions/setup-playwright
-
-      - name: Start dev server
-        # Run electron dev server as it is a superset of the web dev server
-        # We do want electron specific UIs to be translated.
-        run: pnpm dev:electron &
-
-      # Update locales, collect new strings and update translations using OpenAI, then commit changes
-      - name: Update en.json
-        run: pnpm collect-i18n
-        env:
-          PLAYWRIGHT_TEST_URL: http://localhost:5173
-      - name: Update translations
-        run: pnpm locale && pnpm format
-        env:
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-      - name: Commit updated locales
-        run: |
-          git config --global user.name 'github-actions'
-          git config --global user.email 'github-actions@github.com'
-          git fetch origin ${{ github.head_ref }}
-          # Stash any local changes before checkout
-          git stash -u
-          git checkout -B ${{ github.head_ref }} origin/${{ github.head_ref }}
-          # Apply the stashed changes if any
-          git stash pop || true
-          git add src/locales/
-          git diff --staged --quiet || git commit -m "Update locales"
-          git push origin HEAD:${{ github.head_ref }}

.github/workflows/i18n-update-custom-nodes.yaml

@@ -1,136 +0,0 @@
-name: i18n Update Custom Nodes
-
-on:
-  workflow_dispatch:
-    inputs:
-      owner:
-        description: 'Owner of the repository to update locales for'
-        required: true
-        type: string
-      repository:
-        description: 'Repository to update locales for'
-        required: true
-        type: string
-      fork_owner:
-        description: 'Owner of the forked repository'
-        required: false
-        type: string
-        default: 'Comfy-Org'
-
-jobs:
-  update-locales:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      # Setup playwright environment with custom node repository
-      - name: Setup ComfyUI Server (without launching)
-        uses: ./.github/actions/setup-comfyui-server
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: 'true'
-      - name: Setup Playwright
-        uses: ./.github/actions/setup-playwright
-
-      # Install the custom node repository
-      - name: Checkout custom node repository
-        uses: actions/checkout@v6
-        with:
-          repository: ${{ inputs.owner }}/${{ inputs.repository }}
-          path: 'ComfyUI/custom_nodes/${{ inputs.repository }}'
-      - name: Install custom node Python requirements
-        working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
-        run: |
-          if [ -f "requirements.txt" ]; then
-            pip install -r requirements.txt
-          fi
-
-      # Start ComfyUI Server
-      - name: Start ComfyUI Server
-        shell: bash
-        working-directory: ComfyUI
-        run: |
-          python main.py --cpu --multi-user --front-end-root ../dist --custom-node-path ../ComfyUI/custom_nodes/${{ inputs.repository }} &
-          wait-for-it --service
-
-      - name: Start dev server
-        # Run electron dev server as it is a superset of the web dev server
-        # We do want electron specific UIs to be translated.
-        run: pnpm dev:electron &
-
-      - name: Capture base i18n
-        run: pnpm exec tsx scripts/diff-i18n capture
-      - name: Update en.json
-        run: pnpm collect-i18n
-        env:
-          PLAYWRIGHT_TEST_URL: http://localhost:5173
-      - name: Update translations
-        run: pnpm locale
-        env:
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-      - name: Diff base vs updated i18n
-        run: pnpm exec tsx scripts/diff-i18n diff
-      - name: Update i18n in custom node repository
-        run: |
-          LOCALE_DIR=ComfyUI/custom_nodes/${{ inputs.repository }}/locales/
-          install -d "$LOCALE_DIR"
-          cp -rf ComfyUI_frontend/temp/diff/* "$LOCALE_DIR"
-
-      # Git ops for pushing changes and creating PR
-      - name: Check and create fork of custom node repository
-        run: |
-          # Try to fork the repository
-          gh repo fork ${{ inputs.owner }}/${{ inputs.repository }} --clone=false || {
-            echo "Fork failed - repository might already be forked"
-            # Exit 0 to prevent the workflow from failing
-            exit 0
-          }
-
-          # Enable workflows on the forked repository
-          gh api \
-            --method PUT \
-            -H "Accept: application/vnd.github+json" \
-            "/repos/${{ inputs.fork_owner }}/${{ inputs.repository }}/actions/permissions/workflow" \
-            -F can_approve_pull_request_reviews=true \
-            -F default_workflow_permissions="write" \
-            -F enabled=true
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}
-
-      - name: Commit changes
-        working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
-        run: |
-          git config --global user.name 'github-actions'
-          git config --global user.email 'github-actions@github.com'
-
-          # Create and switch to new branch
-          git checkout -b update-locales
-
-          # Stage and commit changes
-          git add -A
-          git commit -m "Update locales"
-
-      - name: Install SSH key For PUSH
-        uses: shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4 # v2.7.0
-        with:
-          # PR private key from action server
-          key: ${{ secrets.PR_SSH_PRIVATE_KEY }}
-          # github public key to confirm it's github server
-          known_hosts: github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
-
-      - name: Push changes
-        working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
-        run: |
-          # Force push to create the branch
-          echo "Pushing changes to ${{ inputs.fork_owner }}/${{ inputs.repository }}"
-          git push -f git@github.com:${{ inputs.fork_owner }}/${{ inputs.repository }}.git update-locales
-
-      - name: Create PR
-        working-directory: ComfyUI/custom_nodes/${{ inputs.repository }}
-        run: |
-          # Create PR using gh cli
-          gh pr create --title "Update locales for ${{ inputs.repository }}" --repo ${{ inputs.owner }}/${{ inputs.repository }} --head ${{ inputs.fork_owner }}:update-locales --body "Update locales for ${{ inputs.repository }}"
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}

.github/workflows/i18n-update-nodes.yaml

@@ -1,54 +0,0 @@
-name: i18n Update Nodes
-
-on:
-  workflow_dispatch:
-    inputs:
-      trigger_type:
-        description: 'Type of trigger (manual or automatic)'
-        required: false
-        type: string
-        default: 'manual'
-
-jobs:
-  update-locales:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-      # Setup playwright environment
-      - name: Setup ComfyUI Server (and start)
-        uses: ./.github/actions/setup-comfyui-server
-        with:
-          launch_server: true
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: true
-      - name: Setup Playwright
-        uses: ./.github/actions/setup-playwright
-
-      - name: Start dev server
-        # Run electron dev server as it is a superset of the web dev server
-        # We do want electron specific UIs to be translated.
-        run: pnpm dev:electron &
-      - name: Update en.json
-        run: pnpm collect-i18n -- scripts/collect-i18n-node-defs.ts
-        env:
-          PLAYWRIGHT_TEST_URL: http://localhost:5173
-      - name: Update translations
-        run: pnpm locale
-        env:
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
-        with:
-          token: ${{ secrets.PR_GH_TOKEN }}
-          commit-message: 'Update locales for node definitions'
-          title: 'Update locales for node definitions'
-          body: |
-            Automated PR to update locales for node definitions
-
-            This PR was created automatically by the frontend update workflow.
-          branch: update-locales-node-defs-${{ github.event.inputs.trigger_type }}-${{ github.run_id }}
-          base: main
-          labels: dependencies

.github/workflows/i18n.yaml

@@ -0,0 +1,45 @@
+name: Update Locales
+
+on:
+  pull_request:
+    branches: [ main, master, dev* ]
+
+jobs:
+  update-locales:
+    # Don't run on fork PRs
+    if: github.event.pull_request.head.repo.full_name == github.repository
+    runs-on: ubuntu-latest
+    steps:
+    - uses: Comfy-Org/ComfyUI_frontend_setup_action@v2.3
+    - name: Install Playwright Browsers
+      run: npx playwright install chromium --with-deps
+      working-directory: ComfyUI_frontend
+    - name: Start dev server
+      # Run electron dev server as it is a superset of the web dev server
+      # We do want electron specific UIs to be translated.
+      run: npm run dev:electron &
+      working-directory: ComfyUI_frontend
+    - name: Update en.json
+      run: npm run collect-i18n -- scripts/collect-i18n-general.ts
+      env:
+        PLAYWRIGHT_TEST_URL: http://localhost:5173
+      working-directory: ComfyUI_frontend
+    - name: Update translations
+      run: npm run locale
+      env:
+        OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+      working-directory: ComfyUI_frontend
+    - name: Commit updated locales
+      run: |
+        git config --global user.name 'github-actions'
+        git config --global user.email 'github-actions@github.com'
+        git fetch origin ${{ github.head_ref }}
+        # Stash any local changes before checkout
+        git stash -u
+        git checkout -B ${{ github.head_ref }} origin/${{ github.head_ref }}
+        # Apply the stashed changes if any
+        git stash pop || true
+        git add src/locales/
+        git diff --staged --quiet || git commit -m "Update locales [skip ci]"
+        git push origin HEAD:${{ github.head_ref }}
+      working-directory: ComfyUI_frontend

.github/workflows/pr-backport.yaml

@@ -1,469 +0,0 @@
-name: PR Backport
-
-on:
-  pull_request_target:
-    types: [closed, labeled]
-    branches: [main]
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: 'PR number to backport'
-        required: true
-        type: string
-      force_rerun:
-        description: 'Force rerun even if backports exist'
-        required: false
-        type: boolean
-        default: false
-
-concurrency:
-  group: backport-${{ github.event_name == 'workflow_dispatch' && inputs.pr_number || github.event.pull_request.number }}
-  cancel-in-progress: false
-
-jobs:
-  backport:
-    if: >
-      (github.event_name == 'pull_request_target' &&
-       github.event.pull_request.merged == true &&
-       contains(github.event.pull_request.labels.*.name, 'needs-backport')) ||
-      github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-      issues: write
-
-    steps:
-      - name: Validate inputs for manual triggers
-        if: github.event_name == 'workflow_dispatch'
-        run: |
-          # Validate PR number format
-          if ! [[ "${{ inputs.pr_number }}" =~ ^[0-9]+$ ]]; then
-            echo "::error::Invalid PR number format. Must be a positive integer."
-            exit 1
-          fi
-
-          # Validate PR exists and is merged
-          if ! gh pr view "${{ inputs.pr_number }}" --json merged >/dev/null 2>&1; then
-            echo "::error::PR #${{ inputs.pr_number }} not found or inaccessible."
-            exit 1
-          fi
-
-          MERGED=$(gh pr view "${{ inputs.pr_number }}" --json merged --jq '.merged')
-          if [ "$MERGED" != "true" ]; then
-            echo "::error::PR #${{ inputs.pr_number }} is not merged. Only merged PRs can be backported."
-            exit 1
-          fi
-
-          # Validate PR has needs-backport label
-          if ! gh pr view "${{ inputs.pr_number }}" --json labels --jq '.labels[].name' | grep -q "needs-backport"; then
-            echo "::error::PR #${{ inputs.pr_number }} does not have 'needs-backport' label."
-            exit 1
-          fi
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-
-      - name: Configure git
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-      - name: Collect backport targets
-        id: targets
-        run: |
-          TARGETS=()
-          declare -A SEEN=()
-
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            LABELS=$(gh pr view ${{ inputs.pr_number }} --json labels | jq -r '.labels[].name')
-          else
-            LABELS=$(jq -r '.pull_request.labels[].name' "$GITHUB_EVENT_PATH")
-          fi
-
-          add_target() {
-            local label="$1"
-            local target="$2"
-
-            if [ -z "$target" ]; then
-              return
-            fi
-
-            target=$(echo "$target" | xargs)
-
-            if [ -z "$target" ] || [ -n "${SEEN[$target]}" ]; then
-              return
-            fi
-
-            if git ls-remote --exit-code origin "$target" >/dev/null 2>&1; then
-              TARGETS+=("$target")
-              SEEN["$target"]=1
-            else
-              echo "::warning::Label '${label}' references missing branch '${target}'"
-            fi
-          }
-
-          while IFS= read -r label; do
-            [ -z "$label" ] && continue
-
-            if [[ "$label" =~ ^branch:(.+)$ ]]; then
-              add_target "$label" "${BASH_REMATCH[1]}"
-            elif [[ "$label" =~ ^backport:(.+)$ ]]; then
-              add_target "$label" "${BASH_REMATCH[1]}"
-            elif [[ "$label" =~ ^core\/([0-9]+)\.([0-9]+)$ ]]; then
-              SAFE_MAJOR="${BASH_REMATCH[1]}"
-              SAFE_MINOR="${BASH_REMATCH[2]}"
-              add_target "$label" "core/${SAFE_MAJOR}.${SAFE_MINOR}"
-            elif [[ "$label" =~ ^cloud\/([0-9]+)\.([0-9]+)$ ]]; then
-              SAFE_MAJOR="${BASH_REMATCH[1]}"
-              SAFE_MINOR="${BASH_REMATCH[2]}"
-              add_target "$label" "cloud/${SAFE_MAJOR}.${SAFE_MINOR}"
-            elif [[ "$label" =~ ^[0-9]+\.[0-9]+$ ]]; then
-              add_target "$label" "core/${label}"
-            fi
-          done <<< "$LABELS"
-
-          if [ "${#TARGETS[@]}" -eq 0 ]; then
-            echo "::error::No backport targets found (use labels like '1.24' or 'branch:release/hotfix')"
-            exit 1
-          fi
-
-          echo "targets=${TARGETS[*]}" >> $GITHUB_OUTPUT
-          echo "Found backport targets: ${TARGETS[*]}"
-
-      - name: Filter already backported targets
-        id: filter-targets
-        env:
-          EVENT_NAME: ${{ github.event_name }}
-          FORCE_RERUN_INPUT: >-
-            ${{ github.event_name == 'workflow_dispatch' && inputs.force_rerun
-            || 'false' }}
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          PR_NUMBER: >-
-            ${{ github.event_name == 'workflow_dispatch' && inputs.pr_number
-            || github.event.pull_request.number }}
-        run: |
-          set -euo pipefail
-
-          REQUESTED_TARGETS="${{ steps.targets.outputs.targets }}"
-          if [ -z "$REQUESTED_TARGETS" ]; then
-            echo "skip=true" >> $GITHUB_OUTPUT
-            echo "pending-targets=" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          FORCE_RERUN=false
-          if [ "$EVENT_NAME" = "workflow_dispatch" ] && [ "$FORCE_RERUN_INPUT" = "true" ]; then
-            FORCE_RERUN=true
-          fi
-
-          mapfile -t EXISTING_BRANCHES < <(
-            git ls-remote --heads origin "backport-${PR_NUMBER}-to-*" || true
-          )
-
-          PENDING=()
-          SKIPPED=()
-          REUSED=()
-
-          for target in $REQUESTED_TARGETS; do
-            SAFE_TARGET=$(echo "$target" | tr '/' '-')
-            BACKPORT_BRANCH="backport-${PR_NUMBER}-to-${SAFE_TARGET}"
-
-            if [ "$FORCE_RERUN" = true ]; then
-              PENDING+=("$target")
-              continue
-            fi
-
-            if printf '%s\n' "${EXISTING_BRANCHES[@]:-}" |
-              grep -Fq "refs/heads/${BACKPORT_BRANCH}"; then
-              OPEN_PR=$(
-                gh pr list \
-                  --state open \
-                  --head "${BACKPORT_BRANCH}" \
-                  --json number \
-                  --jq 'if length > 0 then .[0].number else "" end'
-              )
-              if [ -n "$OPEN_PR" ]; then
-                SKIPPED+=("${target} (PR #${OPEN_PR})")
-                continue
-              fi
-
-              REUSED+=("$BACKPORT_BRANCH")
-            fi
-
-            PENDING+=("$target")
-          done
-
-          SKIPPED_JOINED="${SKIPPED[*]:-}"
-          PENDING_JOINED="${PENDING[*]:-}"
-
-          echo "already-exists=${SKIPPED_JOINED}" >> $GITHUB_OUTPUT
-          echo "pending-targets=${PENDING_JOINED}" >> $GITHUB_OUTPUT
-          echo "reused-branches=${REUSED[*]:-}" >> $GITHUB_OUTPUT
-
-          if [ -z "$PENDING_JOINED" ]; then
-            echo "skip=true" >> $GITHUB_OUTPUT
-            if [ -n "$SKIPPED_JOINED" ]; then
-              echo "::warning::Backport branches exist: ${SKIPPED_JOINED}"
-            fi
-          else
-            echo "skip=false" >> $GITHUB_OUTPUT
-            if [ -n "$SKIPPED_JOINED" ]; then
-              echo "::notice::Skipping backport targets: ${SKIPPED_JOINED}"
-            fi
-            if [ "${#REUSED[@]}" -gt 0 ]; then
-              echo "::notice::Reusing backport branches: ${REUSED[*]}"
-            fi
-          fi
-
-      - name: Backport commits
-        if: steps.filter-targets.outputs.skip != 'true'
-        id: backport
-        env:
-          PR_NUMBER: ${{ github.event_name == 'workflow_dispatch' && inputs.pr_number || github.event.pull_request.number }}
-        run: |
-          FAILED=""
-          SUCCESS=""
-
-          CREATED_BRANCHES_FILE="$(
-            mktemp "$RUNNER_TEMP/backport-branches-XXXXXX"
-          )"
-          echo "CREATED_BRANCHES_FILE=$CREATED_BRANCHES_FILE" >> "$GITHUB_ENV"
-
-          # Get PR data for manual triggers
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            PR_DATA=$(gh pr view ${{ inputs.pr_number }} --json title,mergeCommit)
-            PR_TITLE=$(echo "$PR_DATA" | jq -r '.title')
-            MERGE_COMMIT=$(echo "$PR_DATA" | jq -r '.mergeCommit.oid')
-          else
-            PR_TITLE=$(jq -r '.pull_request.title' "$GITHUB_EVENT_PATH")
-            MERGE_COMMIT=$(jq -r '.pull_request.merge_commit_sha' "$GITHUB_EVENT_PATH")
-          fi
-
-          for target in ${{ steps.filter-targets.outputs.pending-targets }}; do
-            TARGET_BRANCH="${target}"
-            SAFE_TARGET=$(echo "$TARGET_BRANCH" | tr '/' '-')
-            BACKPORT_BRANCH="backport-${PR_NUMBER}-to-${SAFE_TARGET}"
-            REMOTE_BACKPORT_EXISTS=false
-
-            if git ls-remote --exit-code origin "${BACKPORT_BRANCH}" >/dev/null 2>&1; then
-              REMOTE_BACKPORT_EXISTS=true
-              echo "::notice::Updating existing branch ${BACKPORT_BRANCH}"
-            fi
-
-            echo "::group::Backporting to ${TARGET_BRANCH}"
-
-            # Fetch target branch (fail if doesn't exist)
-            if ! git fetch origin "${TARGET_BRANCH}"; then
-              echo "::error::Target branch ${TARGET_BRANCH} does not exist"
-              FAILED="${FAILED}${TARGET_BRANCH}:branch-missing "
-              echo "::endgroup::"
-              continue
-            fi
-
-            # Check if commit already exists on target branch
-            if git branch -r --contains "${MERGE_COMMIT}" | grep -q "origin/${TARGET_BRANCH}"; then
-              echo "::notice::Commit ${MERGE_COMMIT} already exists on ${TARGET_BRANCH}, skipping backport"
-              FAILED="${FAILED}${TARGET_BRANCH}:already-exists "
-              echo "::endgroup::"
-              continue
-            fi
-
-            # Create backport branch
-            git checkout -b "${BACKPORT_BRANCH}" "origin/${TARGET_BRANCH}"
-
-            # Try cherry-pick
-            if git cherry-pick "${MERGE_COMMIT}"; then
-              if [ "$REMOTE_BACKPORT_EXISTS" = true ]; then
-                git push --force-with-lease origin "${BACKPORT_BRANCH}"
-              else
-                git push origin "${BACKPORT_BRANCH}"
-              fi
-              echo "${BACKPORT_BRANCH}" >> "$CREATED_BRANCHES_FILE"
-              SUCCESS="${SUCCESS}${TARGET_BRANCH}:${BACKPORT_BRANCH} "
-              echo "Successfully created backport branch: ${BACKPORT_BRANCH}"
-              # Return to main (keep the branch, we need it for PR)
-              git checkout main
-            else
-              # Get conflict info
-              CONFLICTS=$(git diff --name-only --diff-filter=U | tr '\n' ',')
-              git cherry-pick --abort
-
-              echo "::error::Cherry-pick failed due to conflicts"
-              FAILED="${FAILED}${TARGET_BRANCH}:conflicts:${CONFLICTS} "
-
-              # Clean up the failed branch
-              git checkout main
-              git branch -D "${BACKPORT_BRANCH}"
-            fi
-
-            echo "::endgroup::"
-          done
-
-          echo "success=${SUCCESS}" >> $GITHUB_OUTPUT
-          echo "failed=${FAILED}" >> $GITHUB_OUTPUT
-
-          if [ -s "$CREATED_BRANCHES_FILE" ]; then
-            CREATED_LIST=$(paste -sd' ' "$CREATED_BRANCHES_FILE")
-            echo "created-branches=${CREATED_LIST}" >> $GITHUB_OUTPUT
-          else
-            echo "created-branches=" >> $GITHUB_OUTPUT
-          fi
-
-          if [ -n "${FAILED}" ]; then
-            exit 1
-          fi
-
-      - name: Create PR for each successful backport
-        if: steps.filter-targets.outputs.skip != 'true' && steps.backport.outputs.success
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}
-          PR_NUMBER: ${{ github.event_name == 'workflow_dispatch' && inputs.pr_number || github.event.pull_request.number }}
-        run: |
-          # Get PR data for manual triggers
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            PR_DATA=$(gh pr view ${{ inputs.pr_number }} --json title,author)
-            PR_TITLE=$(echo "$PR_DATA" | jq -r '.title')
-            PR_AUTHOR=$(echo "$PR_DATA" | jq -r '.author.login')
-          else
-            PR_TITLE=$(jq -r '.pull_request.title' "$GITHUB_EVENT_PATH")
-            PR_AUTHOR=$(jq -r '.pull_request.user.login' "$GITHUB_EVENT_PATH")
-          fi
-
-          for backport in ${{ steps.backport.outputs.success }}; do
-            IFS=':' read -r target branch <<< "${backport}"
-
-            if PR_URL=$(gh pr create \
-              --base "${target}" \
-              --head "${branch}" \
-              --title "[backport ${target}] ${PR_TITLE}" \
-              --body "Backport of #${PR_NUMBER} to \`${target}\`"$'\n\n'"Automatically created by backport workflow." \
-              --label "backport" 2>&1); then
-
-              # Extract PR number from URL
-              PR_NUM=$(echo "${PR_URL}" | grep -o '[0-9]*$')
-
-              if [ -n "${PR_NUM}" ]; then
-                gh pr comment "${PR_NUMBER}" --body "@${PR_AUTHOR} Successfully backported to #${PR_NUM}"
-              fi
-            else
-              echo "::error::Failed to create PR for ${target}: ${PR_URL}"
-              # Still try to comment on the original PR about the failure
-              gh pr comment "${PR_NUMBER}" --body "@${PR_AUTHOR} Backport branch created but PR creation failed for \`${target}\`. Please create the PR manually from branch \`${branch}\`"
-            fi
-          done
-
-      - name: Comment on failures
-        if: steps.filter-targets.outputs.skip != 'true' && failure() && steps.backport.outputs.failed
-        env:
-          GH_TOKEN: ${{ github.token }}
-          BACKPORT_AGENT_PROMPT_TEMPLATE: |
-            Backport PR #${PR_NUMBER} (${PR_URL}) to ${target}.
-            Cherry-pick merge commit ${MERGE_COMMIT} onto new branch
-            ${BACKPORT_BRANCH} from origin/${target}.
-            Resolve conflicts in: ${CONFLICTS_INLINE}.
-            For test snapshots (browser_tests/**/*-snapshots/), accept PR version if
-            changed in original PR, else keep target. For package.json versions, keep
-            target branch. For pnpm-lock.yaml, regenerate with pnpm install.
-            Ask user for non-obvious conflicts.
-            Create PR titled "[backport ${target}] <original title>" with label "backport".
-            See .github/workflows/pr-backport.yaml for workflow details.
-          COMMENT_BODY_TEMPLATE: |
-            ### ⚠️ Backport to `${target}` failed
-
-            **Reason:** Merge conflicts detected during cherry-pick of `${MERGE_COMMIT_SHORT}`
-
-            <details>
-            <summary>📄 Conflicting files</summary>
-
-            ```
-            ${CONFLICTS_BLOCK}
-            ```
-
-            </details>
-
-            <details>
-            <summary>🤖 Prompt for AI Agents</summary>
-
-            ```
-            ${AGENT_PROMPT}
-            ```
-
-            </details>
-
-            ---
-            cc @${PR_AUTHOR}
-        run: |
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            PR_DATA=$(gh pr view ${{ inputs.pr_number }} --json author,mergeCommit)
-            PR_NUMBER="${{ inputs.pr_number }}"
-            PR_AUTHOR=$(echo "$PR_DATA" | jq -r '.author.login')
-            MERGE_COMMIT=$(echo "$PR_DATA" | jq -r '.mergeCommit.oid')
-          else
-            PR_NUMBER=$(jq -r '.pull_request.number' "$GITHUB_EVENT_PATH")
-            PR_AUTHOR=$(jq -r '.pull_request.user.login' "$GITHUB_EVENT_PATH")
-            MERGE_COMMIT=$(jq -r '.pull_request.merge_commit_sha' "$GITHUB_EVENT_PATH")
-          fi
-
-          for failure in ${{ steps.backport.outputs.failed }}; do
-            IFS=':' read -r target reason conflicts <<< "${failure}"
-
-            if [ "${reason}" = "branch-missing" ]; then
-              gh pr comment "${PR_NUMBER}" --body "@${PR_AUTHOR} Backport failed: Branch \`${target}\` does not exist"
-
-            elif [ "${reason}" = "already-exists" ]; then
-              gh pr comment "${PR_NUMBER}" --body "@${PR_AUTHOR} Commit \`${MERGE_COMMIT}\` already exists on branch \`${target}\`. No backport needed."
-
-            elif [ "${reason}" = "conflicts" ]; then
-              CONFLICTS_INLINE=$(echo "${conflicts}" | tr ',' ' ')
-              SAFE_TARGET=$(echo "$target" | tr '/' '-')
-              BACKPORT_BRANCH="backport-${PR_NUMBER}-to-${SAFE_TARGET}"
-              PR_URL="${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/pull/${PR_NUMBER}"
-
-              export PR_NUMBER PR_URL MERGE_COMMIT target BACKPORT_BRANCH CONFLICTS_INLINE
-
-              # envsubst is provided by gettext-base
-              if ! command -v envsubst >/dev/null 2>&1; then
-                sudo apt-get update && sudo apt-get install -y gettext-base
-              fi
-
-              AGENT_PROMPT=$(envsubst '${PR_NUMBER} ${PR_URL} ${target} ${MERGE_COMMIT} ${BACKPORT_BRANCH} ${CONFLICTS_INLINE}' <<<"$BACKPORT_AGENT_PROMPT_TEMPLATE")
-
-              # Use fenced code block for conflicts to handle special chars in filenames
-              CONFLICTS_BLOCK=$(echo "${conflicts}" | tr ',' '\n')
-              MERGE_COMMIT_SHORT="${MERGE_COMMIT:0:7}"
-
-              export target MERGE_COMMIT_SHORT CONFLICTS_BLOCK AGENT_PROMPT PR_AUTHOR
-              COMMENT_BODY=$(envsubst '${target} ${MERGE_COMMIT_SHORT} ${CONFLICTS_BLOCK} ${AGENT_PROMPT} ${PR_AUTHOR}' <<<"$COMMENT_BODY_TEMPLATE")
-
-              gh pr comment "${PR_NUMBER}" --body "${COMMENT_BODY}"
-            fi
-          done
-
-      - name: Cleanup stranded backport branches
-        if: steps.filter-targets.outputs.skip != 'true' && failure()
-        run: |
-          FILE="${CREATED_BRANCHES_FILE:-}"
-
-          if [ -z "$FILE" ] || [ ! -f "$FILE" ]; then
-            echo "No backport branches recorded for cleanup"
-            exit 0
-          fi
-
-          while IFS= read -r branch; do
-            [ -z "$branch" ] && continue
-            printf 'Deleting branch %s\n' "${branch}"
-            if ! git push origin --delete "$branch"; then
-              echo "::warning::Failed to delete ${branch}"
-            fi
-          done < "$FILE"
-
-      - name: Remove needs-backport label
-        if: steps.filter-targets.outputs.skip != 'true' && success()
-        run: gh pr edit ${{ github.event_name == 'workflow_dispatch' && inputs.pr_number || github.event.pull_request.number }} --remove-label "needs-backport"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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

@@ -1,69 +0,0 @@
-# Description: AI-powered code review triggered by adding the 'claude-review' label to a PR
-name: 'PR: Claude Review'
-
-permissions:
-  contents: read
-  pull-requests: write
-  issues: write
-  id-token: write
-  statuses: write
-
-on:
-  pull_request:
-    types: [labeled]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  claude-review:
-    runs-on: ubuntu-latest
-    if: github.event.label.name == 'claude-review'
-    timeout-minutes: 30
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-          ref: refs/pull/${{ github.event.pull_request.number }}/head
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Install dependencies for analysis tools
-        run: |
-          pnpm install -g typescript @vue/compiler-sfc
-
-      - name: Run Claude PR Review
-        uses: anthropics/claude-code-action@ff34ce0ff04a470bd3fa56c1ef391c8f1c19f8e9 # v1.0.38
-        with:
-          label_trigger: 'claude-review'
-          prompt: |
-            Read the file .claude/commands/comprehensive-pr-review.md and follow ALL the instructions exactly.
-
-            CRITICAL: You must post individual inline comments using the gh api commands shown in the file.
-            DO NOT create a summary comment.
-            Each issue must be posted as a separate inline comment on the specific line of code.
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          claude_args: "--max-turns 256 --allowedTools 'Bash(git:*),Bash(gh api:*),Bash(gh pr:*),Bash(gh repo:*),Bash(jq:*),Bash(echo:*),Read,Write,Edit,Glob,Grep,WebFetch'"
-        env:
-          PR_NUMBER: ${{ github.event.pull_request.number }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          COMMIT_SHA: ${{ github.event.pull_request.head.sha }}
-          BASE_SHA: ${{ github.event.pull_request.base.sha }}
-          REPOSITORY: ${{ github.repository }}
-
-      - name: Remove claude-review label
-        if: always()
-        run: gh pr edit ${{ github.event.pull_request.number }} --remove-label "claude-review"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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

@@ -1,102 +0,0 @@
-name: 'PR: Performance Report'
-
-on:
-  workflow_run:
-    workflows: ['CI: Performance Report']
-    types:
-      - completed
-
-permissions:
-  contents: read
-  pull-requests: write
-  issues: write
-
-jobs:
-  comment:
-    runs-on: ubuntu-latest
-    if: >
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      github.event.workflow_run.event == 'pull_request' &&
-      github.event.workflow_run.conclusion == 'success'
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Setup Node
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Download PR metadata
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          name: perf-meta
-          run_id: ${{ github.event.workflow_run.id }}
-          path: temp/perf-meta/
-
-      - name: Resolve and validate PR metadata
-        id: pr-meta
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const fs = require('fs');
-            const artifactPr = Number(fs.readFileSync('temp/perf-meta/number.txt', 'utf8').trim());
-            const artifactBase = fs.readFileSync('temp/perf-meta/base.txt', 'utf8').trim();
-
-            // Resolve PR from trusted workflow context
-            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.setFailed('Unable to resolve PR from workflow_run context.');
-              return;
-            }
-
-            if (Number(pr.number) !== artifactPr) {
-              core.setFailed(`Artifact PR number (${artifactPr}) does not match trusted context (${pr.number}).`);
-              return;
-            }
-
-            const trustedBase = pr.base?.ref;
-            if (!trustedBase || artifactBase !== trustedBase) {
-              core.setFailed(`Artifact base (${artifactBase}) does not match trusted context (${trustedBase}).`);
-              return;
-            }
-
-            core.setOutput('number', String(pr.number));
-            core.setOutput('base', trustedBase);
-
-      - name: Download PR perf metrics
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          name: perf-metrics
-          run_id: ${{ github.event.workflow_run.id }}
-          path: test-results/
-
-      - name: Download baseline perf metrics
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          branch: ${{ steps.pr-meta.outputs.base }}
-          workflow: ci-perf-report.yaml
-          event: push
-          name: perf-metrics
-          path: temp/perf-baseline/
-          if_no_artifact_found: warn
-
-      - name: Generate perf report
-        run: npx --yes tsx scripts/perf-report.ts > perf-report.md
-
-      - name: Post PR comment
-        uses: ./.github/actions/post-pr-report-comment
-        with:
-          pr-number: ${{ steps.pr-meta.outputs.number }}
-          report-file: ./perf-report.md
-          comment-marker: '<!-- COMFYUI_FRONTEND_PERF -->'
-          token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/pr-size-report.yaml

@@ -1,133 +0,0 @@
-name: 'PR: Size Report'
-
-on:
-  workflow_run:
-    workflows: ['CI: Size Data']
-    types:
-      - completed
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: 'PR number to report on'
-        required: true
-        type: number
-      run_id:
-        description: 'Size data workflow run ID'
-        required: true
-        type: string
-
-permissions:
-  contents: read
-  pull-requests: write
-  issues: write
-
-jobs:
-  comment:
-    runs-on: ubuntu-latest
-    if: >
-      github.repository == 'Comfy-Org/ComfyUI_frontend' &&
-      (
-        (github.event_name == 'workflow_run' &&
-         github.event.workflow_run.event == 'pull_request' &&
-         github.event.workflow_run.conclusion == 'success') ||
-        github.event_name == 'workflow_dispatch'
-      )
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-
-      - name: Download size data
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          name: size-data
-          run_id: ${{ github.event_name == 'workflow_dispatch' && inputs.run_id || github.event.workflow_run.id }}
-          path: temp/size
-
-      - name: Resolve and validate PR metadata
-        id: pr-meta
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const fs = require('fs');
-
-            // workflow_dispatch: validate artifact metadata against API-resolved PR
-            if (context.eventName === 'workflow_dispatch') {
-              const pullNumber = Number('${{ inputs.pr_number }}');
-              const { data: dispatchPr } = await github.rest.pulls.get({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                pull_number: pullNumber,
-              });
-
-              const artifactPr = Number(fs.readFileSync('temp/size/number.txt', 'utf8').trim());
-              const artifactBase = fs.readFileSync('temp/size/base.txt', 'utf8').trim();
-
-              if (artifactPr !== dispatchPr.number) {
-                core.setFailed(`Artifact PR number (${artifactPr}) does not match dispatch PR (${dispatchPr.number}).`);
-                return;
-              }
-              if (artifactBase !== dispatchPr.base.ref) {
-                core.setFailed(`Artifact base (${artifactBase}) does not match dispatch PR base (${dispatchPr.base.ref}).`);
-                return;
-              }
-
-              core.setOutput('number', String(dispatchPr.number));
-              core.setOutput('base', dispatchPr.base.ref);
-              return;
-            }
-
-            // workflow_run: validate artifact metadata against trusted context
-            const artifactPr = Number(fs.readFileSync('temp/size/number.txt', 'utf8').trim());
-            const artifactBase = fs.readFileSync('temp/size/base.txt', 'utf8').trim();
-
-            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.setFailed('Unable to resolve PR from workflow_run context.');
-              return;
-            }
-
-            if (Number(pr.number) !== artifactPr) {
-              core.setFailed(`Artifact PR number (${artifactPr}) does not match trusted context (${pr.number}).`);
-              return;
-            }
-
-            const trustedBase = pr.base?.ref;
-            if (!trustedBase || artifactBase !== trustedBase) {
-              core.setFailed(`Artifact base (${artifactBase}) does not match trusted context (${trustedBase}).`);
-              return;
-            }
-
-            core.setOutput('number', String(pr.number));
-            core.setOutput('base', trustedBase);
-
-      - name: Download previous size data
-        uses: dawidd6/action-download-artifact@0bd50d53a6d7fb5cb921e607957e9cc12b4ce392 # v12
-        with:
-          branch: ${{ steps.pr-meta.outputs.base }}
-          workflow: ci-size-data.yaml
-          event: push
-          name: size-data
-          path: temp/size-prev
-          if_no_artifact_found: warn
-
-      - name: Generate size report
-        run: node scripts/size-report.js > size-report.md
-
-      - name: Post PR comment
-        uses: ./.github/actions/post-pr-report-comment
-        with:
-          pr-number: ${{ steps.pr-meta.outputs.number }}
-          report-file: ./size-report.md
-          comment-marker: '<!-- COMFYUI_FRONTEND_SIZE -->'
-          token: ${{ secrets.GITHUB_TOKEN }}

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

@@ -1,309 +0,0 @@
-# Setting test expectation screenshots for Playwright
-name: 'PR: Update Playwright Expectations'
-
-on:
-  pull_request:
-    types: [labeled]
-  issue_comment:
-    types: [created]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  setup:
-    runs-on: ubuntu-latest
-    if: >
-      ( github.event_name == 'pull_request' && github.event.label.name == 'New Browser Test Expectations' ) ||
-      ( 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-playwright') )
-    outputs:
-      pr-number: ${{ steps.pr-info.outputs.pr-number }}
-      branch: ${{ steps.pr-info.outputs.branch }}
-      comment-id: ${{ steps.find-update-comment.outputs.comment-id }}
-    steps:
-      - name: Get PR info
-        id: pr-info
-        run: |
-          echo "pr-number=${{ github.event.number || github.event.issue.number }}" >> $GITHUB_OUTPUT
-          echo "branch=$(gh pr view ${{ github.event.number || github.event.issue.number }} --repo ${{ github.repository }} --json headRefName --jq '.headRefName')" >> $GITHUB_OUTPUT
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Find Update Comment
-        uses: peter-evans/find-comment@b30e6a3c0ed37e7c023ccd3f1db5c6c0b0c23aad # v4.0.0
-        id: 'find-update-comment'
-        with:
-          issue-number: ${{ steps.pr-info.outputs.pr-number }}
-          comment-author: 'github-actions[bot]'
-          body-includes: 'Updating Playwright Expectations'
-
-      - name: Add Starting Reaction
-        uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9 # v5.0.0
-        with:
-          comment-id: ${{ steps.find-update-comment.outputs.comment-id }}
-          issue-number: ${{ steps.pr-info.outputs.pr-number }}
-          body: |
-            Updating Playwright Expectations
-          edit-mode: replace
-          reactions: eyes
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ steps.pr-info.outputs.branch }}
-      - name: Setup frontend
-        uses: ./.github/actions/setup-frontend
-        with:
-          include_build_step: true
-
-      # Upload built dist/ (containerized test jobs will pnpm install without cache)
-      - name: Upload built frontend
-        uses: actions/upload-artifact@v6
-        with:
-          name: frontend-dist
-          path: dist/
-          retention-days: 1
-
-  # Sharded snapshot updates
-  update-snapshots-sharded:
-    needs: setup
-    runs-on: ubuntu-latest
-    container:
-      image: ghcr.io/comfy-org/comfyui-ci-container:0.0.13
-      credentials:
-        username: ${{ github.actor }}
-        password: ${{ secrets.GITHUB_TOKEN }}
-    permissions:
-      contents: read
-      packages: read
-    strategy:
-      fail-fast: false
-      matrix:
-        shardIndex: [1, 2, 3, 4]
-        shardTotal: [4]
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ needs.setup.outputs.branch }}
-      - name: Download built frontend
-        uses: actions/download-artifact@v7
-        with:
-          name: frontend-dist
-          path: dist/
-
-      - name: Start ComfyUI server
-        uses: ./.github/actions/start-comfyui-server
-
-      - name: Install frontend deps
-        run: pnpm install --frozen-lockfile
-
-      # Run sharded tests with snapshot updates (browsers pre-installed in container)
-      - name: Update snapshots (Shard ${{ matrix.shardIndex }}/${{ matrix.shardTotal }})
-        id: playwright-tests
-        run: pnpm exec playwright test --update-snapshots --grep @screenshot --shard=${{ matrix.shardIndex }}/${{ matrix.shardTotal }}
-        continue-on-error: true
-
-      - name: Stage changed snapshot files
-        id: changed-snapshots
-        shell: bash
-        run: |
-          set -euo pipefail
-
-          # Configure git safe.directory for container environment
-          git config --global --add safe.directory "$(pwd)"
-
-          # Get list of changed snapshot files (including untracked/new files)
-          changed_files=$( (
-            git diff --name-only browser_tests/ 2>/dev/null || true
-            git ls-files --others --exclude-standard browser_tests/ 2>/dev/null || true
-          ) | sort -u | grep -E '\-snapshots/' || true )
-
-          if [ -z "$changed_files" ]; then
-            echo "No snapshot changes in shard ${{ matrix.shardIndex }}"
-            echo "has-changes=false" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          file_count=$(echo "$changed_files" | wc -l)
-          echo "Shard ${{ matrix.shardIndex }}: $file_count changed snapshot(s):"
-          echo "$changed_files"
-          echo "has-changes=true" >> $GITHUB_OUTPUT
-
-          # Copy changed files to staging directory
-          mkdir -p /tmp/changed_snapshots_shard
-          while IFS= read -r file; do
-            [ -f "$file" ] || continue
-            file_without_prefix="${file#browser_tests/}"
-            mkdir -p "/tmp/changed_snapshots_shard/$(dirname "$file_without_prefix")"
-            cp "$file" "/tmp/changed_snapshots_shard/$file_without_prefix"
-          done <<< "$changed_files"
-
-      # Upload ONLY the changed files from this shard
-      - name: Upload changed snapshots
-        uses: actions/upload-artifact@v6
-        if: steps.changed-snapshots.outputs.has-changes == 'true'
-        with:
-          name: snapshots-shard-${{ matrix.shardIndex }}
-          path: /tmp/changed_snapshots_shard/
-          retention-days: 1
-
-      - name: Upload test report
-        uses: actions/upload-artifact@v6
-        if: always()
-        with:
-          name: playwright-report-shard-${{ matrix.shardIndex }}
-          path: ./playwright-report/
-          retention-days: 30
-
-  # Merge snapshots and commit
-  merge-and-commit:
-    needs: [setup, update-snapshots-sharded]
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ needs.setup.outputs.branch }}
-          token: ${{ secrets.PR_GH_TOKEN }}
-
-      # Download all changed snapshot files from shards
-      - name: Download snapshot artifacts
-        uses: actions/download-artifact@v7
-        with:
-          pattern: snapshots-shard-*
-          path: ./downloaded-snapshots
-          merge-multiple: true
-
-      - name: List downloaded files
-        run: |
-          echo "=========================================="
-          echo "DOWNLOADED SNAPSHOT FILES"
-          echo "=========================================="
-          if [ -d "./downloaded-snapshots" ]; then
-            find ./downloaded-snapshots -type f
-            echo ""
-            echo "Total files: $(find ./downloaded-snapshots -type f | wc -l)"
-          else
-            echo "No snapshot artifacts downloaded (no changes in any shard)"
-            echo ""
-            echo "Total files: 0"
-          fi
-
-      # Merge only the changed files into browser_tests
-      - name: Merge changed snapshots
-        run: |
-          set -euo pipefail
-
-          echo "=========================================="
-          echo "MERGING CHANGED SNAPSHOTS"
-          echo "=========================================="
-
-          # Check if any artifacts were downloaded (merge-multiple puts files directly in path)
-          if [ ! -d "./downloaded-snapshots" ]; then
-            echo "No snapshot artifacts to merge"
-            echo "=========================================="
-            echo "MERGE COMPLETE"
-            echo "=========================================="
-            echo "Files merged: 0"
-            exit 0
-          fi
-
-          # Verify target directory exists
-          if [ ! -d "browser_tests" ]; then
-            echo "::error::Target directory 'browser_tests' does not exist"
-            exit 1
-          fi
-
-          # Count files to merge
-          file_count=$(find ./downloaded-snapshots -type f | wc -l)
-
-          if [ "$file_count" -eq 0 ]; then
-            echo "No snapshot files found in downloaded artifacts"
-            echo "=========================================="
-            echo "MERGE COMPLETE"
-            echo "=========================================="
-            echo "Files merged: 0"
-            exit 0
-          fi
-
-          echo "Merging $file_count snapshot file(s)..."
-
-          # Copy all files directly, preserving directory structure
-          # With merge-multiple: true, files are directly in ./downloaded-snapshots/ without shard subdirs
-          cp -v -r ./downloaded-snapshots/* browser_tests/ 2>&1 | sed 's/^/  /'
-
-          echo ""
-          echo "=========================================="
-          echo "MERGE COMPLETE"
-          echo "=========================================="
-          echo "Files merged: $file_count"
-
-      - name: Show changes
-        run: |
-          echo "=========================================="
-          echo "CHANGES SUMMARY"
-          echo "=========================================="
-          echo ""
-          echo "Changed files in browser_tests (including untracked):"
-          CHANGES=$(git status --porcelain=v1 --untracked-files=all -- browser_tests/)
-          if [ -z "$CHANGES" ]; then
-            echo "No changes"
-            echo ""
-            echo "Total changes:"
-            echo "0"
-          else
-            echo "$CHANGES" | head -50
-            echo ""
-            echo "Total changes:"
-            echo "$CHANGES" | wc -l
-          fi
-
-      - name: Commit updated expectations
-        id: commit
-        run: |
-          git config --global user.name 'github-actions'
-          git config --global user.email 'github-actions@github.com'
-
-          if [ -z "$(git status --porcelain=v1 --untracked-files=all -- browser_tests/)" ]; then
-            echo "No changes to commit"
-            echo "has-changes=false" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          echo "=========================================="
-          echo "COMMITTING CHANGES"
-          echo "=========================================="
-
-          echo "has-changes=true" >> $GITHUB_OUTPUT
-
-          git add browser_tests/
-          git commit -m "[automated] Update test expectations"
-
-          echo "Pushing to ${{ needs.setup.outputs.branch }}..."
-          git push origin ${{ needs.setup.outputs.branch }}
-
-          echo "✓ Commit and push successful"
-
-      - name: Add Done Reaction
-        uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9 # v5.0.0
-        if: github.event_name == 'issue_comment' && steps.commit.outputs.has-changes == 'true'
-        with:
-          comment-id: ${{ needs.setup.outputs.comment-id }}
-          issue-number: ${{ needs.setup.outputs.pr-number }}
-          reactions: +1
-          reactions-edit-mode: replace
-
-      - name: Remove New Browser Test Expectations label
-        if: always() && github.event_name == 'pull_request'
-        run: gh pr edit ${{ needs.setup.outputs.pr-number }} --remove-label "New Browser Test Expectations"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/publish-desktop-ui-on-merge.yaml

@@ -1,83 +0,0 @@
----
-name: Publish Desktop UI on PR Merge
-
-on:
-  pull_request:
-    types: ['closed']
-    branches: [main, core/*]
-    paths:
-      - 'apps/desktop-ui/package.json'
-
-jobs:
-  resolve:
-    name: Resolve Version and Dist Tag
-    runs-on: ubuntu-latest
-    if: >
-      github.event.pull_request.merged == true &&
-      contains(github.event.pull_request.labels.*.name, 'Release')
-    outputs:
-      version: ${{ steps.get_version.outputs.version }}
-      dist_tag: ${{ steps.dist.outputs.dist_tag }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.merge_commit_sha }}
-          persist-credentials: false
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Read desktop-ui version
-        id: get_version
-        run: |
-          VERSION=$(node -p "require('./apps/desktop-ui/package.json').version")
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-
-      - name: Determine dist-tag
-        id: dist
-        env:
-          VERSION: ${{ steps.get_version.outputs.version }}
-        run: |
-          if [[ "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+- ]]; then
-            echo "dist_tag=next" >> $GITHUB_OUTPUT
-          else
-            echo "dist_tag=latest" >> $GITHUB_OUTPUT
-          fi
-
-  publish:
-    name: Publish Desktop UI to npm
-    needs: resolve
-    uses: ./.github/workflows/publish-desktop-ui.yaml
-    with:
-      version: ${{ needs.resolve.outputs.version }}
-      dist_tag: ${{ needs.resolve.outputs.dist_tag }}
-      ref: ${{ github.event.pull_request.merge_commit_sha }}
-    secrets:
-      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-  comment_desktop_publish:
-    name: Comment Desktop Publish Summary
-    needs:
-      - resolve
-      - publish
-    if: success()
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      issues: write
-      pull-requests: write
-    steps:
-      - name: Checkout merge commit
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.merge_commit_sha }}
-          fetch-depth: 2
-
-      - name: Post desktop release summary comment
-        uses: ./.github/actions/comment-release-links
-        with:
-          issue-number: ${{ github.event.pull_request.number }}
-          version_file: apps/desktop-ui/package.json

.github/workflows/publish-desktop-ui.yaml

@@ -1,192 +0,0 @@
-name: Publish Desktop UI
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to publish (e.g., 1.2.3)'
-        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-ui-${{ github.workflow }}-${{ inputs.version }}-${{ inputs.dist_tag }}
-  cancel-in-progress: false
-
-jobs:
-  publish_desktop_ui:
-    name: Publish @comfyorg/desktop-ui
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    env:
-      PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: '1'
-      ENABLE_MINIFY: 'true'
-    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 }}
-          VERSION: ${{ inputs.version }}
-        shell: bash
-        run: |
-          set -euo pipefail
-          if [ -n "$REF" ]; then
-            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"
-          else
-            echo "ref=refs/tags/v$VERSION" >> "$GITHUB_OUTPUT"
-          fi
-
-      - 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@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - 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
-
-      - name: Build Desktop UI
-        run: pnpm build:desktop
-
-      - name: Prepare npm package
-        id: pkg
-        shell: bash
-        run: |
-          set -euo pipefail
-          APP_PKG=apps/desktop-ui/package.json
-          ROOT_PKG=package.json
-
-          NAME=$(jq -r .name "$APP_PKG")
-          APP_VERSION=$(jq -r .version "$APP_PKG")
-          ROOT_LICENSE=$(jq -r .license "$ROOT_PKG")
-          REPO=$(jq -r .repository "$ROOT_PKG")
-
-          if [ -z "$NAME" ] || [ "$NAME" = "null" ]; then
-            echo "::error title=Missing name::apps/desktop-ui/package.json is missing 'name'" >&2
-            exit 1
-          fi
-
-          INPUT_VERSION="${{ inputs.version }}"
-          if [ "$APP_VERSION" != "$INPUT_VERSION" ]; then
-            echo "::error title=Version mismatch::apps/desktop-ui version $APP_VERSION does not match input $INPUT_VERSION" >&2
-            exit 1
-          fi
-
-          if [ ! -d apps/desktop-ui/dist ]; then
-            echo "::error title=Missing build::apps/desktop-ui/dist not found. Did build succeed?" >&2
-            exit 1
-          fi
-
-          PUBLISH_DIR=apps/desktop-ui/.npm-publish
-          rm -rf "$PUBLISH_DIR"
-          mkdir -p "$PUBLISH_DIR"
-          cp -R apps/desktop-ui/dist "$PUBLISH_DIR/dist"
-
-          INPUT_VERSION="${{ inputs.version }}"
-          jq -n \
-            --arg name "$NAME" \
-            --arg version "$INPUT_VERSION" \
-            --arg description "Static assets for the ComfyUI Desktop UI" \
-            --arg license "$ROOT_LICENSE" \
-            --arg repository "$REPO" \
-            '{
-              name: $name,
-              version: $version,
-              description: $description,
-              license: $license,
-              repository: $repository,
-              type: "module",
-              private: false,
-              files: ["dist"],
-              publishConfig: { access: "public" }
-            }' > "$PUBLISH_DIR/package.json"
-
-          if [ -f apps/desktop-ui/README.md ]; then
-            cp apps/desktop-ui/README.md "$PUBLISH_DIR/README.md"
-          fi
-
-          echo "publish_dir=$PUBLISH_DIR" >> "$GITHUB_OUTPUT"
-          echo "name=$NAME" >> "$GITHUB_OUTPUT"
-
-      - name: Check if version already on npm
-        id: check_npm
-        env:
-          NAME: ${{ steps.pkg.outputs.name }}
-          VER: ${{ inputs.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: ${{ steps.pkg.outputs.publish_dir }}

.github/workflows/release-biweekly-comfyui.yaml

@@ -1,324 +0,0 @@
-# Automated bi-weekly workflow to bump ComfyUI frontend RC releases
-name: 'Release: Bi-weekly ComfyUI'
-
-on:
-  # Schedule for Monday at 12:00 PM PST (20:00 UTC)
-  schedule:
-    - cron: '0 20 * * 1'
-
-  # Allow manual triggering (bypasses bi-weekly check)
-  workflow_dispatch:
-    inputs:
-      comfyui_fork:
-        description: 'ComfyUI fork to use for PR (e.g., Comfy-Org/ComfyUI)'
-        required: false
-        default: 'Comfy-Org/ComfyUI'
-        type: string
-
-jobs:
-  check-release-week:
-    runs-on: ubuntu-latest
-    outputs:
-      is_release_week: ${{ steps.check.outputs.is_release_week }}
-    steps:
-      - name: Check if release week
-        id: check
-        run: |
-          # Anchor date: first bi-weekly release Monday
-          ANCHOR="2025-12-22"
-
-          ANCHOR_EPOCH=$(date -d "$ANCHOR" +%s)
-          NOW_EPOCH=$(date +%s)
-          WEEKS_SINCE=$(( (NOW_EPOCH - ANCHOR_EPOCH) / 604800 ))
-
-          if [ $((WEEKS_SINCE % 2)) -eq 0 ]; then
-            echo "Release week (week $WEEKS_SINCE since anchor $ANCHOR)"
-            echo "is_release_week=true" >> $GITHUB_OUTPUT
-          else
-            echo "Not a release week (week $WEEKS_SINCE since anchor $ANCHOR)"
-            echo "is_release_week=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Summary
-        run: |
-          echo "## Bi-weekly Check" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "- Is release week: ${{ steps.check.outputs.is_release_week }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Manual trigger: ${{ github.event_name == 'workflow_dispatch' }}" >> $GITHUB_STEP_SUMMARY
-
-  resolve-version:
-    needs: check-release-week
-    if: needs.check-release-week.outputs.is_release_week == 'true' || github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    outputs:
-      current_version: ${{ steps.resolve.outputs.current_version }}
-      target_version: ${{ steps.resolve.outputs.target_version }}
-      target_minor: ${{ steps.resolve.outputs.target_minor }}
-      target_branch: ${{ steps.resolve.outputs.target_branch }}
-      needs_release: ${{ steps.resolve.outputs.needs_release }}
-      diff_url: ${{ steps.resolve.outputs.diff_url }}
-      latest_patch_tag: ${{ steps.resolve.outputs.latest_patch_tag }}
-
-    steps:
-      - name: Checkout ComfyUI_frontend
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-          path: frontend
-
-      - name: Checkout ComfyUI (sparse)
-        uses: actions/checkout@v6
-        with:
-          repository: Comfy-Org/ComfyUI
-          sparse-checkout: |
-            requirements.txt
-          path: comfyui
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: 'frontend/.nvmrc'
-
-      - name: Install dependencies
-        working-directory: frontend
-        run: pnpm install --frozen-lockfile
-
-      - name: Resolve release information
-        id: resolve
-        working-directory: frontend
-        run: |
-          set -euo pipefail
-
-          # Run the resolver script
-          if ! RESULT=$(pnpm exec tsx scripts/cicd/resolve-comfyui-release.ts ../comfyui .); then
-            echo "Failed to resolve release information"
-            exit 1
-          fi
-
-          echo "Resolver output:"
-          echo "$RESULT"
-
-          # Validate JSON output
-          if ! echo "$RESULT" | jq empty 2>/dev/null; then
-            echo "Invalid JSON output from resolver"
-            exit 1
-          fi
-
-          # Parse JSON output and set outputs
-          echo "current_version=$(echo "$RESULT" | jq -r '.current_version')" >> $GITHUB_OUTPUT
-          echo "target_version=$(echo "$RESULT" | jq -r '.target_version')" >> $GITHUB_OUTPUT
-          echo "target_minor=$(echo "$RESULT" | jq -r '.target_minor')" >> $GITHUB_OUTPUT
-          echo "target_branch=$(echo "$RESULT" | jq -r '.target_branch')" >> $GITHUB_OUTPUT
-          echo "needs_release=$(echo "$RESULT" | jq -r '.needs_release')" >> $GITHUB_OUTPUT
-          echo "diff_url=$(echo "$RESULT" | jq -r '.diff_url')" >> $GITHUB_OUTPUT
-          echo "latest_patch_tag=$(echo "$RESULT" | jq -r '.latest_patch_tag')" >> $GITHUB_OUTPUT
-
-      - name: Summary
-        run: |
-          echo "## Release Information" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "- Current version: ${{ steps.resolve.outputs.current_version }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Target version: ${{ steps.resolve.outputs.target_version }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Target branch: ${{ steps.resolve.outputs.target_branch }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Needs release: ${{ steps.resolve.outputs.needs_release }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Diff: [${{ steps.resolve.outputs.current_version }}...${{ steps.resolve.outputs.target_version }}](${{ steps.resolve.outputs.diff_url }})" >> $GITHUB_STEP_SUMMARY
-
-  trigger-release-if-needed:
-    needs: resolve-version
-    if: needs.resolve-version.outputs.needs_release == 'true'
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Trigger release workflow
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}
-        run: |
-          set -euo pipefail
-
-          echo "Triggering release workflow for branch ${{ needs.resolve-version.outputs.target_branch }}"
-
-          # Trigger the release-version-bump workflow
-          if ! gh workflow run release-version-bump.yaml \
-            --repo Comfy-Org/ComfyUI_frontend \
-            --ref main \
-            --field version_type=patch \
-            --field branch=${{ needs.resolve-version.outputs.target_branch }}; then
-            echo "Failed to trigger release workflow"
-            exit 1
-          fi
-
-          echo "Release workflow triggered successfully for ${{ needs.resolve-version.outputs.target_branch }}"
-
-      - name: Summary
-        run: |
-          echo "## Release Workflow Triggered" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "- Branch: ${{ needs.resolve-version.outputs.target_branch }}" >> $GITHUB_STEP_SUMMARY
-          echo "- Target version: ${{ needs.resolve-version.outputs.target_version }}" >> $GITHUB_STEP_SUMMARY
-          echo "- [View workflow runs](https://github.com/Comfy-Org/ComfyUI_frontend/actions/workflows/release-version-bump.yaml)" >> $GITHUB_STEP_SUMMARY
-
-  create-comfyui-pr:
-    needs: [check-release-week, resolve-version, trigger-release-if-needed]
-    if: always() && needs.resolve-version.result == 'success' && (needs.check-release-week.outputs.is_release_week == 'true' || github.event_name == 'workflow_dispatch')
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout ComfyUI fork
-        uses: actions/checkout@v6
-        with:
-          repository: ${{ inputs.comfyui_fork || 'Comfy-Org/ComfyUI' }}
-          token: ${{ secrets.PR_GH_TOKEN }}
-          path: comfyui
-
-      - name: Sync with upstream
-        working-directory: comfyui
-        run: |
-          set -euo pipefail
-
-          # Fetch latest upstream to base our branch on fresh code
-          # Note: This only affects the local checkout, NOT the fork's master branch
-          # We only push the automation branch, leaving the fork's master untouched
-          echo "Fetching upstream master..."
-          if ! git fetch https://github.com/Comfy-Org/ComfyUI.git master; then
-            echo "Failed to fetch upstream master"
-            exit 1
-          fi
-
-          echo "Checking out upstream master..."
-          if ! git checkout FETCH_HEAD; then
-            echo "Failed to checkout FETCH_HEAD"
-            exit 1
-          fi
-
-          echo "Successfully synced with upstream master"
-
-      - name: Update requirements.txt
-        working-directory: comfyui
-        run: |
-          set -euo pipefail
-
-          TARGET_VERSION="${{ needs.resolve-version.outputs.target_version }}"
-          echo "Updating comfyui-frontend-package to ${TARGET_VERSION}"
-
-          # Update the comfyui-frontend-package version (POSIX-compatible)
-          sed -i.bak "s/comfyui-frontend-package==[0-9.][0-9.]*/comfyui-frontend-package==${TARGET_VERSION}/" requirements.txt
-          rm requirements.txt.bak
-
-          # Verify the change was made
-          if ! grep -q "comfyui-frontend-package==${TARGET_VERSION}" requirements.txt; then
-            echo "Failed to update requirements.txt"
-            exit 1
-          fi
-
-          echo "Updated requirements.txt:"
-          grep comfyui-frontend-package requirements.txt
-
-      - name: Build PR description
-        id: pr-body
-        run: |
-          BODY=$(cat <<'EOF'
-          Bumps frontend to ${{ needs.resolve-version.outputs.target_version }}
-
-          Test quickly:
-
-          ```bash
-          python main.py --front-end-version Comfy-Org/ComfyUI_frontend@${{ needs.resolve-version.outputs.target_version }}
-          ```
-
-          - Diff: [v${{ needs.resolve-version.outputs.current_version }}...v${{ needs.resolve-version.outputs.target_version }}](${{ needs.resolve-version.outputs.diff_url }})
-          - PyPI: https://pypi.org/project/comfyui-frontend-package/${{ needs.resolve-version.outputs.target_version }}/
-          - npm: https://www.npmjs.com/package/@comfyorg/comfyui-frontend-types/v/${{ needs.resolve-version.outputs.target_version }}
-          EOF
-          )
-
-          # Add release PR note if release was triggered
-          if [ "${{ needs.resolve-version.outputs.needs_release }}" = "true" ]; then
-            RELEASE_NOTE="⚠️ **Release PR must be merged first** - check [release workflow runs](https://github.com/Comfy-Org/ComfyUI_frontend/actions/workflows/release-version-bump.yaml)"
-            BODY=$''"${RELEASE_NOTE}"$'\n\n'"${BODY}"
-          fi
-
-          # Save to file for later use
-          printf '%s\n' "$BODY" > pr-body.txt
-          cat pr-body.txt
-
-      - name: Create PR to ComfyUI
-        working-directory: comfyui
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN }}
-          COMFYUI_FORK: ${{ inputs.comfyui_fork || 'Comfy-Org/ComfyUI' }}
-        run: |
-          set -euo pipefail
-
-          # Extract fork owner from repository name
-          FORK_OWNER=$(echo "$COMFYUI_FORK" | cut -d'/' -f1)
-
-          echo "Creating PR from ${COMFYUI_FORK} to Comfy-Org/ComfyUI"
-
-          # Configure git
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-          # Create/update branch (reuse same branch name each release cycle)
-          BRANCH="automation/comfyui-frontend-bump"
-          git checkout -B "$BRANCH"
-          git add requirements.txt
-
-          if ! git diff --cached --quiet; then
-            git commit -m "Bump comfyui-frontend-package to ${{ needs.resolve-version.outputs.target_version }}"
-          else
-            echo "No changes to commit"
-            exit 0
-          fi
-
-          # Force push to fork (overwrites previous release cycle's branch)
-          # Note: This intentionally destroys branch history to maintain a single PR
-          # Any review comments or manual commits will need to be re-applied
-          if ! git push -f origin "$BRANCH"; then
-            echo "Failed to push branch to fork"
-            exit 1
-          fi
-
-          # Create draft PR from fork to upstream
-          PR_BODY=$(cat ../pr-body.txt)
-
-          # Try to create PR, ignore error if it already exists
-          if ! gh pr create \
-            --repo Comfy-Org/ComfyUI \
-            --head "${FORK_OWNER}:${BRANCH}" \
-            --base master \
-            --title "Bump comfyui-frontend-package to ${{ needs.resolve-version.outputs.target_version }}" \
-            --body "$PR_BODY" \
-            --draft 2>&1; then
-
-            # Check if PR already exists
-            set +e
-            EXISTING_PR=$(gh pr list --repo Comfy-Org/ComfyUI --head "${FORK_OWNER}:${BRANCH}" --json number --jq '.[0].number' 2>&1)
-            PR_LIST_EXIT=$?
-            set -e
-
-            if [ $PR_LIST_EXIT -ne 0 ]; then
-              echo "Failed to check for existing PR: $EXISTING_PR"
-              exit 1
-            fi
-
-            if [ -n "$EXISTING_PR" ] && [ "$EXISTING_PR" != "null" ]; then
-              echo "PR already exists (#${EXISTING_PR}), updating branch will update the PR"
-            else
-              echo "Failed to create PR and no existing PR found"
-              exit 1
-            fi
-          fi
-
-      - name: Summary
-        run: |
-          echo "## ComfyUI PR Created" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "Draft PR created in Comfy-Org/ComfyUI" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "### PR Body:" >> $GITHUB_STEP_SUMMARY
-          cat pr-body.txt >> $GITHUB_STEP_SUMMARY

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

@@ -1,281 +0,0 @@
-name: Release Branch Create
-
-on:
-  pull_request:
-    types: [closed]
-    branches: [main]
-    paths:
-      - 'package.json'
-
-jobs:
-  create-release-branch:
-    runs-on: ubuntu-latest
-    if: >
-      github.event.pull_request.merged == true &&
-      contains(github.event.pull_request.labels.*.name, 'Release')
-    permissions:
-      contents: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.PR_GH_TOKEN || secrets.GITHUB_TOKEN }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Check version bump type
-        id: check_version
-        run: |
-          # Get current version from main
-          CURRENT_VERSION=$(node -p "require('./package.json').version")
-          # Remove 'v' prefix if present (shouldn't be in package.json, but defensive)
-          CURRENT_VERSION=${CURRENT_VERSION#v}
-          echo "current_version=$CURRENT_VERSION" >> $GITHUB_OUTPUT
-
-          # Validate version format
-          if ! [[ "$CURRENT_VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+ ]]; then
-            echo "ERROR: Invalid version format: $CURRENT_VERSION"
-            exit 1
-          fi
-
-          # Extract major and minor versions
-          MAJOR=$(echo $CURRENT_VERSION | cut -d. -f1)
-          MINOR=$(echo $CURRENT_VERSION | cut -d. -f2)
-          PATCH=$(echo $CURRENT_VERSION | cut -d. -f3 | cut -d- -f1)
-
-          echo "major=$MAJOR" >> $GITHUB_OUTPUT
-          echo "minor=$MINOR" >> $GITHUB_OUTPUT
-          echo "patch=$PATCH" >> $GITHUB_OUTPUT
-
-          # Get previous version from the commit before the merge
-          git checkout HEAD^1
-          PREV_VERSION=$(node -p "require('./package.json').version" 2>/dev/null || echo "0.0.0")
-          # Remove 'v' prefix if present
-          PREV_VERSION=${PREV_VERSION#v}
-
-          # Validate previous version format
-          if ! [[ "$PREV_VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+ ]]; then
-            echo "WARNING: Invalid previous version format: $PREV_VERSION, using 0.0.0"
-            PREV_VERSION="0.0.0"
-          fi
-
-          PREV_MINOR=$(echo $PREV_VERSION | cut -d. -f2)
-
-          echo "prev_version=$PREV_VERSION" >> $GITHUB_OUTPUT
-          echo "prev_minor=$PREV_MINOR" >> $GITHUB_OUTPUT
-
-          BASE_COMMIT=$(git rev-parse HEAD)
-          echo "base_commit=$BASE_COMMIT" >> $GITHUB_OUTPUT
-
-          # Get previous major version for comparison
-          PREV_MAJOR=$(echo $PREV_VERSION | cut -d. -f1)
-
-          # Check if current version is a pre-release
-          if [[ "$CURRENT_VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+- ]]; then
-            IS_PRERELEASE=true
-          else
-            IS_PRERELEASE=false
-          fi
-
-          # Check if this was a minor version bump or major version bump
-          # But skip if it's a pre-release version
-          if [[ "$IS_PRERELEASE" == "true" ]]; then
-            echo "is_minor_bump=false" >> $GITHUB_OUTPUT
-            echo "reason=prerelease version" >> $GITHUB_OUTPUT
-          elif [[ "$MAJOR" -gt "$PREV_MAJOR" && "$MINOR" == "0" && "$PATCH" == "0" ]]; then
-            # Major version bump (e.g., 1.99.x → 2.0.0)
-            echo "is_minor_bump=true" >> $GITHUB_OUTPUT
-            BRANCH_BASE="${PREV_MAJOR}.${PREV_MINOR}"
-            echo "branch_base=$BRANCH_BASE" >> $GITHUB_OUTPUT
-          elif [[ "$MAJOR" == "$PREV_MAJOR" && "$MINOR" -gt "$PREV_MINOR" && "$PATCH" == "0" ]]; then
-            # Minor version bump (e.g., 1.23.x → 1.24.0)
-            echo "is_minor_bump=true" >> $GITHUB_OUTPUT
-            BRANCH_BASE="${MAJOR}.${PREV_MINOR}"
-            echo "branch_base=$BRANCH_BASE" >> $GITHUB_OUTPUT
-          else
-            echo "is_minor_bump=false" >> $GITHUB_OUTPUT
-          fi
-
-          # Return to main branch
-          git checkout main
-
-      - name: Create release branches
-        id: create_branches
-        if: steps.check_version.outputs.is_minor_bump == 'true'
-        run: |
-          BRANCH_BASE="${{ steps.check_version.outputs.branch_base }}"
-          PREV_VERSION="${{ steps.check_version.outputs.prev_version }}"
-
-          if [[ -z "$BRANCH_BASE" ]]; then
-            echo "::error::Branch base not set; unable to determine release branches"
-            exit 1
-          fi
-
-          BASE_COMMIT="${{ steps.check_version.outputs.base_commit }}"
-
-          if [[ -z "$BASE_COMMIT" ]]; then
-            echo "::error::Base commit not provided; cannot create release branches"
-            exit 1
-          fi
-
-          RESULTS_FILE=$(mktemp)
-          trap 'rm -f "$RESULTS_FILE"' EXIT
-
-          for PREFIX in core cloud; do
-            BRANCH_NAME="${PREFIX}/${BRANCH_BASE}"
-
-            if git ls-remote --exit-code --heads origin \
-              "$BRANCH_NAME" >/dev/null 2>&1; then
-              echo "⚠️  Branch $BRANCH_NAME already exists"
-              echo "ℹ️  Skipping creation for $BRANCH_NAME"
-              STATUS="exists"
-            else
-              # Create branch from the commit BEFORE the version bump
-              if ! git push origin "$BASE_COMMIT:refs/heads/$BRANCH_NAME"; then
-                echo "::error::Failed to push release branch $BRANCH_NAME"
-                exit 1
-              fi
-              echo "✅ Created release branch: $BRANCH_NAME"
-              STATUS="created"
-            fi
-
-            echo "$BRANCH_NAME|$STATUS|$PREV_VERSION" >> "$RESULTS_FILE"
-          done
-
-          {
-            echo "results<<EOF"
-            cat "$RESULTS_FILE"
-            echo "EOF"
-          } >> "$GITHUB_OUTPUT"
-
-      - name: Ensure release labels
-        if: steps.check_version.outputs.is_minor_bump == 'true'
-        env:
-          GH_TOKEN: ${{ secrets.PR_GH_TOKEN || secrets.GITHUB_TOKEN }}
-        run: |
-          set -euo pipefail
-
-          BRANCH_BASE="${{ steps.check_version.outputs.branch_base }}"
-
-          if [[ -z "$BRANCH_BASE" ]]; then
-            echo "::error::Branch base not set; unable to manage labels"
-            exit 1
-          fi
-
-          declare -A COLORS=(
-            [core]="4361ee"
-            [cloud]="4f6ef5"
-          )
-
-          for PREFIX in core cloud; do
-            LABEL="${PREFIX}/${BRANCH_BASE}"
-            COLOR="${COLORS[$PREFIX]}"
-            DESCRIPTION="Backport PRs for ${PREFIX} ${BRANCH_BASE}"
-
-            if gh label view "$LABEL" >/dev/null 2>&1; then
-              gh label edit "$LABEL" \
-                --color "$COLOR" \
-                --description "$DESCRIPTION"
-              echo "🔄 Updated label $LABEL"
-            else
-              gh label create "$LABEL" \
-                --color "$COLOR" \
-                --description "$DESCRIPTION"
-              echo "✨ Created label $LABEL"
-            fi
-          done
-
-          MIN_LABELS_TO_KEEP=3
-          MAX_LABELS_TO_FETCH=200
-
-          for PREFIX in core cloud; do
-            mapfile -t LABELS < <(
-              gh label list \
-                --json name \
-                --limit "$MAX_LABELS_TO_FETCH" \
-                --jq '.[].name' |
-              grep -E "^${PREFIX}/[0-9]+\.[0-9]+$" |
-              sort -t/ -k2,2V
-            )
-
-            TOTAL=${#LABELS[@]}
-
-            if (( TOTAL <= MIN_LABELS_TO_KEEP )); then
-              echo "ℹ️  Nothing to prune for $PREFIX labels"
-              continue
-            fi
-
-            REMOVE_COUNT=$((TOTAL - MIN_LABELS_TO_KEEP))
-
-            if (( REMOVE_COUNT > 1 )); then
-              REMOVE_COUNT=1
-            fi
-
-            for ((i=0; i<REMOVE_COUNT; i++)); do
-              OLD_LABEL="${LABELS[$i]}"
-              gh label delete "$OLD_LABEL" --yes
-              echo "🗑️ Removed old label $OLD_LABEL"
-            done
-          done
-
-      - name: Post summary
-        if: always() && steps.check_version.outputs.is_minor_bump == 'true'
-        run: |
-          CURRENT_VERSION="${{ steps.check_version.outputs.current_version }}"
-          RESULTS="${{ steps.create_branches.outputs.results }}"
-
-          if [[ -z "$RESULTS" ]]; then
-            cat >> $GITHUB_STEP_SUMMARY << EOF
-          ## 🌿 Release Branch Summary
-
-          Release branch creation skipped; no eligible branches were found.
-          EOF
-            exit 0
-          fi
-
-          cat >> $GITHUB_STEP_SUMMARY << EOF
-          ## 🌿 Release Branch Summary
-
-          - **Main branch**: \`$CURRENT_VERSION\` (active development)
-
-          ### Branch Status
-          EOF
-
-          while IFS='|' read -r BRANCH STATUS PREV_VERSION; do
-            if [[ "$STATUS" == "created" ]]; then
-              cat >> $GITHUB_STEP_SUMMARY << EOF
-
-          - \`$BRANCH\` created from version \`$PREV_VERSION\`
-          EOF
-            else
-              cat >> $GITHUB_STEP_SUMMARY << EOF
-
-          - \`$BRANCH\` already existed (based on version \`$PREV_VERSION\`)
-          EOF
-            fi
-          done <<< "$RESULTS"
-
-          cat >> $GITHUB_STEP_SUMMARY << EOF
-
-          ### Branch Policy
-
-          Release branches are feature-frozen and only accept:
-          - 🐛 Bug fixes
-          - 🔒 Security patches
-          - 📚 Documentation updates
-
-          All new features should continue to be developed against \`main\`.
-
-          ### Backporting Changes
-
-          To backport a fix:
-          1. Create your fix on \`main\` first
-          2. Cherry-pick to the target release branch
-          3. Create a PR targeting that branch
-          4. Apply the matching \`core/x.y\` or \`cloud/x.y\` label
-          EOF

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

@@ -1,164 +0,0 @@
----
-name: Release Draft Create
-
-on:
-  pull_request:
-    types: ['closed']
-    branches: [main, core/*]
-    paths:
-      - 'package.json'
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    if: >
-      github.event.pull_request.merged == true &&
-      contains(github.event.pull_request.labels.*.name, 'Release')
-    outputs:
-      version: ${{ steps.current_version.outputs.version }}
-      is_prerelease: ${{ steps.check_prerelease.outputs.is_prerelease }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-      - uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Get current version
-        id: current_version
-        run: |
-          VERSION=$(node -p "require('./package.json').version")
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-      - name: Check if prerelease
-        id: check_prerelease
-        run: |
-          VERSION=${{ steps.current_version.outputs.version }}
-          if [[ "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+- ]]; then
-            echo "is_prerelease=true" >> $GITHUB_OUTPUT
-          else
-            echo "is_prerelease=false" >> $GITHUB_OUTPUT
-          fi
-      - name: Build project
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          ALGOLIA_APP_ID: ${{ secrets.ALGOLIA_APP_ID }}
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
-          ENABLE_MINIFY: 'true'
-          USE_PROD_CONFIG: 'true'
-          IS_NIGHTLY: ${{  case(github.ref == 'refs/heads/main', 'true', 'false') }}
-        run: |
-          pnpm install --frozen-lockfile
-
-          # Desktop-specific release artifact with desktop distribution flags.
-          DISTRIBUTION=desktop pnpm build
-          pnpm zipdist ./dist ./dist-desktop.zip
-
-          # Default release artifact for core/PyPI.
-          NX_SKIP_NX_CACHE=true pnpm build
-          pnpm zipdist
-      - name: Upload dist artifact
-        uses: actions/upload-artifact@v6
-        with:
-          name: dist-files
-          path: |
-            dist/
-            dist.zip
-            dist-desktop.zip
-
-  draft_release:
-    needs: build
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download dist artifact
-        uses: actions/download-artifact@v7
-        with:
-          name: dist-files
-      - name: Create release
-        id: create_release
-        uses: softprops/action-gh-release@a06a81a03ee405af7f2048a818ed3f03bbf83c7b # v2.5.0
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          files: |
-            dist.zip
-            dist-desktop.zip
-          tag_name: v${{ needs.build.outputs.version }}
-          target_commitish: ${{ github.event.pull_request.base.ref }}
-          make_latest: >-
-            ${{ github.event.pull_request.base.ref == 'main' &&
-                needs.build.outputs.is_prerelease == 'false' }}
-          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
-
-  publish_pypi:
-    needs: build
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-      - name: Download dist artifact
-        uses: actions/download-artifact@v7
-        with:
-          name: dist-files
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: '3.x'
-      - name: Install build dependencies
-        run: python -m pip install build
-      - name: Setup pypi package
-        run: |
-          mkdir -p comfyui_frontend_package/comfyui_frontend_package/static/
-          cp -r dist/* comfyui_frontend_package/comfyui_frontend_package/static/
-      - name: Build pypi package
-        run: python -m build
-        working-directory: comfyui_frontend_package
-        env:
-          COMFYUI_FRONTEND_VERSION: ${{ needs.build.outputs.version }}
-      - name: Publish pypi package
-        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e # v1.13.0
-        with:
-          password: ${{ secrets.PYPI_TOKEN }}
-          packages-dir: comfyui_frontend_package/dist
-
-  publish_types:
-    needs: build
-    uses: ./.github/workflows/release-npm-types.yaml
-    with:
-      version: ${{ needs.build.outputs.version }}
-      ref: ${{ github.event.pull_request.merge_commit_sha }}
-    secrets: inherit
-
-  comment_release_summary:
-    name: Comment Release Summary
-    needs:
-      - draft_release
-      - publish_pypi
-      - publish_types
-    if: success()
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      issues: write
-      pull-requests: write
-    steps:
-      - name: Checkout merge commit
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ github.event.pull_request.merge_commit_sha }}
-          fetch-depth: 2
-
-      - name: Post release summary comment
-        uses: ./.github/actions/comment-release-links
-        with:
-          issue-number: ${{ github.event.pull_request.number }}
-          version_file: package.json

.github/workflows/release-npm-types.yaml

@@ -1,139 +0,0 @@
-name: Release NPM Types
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version to publish (e.g., 1.26.7)'
-        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
-
-concurrency:
-  group: publish-frontend-types-${{ github.workflow }}-${{ inputs.version }}-${{ inputs.dist_tag }}
-  cancel-in-progress: false
-
-jobs:
-  publish_types_manual:
-    name: Publish @comfyorg/comfyui-frontend-types
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - name: Validate inputs
-        shell: bash
-        run: |
-          set -euo pipefail
-          VERSION="${{ inputs.version }}"
-          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
-        shell: bash
-        run: |
-          set -euo pipefail
-          REF="${{ inputs.ref }}"
-          VERSION="${{ inputs.version }}"
-          if [ -n "$REF" ]; then
-            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"
-          else
-            echo "ref=refs/tags/v$VERSION" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ steps.resolve_ref.outputs.ref }}
-          fetch-depth: 1
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - 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
-        env:
-          PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: '1'
-
-      - name: Build types
-        run: pnpm build:types
-
-      - name: Verify version matches input
-        id: verify
-        shell: bash
-        run: |
-          PKG_VERSION=$(node -p "require('./package.json').version")
-          TYPES_PKG_VERSION=$(node -p "require('./dist/package.json').version")
-          if [ "$PKG_VERSION" != "${{ inputs.version }}" ]; then
-            echo "Error: package.json version $PKG_VERSION does not match input ${{ inputs.version }}" >&2
-            exit 1
-          fi
-          if [ "$TYPES_PKG_VERSION" != "${{ inputs.version }}" ]; then
-            echo "Error: dist/package.json version $TYPES_PKG_VERSION does not match input ${{ inputs.version }}" >&2
-            exit 1
-          fi
-          echo "version=${{ inputs.version }}" >> $GITHUB_OUTPUT
-
-      - name: Check if version already on npm
-        id: check_npm
-        shell: bash
-        run: |
-          set -euo pipefail
-          NAME=$(node -p "require('./dist/package.json').name")
-          VER="${{ steps.verify.outputs.version }}"
-          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'
-        run: pnpm publish --access public --tag "${{ inputs.dist_tag }}" --no-git-checks
-        working-directory: dist
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/release-pypi-dev.yaml

@@ -1,79 +0,0 @@
-name: Release PyPI Dev
-
-on:
-  workflow_dispatch:
-    inputs:
-      devVersion:
-        description: 'Dev version'
-        required: true
-        type: number
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    outputs:
-      version: ${{ steps.current_version.outputs.version }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-      - uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
-
-      - name: Get current version
-        id: current_version
-        run: echo "version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
-      - name: Build project
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          ALGOLIA_APP_ID: ${{ secrets.ALGOLIA_APP_ID }}
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
-          ENABLE_MINIFY: 'true'
-          USE_PROD_CONFIG: 'true'
-        run: |
-          pnpm install --frozen-lockfile
-          pnpm build
-          pnpm zipdist
-      - name: Upload dist artifact
-        uses: actions/upload-artifact@v6
-        with:
-          name: dist-files
-          path: |
-            dist/
-            dist.zip
-
-  publish_pypi:
-    needs: build
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-      - name: Download dist artifact
-        uses: actions/download-artifact@v7
-        with:
-          name: dist-files
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: '3.x'
-      - name: Install build dependencies
-        run: python -m pip install build
-      - name: Setup pypi package
-        run: |
-          mkdir -p comfyui_frontend_package/comfyui_frontend_package/static/
-          cp -r dist/* comfyui_frontend_package/comfyui_frontend_package/static/
-      - name: Build pypi package
-        run: python -m build
-        working-directory: comfyui_frontend_package
-        env:
-          COMFYUI_FRONTEND_VERSION: ${{ format('{0}.dev{1}', needs.build.outputs.version, inputs.devVersion) }}
-      - name: Publish pypi package
-        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e # v1.13.0
-        with:
-          password: ${{ secrets.PYPI_TOKEN }}
-          packages-dir: comfyui_frontend_package/dist

.github/workflows/release-version-bump.yaml

@@ -1,195 +0,0 @@
-# Description: Manual workflow to increment package version with semantic versioning support
-name: 'Release: Version Bump'
-
-on:
-  workflow_dispatch:
-    inputs:
-      version_type:
-        description: 'Version increment type'
-        required: true
-        default: 'patch'
-        type: 'choice'
-        options: [patch, minor, major, prepatch, preminor, premajor, prerelease]
-      pre_release:
-        description: Pre-release ID (suffix)
-        required: false
-        default: ''
-        type: string
-      branch:
-        description: 'Base branch to bump (e.g., main, core/1.29, core/1.30)'
-        required: true
-        default: 'main'
-        type: string
-  schedule:
-    # 00:00 UTC ≈ 4:00 PM PST / 5:00 PM PDT on the previous calendar day
-    - cron: '0 0 * * *'
-
-concurrency:
-  group: release-version-bump
-  cancel-in-progress: true
-
-jobs:
-  bump-version:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-      - name: Prepare inputs
-        id: prepared-inputs
-        shell: bash
-        env:
-          RAW_VERSION_TYPE: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.version_type || '' }}
-          RAW_PRE_RELEASE: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.pre_release || '' }}
-          RAW_BRANCH: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.branch || '' }}
-        run: |
-          set -euo pipefail
-          VERSION_TYPE="$RAW_VERSION_TYPE"
-          PRE_RELEASE="$RAW_PRE_RELEASE"
-          TARGET_BRANCH="$RAW_BRANCH"
-
-          if [[ -z "$VERSION_TYPE" ]]; then
-            VERSION_TYPE='patch'
-          fi
-
-          if [[ -z "$TARGET_BRANCH" ]]; then
-            TARGET_BRANCH='main'
-          fi
-
-          {
-            echo "version_type=$VERSION_TYPE"
-            echo "pre_release=$PRE_RELEASE"
-            echo "branch=$TARGET_BRANCH"
-          } >> "$GITHUB_OUTPUT"
-
-      - name: Close stale nightly version bump PRs
-        if: github.event_name == 'schedule'
-        uses: actions/github-script@v8
-        with:
-          github-token: ${{ github.token }}
-          script: |
-            const prefix = 'version-bump-'
-            const closed = []
-            const prs = await github.paginate(github.rest.pulls.list, {
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              state: 'open',
-              per_page: 100
-            })
-
-            for (const pr of prs) {
-              if (!pr.head?.ref?.startsWith(prefix)) {
-                continue
-              }
-
-              if (pr.user?.login !== 'github-actions[bot]') {
-                continue
-              }
-
-              // Only clean up stale nightly PRs targeting main.
-              // Adjust here if other target branches should be cleaned.
-              if (pr.base?.ref !== 'main') {
-                continue
-              }
-
-              await github.rest.pulls.update({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                pull_number: pr.number,
-                state: 'closed'
-              })
-
-              try {
-                await github.rest.git.deleteRef({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  ref: `heads/${pr.head.ref}`
-                })
-              } catch (error) {
-                if (![404, 422].includes(error.status)) {
-                  throw error
-                }
-              }
-
-              closed.push(pr.number)
-            }
-
-            core.info(`Closed ${closed.length} stale PR(s).`)
-
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ steps.prepared-inputs.outputs.branch }}
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Validate branch exists
-        env:
-          TARGET_BRANCH: ${{ steps.prepared-inputs.outputs.branch }}
-        run: |
-          BRANCH="$TARGET_BRANCH"
-          if ! git show-ref --verify --quiet "refs/heads/$BRANCH" && ! git show-ref --verify --quiet "refs/remotes/origin/$BRANCH"; then
-            echo "❌ Branch '$BRANCH' does not exist"
-            echo ""
-            echo "Available core branches:"
-            git branch -r | grep 'origin/core/' | sed 's/.*origin\//  - /' || echo "  (none found)"
-            echo ""
-            echo "Main branch:"
-            echo "  - main"
-            exit 1
-          fi
-          echo "✅ Branch '$BRANCH' exists"
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version-file: '.nvmrc'
-
-      - name: Bump version
-        id: bump-version
-        env:
-          VERSION_TYPE: ${{ steps.prepared-inputs.outputs.version_type }}
-          PRE_RELEASE: ${{ steps.prepared-inputs.outputs.pre_release }}
-        run: |
-          set -euo pipefail
-          if [[ -n "$PRE_RELEASE" && ! "$VERSION_TYPE" =~ ^pre(major|minor|patch)$ && "$VERSION_TYPE" != "prerelease" ]]; then
-            echo "❌ pre_release was provided but version_type='$VERSION_TYPE' does not support --preid"
-            exit 1
-          fi
-          if [[ -n "$PRE_RELEASE" ]]; then
-            pnpm version "$VERSION_TYPE" --preid "$PRE_RELEASE" --no-git-tag-version
-          else
-            pnpm version "$VERSION_TYPE" --no-git-tag-version
-          fi
-
-          NEW_VERSION=$(node -p "require('./package.json').version")
-          echo "NEW_VERSION=$NEW_VERSION" >> "$GITHUB_OUTPUT"
-
-      - name: Format PR string
-        id: capitalised
-        env:
-          VERSION_TYPE: ${{ steps.prepared-inputs.outputs.version_type }}
-        run: |
-          CAPITALISED_TYPE="$VERSION_TYPE"
-          echo "capitalised=${CAPITALISED_TYPE@u}" >> "$GITHUB_OUTPUT"
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
-        with:
-          token: ${{ secrets.PR_GH_TOKEN }}
-          commit-message: '[release] Increment version to ${{ steps.bump-version.outputs.NEW_VERSION }}'
-          title: ${{ steps.bump-version.outputs.NEW_VERSION }}
-          body: |
-            ${{ steps.capitalised.outputs.capitalised }} version increment to ${{ steps.bump-version.outputs.NEW_VERSION }}
-
-            **Base branch:** `${{ steps.prepared-inputs.outputs.branch }}`
-          branch: version-bump-${{ steps.bump-version.outputs.NEW_VERSION }}
-          base: ${{ steps.prepared-inputs.outputs.branch }}
-          labels: |
-            Release

.github/workflows/release.yaml

@@ -0,0 +1,116 @@
+name: Create Release Draft
+
+on:
+  pull_request:
+    types: [ closed ]
+    branches: [ main, core/* ]
+    paths:
+      - 'package.json'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: >
+      github.event.pull_request.merged == true &&
+      contains(github.event.pull_request.labels.*.name, 'Release')
+    outputs:
+      version: ${{ steps.current_version.outputs.version }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 'lts/*'
+      - name: Get current version
+        id: current_version
+        run: echo "version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
+      - name: Build project
+        env:
+          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
+          ALGOLIA_APP_ID: ${{ secrets.ALGOLIA_APP_ID }}
+          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
+        run: |
+          npm ci
+          npm run fetch-templates
+          npm run build
+          npm run zipdist
+      - name: Upload dist artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist-files
+          path: |
+            dist/
+            dist.zip
+
+  draft_release:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Download dist artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: dist-files
+      - name: Create release
+        id: create_release
+        uses: softprops/action-gh-release@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          files: |
+            dist.zip
+          tag_name: v${{ needs.build.outputs.version }}
+          target_commitish: ${{ github.event.pull_request.base.ref }}
+          make_latest: ${{ github.event.pull_request.base.ref == 'main' }}
+          draft: ${{ github.event.pull_request.base.ref != 'main' }}
+          prerelease: false
+          generate_release_notes: true
+
+  publish_pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Download dist artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: dist-files
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.x'
+      - name: Install build dependencies
+        run: python -m pip install build
+      - name: Setup pypi package
+        run: |
+          mkdir -p comfyui_frontend_package/comfyui_frontend_package/static/
+          cp -r dist/* comfyui_frontend_package/comfyui_frontend_package/static/
+      - name: Build pypi package
+        run: python -m build
+        working-directory: comfyui_frontend_package
+        env:
+          COMFYUI_FRONTEND_VERSION: ${{ needs.build.outputs.version }}
+      - name: Publish pypi package
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_TOKEN }}
+          packages-dir: comfyui_frontend_package/dist
+
+  publish_types:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 'lts/*'
+          registry-url: https://registry.npmjs.org
+      - run: npm ci
+      - run: npm run build:types
+      - name: Publish package
+        run: npm publish --access public
+        working-directory: dist
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/test-browser-exp.yaml

@@ -0,0 +1,42 @@
+# Setting test expectation screenshots for Playwright
+name: Update Playwright Expectations
+
+on:
+  pull_request:
+    types: [ labeled ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'New Browser Test Expectations'
+    steps:
+    - uses: Comfy-Org/ComfyUI_frontend_setup_action@v2.3
+    - name: Install Playwright Browsers
+      run: npx playwright install chromium --with-deps
+      working-directory: ComfyUI_frontend
+    - name: Run Playwright tests and update snapshots
+      id: playwright-tests
+      run: npx playwright test --update-snapshots
+      continue-on-error: true
+      working-directory: ComfyUI_frontend
+    - uses: actions/upload-artifact@v4
+      if: always()
+      with:
+        name: playwright-report
+        path: ComfyUI_frontend/playwright-report/
+        retention-days: 30
+    - name: Debugging info
+      run: |
+        echo "Branch: ${{ github.head_ref }}"
+        git status
+      working-directory: ComfyUI_frontend
+    - name: Commit updated expectations
+      run: |
+        git config --global user.name 'github-actions'
+        git config --global user.email 'github-actions@github.com'
+        git fetch origin ${{ github.head_ref }}
+        git checkout -B ${{ github.head_ref }} origin/${{ github.head_ref }}
+        git add browser_tests
+        git commit -m "Update test expectations [skip ci]"
+        git push origin HEAD:${{ github.head_ref }}
+      working-directory: ComfyUI_frontend

.github/workflows/test-ui.yaml

@@ -0,0 +1,105 @@
+name: Tests CI
+
+on:
+  push:
+    branches: [main, master, core/*, desktop/*]
+  pull_request:
+    branches: [main, master, dev*, core/*, desktop/*]
+
+jobs:
+  setup:
+    runs-on: ubuntu-latest
+    outputs:
+      cache-key: ${{ steps.cache-key.outputs.key }}
+    steps:
+      - name: Checkout ComfyUI
+        uses: actions/checkout@v4
+        with:
+          repository: 'comfyanonymous/ComfyUI'
+          path: 'ComfyUI'
+          ref: master
+
+      - name: Checkout ComfyUI_frontend
+        uses: actions/checkout@v4
+        with:
+          repository: 'Comfy-Org/ComfyUI_frontend'
+          path: 'ComfyUI_frontend'
+
+      - name: Checkout ComfyUI_devtools
+        uses: actions/checkout@v4
+        with:
+          repository: 'Comfy-Org/ComfyUI_devtools'
+          path: 'ComfyUI/custom_nodes/ComfyUI_devtools'
+          ref: '49c8220be49120dbaff85f32813d854d6dff2d05'
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: lts/*
+
+      - name: Build ComfyUI_frontend
+        run: |
+          npm ci
+          npm run fetch-templates
+          npm run build
+        working-directory: ComfyUI_frontend
+
+      - name: Generate cache key
+        id: cache-key
+        run: echo "key=$(date +%s)" >> $GITHUB_OUTPUT
+
+      - name: Cache setup
+        uses: actions/cache@v3
+        with:
+          path: |
+            ComfyUI
+            ComfyUI_frontend
+          key: comfyui-setup-${{ steps.cache-key.outputs.key }}
+
+  playwright-tests:
+    needs: setup
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        browser: [chromium, chromium-2x, mobile-chrome]
+    steps:
+      - name: Restore cached setup
+        uses: actions/cache@v3
+        with:
+          path: |
+            ComfyUI
+            ComfyUI_frontend
+          key: comfyui-setup-${{ needs.setup.outputs.cache-key }}
+
+      - uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'
+
+      - name: Install requirements
+        run: |
+          python -m pip install --upgrade pip
+          pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu
+          pip install -r requirements.txt
+          pip install wait-for-it
+        working-directory: ComfyUI
+
+      - name: Start ComfyUI server
+        run: |
+          python main.py --cpu --multi-user --front-end-root ../ComfyUI_frontend/dist &
+          wait-for-it --service 127.0.0.1:8188 -t 600
+        working-directory: ComfyUI
+
+      - name: Install Playwright Browsers
+        run: npx playwright install chromium --with-deps
+        working-directory: ComfyUI_frontend
+
+      - name: Run Playwright tests (${{ matrix.browser }})
+        run: npx playwright test --project=${{ matrix.browser }}
+        working-directory: ComfyUI_frontend
+
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: playwright-report-${{ matrix.browser }}
+          path: ComfyUI_frontend/playwright-report/
+          retention-days: 30

.github/workflows/update-electron-types.yaml

@@ -1,5 +1,4 @@
-# Description: When upstream electron API is updated, click dispatch to update the TypeScript type definitions in this repo
-name: 'Api: Update Electron API Types'
+name: Update Electron Types
 
 on:
   workflow_dispatch:
@@ -13,32 +12,27 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
-        with:
-          version: 10
+        uses: actions/checkout@v4
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version-file: '.nvmrc'
-          cache: 'pnpm'
+          node-version: lts/*
+          cache: 'npm'
 
       - name: Update electron types
-        run: pnpm install --workspace-root @comfyorg/comfyui-electron-types@latest
+        run: npm install @comfyorg/comfyui-electron-types@latest
 
       - name: Get new version
         id: get-version
         run: |
-          NEW_VERSION=$(pnpm list @comfyorg/comfyui-electron-types --json --depth=0 | jq -r '.[0].dependencies."@comfyorg/comfyui-electron-types".version')
+          NEW_VERSION=$(node -e "console.log(JSON.parse(require('fs').readFileSync('./package-lock.json')).packages['node_modules/@comfyorg/comfyui-electron-types'].version)")
           echo "NEW_VERSION=$NEW_VERSION" >> $GITHUB_OUTPUT
 
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
+        uses: peter-evans/create-pull-request@v7
         with:
-          token: ${{ secrets.PR_GH_TOKEN }}
+          token: ${{ secrets.GITHUB_TOKEN }}
           commit-message: '[chore] Update electron-types to ${{ steps.get-version.outputs.NEW_VERSION }}'
           title: '[chore] Update electron-types to ${{ steps.get-version.outputs.NEW_VERSION }}'
           body: |