Mirror from https://github.com/sammykumar/ComfyUI-SwissArmyKnife

.dockerignore

@@ -0,0 +1,14 @@
+.git
+.github
+.vscode
+.env
+*.md
+ui-react_backup
+web/node_modules
+docs
+*.pyc
+__pycache__
+.pytest_cache
+.coverage
+.mypy_cache
+.ruff_cache

.editorconfig

@@ -0,0 +1,21 @@
+# http://editorconfig.org
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+insert_final_newline = true
+charset = utf-8
+end_of_line = lf
+
+[*.bat]
+indent_style = tab
+end_of_line = crlf
+
+[LICENSE]
+insert_final_newline = false
+
+[Makefile]
+indent_style = tab

.env.example

@@ -0,0 +1,15 @@
+# ComfyUI-SwissArmyKnife Environment Variables
+# Copy this file to .env and fill in your actual API keys
+
+# Debug Mode (optional)
+# Set to "true" to enable verbose debug logging in both Python and JavaScript
+# Default: false
+DEBUG=false
+
+# Google Gemini API Key
+# Get your API key from: https://aistudio.google.com/app/apikey
+GEMINI_API_KEY=YOUR_GEMINI_API_KEY_HERE
+
+# Optional: ComfyUI Registry Access Token (for publishing)
+# Only needed if you plan to publish to ComfyUI Registry
+REGISTRY_ACCESS_TOKEN=YOUR_REGISTRY_TOKEN_HERE

.github/workflows/ci.yml

@@ -0,0 +1,50 @@
+name: Code Quality Checks
+
+on:
+  push:
+    branches: [master, develop]
+  pull_request:
+    branches: [master, develop]
+
+jobs:
+  quality-checks:
+    name: Python Code Quality
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python 3.11
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install system dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y ffmpeg
+
+      - name: Install Python dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e .
+          pip install ruff pytest
+
+      - name: Lint with ruff
+        run: ruff check .
+
+      - name: Test Python imports and node loading
+        run: |
+          python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('✓ Custom nodes loaded successfully:', list(NODE_CLASS_MAPPINGS.keys()))"
+
+      - name: Check pyproject.toml validity
+        run: |
+          python -c "
+          import tomllib
+          with open('pyproject.toml', 'rb') as f:
+              config = tomllib.load(f)
+              assert 'project' in config, 'Missing project section'
+              assert 'name' in config['project'], 'Missing project name'
+              assert 'version' in config['project'], 'Missing project version'
+              print('✓ pyproject.toml is valid')
+          "

.github/workflows/publish-to-registry.yml

@@ -0,0 +1,53 @@
+name: Publish to ComfyUI Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master
+    paths:
+      - "pyproject.toml"
+
+jobs:
+  publish-node:
+    name: Publish Custom Node to ComfyUI Registry
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # Fetch full history for tagging
+
+      - name: Extract version from pyproject.toml
+        id: get_version
+        run: |
+          VERSION=$(grep '^version = ' pyproject.toml | sed 's/version = "\(.*\)"/\1/')
+          echo "VERSION=$VERSION" >> $GITHUB_OUTPUT
+          echo "Extracted version: $VERSION"
+
+      - name: Check if tag already exists
+        id: check_tag
+        run: |
+          if git tag | grep -q "^v${{ steps.get_version.outputs.VERSION }}$"; then
+            echo "Tag v${{ steps.get_version.outputs.VERSION }} already exists"
+            echo "TAG_EXISTS=true" >> $GITHUB_OUTPUT
+          else
+            echo "Tag v${{ steps.get_version.outputs.VERSION }} does not exist"
+            echo "TAG_EXISTS=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Publish Custom Node to Registry
+        uses: Comfy-Org/publish-node-action@main
+        with:
+          personal_access_token: ${{ secrets.REGISTRY_ACCESS_TOKEN }}
+
+      - name: Create and push tag
+        if: steps.check_tag.outputs.TAG_EXISTS == 'false'
+        run: |
+          git config user.name "GitHub Actions"
+          git config user.email "actions@github.com"
+          git tag -a "v${{ steps.get_version.outputs.VERSION }}" -m "Release version ${{ steps.get_version.outputs.VERSION }}"
+          git push origin "v${{ steps.get_version.outputs.VERSION }}"
+          echo "Created and pushed tag: v${{ steps.get_version.outputs.VERSION }}"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,159 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# OSX useful to ignore
+*.DS_Store
+.AppleDouble
+.LSOverride
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+env/
+venv/
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+
+# Sphinx documentation
+docs/_build/
+
+# IntelliJ Idea
+.idea
+*.iml
+*.ipr
+*.iws
+
+# PyBuilder
+target/
+
+# Cookiecutter
+output/
+python_boilerplate/
+cookiecutter-pypackage-env/
+
+# vscode settings
+.history/
+*.code-workspace
+
+# Frontend extension
+node_modules/
+node_modules
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+node.zip
+.vscode/
+.claude/
+
+# Dev container and development files
+.devcontainer/.env
+temp/
+input/
+output/
+models/
+.ruff_cache/
+
+# Gemini description cache
+cache/
+
+# OS and editor files
+.DS_Store
+Thumbs.db
+*.swp
+*.swo
+*~
+
+# Environment variables and API keys - SECURITY
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# API keys and secrets - SECURITY
+*.key
+*.pem
+secrets.json
+config.json
+api_keys.txt
+*_secrets.*
+
+# Cache directories
+cache/
+.cache/
+
+# Cache busting files
+cache_info.json
+
+# ComfyUI Local
+.comfyui/
+.comfyui-user/

.pre-commit-config.yaml

@@ -0,0 +1,10 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    # Ruff version.
+    rev: v0.4.9
+    hooks:
+      # Run the linter.
+      - id: ruff
+        args: [ --fix ]
+      # Run the formatter.
+      - id: ruff-format

AGENTS.md

@@ -0,0 +1,878 @@
+# ComfyUI-SwissArmyKnife - ComfyUI Extension Development Guide
+
+**ALWAYS reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.**
+
+## Official ComfyUI Documentation
+
+For technical implementation details, reference these official ComfyUI custom node development guides:
+
+- **Backend (Python) Development**: https://docs.comfy.org/custom-nodes/backend/server_overview
+- **Web Extension (JavaScript) Development**: https://docs.comfy.org/custom-nodes/js/javascript_overview
+- **Lite Graph (ComfyUi is built on top of Lite Graph)**:https://github.com/jagenjo/litegraph.js/tree/master
+
+_Note: These are the official JavaScript widget docs, not React-based extensions._
+
+## Project Overview
+
+ComfyUI-SwissArmyKnife is a ComfyUI extension that consists of two essential components that work together:
+
+### Backend (Python Custom Nodes)
+
+- Python custom nodes in `nodes/*.py` for Gemini AI video analysis and processing
+- Core business logic and AI integration
+- Requires ComfyUI server restart when modified
+
+### Web Extension (JavaScript Widgets)
+
+- Plain JavaScript widgets in `./web/js/` for enhanced ComfyUI interaction
+- UI components and client-side functionality
+- Requires browser cache refresh when modified
+
+### Additional Components
+
+- ~~React/TypeScript UI extension with internationalization~~ **DISABLED FOR NOW**
+- GitHub Actions for automated building and publishing
+- Playwright tests in `./web/tests/` for testing against hosted ComfyUI server
+- Documentation in `docs/` directory - organized into categorized folders (see Documentation Organization section)
+
+**IMPORTANT**: Both backend and web extension components are required for the custom node to function properly. Changes to backend Python files require restarting the ComfyUI server, while changes to web JavaScript files require refreshing the browser cache.
+
+**DOCUMENTATION REQUIREMENT**: All documentation, guides, troubleshooting notes, implementation details, and technical specifications must be added to the appropriate folder in the `docs/` directory. The documentation is organized by category - see the "Documentation Organization" section below for the proper folder structure. Never document directly in code comments when a separate documentation file would be more appropriate. Always attempt to update documentation for existing markdown files before creating new ones.
+
+**Note: The React UI component (`ui-react_backup/`) is currently disabled and not in active development.**
+
+## Documentation Organization
+
+**All project documentation is organized in a hierarchical folder structure:**
+
+```
+docs/
+├── README.md                    # Main documentation index and navigation
+├── IMPLEMENTATION_STATUS.md     # Overall project status
+├── DOCUMENTATION_REORGANIZATION.md # Documentation structure guide
+│
+├── nodes/                       # Node-specific documentation
+│   ├── video-preview/          # Video Preview node (6 files + README)
+│   ├── video-metadata/         # Video Metadata node (4 files + README)
+│   ├── media-describe/         # Gemini AI Media Description (6 files + README)
+│   ├── lora-loader/            # LoRA Loader node (14 files + README)
+│   └── reddit-media/           # Reddit Media Extraction (6 files + README)
+│
+├── infrastructure/              # Infrastructure & system components
+│   ├── caching/                # Caching system (6 files + README)
+│   ├── debug/                  # Debug & logging (2 files + README)
+│   ├── docker/                 # Docker setup (2 files + README)
+│   └── build-deploy/           # Build & deployment (3 files + README)
+│
+├── integrations/                # External service integrations
+│   └── civitai/                # CivitAI API integration (3 files + README)
+│
+├── ui-widgets/                  # UI widget documentation (10 files + README)
+├── features/                    # Feature implementations (13 files + README)
+└── examples/                    # Example workflows (3 files + README)
+```
+
+### Documentation Rules
+
+1. **Node-specific docs** → `docs/nodes/[node-name]/`
+2. **Infrastructure docs** → `docs/infrastructure/[category]/`
+3. **Integration docs** → `docs/integrations/[service]/`
+4. **Widget docs** → `docs/ui-widgets/`
+5. **Feature docs** → `docs/features/`
+6. **Examples** → `docs/examples/`
+
+### Finding Documentation
+
+- **Start here**: `docs/README.md` - Main index with links to all categories
+- **Category indexes**: Each folder has a `README.md` listing all files
+- **By node**: `docs/nodes/[node-name]/README.md`
+- **By topic**: Browse appropriate category folder
+
+## Working Effectively
+
+### Virtual Environment Activation
+
+**CRITICAL**: Always activate the virtual environment before running any Python commands:
+
+```bash
+# Activate virtual environment (REQUIRED for all Python operations)
+source /Users/samkumar/Development/dev-lab-hq/ai-image-hub/apps/comfyui-swiss-army-knife/.venv/bin/activate
+
+# Or use relative path if in project root:
+source .venv/bin/activate
+
+# Verify activation (you should see (.venv) in your prompt)
+which python3  # Should show path inside .venv directory
+```
+
+**IMPORTANT**: Run the activation command before:
+
+- Installing Python packages (`pip3 install`)
+- Running Python scripts or commands
+- Running tests (`pytest`)
+- Linting Python code (`ruff check`)
+- Any other Python-related terminal operations
+
+### Essential System Dependencies
+
+Install these system dependencies first:
+
+```bash
+# FFmpeg is REQUIRED for video processing functionality
+sudo apt-get update && sudo apt-get install -y ffmpeg
+
+# Verify installation
+ffmpeg -version  # Should show version 6.1.1 or newer
+```
+
+### Bootstrap React UI Development _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# Navigate to React UI directory
+# cd ui-react_backup/ui
+
+# Install Node.js dependencies - takes ~40 seconds
+# npm install  # NEVER CANCEL: Takes 40 seconds. Set timeout to 60+ seconds.
+
+# Build React extension - takes ~5 seconds
+# npm run build  # NEVER CANCEL: Takes 5 seconds. Set timeout to 30+ seconds.
+```
+
+### Bootstrap Python Development
+
+```bash
+# ALWAYS activate virtual environment first
+source .venv/bin/activate
+
+# Install Python package and dependencies
+pip3 install -e .  # Takes ~12 seconds for basic dependencies
+
+# Install essential Python dependencies for full functionality
+# NEVER CANCEL: Takes 2-3 minutes for torch/opencv. Set timeout to 300+ seconds.
+pip3 install torch opencv-python
+
+# Install development tools
+pip3 install pytest mypy coverage ruff pre-commit
+
+# Verify Python modules work
+python3 -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('Available nodes:', list(NODE_CLASS_MAPPINGS.keys()))"
+# Should output: Available nodes: ['GeminiUtilVideoDescribe']
+```
+
+## Development Workflows
+
+### Documentation Workflow
+
+**Documentation is now organized by category. Always place documentation in the appropriate folder:**
+
+```bash
+# Documentation structure
+docs/
+├── README.md                    # Main documentation index
+├── IMPLEMENTATION_STATUS.md     # Overall project status
+├── nodes/                       # Node-specific documentation
+│   ├── video-preview/          # Video Preview node docs
+│   ├── video-metadata/         # Video Metadata node docs
+│   ├── media-describe/         # Gemini AI Media Description docs
+│   ├── lora-loader/            # LoRA Loader node docs
+│   └── reddit-media/           # Reddit Media Extraction docs
+├── infrastructure/              # Infrastructure components
+│   ├── caching/                # Caching system docs
+│   ├── debug/                  # Debug & logging docs
+│   ├── docker/                 # Docker setup docs
+│   └── build-deploy/           # Build & deployment docs
+├── integrations/                # External service integrations
+│   └── civitai/                # CivitAI API integration docs
+├── ui-widgets/                  # UI widget documentation
+├── features/                    # Feature implementations
+└── examples/                    # Example workflows
+```
+
+**Adding New Documentation:**
+
+```bash
+# For node-specific documentation
+touch docs/nodes/[node-name]/NEW_FEATURE.md
+
+# For infrastructure documentation
+touch docs/infrastructure/[category]/NEW_SYSTEM.md
+
+# For UI widgets
+touch docs/ui-widgets/NEW_WIDGET_IMPLEMENTATION.md
+
+# For features
+touch docs/features/NEW_FEATURE_GUIDE.md
+
+# For integrations
+touch docs/integrations/[service]/NEW_INTEGRATION.md
+```
+
+**Documentation file naming convention:**
+
+- Use ALL_CAPS with underscores
+- Be descriptive: `SEED_WIDGET_IMPLEMENTATION.md`
+- Include purpose: `TROUBLESHOOTING_`, `GUIDE_`, `IMPLEMENTATION_`, `_FIX`
+- Node docs go in `docs/nodes/[node-name]/`
+- Infrastructure docs go in `docs/infrastructure/[category]/`
+
+**CRITICAL**: Whenever you implement a new feature, fix a bug, or solve a technical problem:
+
+1. Identify the correct documentation folder:
+    - Node changes → `docs/nodes/[node-name]/`
+    - System changes → `docs/infrastructure/[category]/`
+    - Widget changes → `docs/ui-widgets/`
+    - Feature additions → `docs/features/`
+    - Integration work → `docs/integrations/[service]/`
+2. Create documentation file with descriptive name
+3. Include implementation details, gotchas, and future considerations
+4. Update the folder's `README.md` index if needed
+5. Reference the documentation file in commit messages
+6. Cross-reference related documentation in other folders
+
+### React UI Development _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# cd ui-react_backup/ui
+
+# Development with auto-reload (watches for changes)
+# npm run watch
+
+# Build for production
+# npm run build  # NEVER CANCEL: Takes 5 seconds. Set timeout to 30+ seconds.
+
+# TypeScript type checking
+# npm run typecheck
+```
+
+### Backend (Python) Development
+
+```bash
+# ALWAYS activate virtual environment first
+source .venv/bin/activate
+
+# Import and test Python nodes
+python3 -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print(list(NODE_CLASS_MAPPINGS.keys()))"
+
+# Run Python linting (fast, < 1 second)
+ruff check .
+
+# Fix auto-fixable linting issues
+ruff check --fix .
+```
+
+### Web Extension (JavaScript) Development
+
+```bash
+# JavaScript widgets are located in ./web/js/
+# No build step required - plain JavaScript files
+
+# Verify web extension files exist
+ls -la web/js/gemini_widgets.js
+ls -la web/css/gemini_widgets.css
+
+# After making changes to JavaScript widgets:
+# 1. No compilation needed (plain JS)
+# 2. Browser cache refresh required for changes to take effect
+```
+
+## Testing
+
+### Backend (Python) Testing
+
+```bash
+# ALWAYS activate virtual environment first
+source .venv/bin/activate
+
+# Run pytest (currently no tests exist)
+pytest  # NEVER CANCEL: Takes < 30 seconds. Set timeout to 60+ seconds.
+# Expected: "no tests ran" - this is normal, no tests exist yet
+
+# When adding tests, create them in a tests/ directory
+```
+
+### Web Extension Testing
+
+```bash
+# Playwright tests for testing against hosted ComfyUI server
+cd web/tests/
+
+# Install Playwright dependencies (if not already installed)
+npm install
+
+# Run Playwright tests against hosted ComfyUI server
+npm test
+
+# Note: Tests require a running ComfyUI server with the custom node installed
+```
+
+### React UI Testing _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# cd ui-react_backup/ui
+
+# This command WILL FAIL with ES module errors
+# npm test
+# Error: "Jest encountered an unexpected token" - this is a known issue
+
+# To add working tests, fix jest.config.js ES module configuration first
+```
+
+## Linting and Code Quality
+
+### Python Linting (Works)
+
+```bash
+# ALWAYS activate virtual environment first
+source .venv/bin/activate
+
+# Fast linting check (< 1 second)
+ruff check .
+
+# Fix automatically fixable issues
+ruff check --fix .
+
+# Note: Some unused import warnings are expected and can be ignored
+# The code functions correctly despite these warnings
+```
+
+### React UI Linting _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# cd ui-react_backup/ui
+
+# This will show configuration errors but runs
+# npm run lint  # Shows ESLint TypeScript project configuration issues
+
+# Auto-fix formatting issues
+# npm run lint:fix
+
+# Format code
+# npm run format
+```
+
+## Build and Publish Workflow
+
+### Local Build Process _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# Complete build from scratch
+# cd ui-react_backup/ui
+# npm install  # 40 seconds
+# npm run build  # 5 seconds
+
+# Verify built files exist
+# ls -la ../dist/example_ext/  # Should show main.js, main.css, etc.
+```
+
+### GitHub Actions Publishing
+
+The repository includes automated publishing via `.github/workflows/react-build.yml`:
+
+- Triggers on `pyproject.toml` changes pushed to main branch
+- Requires `REGISTRY_ACCESS_TOKEN` secret in repository settings
+- Automatically builds React UI and publishes to ComfyUI Registry
+
+## pyproject.toml Specifications
+
+Reference: https://docs.comfy.org/registry/specifications
+
+The `pyproject.toml` file contains two main sections for ComfyUI custom nodes: `[project]` and `[tool.comfy]`.
+
+### [project] Section
+
+#### name (required)
+
+The node id uniquely identifies the custom node and will be used in URLs from the registry. Users can install the node by referencing this name:
+
+```bash
+comfy node install <node-id>
+```
+
+**Requirements:**
+
+- Must be less than 100 characters
+- Can only contain alphanumeric characters, hyphens, underscores, and periods
+- Cannot have consecutive special characters
+- Cannot start with a number or special character
+- Case-insensitive comparison
+
+**Best Practices:**
+
+- Use a short, descriptive name
+- Don't include "ComfyUI" in the name
+- Make it memorable and easy to type
+
+**Examples:**
+
+```toml
+name = "image-processor"      # ✅ Good: Simple and clear
+name = "super-resolution"     # ✅ Good: Describes functionality
+name = "ComfyUI-enhancer"    # ❌ Bad: Includes ComfyUI
+name = "123-tool"            # ❌ Bad: Starts with number
+```
+
+#### version (required)
+
+Uses [semantic versioning](https://semver.org/) with a three-digit version number X.Y.Z:
+
+- X (MAJOR): Breaking changes
+- Y (MINOR): New features (backwards compatible)
+- Z (PATCH): Bug fixes
+
+**Examples:**
+
+```toml
+version = "1.0.0"    # Initial release
+version = "1.1.0"    # Added new features
+version = "1.1.1"    # Bug fix
+version = "2.0.0"    # Breaking changes
+```
+
+#### license (optional)
+
+Specifies the license for your custom node. Can be specified in two ways:
+
+1. **File Reference:**
+
+```toml
+license = { file = "LICENSE" }     # ✅ Points to LICENSE file
+license = { file = "LICENSE.txt" } # ✅ Points to LICENSE.txt
+license = "LICENSE"                # ❌ Incorrect format
+```
+
+2. **License Name:**
+
+```toml
+license = { text = "MIT License" }  # ✅ Correct format
+license = { text = "Apache-2.0" }   # ✅ Correct format
+license = "MIT LICENSE"             # ❌ Incorrect format
+```
+
+Common licenses: [MIT](https://opensource.org/license/mit), [GPL](https://www.gnu.org/licenses/gpl-3.0.en.html), [Apache](https://www.apache.org/licenses/LICENSE-2.0)
+
+#### description (recommended)
+
+A brief description of what your custom node does.
+
+```toml
+description = "A super resolution node for enhancing image quality"
+```
+
+#### repository (required)
+
+Links to the repository:
+
+```toml
+[project.urls]
+Repository = "https://github.com/username/repository"
+```
+
+#### urls (recommended)
+
+Links to related resources:
+
+```toml
+[project.urls]
+Documentation = "https://github.com/username/repository/wiki"
+"Bug Tracker" = "https://github.com/username/repository/issues"
+```
+
+#### requires-python (recommended)
+
+Specifies the Python versions that your node supports:
+
+```toml
+requires-python = ">=3.8"        # Python 3.8 or higher
+requires-python = ">=3.8,<3.11"  # Python 3.8 up to (but not including) 3.11
+```
+
+#### Frontend Version Compatibility (optional)
+
+If your node has specific requirements for which ComfyUI frontend versions it supports, you can specify this using the `comfyui-frontend-package` dependency. This package is published on [PyPI](https://pypi.org/project/comfyui-frontend-package/).
+
+Use this field when:
+
+- Your custom node uses frontend APIs that were introduced in a specific version
+- You've identified incompatibilities between your node and certain frontend versions
+- Your node requires specific UI features only available in newer frontend versions
+
+```toml
+[project]
+dependencies = [
+    "comfyui-frontend-package>=1.20.0"       # Requires frontend 1.20.0 or newer
+    "comfyui-frontend-package<=1.21.6"       # Restricts to frontend versions up to 1.21.6
+    "comfyui-frontend-package>=1.19,<1.22"   # Works with frontend 1.19 to 1.21.x
+    "comfyui-frontend-package~=1.20.0"       # Compatible with 1.20.x but not 1.21.0
+    "comfyui-frontend-package!=1.21.3"       # Works with any version except 1.21.3
+]
+```
+
+#### classifiers (recommended)
+
+Use classifiers to specify operating system compatibility and GPU accelerators. This information is used to help users find the right node for their system.
+
+```toml
+[project]
+classifiers = [
+    # For OS-independent nodes (works on all operating systems)
+    "Operating System :: OS Independent",
+
+    # OR for OS-specific nodes, specify the supported systems:
+    "Operating System :: Microsoft :: Windows",  # Windows specific
+    "Operating System :: POSIX :: Linux",        # Linux specific
+    "Operating System :: MacOS",                 # macOS specific
+
+    # GPU Accelerator support
+    "Environment :: GPU :: NVIDIA CUDA",    # NVIDIA CUDA support
+    "Environment :: GPU :: AMD ROCm",       # AMD ROCm support
+    "Environment :: GPU :: Intel Arc",      # Intel Arc support
+    "Environment :: NPU :: Huawei Ascend",  # Huawei Ascend support
+    "Environment :: GPU :: Apple Metal",    # Apple Metal support
+]
+```
+
+### [tool.comfy] Section
+
+#### PublisherId (required)
+
+Your unique publisher identifier, typically matching your GitHub username.
+
+**Examples:**
+
+```toml
+PublisherId = "john-doe"        # ✅ Matches GitHub username
+PublisherId = "image-wizard"    # ✅ Unique identifier
+```
+
+#### DisplayName (optional)
+
+A user-friendly name for your custom node.
+
+```toml
+DisplayName = "Super Resolution Node"
+```
+
+#### Icon (optional)
+
+URL to your custom node's icon that will be displayed on the ComfyUI Registry and ComfyUI-Manager.
+
+**Requirements:**
+
+- File types: SVG, PNG, JPG, or GIF
+- Maximum resolution: 400px × 400px
+- Aspect ratio should be square
+
+```toml
+Icon = "https://raw.githubusercontent.com/username/repo/main/icon.png"
+```
+
+#### Banner (optional)
+
+URL to a larger banner image that will be displayed on the ComfyUI Registry and ComfyUI-Manager.
+
+**Requirements:**
+
+- File types: SVG, PNG, JPG, or GIF
+- Aspect ratio: 21:9
+
+```toml
+Banner = "https://raw.githubusercontent.com/username/repo/main/banner.png"
+```
+
+#### requires-comfyui (optional)
+
+Specifies which version of ComfyUI your node is compatible with. This helps users ensure they have the correct version of ComfyUI installed.
+
+**Supported operators:** `<`, `>`, `<=`, `>=`, `~=`, `<>`, `!=` and ranges
+
+**Examples:**
+
+```toml
+requires-comfyui = ">=1.0.0"        # ComfyUI 1.0.0 or higher
+requires-comfyui = ">=1.0.0,<2.0.0"  # ComfyUI 1.0.0 up to (but not including) 2.0.0
+requires-comfyui = "~=1.0.0"         # Compatible release: version 1.0.0 or newer, but not version 2.0.0
+requires-comfyui = "!=1.2.3"         # Any version except 1.2.3
+requires-comfyui = ">0.1.3,<1.0.0"   # Greater than 0.1.3 and less than 1.0.0
+```
+
+#### includes (optional)
+
+Specifies whether to force include certain specific folders. For some situations, such as custom nodes in frontend projects, the final packaged output folder might be included in .gitignore. In such cases, we need to force include it for registry use.
+
+```toml
+includes = ['dist']
+```
+
+### Complete Example
+
+```toml
+[project]
+name = "super-resolution-node"
+version = "1.0.0"
+description = "Enhance image quality using advanced super resolution techniques"
+license = { file = "LICENSE" }
+requires-python = ">=3.8"
+dependencies = [
+    "comfyui-frontend-package<=1.21.6"  # Frontend version compatibility
+]
+classifiers = [
+    "Operating System :: OS Independent"  # Works on all operating systems
+]
+dynamic = ["dependencies"]
+
+[tool.setuptools.dynamic]
+dependencies = {file = ["requirements.txt"]}
+
+[project.urls]
+Repository = "https://github.com/username/super-resolution-node"
+Documentation = "https://github.com/username/super-resolution-node/wiki"
+"Bug Tracker" = "https://github.com/username/super-resolution-node/issues"
+
+[tool.comfy]
+PublisherId = "image-wizard"
+DisplayName = "Super Resolution Node"
+Icon = "https://raw.githubusercontent.com/username/super-resolution-node/main/icon.png"
+Banner = "https://raw.githubusercontent.com/username/super-resolution-node/main/banner.png"
+requires-comfyui = ">=1.0.0"  # ComfyUI version compatibility
+```
+
+## Validation Scenarios
+
+### Always validate changes by running these verification steps:
+
+#### Documentation Validation
+
+```bash
+# 1. Verify all changes are documented
+ls -la docs/  # Check for relevant documentation files
+
+# 2. Ensure documentation is up-to-date
+grep -r "TODO\|FIXME\|OUTDATED" docs/  # Should return no results
+
+# 3. Validate markdown formatting
+# (Optional: install markdownlint if available)
+# markdownlint docs/*.md
+```
+
+#### Python Node Validation
+
+```bash
+# ALWAYS activate virtual environment first
+source .venv/bin/activate
+
+# 1. Import test
+python3 -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('✓ Python imports work')"
+
+# 2. Linting
+ruff check .  # Accept unused import warnings as normal
+
+# 3. Verify system dependencies
+ffmpeg -version | head -1  # Should show FFmpeg version
+```
+
+#### React UI Validation _(DISABLED)_
+
+**⚠️ The React UI component is currently disabled and not in active development.**
+
+```bash
+# THESE COMMANDS ARE CURRENTLY DISABLED
+# cd ui-react_backup/ui
+
+# 1. Build test
+# npm run build  # Should complete in ~5 seconds
+
+# 2. Verify outputs
+# ls -la ../dist/example_ext/main.js  # Should exist
+# ls -la ../dist/locales/  # Should contain en/ and zh/ directories
+
+# 3. TypeScript check
+# npm run typecheck  # Should pass without errors
+```
+
+#### Full Integration Test _(PARTIALLY DISABLED)_
+
+**⚠️ React UI components are disabled, but JavaScript widgets remain active.**
+
+```bash
+# 1. Clean build (DISABLED - React components only)
+# cd ui-react_backup/ui
+# rm -rf ../dist/
+# npm run build
+
+# 2. Verify ComfyUI integration files
+# ls -la ../dist/example_ext/  # React build outputs (DISABLED)
+ls -la ../../web/js/  # JavaScript widgets (ACTIVE)
+ls -la ../../__init__.py  # Python entry point (ACTIVE)
+```
+
+## Known Issues and Limitations
+
+### Jest Testing Configuration
+
+- Jest tests fail due to ES module configuration issues
+- Example test exists in `src/__tests__/dummy.test.tsx` but won't run
+- Fix requires updating jest.config.js and jest.setup.js for ESM support
+
+### ESLint Configuration
+
+- ESLint shows TypeScript project configuration warnings
+- Code builds and runs correctly despite these warnings
+- Focus on functional validation rather than linting perfection
+
+### Python Import Warnings
+
+- Ruff reports unused imports in `__init__.py` files
+- These imports are intentional for ComfyUI integration
+- The warnings can be safely ignored
+
+### System Dependencies
+
+- FFmpeg is required for video processing features
+- Without FFmpeg, video-related functionality will fail at runtime
+- Always verify FFmpeg is installed in your environment
+
+## Common Tasks
+
+### Documentation Tasks
+
+```bash
+# Create new feature documentation
+touch docs/nodes/[node-name]/NEW_FEATURE.md
+touch docs/features/NEW_FEATURE_IMPLEMENTATION.md
+
+# Document a bug fix or implementation detail
+touch docs/nodes/[node-name]/BUG_NAME_FIX.md
+touch docs/infrastructure/[category]/TECHNICAL_IMPLEMENTATION_DETAILS.md
+
+# Update existing documentation after changes
+vim docs/nodes/video-preview/EXISTING_FEATURE.md
+
+# Search for documentation gaps
+grep -r "TODO\|FIXME\|INCOMPLETE" docs/
+
+# Browse documentation by category
+ls -la docs/nodes/           # Node-specific docs
+ls -la docs/infrastructure/  # System/infrastructure docs
+ls -la docs/integrations/    # External service integrations
+ls -la docs/ui-widgets/      # UI widget documentation
+ls -la docs/features/        # Feature implementations
+ls -la docs/examples/        # Example workflows
+
+# View category index
+cat docs/nodes/video-preview/README.md  # See what docs exist for Video Preview node
+
+# Common documentation file types and locations:
+# - docs/nodes/[node-name]/FEATURE_NAME.md - Node feature implementations
+# - docs/nodes/[node-name]/ISSUE_NAME_FIX.md - Node-specific bug fixes
+# - docs/infrastructure/[category]/SYSTEM_NAME.md - Infrastructure documentation
+# - docs/integrations/[service]/INTEGRATION_GUIDE.md - Integration guides
+# - docs/ui-widgets/WIDGET_IMPLEMENTATION.md - UI widget documentation
+# - docs/features/FEATURE_GUIDE.md - Cross-cutting feature documentation
+# - docs/IMPLEMENTATION_STATUS.md - Overall project status (root level)
+```
+
+### File Structure Overview
+
+```
+comfyui_swissarmyknife/
+├── .github/workflows/react-build.yml  # CI/CD automation
+├── __init__.py                         # Python entry point
+├── pyproject.toml                      # Project metadata & publishing config
+├── docs/                              # ALL PROJECT DOCUMENTATION (ORGANIZED)
+│   ├── README.md                      # Main documentation index
+│   ├── IMPLEMENTATION_STATUS.md       # Overall project status
+│   ├── DOCUMENTATION_REORGANIZATION.md # Documentation structure guide
+│   ├── nodes/                         # Node-specific documentation
+│   │   ├── video-preview/            # Video Preview node docs
+│   │   ├── video-metadata/           # Video Metadata node docs
+│   │   ├── media-describe/           # Gemini AI Media Description docs
+│   │   ├── lora-loader/              # LoRA Loader node docs
+│   │   └── reddit-media/             # Reddit Media Extraction docs
+│   ├── infrastructure/                # Infrastructure components
+│   │   ├── caching/                  # Caching system docs
+│   │   ├── debug/                    # Debug & logging docs
+│   │   ├── docker/                   # Docker setup docs
+│   │   └── build-deploy/             # Build & deployment docs
+│   ├── integrations/                  # External service integrations
+│   │   └── civitai/                  # CivitAI API integration docs
+│   ├── ui-widgets/                    # UI widget documentation
+│   ├── features/                      # Feature implementations
+│   └── examples/                      # Example workflows
+├── nodes/nodes.py                      # Main Python custom nodes
+├── web/js/                            # JavaScript widgets
+│   ├── video_preview/                # Video preview widget
+│   ├── gemini_widgets.js             # Gemini widgets
+│   └── ...
+└── ui-react_backup/                   # React UI extension (DISABLED)
+    ├── ui/src/                        # React source code
+    ├── ui/package.json                # Node.js dependencies
+    └── dist/                          # Built React outputs
+```
+
+### Package Management
+
+```bash
+# React dependencies
+cd ui-react_backup/ui
+npm install  # Install from package.json
+
+# Python dependencies (ALWAYS activate venv first)
+source .venv/bin/activate
+pip3 install -e .  # Install from pyproject.toml
+pip3 install torch opencv-python  # Additional ML dependencies
+```
+
+### Environment Verification
+
+```bash
+# Verify tool versions
+node --version    # Should be v20.19.4+
+npm --version     # Should be 10.8.2+
+python3 --version # Should be 3.12.3+
+ffmpeg -version   # Should be 6.1.1+
+
+# Verify Python dependencies (activate venv first)
+source .venv/bin/activate
+which python3     # Should point to .venv/bin/python3
+pip3 list | grep -E "(torch|opencv|google-genai)"  # Show Python ML deps
+
+# Verify Node dependencies
+npm list --prefix ui-react_backup/ui  # Show React dependencies
+```
+
+## Timing Expectations
+
+**NEVER CANCEL these operations - they may appear to hang but are working:**
+
+- `npm install`: 40 seconds (normal)
+- `npm run build`: 5 seconds (very fast)
+- `pip3 install torch opencv-python`: 2-3 minutes (downloads large binaries)
+- `npm run watch`: Runs continuously until stopped
+- `ruff check`: < 1 second (very fast)
+- `pytest`: < 30 seconds (but no tests exist currently)
+
+Set appropriate timeouts: 60+ seconds for npm install, 300+ seconds for Python ML dependencies.
+
+## Development Tips
+
+- **Backend changes**: Restart ComfyUI server after modifying Python files in `nodes/`
+- **Web extension changes**: Refresh browser cache after modifying JavaScript files in `web/js/`
+- JavaScript widgets require no build step (plain JS files)
+- Use Playwright tests in `web/tests/` to validate functionality against hosted ComfyUI server
+- Focus on functional testing since automated tests have configuration issues
+- FFmpeg must be available in PATH for video processing features to work

CONTRIBUTING.md

@@ -0,0 +1,320 @@
+# Contributing to ComfyUI-SwissArmyKnife
+
+Welcome to ComfyUI-SwissArmyKnife! This document provides guidelines for contributors and the Copilot coding agent.
+
+## Development Environment Setup
+
+### Dev Container (Recommended)
+
+The easiest way to get started is using the provided dev container with GPU support:
+
+1. **Prerequisites:**
+    - Docker with NVIDIA GPU support
+    - VS Code with Dev Containers extension
+    - NVIDIA GPU drivers
+
+2. **Quick Start:**
+
+    ```bash
+    # Open in VS Code and use "Reopen in Container"
+    # OR run directly with Docker:
+    docker run --gpus all -v $(pwd):/workspaces/repo -p 8188:8188 mmartial/comfyui-nvidia-docker:ubuntu24_cuda12.8-latest
+    ```
+
+3. **Start ComfyUI:**
+    ```bash
+    ./.devcontainer/run-comfy.sh
+    # ComfyUI will be available at http://localhost:8188
+    ```
+
+### Manual Setup
+
+If you prefer to set up locally:
+
+1. **Install Python dependencies:**
+
+    ```bash
+    pip install -e .
+    pip install ruff black mypy pytest opencv-python pillow
+    ```
+
+2. **Install JavaScript tooling:**
+
+    ```bash
+    cd web
+    npm install
+    ```
+
+3. **Install FFmpeg:**
+
+    ```bash
+    # Ubuntu/Debian
+    sudo apt-get install ffmpeg
+
+    # macOS
+    brew install ffmpeg
+    ```
+
+## Development Workflow
+
+### Python Backend Development
+
+The backend nodes are located in `nodes/`:
+
+- `nodes/nodes.py` - Main Gemini AI integration nodes
+- `nodes/helper_nodes.py` - Helper/utility nodes
+- `nodes/lora_manager/` - LoRA Manager (forked from nd-super-nodes)
+
+**Development commands:**
+
+```bash
+# Lint Python code
+ruff check .
+ruff check --fix .  # Auto-fix issues
+
+# Format Python code
+black .
+
+# Type checking
+mypy .
+
+# Run tests
+pytest
+
+# Test imports work
+python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('Nodes:', list(NODE_CLASS_MAPPINGS.keys()))"
+```
+
+### JavaScript Web Extension Development
+
+The web extension consists of plain JavaScript widgets in `web/`:
+
+- `web/js/gemini_widgets.js` - Main widget implementation
+- `web/css/gemini_widgets.css` - Widget styling
+
+**No build step required** - files are loaded directly by ComfyUI.
+
+**Development commands:**
+
+```bash
+cd web
+
+# Lint JavaScript
+npm run lint
+npm run lint:fix  # Auto-fix issues
+
+# Format code
+npm run format
+
+# Test (Playwright tests)
+cd tests
+npm test
+```
+
+**Important:** After making changes to JavaScript files, refresh the browser cache in ComfyUI to see changes.
+
+### Pre-commit Hooks
+
+This project uses pre-commit hooks to maintain code quality:
+
+```bash
+# Install hooks
+pre-commit install
+
+# Run manually
+pre-commit run --all-files
+
+# Skip hooks (for testing)
+git commit --no-verify
+```
+
+## Testing
+
+### Python Testing
+
+```bash
+pytest  # Run all Python tests
+```
+
+### JavaScript Testing
+
+```bash
+cd web/tests
+npm test  # Run Playwright tests against hosted ComfyUI
+```
+
+**Note:** JavaScript tests require a running ComfyUI server with the custom node installed.
+
+## Code Style Guidelines
+
+### Python
+
+- Use `ruff` for linting (configured in `pyproject.toml`)
+- Use `black` for formatting
+- Follow type hints with `mypy`
+- Maximum line length: 140 characters
+
+### JavaScript
+
+- Use ESLint for linting
+- Use Prettier for formatting
+- Follow ComfyUI widget conventions
+- No build step - plain JavaScript files
+
+## Project Structure
+
+```
+comfyui_swissarmyknife/
+├── .devcontainer/          # Dev container configuration
+│   ├── devcontainer.json   # Main dev container config
+│   ├── postCreate.sh       # Setup script
+│   └── run-comfy.sh        # ComfyUI start script
+├── nodes/                  # Python backend nodes
+│   ├── nodes.py           # Main Gemini AI nodes
+│   ├── helper_nodes.py    # Helper nodes
+│   └── lora_manager/      # LoRA Manager (forked from nd-super-nodes)
+│       ├── __init__.py
+│       ├── nd_super_lora_node.py
+│       ├── lora_utils.py
+│       ├── civitai_service.py
+│       ├── template_manager.py
+│       ├── web_api.py
+│       ├── file_api.py
+│       └── version_utils.py
+├── web/                   # JavaScript web extension
+│   ├── js/                # Widget JavaScript files
+│   │   └── lora_manager/  # LoRA Manager web extension
+│   ├── css/               # Widget CSS files
+│   │   └── lora_manager/  # LoRA Manager styles
+│   ├── tests/             # Playwright tests
+│   └── package.json       # Node.js dependencies
+├── docs/                  # Project documentation
+│   └── LORA_MANAGER_INTEGRATION.md  # LoRA Manager docs
+├── __init__.py            # ComfyUI entry point
+├── pyproject.toml         # Python project configuration
+└── README.md              # Project documentation
+```
+
+## ComfyUI Integration
+
+### Backend Nodes
+
+- Exported via `NODE_CLASS_MAPPINGS` and `NODE_DISPLAY_NAME_MAPPINGS` in `__init__.py`
+- Require ComfyUI server restart after changes
+
+### Web Extension
+
+- Loaded via `WEB_DIRECTORY = "./web"` in `__init__.py`
+- Changes require browser cache refresh only
+
+## CI/CD
+
+### Continuous Integration
+
+- Automated linting and testing via GitHub Actions
+- **No GPU required** for CI - only static analysis
+- Runs on Python and JavaScript code changes
+
+### Publishing
+
+- Automatic publishing to ComfyUI Registry via GitHub Actions
+- Triggered by `pyproject.toml` version updates
+- Requires `REGISTRY_ACCESS_TOKEN` secret
+
+## Common Tasks
+
+### Adding a New Python Node
+
+1. Add node class to `nodes/nodes.py` or `nodes/helper_nodes.py`
+2. Export in `NODE_CLASS_MAPPINGS`
+3. Add tests in `tests/` directory
+4. Update documentation
+
+### Adding JavaScript Widgets
+
+1. Add widget code to `web/js/`
+2. Add styling to `web/css/`
+3. Register with ComfyUI using `app.registerExtension()`
+4. Test with browser refresh
+
+### Working with LoRA Manager
+
+The LoRA Manager is a forked sub-module from [nd-super-nodes](https://github.com/HenkDz/nd-super-nodes). See [docs/LORA_MANAGER_INTEGRATION.md](docs/LORA_MANAGER_INTEGRATION.md) for detailed information.
+
+**Key files:**
+
+- Backend: `nodes/lora_manager/*.py`
+- Frontend: `web/js/lora_manager/extension.js`
+- Styles: `web/css/lora_manager/style.css`
+
+**Testing lora_manager:**
+
+```bash
+# Test imports
+python -c "from nodes.lora_manager import NODE_CLASS_MAPPINGS; print('LoRA Manager nodes:', list(NODE_CLASS_MAPPINGS.keys()))"
+
+# With ComfyUI running, check console for:
+# "Swiss Army Knife LoRA Manager: API routes registered"
+```
+
+### Running Local Tests
+
+```bash
+# Python
+python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('Available nodes:', list(NODE_CLASS_MAPPINGS.keys()))"
+ruff check .
+pytest
+
+# JavaScript
+cd web
+npm run lint
+cd tests && npm test  # Requires running ComfyUI server
+```
+
+## Copilot Coding Agent Guidelines
+
+For the GitHub Copilot coding agent working on this repository:
+
+### Safe Commands to Run
+
+```bash
+# Linting (fast, safe)
+ruff check .
+ruff check --fix .
+
+# Testing imports (fast)
+python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print(list(NODE_CLASS_MAPPINGS.keys()))"
+
+# JavaScript linting
+cd web && npm run lint
+
+# Run tests
+pytest
+cd web/tests && npm test
+```
+
+### Expected Timeouts
+
+- `ruff check .`: < 1 second
+- `pip install -e .`: ~12 seconds
+- `pip install opencv-python`: 2-3 minutes (large downloads)
+- `npm install`: ~40 seconds
+- `pytest`: < 30 seconds
+
+### Key Development Points
+
+- Backend changes require ComfyUI server restart
+- Web extension changes require browser cache refresh only
+- JavaScript widgets are plain JS files (no build step)
+- Focus on minimal, surgical changes
+- Use pre-commit hooks to maintain quality
+
+## Getting Help
+
+- Check existing issues on GitHub
+- Review ComfyUI custom node documentation: https://docs.comfy.org/custom-nodes/overview
+- Check the project's implementation status in `IMPLEMENTATION_STATUS.md`
+
+## License
+
+This project is licensed under the GNU General Public License v3. See `LICENSE` for details.

Dockerfile

@@ -0,0 +1,55 @@
+FROM python:3.11-slim
+
+# Prevent interactive prompts during package installation
+ENV DEBIAN_FRONTEND=noninteractive
+
+# Install system dependencies
+RUN apt-get update && apt-get install -y \
+    git \
+    wget \
+    ffmpeg \
+    libglib2.0-0 \
+    libsm6 \
+    libxext6 \
+    libxrender-dev \
+    libgomp1 \
+    && rm -rf /var/lib/apt/lists/*
+
+# Create workspace directory
+WORKDIR /workspace
+
+# Clone ComfyUI
+RUN git clone https://github.com/comfyanonymous/ComfyUI.git
+
+# Set ComfyUI as working directory
+WORKDIR /workspace/ComfyUI
+
+# Install PyTorch CPU version first
+RUN pip install --no-cache-dir \
+    torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu
+
+# Install ComfyUI dependencies from requirements.txt
+RUN pip install --no-cache-dir -r requirements.txt
+
+# Install additional dependencies needed for ComfyUI-SwissArmyKnife
+RUN pip install --no-cache-dir \
+    google-genai \
+    opencv-python \
+    requests \
+    httpx
+
+# Create directories for models and custom nodes if they don't exist
+RUN mkdir -p models custom_nodes input output
+
+# Install ComfyUI-Manager
+RUN cd custom_nodes && \
+    git clone https://github.com/ltdrdata/ComfyUI-Manager.git comfyui-manager
+
+# Install ComfyUI-Manager dependencies (includes GitPython and other required packages)
+RUN pip install --no-cache-dir -r custom_nodes/comfyui-manager/requirements.txt
+
+# Expose ComfyUI port
+EXPOSE 8188
+
+# Default command (can be overridden in docker-compose.yml)
+CMD ["python", "main.py", "--listen", "0.0.0.0", "--port", "8188", "--cpu", "--base-directory", "/workspace/ComfyUI"]

LICENSE

@@ -0,0 +1,675 @@
+GNU GENERAL PUBLIC LICENSE
+Version 3, 29 June 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+		 Preamble
+
+The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+
+The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+The Corresponding Source for a work in source code form is that
+same work.
+
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+a) The work must carry prominent notices stating that you modified
+it, and giving a relevant date.
+
+b) The work must carry prominent notices stating that it is
+released under this License and any conditions added under section
+7.  This requirement modifies the requirement in section 4 to
+"keep intact all notices".
+
+c) You must license the entire work, as a whole, under this
+License to anyone who comes into possession of a copy.  This
+License will therefore apply, along with any applicable section 7
+additional terms, to the whole of the work, and all its parts,
+regardless of how they are packaged.  This License gives no
+permission to license the work in any other way, but it does not
+invalidate such permission if you have separately received it.
+
+d) If the work has interactive user interfaces, each must display
+Appropriate Legal Notices; however, if the Program has interactive
+interfaces that do not display Appropriate Legal Notices, your
+work need not make them do so.
+
+A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+a) Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by the
+Corresponding Source fixed on a durable physical medium
+customarily used for software interchange.
+
+b) Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by a
+written offer, valid for at least three years and valid for as
+long as you offer spare parts or customer support for that product
+model, to give anyone who possesses the object code either (1) a
+copy of the Corresponding Source for all the software in the
+product that is covered by this License, on a durable physical
+medium customarily used for software interchange, for a price no
+more than your reasonable cost of physically performing this
+conveying of source, or (2) access to copy the
+Corresponding Source from a network server at no charge.
+
+c) Convey individual copies of the object code with a copy of the
+written offer to provide the Corresponding Source.  This
+alternative is allowed only occasionally and noncommercially, and
+only if you received the object code with such an offer, in accord
+with subsection 6b.
+
+d) Convey the object code by offering access from a designated
+place (gratis or for a charge), and offer equivalent access to the
+Corresponding Source in the same way through the same place at no
+further charge.  You need not require recipients to copy the
+Corresponding Source along with the object code.  If the place to
+copy the object code is a network server, the Corresponding Source
+may be on a different server (operated by you or a third party)
+that supports equivalent copying facilities, provided you maintain
+clear directions next to the object code saying where to find the
+Corresponding Source.  Regardless of what server hosts the
+Corresponding Source, you remain obligated to ensure that it is
+available for as long as needed to satisfy these requirements.
+
+e) Convey the object code using peer-to-peer transmission, provided
+you inform other peers where the object code and Corresponding
+Source of the work are being offered to the general public at no
+charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+7. Additional Terms.
+
+"Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+a) Disclaiming warranty or limiting liability differently from the
+terms of sections 15 and 16 of this License; or
+
+b) Requiring preservation of specified reasonable legal notices or
+author attributions in that material or in the Appropriate Legal
+Notices displayed by works containing it; or
+
+c) Prohibiting misrepresentation of the origin of that material, or
+requiring that modified versions of such material be marked in
+reasonable ways as different from the original version; or
+
+d) Limiting the use for publicity purposes of names of licensors or
+authors of the material; or
+
+e) Declining to grant rights under trademark law for use of some
+trade names, trademarks, or service marks; or
+
+f) Requiring indemnification of licensors and authors of that
+material by anyone who conveys the material (or modified versions of
+it) with contractual assumptions of liability to the recipient, for
+any liability that these contractual assumptions directly impose on
+those licensors and authors.
+
+All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+<one line to give the program's name and a brief idea of what it does.>
+Copyright (C) <year>  <name of author>
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+<program>  Copyright (C) <year>  <name of author>
+This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.
+

MANIFEST.in

@@ -0,0 +1,25 @@
+# Include the main package files
+include __init__.py
+recursive-include utils *.py
+
+# Include web extension files
+include web/js/*.js
+
+# Include documentation and metadata
+include README.md
+include LICENSE
+include pyproject.toml
+
+# Exclude development and build artifacts
+exclude *.pyc
+recursive-exclude __pycache__ *
+recursive-exclude example_nodes *
+recursive-exclude ui-react_backup *
+recursive-exclude web/tests *
+recursive-exclude web/node_modules *
+recursive-exclude .git *
+exclude .gitignore
+exclude docker-compose.yml
+exclude Dockerfile
+exclude node.zip
+exclude package.json

README.md

@@ -0,0 +1,386 @@
+# ComfyUI-SwissArmyKnife
+
+A collection of custom nodes for ComfyUI featuring Gemini AI integration for video and image analysis, with a complete development environment using GPU-accelerated containers.
+
+## Features
+
+- **🤖 Gemini AI Integration**: Video, image, and media analysis using Google's Gemini AI
+- **🎨 Super LoRA Loader**: Advanced multi-LoRA management with enhanced UI (forked from nd-super-nodes)
+- **🎮 JavaScript Widgets**: Enhanced ComfyUI interfaces with custom video controls
+- **🐳 Dev Container Support**: GPU-enabled development environment with mmartial/ComfyUI-Nvidia-Docker
+- **🧪 Full Testing Suite**: Python and JavaScript testing with CI/CD integration
+- **⚡ Hot Reload Development**: Instant feedback for both backend and frontend changes
+
+## Quick Start with Dev Container (Recommended)
+
+The fastest way to get started is using the provided dev container with GPU support:
+
+### Prerequisites
+
+- Docker with NVIDIA Container Toolkit
+- VS Code with Dev Containers extension
+- NVIDIA GPU with drivers installed
+
+### Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/sammykumar/ComfyUI-SwissArmyKnife.git
+cd ComfyUI-SwissArmyKnife
+
+# Open in VS Code
+code .
+
+# Use "Reopen in Container" from VS Code command palette
+# OR run directly with Docker:
+docker run --gpus all -v $(pwd):/workspaces/repo -p 8188:8188 \
+  mmartial/comfyui-nvidia-docker:ubuntu24_cuda12.8-latest
+
+# Inside the container, start ComfyUI:
+./.devcontainer/run-comfy.sh
+```
+
+ComfyUI will be available at **http://localhost:8188** with your custom nodes automatically loaded.
+
+## Manual Installation
+
+### For ComfyUI Users
+
+If you want to use the nodes in an existing ComfyUI installation:
+
+```bash
+# Go to your ComfyUI custom_nodes directory
+cd ComfyUI/custom_nodes
+
+# Clone the repository
+git clone https://github.com/sammykumar/ComfyUI-SwissArmyKnife.git
+
+# Install dependencies
+cd ComfyUI-SwissArmyKnife
+pip install -e .
+
+# Restart ComfyUI
+```
+
+### For Development
+
+If you're contributing to the project or want to modify the nodes:
+
+```bash
+# Clone the repository
+git clone https://github.com/sammykumar/ComfyUI-SwissArmyKnife.git
+cd ComfyUI-SwissArmyKnife
+
+# Install Python dependencies
+pip install -e .
+pip install ruff black mypy pytest opencv-python pillow
+
+# Install JavaScript tooling
+cd web
+npm install
+
+# Install pre-commit hooks
+pre-commit install
+```
+
+**System Requirements:**
+
+- Python 3.10+
+- Node.js 20+ (for development)
+- FFmpeg (for video processing)
+- NVIDIA GPU (optional, for accelerated inference)
+
+## Available Nodes
+
+### Backend Nodes (Python)
+
+- **GeminiUtilVideoDescribe**: Analyze videos using Gemini AI
+- **GeminiUtilImageDescribe**: Analyze images using Gemini AI
+- **GeminiUtilMediaDescribe**: Multi-media analysis functionality
+- **Super LoRA Loader 🔪**: Advanced multi-LoRA loading with UI enhancements (from nd-super-nodes)
+    - Load multiple LoRAs in a single node
+    - Individual enable/disable controls per LoRA
+    - Dual strength support (model and CLIP)
+    - Automatic trigger word extraction
+    - Template save/load system
+    - Enhanced file picker with search
+    - See [docs/LORA_MANAGER_INTEGRATION.md](docs/LORA_MANAGER_INTEGRATION.md) for details
+
+### Web Extension (JavaScript)
+
+- **Video Controls Widget**: Enhanced video timeline controls with trimming
+- **Custom Styling**: Themed UI components that integrate with ComfyUI
+
+## 🔐 API Key Configuration
+
+### Required: Google Gemini API Key
+
+To use the Gemini AI features, you'll need a Google Gemini API key:
+
+1. **Get your API key**: Visit [Google AI Studio](https://aistudio.google.com/app/apikey)
+2. **Create API key**: Click "Create API Key" and copy the generated key
+3. **Configure securely**:
+
+    ```bash
+    # Copy the environment template
+    cp .env.example .env
+
+    # Edit .env and add your actual API key
+    GEMINI_API_KEY=your_actual_api_key_here
+    ```
+
+⚠️ **Security Note**: Never commit your actual API keys to version control. The `.env` file is already included in `.gitignore`.
+
+**Alternative**: You can also enter your API key directly in the ComfyUI node interface, but using environment variables is more secure.
+
+## Development Workflow
+
+### Dev Container (Recommended)
+
+```bash
+# Start the development environment
+./.devcontainer/run-comfy.sh
+
+# ComfyUI available at http://localhost:8188
+# Changes are automatically reloaded
+```
+
+### Local Development
+
+```bash
+# Python backend development
+ruff check .                    # Lint Python code
+pytest                         # Run Python tests
+python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print(list(NODE_CLASS_MAPPINGS.keys()))"
+
+# JavaScript web extension development
+cd web
+npm run lint                   # Lint JavaScript
+npm run format                 # Format code
+cd tests && npm test           # Run Playwright tests (requires running ComfyUI)
+```
+
+**Important Notes:**
+
+- Python changes require ComfyUI server restart
+- JavaScript changes require browser cache refresh only
+- JavaScript widgets are plain JS files (no build step required)
+
+## Testing
+
+### Automated Testing
+
+The project includes comprehensive CI/CD testing:
+
+- **Python**: Linting (ruff), formatting (black), type checking (mypy), unit tests (pytest)
+- **JavaScript**: Linting (eslint), formatting (prettier), integration tests (playwright)
+- **Integration**: ComfyUI node loading, FFmpeg availability, system compatibility
+
+### Manual Testing
+
+```bash
+# Test Python nodes
+python -c "from nodes.nodes import NODE_CLASS_MAPPINGS; print('Nodes:', list(NODE_CLASS_MAPPINGS.keys()))"
+
+# Test JavaScript widgets
+# 1. Start ComfyUI with the custom node
+# 2. Add a Gemini node to your workflow
+# 3. Test video controls and interface elements
+```
+
+## Usage
+
+This template includes a simple example extension that displays workflow node statistics. After installation:
+
+1. Look for the "React Example" tab in the ComfyUI sidebar
+2. Click to open the example UI
+
+When developing your own extension, you can:
+
+1. Replace the example UI in App.tsx with your own components
+2. Update the tab title and icon in main.tsx
+3. Customize the extension's appearance and behavior
+
+## Development
+
+### Setup Development Environment
+
+```bash
+# Go to the UI directory
+cd ui
+
+# Install dependencies
+npm install
+
+# Start development mode (watches for changes)
+npm run watch
+```
+
+### Available ComfyUI Extension APIs
+
+This template provides access to ComfyUI's powerful JavaScript APIs through the official type definitions. You can use these APIs to build rich extensions:
+
+- **Sidebar Tabs**: Create custom sidebar panels like this template demonstrates
+- **Bottom Bar Panels**: Add panels to the bottom of the UI
+- **Top Menu Items**: Add custom entries to the top menu
+- **Context Menus**: Create custom context menus for the graph
+- **Settings**: Add settings to the ComfyUI settings panel
+- **Toasts**: Display notification messages
+- **Commands**: Create and register custom commands
+- **Hotkeys/Keybindings**: Register custom keyboard shortcuts
+- **About Panel Badges**: Add badges to the about panel
+- **App Events**: Listen to and respond to app events
+- **Graph Manipulation**: Programmatically manipulate the workflow graph
+
+For comprehensive documentation on all available APIs, see the [ComfyUI JavaScript Developer Documentation](https://docs.comfy.org/custom-nodes/js/javascript_overview).
+
+### File Structure
+
+```
+ComfyUI-SwissArmyKnife/
+├── .github/                    # GitHub configurations
+│   └── workflows/
+│       └── react-build.yml     # Automatic build and publishing workflow
+├── __init__.py                 # Python entry point for ComfyUI integration
+├── pyproject.toml              # Project metadata for ComfyUI Registry
+├── dist/                       # Built extension files (generated)
+└── ui/                         # React application
+    ├── public/
+    │   └── locales/            # Internationalization files
+    │       ├── en/
+    │       │   └── main.json   # English translations
+    │       └── zh/
+    │           └── main.json   # Chinese translations
+    ├── src/
+    │   ├── App.tsx             # Main React component with example UI
+    │   ├── App.css             # Styles for the example UI
+    │   ├── index.css           # Global styles and theme variables
+    │   ├── main.tsx            # Entry point for React app
+    │   ├── vite-env.d.ts       # Vite environment types
+    │   ├── setupTests.ts       # Testing environment setup
+    │   ├── __tests__/          # Unit tests for components
+    │   │   └── dummy.test.tsx  # Example test
+    │   └── nodes/
+    │       └── i18n.ts         # Internationalization setup
+    ├── eslint.config.js        # ESLint configuration
+    ├── jest.config.js          # Jest testing configuration
+    ├── jest.setup.js           # Jest setup file
+    ├── package.json            # npm dependencies
+    ├── tsconfig.json           # TypeScript configuration
+    ├── tsconfig.node.json      # TypeScript configuration for Node
+    └── vite.config.ts          # Build configuration
+```
+
+### TypeScript Support
+
+This extension uses the official `@comfyorg/comfyui-frontend-types` package for type-safe interaction with ComfyUI APIs. To install it:
+
+```bash
+cd ui
+npm install -D @comfyorg/comfyui-frontend-types
+```
+
+## Publishing to ComfyUI Registry
+
+### Prerequisites
+
+1. Set up a [Registry](https://registry.comfy.org) account
+2. Create an API key at https://registry.comfy.org/nodes
+
+### Steps to Publish
+
+1. Install the comfy-cli tool:
+
+    ```bash
+    pip install comfy-cli
+    ```
+
+2. Verify your pyproject.toml has the correct metadata:
+
+    ```toml
+    [project]
+    name = "your_extension_name"  # Use a unique name for your extension
+    description = "Your extension description here."
+    version = "0.1.0"  # Increment this with each update
+
+    [tool.comfy]
+    PublisherId = "your_publisher_id"  # Your Registry publisher ID
+    DisplayName = "Your Extension Display Name"
+    includes = ["dist/"]  # Include built React code (normally ignored by .gitignore)
+    ```
+
+3. Publish your extension:
+
+    ```bash
+    comfy-cli publish
+    ```
+
+4. When prompted, enter your API key
+
+### Automatic Publishing with GitHub Actions
+
+This template includes a GitHub Actions workflow that automatically publishes to the ComfyUI Registry whenever you update the version in pyproject.toml:
+
+1. Go to your repository's Settings > Secrets and variables > Actions
+2. Create a new repository secret called `REGISTRY_ACCESS_TOKEN` with your API key
+3. Commit and push an update to pyproject.toml (e.g., increment the version number)
+4. The GitHub Action will automatically run and publish your extension
+
+The workflow configuration is set up in `.github/workflows/react-build.yml` and will trigger when:
+
+- The `pyproject.toml` file is modified and pushed to the `main` branch
+
+The workflow automatically:
+
+1. Sets up Node.js environment
+2. Installs dependencies (`npm install`)
+3. Builds the React extension (`npm run build`)
+4. Publishes the extension to the ComfyUI Registry
+
+## Unit Testing
+
+This template includes a basic setup for unit testing with Jest and React Testing Library:
+
+```bash
+# Run tests
+npm test
+
+# Run tests in watch mode during development
+npm run test:watch
+```
+
+Example tests can be found in the `src/__tests__` directory. The setup includes:
+
+- Jest for running tests
+- React Testing Library for testing components
+- Mock implementation of the ComfyUI window.app object
+
+## Resources
+
+- [ComfyUI JS Extension Documentation](https://docs.comfy.org/custom-nodes/js/javascript_overview) - Official documentation for ComfyUI JavaScript Extensions
+- [ComfyUI Registry Documentation](https://docs.comfy.org/registry/publishing) - Learn how to publish your extension
+- [ComfyUI Frontend Repository](https://github.com/sammykumar/ComfyUI-Frontend) - The main ComfyUI frontend codebase
+- [Official ComfyUI Frontend Types](https://www.npmjs.com/package/@comfyorg/comfyui-frontend-types) - TypeScript definitions for ComfyUI
+- [React Extension Guide](REACT_EXTENSION_GUIDE.md) - Detailed guide for creating React extensions
+- [TypeScript Documentation](https://www.typescriptlang.org/docs/)
+- [React Documentation](https://react.dev/reference/react)
+- [Jest Documentation](https://jestjs.io/docs/getting-started)
+- [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/)
+
+## Contributing
+
+Contributions are welcome! Feel free to open issues or submit pull requests to improve this template.
+
+## Credits
+
+### Third-Party Integrations
+
+- **LoRA Manager** - Forked from [nd-super-nodes](https://github.com/HenkDz/nd-super-nodes) by HenkDz
+    - Super LoRA Loader with multi-LoRA management
+    - Enhanced file picker overlay
+    - Template management system
+    - CivitAI integration for trigger words
+
+## License
+
+GNU General Public License v3

__init__.py

@@ -0,0 +1,106 @@
+import os
+from .nodes.nodes import NODE_CLASS_MAPPINGS as MAIN_NODE_CLASS_MAPPINGS
+from .nodes.nodes import NODE_DISPLAY_NAME_MAPPINGS as MAIN_NODE_DISPLAY_NAME_MAPPINGS
+from .nodes.helper_nodes import HELPER_NODE_CLASS_MAPPINGS
+from .nodes.helper_nodes import HELPER_NODE_DISPLAY_NAME_MAPPINGS
+
+# Import control panel node
+try:
+    from .nodes.utils.control_panel import CONTROL_PANEL_NODE_CLASS_MAPPINGS
+    from .nodes.utils.control_panel import CONTROL_PANEL_NODE_DISPLAY_NAME_MAPPINGS
+except ImportError as e:
+    print(f"Warning: Could not import control panel node: {e}")
+    CONTROL_PANEL_NODE_CLASS_MAPPINGS = {}
+    CONTROL_PANEL_NODE_DISPLAY_NAME_MAPPINGS = {}
+
+# Import civit metadata helper node
+try:
+    from .nodes.utils.civit_metadata_helper import CIVIT_METADATA_HELPER_NODE_CLASS_MAPPINGS
+    from .nodes.utils.civit_metadata_helper import CIVIT_METADATA_HELPER_NODE_DISPLAY_NAME_MAPPINGS
+except ImportError as e:
+    print(f"Warning: Could not import civit metadata helper node: {e}")
+    CIVIT_METADATA_HELPER_NODE_CLASS_MAPPINGS = {}
+    CIVIT_METADATA_HELPER_NODE_DISPLAY_NAME_MAPPINGS = {}
+
+# Import lora_manager nodes
+try:
+    from .nodes.lora_manager import NODE_CLASS_MAPPINGS as LORA_MANAGER_NODE_CLASS_MAPPINGS
+    from .nodes.lora_manager import NODE_DISPLAY_NAME_MAPPINGS as LORA_MANAGER_NODE_DISPLAY_NAME_MAPPINGS
+except ImportError as e:
+    print(f"Warning: Could not import lora_manager nodes: {e}")
+    LORA_MANAGER_NODE_CLASS_MAPPINGS = {}
+    LORA_MANAGER_NODE_DISPLAY_NAME_MAPPINGS = {}
+
+# Import media_selection nodes
+try:
+    from .nodes.media_selection.media_selection import MediaSelection
+    from .nodes.media_selection.frame_extractor import FrameExtractor
+    from .nodes.media_selection.multi_caption_combiner import MultiCaptionCombiner
+    
+    MEDIA_SELECTION_NODE_CLASS_MAPPINGS = {
+        "MediaSelection": MediaSelection,
+        "FrameExtractor": FrameExtractor,
+        "MultiCaptionCombiner": MultiCaptionCombiner,
+    }
+    MEDIA_SELECTION_NODE_DISPLAY_NAME_MAPPINGS = {
+        "MediaSelection": "Media Selection",
+        "FrameExtractor": "Frame Extractor",
+        "MultiCaptionCombiner": "Multi-Caption Combiner",
+    }
+except ImportError as e:
+    print(f"Warning: Could not import media_selection nodes: {e}")
+    MEDIA_SELECTION_NODE_CLASS_MAPPINGS = {}
+    MEDIA_SELECTION_NODE_DISPLAY_NAME_MAPPINGS = {}
+
+# Register config API routes
+try:
+    from .nodes.config_api import register_config_routes
+    from .nodes.restart_api import register_restart_routes
+    from server import PromptServer
+    app = getattr(PromptServer.instance, "app", None) or PromptServer.instance
+    if app:
+        register_config_routes(app)
+        register_restart_routes(app)
+        print("Swiss Army Knife: Registered config API routes")
+except Exception as e:
+    print(f"Swiss Army Knife: Could not register config API routes: {e}")
+
+
+# Get version from pyproject.toml for cache busting
+def get_version():
+    try:
+        import tomllib
+        pyproject_path = os.path.join(os.path.dirname(__file__), "pyproject.toml")
+        with open(pyproject_path, "rb") as f:
+            data = tomllib.load(f)
+            return data["project"]["version"]
+    except Exception:
+        # Fallback to timestamp if version reading fails
+        import time
+        return str(int(time.time()))
+
+# Combine main nodes, helper nodes, control panel, civit metadata helper, lora_manager, and media_selection nodes
+NODE_CLASS_MAPPINGS = {
+    **MAIN_NODE_CLASS_MAPPINGS,
+    **HELPER_NODE_CLASS_MAPPINGS,
+    **CONTROL_PANEL_NODE_CLASS_MAPPINGS,
+    **CIVIT_METADATA_HELPER_NODE_CLASS_MAPPINGS,
+    **LORA_MANAGER_NODE_CLASS_MAPPINGS,
+    **MEDIA_SELECTION_NODE_CLASS_MAPPINGS
+}
+NODE_DISPLAY_NAME_MAPPINGS = {
+    **MAIN_NODE_DISPLAY_NAME_MAPPINGS,
+    **HELPER_NODE_DISPLAY_NAME_MAPPINGS,
+    **CONTROL_PANEL_NODE_DISPLAY_NAME_MAPPINGS,
+    **CIVIT_METADATA_HELPER_NODE_DISPLAY_NAME_MAPPINGS,
+    **LORA_MANAGER_NODE_DISPLAY_NAME_MAPPINGS,
+    **MEDIA_SELECTION_NODE_DISPLAY_NAME_MAPPINGS
+}
+
+WEB_DIRECTORY = "./web"
+VERSION = get_version()
+
+# Load DEBUG setting from environment
+DEBUG = os.environ.get("DEBUG", "false").lower() in ("true", "1", "yes")
+
+__all__ = ["NODE_CLASS_MAPPINGS", "NODE_DISPLAY_NAME_MAPPINGS", "WEB_DIRECTORY", "VERSION", "DEBUG"]

debug_civitai.py

@@ -0,0 +1,141 @@
+#!/usr/bin/env python3
+"""
+CivitAI Integration Debug Helper
+
+This script helps debug CivitAI integration issues in ComfyUI-SwissArmyKnife.
+"""
+
+import os
+import sys
+sys.path.append(os.path.dirname(__file__))
+
+def check_environment():
+    """Check environment setup for CivitAI integration"""
+    print("🔍 CivitAI Integration Debug Helper")
+    print("=" * 50)
+
+    # Check current directory
+    cwd = os.getcwd()
+    print(f"📁 Current directory: {cwd}")
+
+    # Check for .env files
+    env_files = ['.env', '.env.local', '.env.production']
+    print("\n📄 Environment Files:")
+
+    env_file_found = False
+    civitai_config_found = False
+
+    for env_file in env_files:
+        if os.path.exists(env_file):
+            env_file_found = True
+            print(f"  ✅ Found: {env_file}")
+            try:
+                with open(env_file, 'r') as f:
+                    content = f.read()
+                    if 'CIVITAI' in content.upper():
+                        civitai_config_found = True
+                        print("    ✅ Contains CivitAI configuration")
+                        # Show the lines with CIVITAI (masked)
+                        for line_num, line in enumerate(content.split('\n'), 1):
+                            if 'CIVITAI' in line.upper():
+                                if '=' in line and not line.strip().startswith('#'):
+                                    key, value = line.split('=', 1)
+                                    masked_value = value[:8] + '...' + value[-4:] if len(value) > 12 else '***'
+                                    print(f"    📝 Line {line_num}: {key}={masked_value}")
+                                else:
+                                    print(f"    📝 Line {line_num}: {line}")
+                    else:
+                        print("    ❌ No CivitAI configuration found")
+            except Exception as e:
+                print(f"    ❌ Error reading file: {e}")
+        else:
+            print(f"  ❌ Not found: {env_file}")
+
+    # Check environment variables
+    print("\n🌍 Environment Variables:")
+    civitai_vars = [k for k in os.environ.keys() if 'civit' in k.lower()]
+    if civitai_vars:
+        print(f"  ✅ CivitAI-related variables found: {len(civitai_vars)}")
+        for var in civitai_vars:
+            value = os.environ[var]
+            masked_value = value[:8] + '...' + value[-4:] if len(value) > 12 else '***'
+            print(f"    📝 {var}={masked_value}")
+    else:
+        print("  ❌ No CivitAI-related environment variables found")
+
+    # Test service initialization
+    print("\n🔧 Service Test:")
+    try:
+        from nodes.civitai_service import CivitAIService
+        service = CivitAIService()
+        if service.api_key:
+            print("  ✅ CivitAI service initialized with API key")
+        else:
+            print("  ❌ CivitAI service has no API key")
+    except Exception as e:
+        print(f"  ❌ Error initializing service: {e}")
+
+    # Recommendations
+    print("\n💡 Recommendations:")
+
+    if not env_file_found:
+        print("  1. Create a .env file in your project root:")
+        print("     echo 'CIVITAI_API_KEY=your_api_key_here' > .env")
+    elif not civitai_config_found:
+        print("  1. Add CivitAI API key to your .env file:")
+        print("     echo 'CIVITAI_API_KEY=your_api_key_here' >> .env")
+
+    if not civitai_vars:
+        print("  2. Get your CivitAI API key from: https://civitai.com/user/account")
+        print("  3. Set the environment variable or add to .env file")
+
+    print("  4. Restart ComfyUI after setting the API key")
+    print("  5. Test with a known LoRA file from CivitAI")
+
+def test_api_key(api_key):
+    """Test a CivitAI API key"""
+    if not api_key:
+        print("❌ No API key provided")
+        return False
+
+    print(f"🧪 Testing API key: {api_key[:8]}...{api_key[-4:]}")
+
+    try:
+        import requests
+        url = "https://civitai.com/api/v1/models"
+        headers = {"Authorization": f"Bearer {api_key}"}
+
+        print("📡 Making test request to CivitAI API...")
+        response = requests.get(url, headers=headers, timeout=10, params={"limit": 1})
+
+        print(f"📊 Response status: {response.status_code}")
+
+        if response.status_code == 200:
+            print("✅ API key is valid!")
+            return True
+        elif response.status_code == 401:
+            print("❌ API key is invalid or expired")
+            return False
+        else:
+            print(f"⚠️  Unexpected response: {response.status_code}")
+            print(f"Response: {response.text[:200]}")
+            return False
+
+    except Exception as e:
+        print(f"❌ Error testing API key: {e}")
+        return False
+
+if __name__ == "__main__":
+    if len(sys.argv) > 1:
+        # Test provided API key
+        api_key = sys.argv[1]
+        test_api_key(api_key)
+    else:
+        # Check environment
+        check_environment()
+
+        # Offer to test API key
+        api_key = os.environ.get("CIVITAI_API_KEY")
+        if api_key:
+            print("\n" + "="*50)
+            test_api_key(api_key)

docker-compose.yml

@@ -0,0 +1,21 @@
+services:
+    comfyui:
+        build:
+            context: .
+            dockerfile: Dockerfile
+        ports:
+            - "8188:8188"
+        volumes:
+            # Mount your custom node directory
+            - .:/workspace/ComfyUI/custom_nodes/ComfyUI-SwissArmyKnife
+            # Mount user settings and workflows for persistence
+            - ./.comfyui/user:/workspace/ComfyUI/user
+            - ./.comfyui/models/loras:/workspace/ComfyUI/models/loras
+        environment:
+            # Pass through your Gemini API key
+            - GEMINI_API_KEY=${GEMINI_API_KEY}
+            - CIVITAI_API_KEY=${CIVITAI_API_KEY}
+        working_dir: /workspace/ComfyUI
+        command: python main.py --listen 0.0.0.0 --port 8188 --cpu --base-directory /workspace/ComfyUI
+        stdin_open: true
+        tty: true

docs/CONSOLIDATION_SUMMARY.md

@@ -0,0 +1,289 @@
+# Documentation Consolidation Summary
+
+**Date**: October 8, 2025  
+**Task**: Consolidate and organize documentation in the `docs` folder
+
+---
+
+## Overview
+
+Successfully consolidated fragmented documentation files into comprehensive, well-organized documents. This improves discoverability, reduces redundancy, and makes the documentation easier to maintain.
+
+---
+
+## Consolidations Performed
+
+### 1. Features - JavaScript Improvements
+
+**Consolidated into**: `features/JAVASCRIPT_IMPROVEMENTS.md`
+
+**Source files removed**:
+
+- ✅ `JAVASCRIPT_CACHE_BUSTING.md`
+- ✅ `JAVASCRIPT_ERROR_FIX.md`
+- ✅ `JAVASCRIPT_NODE_NAME_UPDATE.md`
+
+**Content includes**:
+
+- Cache busting implementation (version-based, hash-based, timestamp-based)
+- Module loading error resolution
+- Node name updates (GeminiUtilMediaDescribe → MediaDescribe)
+- Development utilities and debugging tips
+
+### 2. UI Widgets - Control Panel
+
+**Consolidated into**: `ui-widgets/CONTROL_PANEL.md`
+
+**Source files removed**:
+
+- ✅ `CONTROL_PANEL_IMPLEMENTATION.md`
+- ✅ `CONTROL_PANEL_JSON_DATA_FIX.md`
+
+**Content includes**:
+
+- Complete implementation details (Python and JavaScript)
+- JSON data format handling
+- Two-column layout system
+- Usage instructions and troubleshooting
+- Known limitations and future enhancements
+
+### 3. UI Widgets - Dimensions Display
+
+**Consolidated into**: `ui-widgets/DIMENSIONS_DISPLAY.md`
+
+**Source files removed**:
+
+- ✅ `DIMENSIONS_DISPLAY_WIDGET.md`
+- ✅ `DIMENSIONS_DISPLAY_TROUBLESHOOTING.md`
+
+**Content includes**:
+
+- Widget implementation and message structure handling
+- API event handler integration
+- Comprehensive troubleshooting guide
+- Testing procedures and expected behavior
+- Multiple message format support
+
+### 4. UI Widgets - Seed Widget
+
+**Consolidated into**: `ui-widgets/SEED_WIDGET.md`
+
+**Source files removed**:
+
+- ✅ `SEED_WIDGET_IMPLEMENTATION.md`
+- ✅ `SEED_WIDGET_RANDOMIZATION_FIX.md`
+
+**Content includes**:
+
+- Problem solved (ComfyUI execution caching)
+- Implementation details (Python and JavaScript)
+- Usage instructions for reproducible workflows
+- Technical benefits and seed range information
+
+### 5. UI Widgets - General Widget Fixes
+
+**Consolidated into**: `ui-widgets/WIDGET_FIXES.md`
+
+**Source files removed**:
+
+- ✅ `WIDGET_INVESTIGATION_AND_FIXES.md`
+- ✅ `FINAL_STRING_WIDGET_FIX.md`
+- ✅ `WIDGET_STATE_PERSISTENCE_FIX.md`
+
+**Content includes**:
+
+- Widget visibility investigation and fixes
+- Final string widget update handling
+- Widget state persistence with onSerialize/onConfigure
+- Upload widget management improvements
+
+---
+
+## README Updates
+
+### Updated Files
+
+1. **`docs/README.md`** - Main documentation index
+    - Updated UI Widgets section with consolidated file references
+    - Updated Features section with JavaScript Improvements reference
+    - Clearer organization and better links
+
+2. **`docs/features/README.md`** - Features index
+    - Added JavaScript & Infrastructure category
+    - Consolidated JavaScript files into single entry
+    - Improved categorization and descriptions
+
+3. **`docs/ui-widgets/README.md`** - UI Widgets index
+    - Replaced individual file listings with consolidated references
+    - Added detailed feature descriptions for each widget
+    - Improved widget categories and implementation patterns
+
+---
+
+## Benefits
+
+### 1. Better Organization
+
+- **Before**: 12 fragmented files across features and ui-widgets
+- **After**: 5 comprehensive, well-structured documents
+- **Reduction**: 58% fewer files to maintain
+
+### 2. Improved Discoverability
+
+- Related content now in single files
+- Clear table of contents in each document
+- Better cross-references between related topics
+
+### 3. Reduced Redundancy
+
+- Eliminated duplicate information across files
+- Consolidated related fixes and improvements
+- Single source of truth for each topic
+
+### 4. Easier Maintenance
+
+- Fewer files to keep in sync
+- Comprehensive documents easier to update
+- Clear structure for adding new content
+
+### 5. Better User Experience
+
+- One-stop documentation for each topic
+- No need to jump between multiple files
+- Complete context in each document
+
+---
+
+## File Structure Summary
+
+### Before Consolidation
+
+```
+docs/
+├── features/
+│   ├── JAVASCRIPT_CACHE_BUSTING.md          ❌ Removed
+│   ├── JAVASCRIPT_ERROR_FIX.md               ❌ Removed
+│   ├── JAVASCRIPT_NODE_NAME_UPDATE.md        ❌ Removed
+│   └── [other feature files]
+└── ui-widgets/
+    ├── CONTROL_PANEL_IMPLEMENTATION.md       ❌ Removed
+    ├── CONTROL_PANEL_JSON_DATA_FIX.md        ❌ Removed
+    ├── DIMENSIONS_DISPLAY_WIDGET.md          ❌ Removed
+    ├── DIMENSIONS_DISPLAY_TROUBLESHOOTING.md ❌ Removed
+    ├── SEED_WIDGET_IMPLEMENTATION.md         ❌ Removed
+    ├── SEED_WIDGET_RANDOMIZATION_FIX.md      ❌ Removed
+    ├── WIDGET_INVESTIGATION_AND_FIXES.md     ❌ Removed
+    ├── FINAL_STRING_WIDGET_FIX.md            ❌ Removed
+    ├── WIDGET_STATE_PERSISTENCE_FIX.md       ❌ Removed
+    └── [other widget files]
+```
+
+### After Consolidation
+
+```
+docs/
+├── features/
+│   ├── JAVASCRIPT_IMPROVEMENTS.md            ✅ New (consolidated)
+│   └── [other feature files]
+└── ui-widgets/
+    ├── CONTROL_PANEL.md                      ✅ New (consolidated)
+    ├── DIMENSIONS_DISPLAY.md                 ✅ New (consolidated)
+    ├── SEED_WIDGET.md                        ✅ New (consolidated)
+    ├── WIDGET_FIXES.md                       ✅ New (consolidated)
+    └── [other widget files]
+```
+
+---
+
+## Document Characteristics
+
+All consolidated documents include:
+
+1. **Clear Title and Metadata**
+    - Last updated date
+    - Related nodes/components
+    - Status information
+
+2. **Table of Contents**
+    - Easy navigation within document
+    - Clear section organization
+
+3. **Comprehensive Coverage**
+    - Problem description
+    - Solution implementation
+    - Usage instructions
+    - Troubleshooting guides
+    - Technical details
+
+4. **Related Documentation Links**
+    - Cross-references to relevant docs
+    - Integration guides
+    - Related feature documentation
+
+5. **Practical Examples**
+    - Code snippets
+    - Testing procedures
+    - Expected behavior descriptions
+
+---
+
+## Next Steps
+
+### Recommended Future Consolidations
+
+Consider consolidating these areas in future:
+
+1. **LoRA Loader Documentation** (16 files)
+    - Could be organized into 3-4 comprehensive documents
+    - Implementation guide, variants, and integrations
+
+2. **Media Describe Documentation** (20 files)
+    - Could consolidate override-related files
+    - Prompt breakdown files could be merged
+    - API and utility files could be combined
+
+3. **Caching Infrastructure** (6 files)
+    - Could merge verification summaries
+    - Combine optimization and busting guides
+
+### Maintenance Guidelines
+
+1. **When adding new documentation**:
+    - Check if it fits into existing consolidated files
+    - Only create new files for distinct new features
+    - Update README files to reflect additions
+
+2. **When updating documentation**:
+    - Update consolidated files, not individual fragments
+    - Keep table of contents current
+    - Update cross-references as needed
+
+3. **Regular reviews**:
+    - Quarterly review for consolidation opportunities
+    - Remove obsolete documentation
+    - Update organization as project evolves
+
+---
+
+## Statistics
+
+- **Files consolidated**: 12 → 5 (58% reduction)
+- **Updated README files**: 3
+- **New comprehensive documents**: 5
+- **Improved cross-references**: 15+
+- **Better organization**: ✅
+
+---
+
+## Conclusion
+
+The documentation consolidation successfully:
+
+✅ Reduced file count by 58%  
+✅ Improved discoverability and navigation  
+✅ Eliminated redundancy and duplication  
+✅ Created comprehensive, well-structured documents  
+✅ Updated all README files for consistency  
+✅ Established better documentation patterns
+
+The documentation is now more organized, easier to maintain, and provides a better experience for developers and users alike.

docs/DOCUMENTATION_REORGANIZATION.md

@@ -0,0 +1,297 @@
+# Documentation Reorganization Summary
+
+**Date**: October 2, 2025  
+**Version**: 2.0
+
+## Overview
+
+Reorganized the documentation structure from a flat list of 70+ markdown files into a well-organized hierarchical structure with dedicated folders for each major component.
+
+## New Structure
+
+```
+docs/
+├── README.md                           # Main documentation index (NEW)
+├── IMPLEMENTATION_STATUS.md            # Overall project status (ROOT)
+│
+├── nodes/                              # Node-specific documentation
+│   ├── video-preview/                  # Video Preview node (6 files)
+│   │   ├── README.md
+│   │   ├── VIDEO_PREVIEW_NODE.md
+│   │   ├── VIDEO_PREVIEW_IMPLEMENTATION_SUMMARY.md
+│   │   ├── VIDEO_PREVIEW_JS_MIGRATION.md
+│   │   ├── VIDEO_PREVIEW_PROGRESSIVE_LOADING.md
+│   │   ├── VIDEO_PREVIEW_TYPEERROR_FIX.md
+│   │   └── CLEAR_VIDEO_PREVIEW_FUNCTION_ORDER_FIX.md
+│   │
+│   ├── video-metadata/                 # Video Metadata node (3 files)
+│   │   ├── README.md
+│   │   ├── VIDEO_METADATA_NODE.md
+│   │   ├── VIDEO_METADATA_JSON_INTEGRATION.md
+│   │   ├── UPDATE_VIDEO_METADATA_APPEND_FUNCTIONALITY.md
+│   │   └── VHS_VIDEOCOMBINE_COMPATIBILITY_FIX.md
+│   │
+│   ├── media-describe/                 # Gemini AI Media Description (6 files)
+│   │   ├── README.md
+│   │   ├── gemini-prompts.md
+│   │   ├── ALL_MEDIA_DESCRIBE_DATA_OUTPUT.md
+│   │   ├── CLASS_RENAME_MEDIADESCRIBE.md
+│   │   ├── GEMINI_API_500_ERROR_FIX.md
+│   │   ├── GEMINI_API_RETRY_LOGIC.md
+│   │   └── GEMINI_UTILS_REFACTORING_PLAN.md
+│   │
+│   ├── lora-loader/                    # LoRA Loader node (14 files)
+│   │   ├── README.md
+│   │   ├── SUPERLORA_IMPLEMENTATION_GUIDE.md
+│   │   ├── SUPERLORA_CLARIFICATION.md
+│   │   ├── SUPER_LORA_LOADER_VARIANTS.md
+│   │   ├── DUAL_LORA_PANEL_IMPLEMENTATION.md
+│   │   ├── SUPERLORA_SINGLE_PANEL_IMPLEMENTATION.md
+│   │   ├── SUPERLORA_SINGLE_STREAM_IMPLEMENTATION.md
+│   │   ├── LORA_METADATA_INTEGRATION.md
+│   │   ├── LORA_MANAGER_INTEGRATION.md
+│   │   ├── LORA_STACK_METADATA_ENHANCEMENT.md
+│   │   ├── LORA_JSON_CLEANUP.md
+│   │   ├── LORA_JSON_WORKFLOW_SERIALIZATION.md
+│   │   ├── MULTIPLE_LORA_SUPPORT.md
+│   │   ├── SUPERLORA_WANVIDLORA_UPDATE.md
+│   │   ├── WAN_MODEL_TYPE_SELECTION.md
+│   │   └── SUPERLORA_PLUS_BUTTON_FIX.md
+│   │
+│   └── reddit-media/                   # Reddit Media Extraction (6 files)
+│       ├── README.md
+│       ├── REDDIT_POST_MEDIA_SOURCE.md
+│       ├── REDDIT_URL_WIDGET_PERSISTENCE_BUG_FIX.md
+│       ├── REDDIT_URL_WIDGET_VISIBILITY_FIX.md
+│       ├── REDGIFS_EXTRACTION_FIX.md
+│       ├── VIDEO_TRIMMING_REDGIFS_FIX.md
+│       └── JAVASCRIPT_REDDIT_POST_FIX.md
+│
+├── infrastructure/                     # Infrastructure & System Components
+│   ├── caching/                        # Caching system (6 files)
+│   │   ├── README.md
+│   │   ├── CACHING.md
+│   │   ├── CACHE_OPTIMIZATION_FIX.md
+│   │   ├── CACHE_BUSTING_SUMMARY.md
+│   │   ├── CACHE_VERIFICATION_OCTOBER_2025.md
+│   │   └── CACHE_VERIFICATION_SUMMARY.md
+│   │
+│   ├── debug/                          # Debug & Logging (2 files)
+│   │   ├── README.md
+│   │   ├── DEBUG_MODE_IMPLEMENTATION.md
+│   │   └── UNIFIED_DEBUG_SYSTEM.md
+│   │
+│   ├── docker/                         # Docker setup (2 files)
+│   │   ├── README.md
+│   │   ├── DOCKER_DEVELOPMENT_SETUP.md
+│   │   └── DOCKER_COMFYUI_MANAGER_FIX.md
+│   │
+│   └── build-deploy/                   # Build & Publishing (3 files)
+│       ├── README.md
+│       ├── PUBLISHING_WORKFLOW.md
+│       ├── PYTHON_PACKAGE_BUILD_FIX.md
+│       └── GET_VERSION_IMPORT_FIX.md
+│
+├── integrations/                       # External Service Integrations
+│   └── civitai/                        # CivitAI API (3 files)
+│       ├── README.md
+│       ├── CIVITAI_API_KEY_WIDGET.md
+│       ├── CIVITAI_SERVICE_CONSOLIDATION.md
+│       └── MULTIPLE_HASH_TYPES_CIVITAI_INTEGRATION.md
+│
+├── ui-widgets/                         # UI Components (9 files)
+│   ├── README.md
+│   ├── CONTROL_PANEL_IMPLEMENTATION.md
+│   ├── CONTROL_PANEL_JSON_DATA_FIX.md
+│   ├── DIMENSIONS_DISPLAY_WIDGET.md
+│   ├── DIMENSIONS_DISPLAY_TROUBLESHOOTING.md
+│   ├── SEED_WIDGET_IMPLEMENTATION.md
+│   ├── SEED_WIDGET_RANDOMIZATION_FIX.md
+│   ├── FINAL_STRING_WIDGET_FIX.md
+│   ├── WIDGET_INVESTIGATION_AND_FIXES.md
+│   └── WIDGET_STATE_PERSISTENCE_FIX.md
+│
+├── features/                           # Feature Implementations (13 files)
+│   ├── README.md
+│   ├── CHANGE_CLOTHING_COLOR_FEATURE.md
+│   ├── CLOTHING_TEXT_EXCLUSION.md
+│   ├── TWERKING_ACTION_REPLACEMENT.md
+│   ├── DECISIVENESS_IMPROVEMENTS.md
+│   ├── CONFIGURABLE_OPTIONS_GUIDE.md
+│   ├── JSON_OUTPUT_FORMAT.md
+│   ├── ND_SUPER_NODES_FORK_SUMMARY.md
+│   ├── ND_SUPER_NODES_UPDATE_REMOVAL.md
+│   ├── ASYNC_EVENT_LOOP_FIX.md
+│   ├── JAVASCRIPT_CACHE_BUSTING.md
+│   ├── JAVASCRIPT_ERROR_FIX.md
+│   ├── JAVASCRIPT_NODE_NAME_UPDATE.md
+│   └── JAVASCRIPT_CACHE_BUSTING.md
+│
+└── examples/                           # Examples & Workflows (2 files)
+    ├── README.md
+    ├── example_workflow.json
+    └── WORKFLOW_DEMO.md
+```
+
+## Files Organized
+
+### Total Count
+
+- **70+ documentation files** organized into **7 major categories**
+- **11 index README.md files** created for navigation
+- **1 main README.md** for the docs directory
+
+### By Category
+
+1. **Nodes** (35 files across 5 node types)
+    - Video Preview: 6 files
+    - Video Metadata: 4 files
+    - Media Describe: 6 files
+    - LoRA Loader: 14 files
+    - Reddit Media: 6 files
+
+2. **Infrastructure** (13 files across 4 categories)
+    - Caching: 6 files
+    - Debug: 2 files
+    - Docker: 2 files
+    - Build/Deploy: 3 files
+
+3. **Integrations** (3 files)
+    - CivitAI: 3 files
+
+4. **UI Widgets** (9 files)
+
+5. **Features** (13 files)
+
+6. **Examples** (2 files)
+
+## Benefits
+
+### Improved Navigation
+
+- **Before**: Scroll through 70+ files in a single directory
+- **After**: Browse by category, then specific component
+
+### Better Discoverability
+
+- Index README in each folder explains what's inside
+- Cross-references between related documentation
+- Clear naming hierarchy
+
+### Maintainability
+
+- New docs go in the appropriate folder
+- Related docs are co-located
+- Easier to identify outdated or duplicate content
+
+### Developer Experience
+
+- Find node-specific docs quickly
+- Understand system architecture from folder structure
+- Clear separation of concerns
+
+## Migration Notes
+
+### What Changed
+
+- **70+ files moved** from flat structure to categorized folders
+- **11 index files created** for navigation
+- **1 main README** provides documentation overview
+- **No files deleted** - all original content preserved
+
+### What Stayed the Same
+
+- **File names unchanged** - easier to find moved files
+- **File content unchanged** - no content modifications
+- **Links may need updating** - internal cross-references may need path updates
+
+## Next Steps
+
+### Recommended Actions
+
+1. **Update Internal Links**: Many docs have cross-references that need path updates
+    - Example: Change `[Doc](DOC.md)` to `[Doc](../category/DOC.md)`
+
+2. **Consolidate Related Docs**: Some files could be merged
+    - Video Preview files could be consolidated
+    - LoRA Loader documentation could be streamlined
+
+3. **Create Node Guides**: Each node should have:
+    - Implementation guide
+    - User guide
+    - API reference
+    - Troubleshooting guide
+
+4. **Add Visual Aids**: Consider adding:
+    - Architecture diagrams
+    - Flow charts
+    - Screenshot examples
+    - Code snippets
+
+5. **Version Control**: Track documentation versions alongside code versions
+
+## Finding Documents
+
+### By Topic
+
+- **Node documentation**: `docs/nodes/[node-name]/`
+- **System infrastructure**: `docs/infrastructure/[category]/`
+- **External integrations**: `docs/integrations/[service]/`
+- **UI components**: `docs/ui-widgets/`
+- **Features**: `docs/features/`
+
+### By Type
+
+- **Implementation guides**: Look for `*_IMPLEMENTATION.md`
+- **Bug fixes**: Look for `*_FIX.md`
+- **Troubleshooting**: Look for `*_TROUBLESHOOTING.md`
+- **Integration guides**: Look for `*_INTEGRATION.md`
+
+### Quick Access
+
+1. Start at `docs/README.md`
+2. Browse to appropriate category
+3. Check category's `README.md` for file list
+4. Open specific documentation file
+
+## Documentation Standards
+
+### File Naming
+
+- Keep existing ALL_CAPS_WITH_UNDERSCORES format
+- Use descriptive names
+- Include type suffix (`_FIX`, `_IMPLEMENTATION`, etc.)
+
+### Folder Naming
+
+- Use lowercase-with-dashes
+- Clear, descriptive names
+- Group by functionality, not file type
+
+### README Files
+
+Each folder should have a `README.md` that includes:
+
+- Overview of folder contents
+- List of documentation files with descriptions
+- Quick reference guide
+- Related documentation links
+- Status and category information
+
+## Conclusion
+
+The documentation is now organized in a logical, hierarchical structure that makes it easier to:
+
+- Find relevant documentation
+- Understand the project architecture
+- Contribute new documentation
+- Maintain existing documentation
+
+The reorganization preserves all existing content while providing a much better navigation and discovery experience.
+
+---
+
+**Reorganization Date**: October 2, 2025  
+**Files Reorganized**: 70+  
+**New Structure Version**: 2.0  
+**Status**: Complete

docs/IMPLEMENTATION_STATUS.md

@@ -0,0 +1,136 @@
+# MediaDescribe Implementation Summary
+
+## ✅ COMPLETED SUCCESSFULLY
+
+### 1. Python Backend Implementation
+
+- **File**: `nodes/nodes.py`
+- **Status**: ✅ Working correctly
+- **Features**:
+    - Clean MediaDescribe class with proper INPUT_TYPES structure
+    - Support for media_source: "Upload Media" vs "Randomize Media from Path"
+    - Support for media_type: "image" vs "video"
+    - Proper error handling for missing inputs
+    - File randomization logic using glob patterns
+    - All existing GeminiVideoDescribe and GeminiImageDescribe classes preserved
+
+### 2. JavaScript Frontend Implementation
+
+- **File**: `web/js/gemini_widgets.js`
+- **Status**: ✅ Working correctly
+- **Features**:
+    - Dynamic UI widgets that show/hide based on media_source selection
+    - Upload widgets appear when "Upload Media" is selected
+    - Path input appears when "Randomize Media from Path" is selected
+    - Proper widget management and event handling
+
+### 3. Input Parameters Structure
+
+```javascript
+Required:
+- gemini_api_key (STRING)
+- gemini_model (["models/gemini-2.5-flash", "models/gemini-2.5-flash-lite", "models/gemini-2.5-pro"])
+- model_type (["Text2Image", "ImageEdit"])
+- description_mode (["Describe without clothing", "Describe with clothing", ...])
+- prefix_text (STRING, multiline)
+- media_source (["Upload Media", "Randomize Media from Path"]) ⭐ NEW
+- media_type (["image", "video"]) ⭐ NEW
+
+Optional:
+- image (IMAGE tensor)
+- media_path (STRING) ⭐ NEW
+- uploaded_image_file (STRING) ⭐ NEW
+- uploaded_video_file (STRING) ⭐ NEW
+```
+
+### 4. Functionality Tests
+
+- ✅ Python imports work correctly
+- ✅ Node class definitions are valid
+- ✅ INPUT_TYPES structure is properly formatted
+- ✅ Error handling works for missing inputs
+- ✅ Function calls execute without syntax errors
+- ✅ Package initialization still works
+
+### 5. Return Values
+
+The node returns 3 outputs:
+
+1. **description**: The generated description or error message
+2. **gemini_status**: Detailed status information with emoji indicators
+3. **final_string**: Concatenated prefix_text + description
+
+## 🎯 CURRENT STATUS: READY FOR TESTING
+
+The consolidated MediaDescribe node (GeminiUtilMediaDescribe) is now fully implemented and ready for UI testing in ComfyUI. The implementation supports:
+
+1. **Upload Media Mode**: Users can upload images/videos via widgets
+2. **Randomize Media from Path Mode**: Users can specify a directory path and the node will randomly select a file
+3. **Dynamic UI**: The interface adapts based on user selections
+4. **Proper Error Handling**: Clear error messages for missing inputs or invalid paths
+5. **Testing Framework**: Basic validation returns test responses
+
+## 🔜 NEXT STEPS
+
+1. Test the node in ComfyUI interface to verify widget behavior
+2. Implement actual Gemini API processing (currently returns test responses)
+3. Add file validation and additional media format support
+4. Test random file selection with actual media directories
+
+---
+
+# VERSION 1.3.0 STATUS - LoRA INTEGRATION & VHS COMPATIBILITY
+
+## ✅ COMPLETED FEATURES (Version 1.3.0)
+
+### Multiple LoRA Support & JSON Integration
+
+- **Status**: ✅ **COMPLETE** - Production Ready
+- **Implementation**: Enhanced LoRAInfoExtractor to process WANVIDLORA list format from WanVideo Lora Select Multi node
+- **Features**:
+    - Multiple LoRA processing with structured JSON output
+    - VideoMetadataNode integration with LoRA JSON input
+    - Automatic metadata generation from LoRA data
+    - CivitAI API integration for LoRA metadata lookup
+- **Testing**: ✅ Comprehensive end-to-end testing completed
+- **Documentation**: ✅ Complete in `MULTIPLE_LORA_SUPPORT.md`, `JSON_OUTPUT_FORMAT.md`, `VIDEO_METADATA_JSON_INTEGRATION.md`
+
+### VHS VideoCombine Compatibility
+
+- **Status**: ✅ **COMPLETE** - Production Ready
+- **Implementation**: Updated VideoMetadataNode to use VHS_FILENAMES type for full VHS ecosystem compatibility
+- **Solution**: Fixed input/output types to match VHS VideoCombine (VHS_FILENAMES → VHS_FILENAMES)
+- **Testing**: ✅ All integration tests passed - complete workflow verified
+- **Documentation**: ✅ Complete in `VHS_VIDEOCOMBINE_COMPATIBILITY_FIX.md`
+
+### Complete Workflow Chain Verified
+
+```
+WAN Video Lora Select Multi → WANVIDLORA list
+                ↓
+LoRAInfoExtractor → (JSON_STRING, info_text, passthrough)
+                ↓
+VHS VideoCombine → VHS_FILENAMES
+                ↓
+VideoMetadataNode → VHS_FILENAMES
+                ↓
+[Other VHS nodes] → Compatible chaining
+```
+
+## 🎯 VERSION 1.3.0 READY FOR RELEASE
+
+All features tested and documented. Full compatibility achieved with:
+
+- ✅ Multiple LoRA processing from WANVIDLORA
+- ✅ Structured JSON output with metadata
+- ✅ VideoMetadataNode simplified inputs
+- ✅ VHS VideoCombine compatibility (VHS_FILENAMES type)
+- ✅ FFmpeg metadata embedding
+- ✅ Full workflow integration
+
+## 📁 Files Modified
+
+- `nodes/nodes.py` - Clean implementation with all three node classes
+- `web/js/gemini_widgets.js` - Dynamic UI widgets (already working)
+- `nodes/nodes_corrupted_backup.py` - Backup of broken version
+- `nodes/nodes_clean.py` - Clean working version (used to restore nodes.py)

docs/README.md

@@ -0,0 +1,162 @@
+# ComfyUI-SwissArmyKnife Documentation
+
+Welcome to the ComfyUI-SwissArmyKnife documentation! This directory contains comprehensive documentation for all nodes, features, integrations, and infrastructure components.
+
+## 📁 Documentation Structure
+
+### 🎬 Nodes (`/nodes`)
+
+Core custom nodes that extend ComfyUI functionality:
+
+- **[video-preview](nodes/video-preview/)** - Video preview widget for comparing multiple videos side-by-side
+- **[video-metadata](nodes/video-metadata/)** - Video metadata extraction and manipulation
+- **[media-describe](nodes/media-describe/)** - AI-powered media description using Gemini API
+- **[lora-loader](nodes/lora-loader/)** - Advanced LoRA loading with metadata integration
+- **[reddit-media](nodes/reddit-media/)** - Reddit and RedGifs media extraction and processing
+
+### 🏗️ Infrastructure (`/infrastructure`)
+
+Core system components and development tools:
+
+- **[caching](infrastructure/caching/)** - Caching strategies and optimization
+- **[debug](infrastructure/debug/)** - Debug mode and logging systems
+- **[docker](infrastructure/docker/)** - Docker setup and container configuration
+- **[build-deploy](infrastructure/build-deploy/)** - Build processes and publishing workflows
+
+### 🔌 Integrations (`/integrations`)
+
+External service integrations:
+
+- **[civitai](integrations/civitai/)** - CivitAI API integration for model metadata
+- **[reddit](integrations/reddit/)** - Reddit API integration (see also nodes/reddit-media)
+
+### 🎨 UI Widgets (`/ui-widgets`)
+
+Reusable UI components and widgets:
+
+- **[Control Panel](ui-widgets/CONTROL_PANEL.md)** - Dashboard widget with JSON data handling and two-column layout
+- **[Dimensions Display](ui-widgets/DIMENSIONS_DISPLAY.md)** - Automatic media dimension display with troubleshooting
+- **[Seed Widget](ui-widgets/SEED_WIDGET.md)** - Randomization seed for reproducible workflows
+- **[Widget Fixes](ui-widgets/WIDGET_FIXES.md)** - Visibility management, state persistence, and general fixes
+
+### ✨ Features (`/features`)
+
+Feature implementations and enhancements:
+
+- **[JavaScript Improvements](features/JAVASCRIPT_IMPROVEMENTS.md)** - Cache busting, module fixes, and node naming updates
+- Clothing color modification and text exclusion
+- Text exclusion and filtering
+- Prompt improvements and decisiveness
+- External integrations (ND Super Nodes)
+
+### 📚 Examples (`/examples`)
+
+Example workflows and demonstrations:
+
+- Sample workflow JSON files
+- Usage demonstrations
+- Integration examples
+
+## 🚀 Quick Start
+
+### For Developers
+
+1. **Node Development**: See individual node documentation in `/nodes/[node-name]/`
+2. **Adding Features**: Check `/features/` for implementation patterns
+3. **Integration**: Review `/integrations/` for external API integration guides
+4. **Infrastructure**: Consult `/infrastructure/` for system-level changes
+
+### For Users
+
+1. **Node Usage**: Each node folder contains usage guides and examples
+2. **Troubleshooting**: Look for `*_FIX.md` or `*_TROUBLESHOOTING.md` files
+3. **Examples**: Check `/examples/` for workflow demonstrations
+
+## 📖 Documentation Conventions
+
+### File Naming
+
+- **Implementation Guides**: `[FEATURE]_IMPLEMENTATION.md` or `[NODE]_NODE.md`
+- **Bug Fixes**: `[ISSUE]_FIX.md`
+- **Troubleshooting**: `[FEATURE]_TROUBLESHOOTING.md`
+- **Integration Guides**: `[SERVICE]_INTEGRATION.md`
+- **API Documentation**: `[FEATURE]_API.md`
+
+### Document Structure
+
+Each documentation file should include:
+
+1. **Problem Statement** - What issue does this address?
+2. **Solution** - How was it solved?
+3. **Implementation Details** - Technical specifics
+4. **Usage/Testing** - How to use or test the feature
+5. **Related Files** - Links to relevant code files
+6. **Implementation Date** - When was this implemented?
+
+## 🔍 Finding Documentation
+
+### By Topic
+
+- **Video Processing**: Check `/nodes/video-preview/` and `/nodes/video-metadata/`
+- **AI/ML Features**: See `/nodes/media-describe/` and `/nodes/lora-loader/`
+- **External APIs**: Look in `/integrations/`
+- **Performance**: Check `/infrastructure/caching/`
+- **Debugging**: See `/infrastructure/debug/`
+
+### By Issue Type
+
+- **Bugs/Fixes**: Search for `*_FIX.md` files
+- **New Features**: Look for `*_IMPLEMENTATION.md` files
+- **API Changes**: Check `*_INTEGRATION.md` or `*_API.md` files
+- **Performance**: See `/infrastructure/caching/` and optimization docs
+
+## 📝 Contributing Documentation
+
+When adding new documentation:
+
+1. **Choose the Right Location**:
+    - Node-specific → `/nodes/[node-name]/`
+    - Infrastructure → `/infrastructure/[category]/`
+    - Integration → `/integrations/[service]/`
+    - UI widget → `/ui-widgets/`
+    - Feature → `/features/`
+
+2. **Follow Naming Conventions**: Use clear, descriptive names with appropriate suffixes
+
+3. **Update Index Files**: Add your documentation to the relevant `README.md` in the subdirectory
+
+4. **Cross-Reference**: Link to related documentation files
+
+5. **Include Examples**: Add code snippets and usage examples
+
+## 🗂️ Index Files
+
+Each subdirectory contains a `README.md` that:
+
+- Lists all documentation files in that directory
+- Provides brief descriptions of each document
+- Links to related documentation in other directories
+- Includes quick reference guides when applicable
+
+## 📊 Project Status
+
+See [IMPLEMENTATION_STATUS.md](IMPLEMENTATION_STATUS.md) for overall project status and feature completion tracking.
+
+## 🆘 Need Help?
+
+1. **Search**: Use your editor's search to find keywords across all docs
+2. **Index Files**: Check the `README.md` in each subdirectory
+3. **Status**: Review `IMPLEMENTATION_STATUS.md` for current project state
+4. **Examples**: Look in `/examples/` for working implementations
+
+## 📅 Documentation Maintenance
+
+- **Regular Updates**: Documentation should be updated when code changes
+- **Version Tracking**: Include implementation dates in documentation
+- **Consolidation**: Related documents should be merged when appropriate
+- **Cleanup**: Outdated documentation should be archived or removed
+
+---
+
+**Last Updated**: October 2, 2025
+**Documentation Structure Version**: 2.0

docs/examples/README.md

@@ -0,0 +1,46 @@
+# Examples & Workflows
+
+Example workflows and demonstrations for ComfyUI-SwissArmyKnife nodes.
+
+## 📄 Files
+
+- **[example_workflow.json](example_workflow.json)** - Sample workflow JSON
+- **[WORKFLOW_DEMO.md](WORKFLOW_DEMO.md)** - Workflow demonstration guide
+
+## 🎯 Example Workflows
+
+### Basic Media Processing
+
+- Load media from Reddit
+- Describe with Gemini AI
+- Process and output
+
+### Video Comparison
+
+- Load multiple video versions
+- Display in Video Preview node
+- Compare side-by-side
+
+### LoRA Workflow
+
+- Load LoRA from CivitAI
+- Apply to model
+- Generate with metadata
+
+## 🔧 Using Examples
+
+1. **Import Workflow**: Drag JSON file into ComfyUI
+2. **Configure Nodes**: Set API keys and paths
+3. **Run Workflow**: Execute to see results
+4. **Modify**: Customize for your needs
+
+## 📚 Related Documentation
+
+- All node documentation in [nodes/](../nodes/)
+- Integration guides in [integrations/](../integrations/)
+- Feature documentation in [features/](../features/)
+
+---
+
+**Category**: Examples
+**Status**: In Progress

docs/examples/WORKFLOW_DEMO.md

@@ -0,0 +1,46 @@
+## Final String Widget Demo Workflow
+
+This shows how to set up a workflow to test the final_string widget functionality:
+
+```
+┌─────────────┐    ┌─────────────────────────┐    ┌─────────────┐
+│ Load Image  │    │ Gemini Image Describe   │    │ Show Text   │
+│             │────▶│                         │────▶│             │
+│ [Load your  │    │ - API Key: [your key]   │    │ Displays    │
+│  test image]│    │ - Model: gemini-2.5-    │    │ final       │
+│             │    │   flash                 │    │ generated   │
+└─────────────┘    │ - System Prompt: [...]  │    │ prompt      │
+                   │ - User Prompt: [...]    │    └─────────────┘
+                   │                         │
+                   │ ┌─────────────────────┐ │
+                   │ │ final_string widget │ │  ← This widget will
+                   │ │ (will auto-update)  │ │     populate after
+                   │ └─────────────────────┘ │     execution!
+                   └─────────────────────────┘
+```
+
+### Step-by-step Instructions:
+
+1. **Import the workflow**:
+   - Copy the contents of `example_workflow.json`
+   - In ComfyUI, go to "Load" → "Load (from file)" or drag the JSON file
+
+2. **Set up the nodes**:
+   - Load Image: Choose any test image
+   - Gemini Image Describe: Enter your valid Gemini API key
+   - Show Text: This will display the final output
+
+3. **Execute the workflow**:
+   - Click "Queue Prompt" to run the workflow
+   - Wait for the Gemini API to process the image
+
+4. **Check the results**:
+   - The `final_string` widget on the Gemini node should populate with generated text
+   - The Show Text node should display the same text
+   - Browser console should show "Updated final_string widget with:" message
+
+### What was fixed:
+- ❌ Before: final_string widget showed placeholder text
+- ✅ After: final_string widget shows actual generated description
+
+The widget update happens automatically when the node execution completes!

docs/examples/example_workflow.json

@@ -0,0 +1,89 @@
+{
+    "last_node_id": 4,
+    "last_link_id": 3,
+    "nodes": [
+        {
+            "id": 1,
+            "type": "LoadImage",
+            "pos": [100, 100],
+            "size": { "0": 315, "1": 314 },
+            "flags": {},
+            "order": 0,
+            "mode": 0,
+            "outputs": [
+                {
+                    "name": "IMAGE",
+                    "type": "IMAGE",
+                    "links": [1],
+                    "shape": 3,
+                    "slot_index": 0
+                },
+                { "name": "MASK", "type": "MASK", "links": null, "shape": 3 }
+            ],
+            "properties": { "Node name for S&R": "LoadImage" },
+            "widgets_values": ["example.jpg", "image"]
+        },
+        {
+            "id": 2,
+            "type": "GeminiUtilImageDescribe",
+            "pos": [500, 100],
+            "size": { "0": 400, "1": 500 },
+            "flags": {},
+            "order": 1,
+            "mode": 0,
+            "inputs": [{ "name": "image", "type": "IMAGE", "link": 1 }],
+            "outputs": [
+                {
+                    "name": "description",
+                    "type": "STRING",
+                    "links": null,
+                    "shape": 3
+                },
+                {
+                    "name": "gemini_status",
+                    "type": "STRING",
+                    "links": null,
+                    "shape": 3
+                },
+                {
+                    "name": "final_string",
+                    "type": "STRING",
+                    "links": [2],
+                    "shape": 3,
+                    "slot_index": 2
+                }
+            ],
+            "properties": { "Node name for S&R": "GeminiUtilImageDescribe" },
+            "widgets_values": [
+                "YOUR_GEMINI_API_KEY_HERE",
+                "models/gemini-2.5-flash",
+                "Generate a detailed image description...",
+                "Please analyze this image...",
+                ""
+            ]
+        },
+        {
+            "id": 3,
+            "type": "ShowText",
+            "pos": [1000, 100],
+            "size": { "0": 300, "1": 200 },
+            "flags": {},
+            "order": 2,
+            "mode": 0,
+            "inputs": [{ "name": "text", "type": "STRING", "link": 2 }],
+            "outputs": [
+                { "name": "text", "type": "STRING", "links": null, "shape": 3 }
+            ],
+            "properties": { "Node name for S&R": "ShowText" },
+            "widgets_values": [""]
+        }
+    ],
+    "links": [
+        [1, 1, 0, 2, 0, "IMAGE"],
+        [2, 2, 2, 3, 0, "STRING"]
+    ],
+    "groups": [],
+    "config": {},
+    "extra": {},
+    "version": 0.4
+}

docs/features/ASYNC_EVENT_LOOP_FIX.md

@@ -0,0 +1,102 @@
+# Async Event Loop Fix for ComfyUI Integration
+
+## Issue Description
+
+When running the LoRA Info Extractor in ComfyUI, users encountered this error:
+
+```
+Error fetching CivitAI data for /path/to/lora.safetensors: Cannot run the event loop while another loop is running
+```
+
+## Root Cause
+
+ComfyUI runs its own asyncio event loop, and our CivitAI service was attempting to create a new event loop using `asyncio.run()` or `new_event_loop().run_until_complete()`. This created a conflict because:
+
+1. ComfyUI's main thread already has an active event loop
+2. You cannot run `asyncio.run()` when an event loop is already running
+3. Creating a new event loop in the same thread causes synchronization issues
+
+## Solution Implemented
+
+Updated the `_run_async()` method in `CivitAIService` to use thread-based async handling:
+
+### Before (Problematic)
+
+```python
+def _run_async(self, coro):
+    try:
+        loop = asyncio.get_running_loop()
+    except RuntimeError:
+        return asyncio.run(coro)
+
+    # This approach failed in ComfyUI
+    new_loop = asyncio.new_event_loop()
+    try:
+        return new_loop.run_until_complete(coro)
+    finally:
+        new_loop.close()
+```
+
+### After (Fixed)
+
+```python
+def _run_async(self, coro):
+    import concurrent.futures
+
+    try:
+        # Check if we're in an event loop
+        loop = asyncio.get_running_loop()
+        # If we are, run the coroutine in a separate thread
+        with concurrent.futures.ThreadPoolExecutor() as executor:
+            future = executor.submit(self._run_in_thread, coro)
+            return future.result()
+    except RuntimeError:
+        # No event loop running, use asyncio.run directly
+        return asyncio.run(coro)
+
+def _run_in_thread(self, coro):
+    """Run coroutine in a new event loop in the current thread."""
+    new_loop = asyncio.new_event_loop()
+    asyncio.set_event_loop(new_loop)
+    try:
+        return new_loop.run_until_complete(coro)
+    finally:
+        new_loop.close()
+        asyncio.set_event_loop(None)
+```
+
+## How It Works
+
+1. **Detection**: Check if an event loop is already running using `asyncio.get_running_loop()`
+2. **Thread Isolation**: If a loop exists, run the async operation in a separate thread
+3. **Clean Execution**: Create a new event loop in the thread, run the coroutine, then clean up
+4. **Fallback**: If no loop is running, use standard `asyncio.run()`
+
+## Benefits
+
+- ✅ **Compatible with ComfyUI**: Works seamlessly within ComfyUI's event loop
+- ✅ **Thread Safe**: Isolates async operations to prevent conflicts
+- ✅ **Backward Compatible**: Still works in non-event-loop environments
+- ✅ **Clean Resource Management**: Properly closes event loops and threads
+
+## Testing
+
+The fix was validated with:
+
+- Service initialization outside event loops
+- Service calls within active event loops (ComfyUI simulation)
+- Multiple hash type API calls
+- Error handling for 404 responses
+
+## Impact
+
+This fix resolves the blocking issue that prevented the LoRA Info Extractor from working in ComfyUI environments while maintaining compatibility with other usage scenarios.
+
+## Related Files
+
+- `nodes/civitai_service.py` - Main implementation
+- `docs/MULTIPLE_HASH_TYPES_CIVITAI_INTEGRATION.md` - Comprehensive documentation
+
+## Date Fixed
+
+September 26, 2025

docs/features/CHANGE_CLOTHING_COLOR_FEATURE.md

@@ -0,0 +1,49 @@
+# CHANGE_CLOTHING_COLOR_FEATURE
+
+Purpose: Add a boolean option to the Gemini Util - Options node to instruct Gemini to change clothing colors in descriptions to new, scene-harmonized hues that differ from the original colors.
+
+## What changed
+
+- New option in `Gemini Util - Options`:
+    - Name: `change_clothing_color`
+    - Type: Boolean (Yes/No)
+    - Default: No
+    - Location: `nodes/nodes.py` under `GeminiUtilOptions.INPUT_TYPES`
+- Propagated through the options object as `change_clothing_color: bool`.
+- Used by both image and video prompts to adjust clothing color language when clothing descriptions are enabled.
+- Included in caching options to avoid stale results when toggled.
+
+## Behavior
+
+- When `describe_clothing` is Yes AND `change_clothing_color` is Yes:
+    - Text2Image prompt: In the CLOTHING paragraph, the model is instructed to state NEW clothing colors that harmonize with the scene (complementary/analogous/neutral), explicitly different from the original. The prompt forbids mentioning or comparing to the original color.
+    - ImageEdit prompt: Adds a clause to change all clothing colors to NEW, scene-harmonized hues, explicitly different from the original; do not mention or reuse the original colors.
+    - Video prompt: Same as image—CLOTHING paragraph instructs changing to NEW scene-harmonized hues and never referencing the original.
+
+- When `describe_clothing` is No: The color-change logic is ignored.
+
+## Files touched
+
+- `nodes/nodes.py`
+    - Added `change_clothing_color` to `GeminiUtilOptions.INPUT_TYPES`
+    - Updated `GeminiUtilOptions.create_options` signature and returned options
+    - Propagated option into `MediaDescribe.describe_media`
+    - Updated `_process_image` and `_process_video` prompts and cache keys
+- No changes needed in `web/js/swiss-army-knife.js` because ComfyUI auto-renders standard widgets for Python-defined inputs for the Options node.
+
+## Validation
+
+- Import check: `from nodes.nodes import NODE_CLASS_MAPPINGS` loads successfully
+- Expected available nodes include `GeminiUtilVideoDescribe` or `GeminiUtilMediaDescribe` depending on current implementation; in this repo: `GeminiUtilMediaDescribe`, `GeminiUtilOptions`, `FilenameGenerator`.
+
+## Usage
+
+1. Add `Gemini Util - Options` node to your workflow.
+2. Enable `Describe clothing` and toggle `Change clothing color` to `Yes`.
+3. Connect the options to `Gemini Util - Media Describe` and run.
+4. For image workflows, the `final_string` will include updated clothing colors; for video, the description will reflect new scene-harmonized clothing colors.
+
+## Notes and future considerations
+
+- Color selection is model-driven guidance; ensure the downstream model uses the prompt accordingly.
+- If you want to force a particular palette family (e.g., warm neutrals), a future enhancement could expose a `clothing_color_palette_hint` string.

docs/features/CLOTHING_TEXT_EXCLUSION.md

@@ -0,0 +1,77 @@
+# Clothing Text and Typography Exclusion Enhancement
+
+## Overview
+
+Enhanced the Gemini clothing description prompts to exclude any text, typography, words, letters, logos, brand names, or written content visible on clothing or accessories. This addresses the issue where brand names like "PSD" on shorts would be included in descriptions.
+
+## Changes Made
+
+### Before
+
+The clothing description prompts only excluded "logos or brand names":
+
+```
+Do not describe logos or brand names. Exclude tattoos, glasses, and other prohibited attributes.
+```
+
+### After
+
+Enhanced exclusion to cover all forms of text and typography:
+
+```
+Do not describe any text, typography, words, letters, logos, brand names, or written content visible on clothing or accessories. Exclude tattoos, glasses, and other prohibited attributes.
+```
+
+## Implementation Details
+
+The changes were applied to both image and video processing in `nodes/nodes.py`:
+
+1. **Image Processing** (Line ~174): Updated the CLOTHING paragraph prompt in the `_process_image` method
+2. **Video Processing** (Line ~416): Updated the CLOTHING paragraph prompt in the `_process_video` method
+
+Both instances now use the comprehensive text exclusion language.
+
+## Examples of Exclusions
+
+### What Gets Excluded Now ✅
+
+- Brand names: "PSD", "Nike", "Adidas", "Supreme"
+- Typography: Stylized fonts, decorative lettering
+- Words/Text: Any readable text on clothing
+- Letters: Individual letters or monograms
+- Written content: Printed messages, slogans, quotes
+- Logos: Company logos, symbols with text components
+
+### What Still Gets Described ✅
+
+- Garment type and style
+- Colors and materials
+- Fit and silhouette
+- Construction details (seams, straps, waistbands)
+- Fabric texture and behavior
+- Overall design elements (excluding text)
+
+## Benefits
+
+1. **Cleaner Descriptions**: No unwanted brand references in generated prompts
+2. **Copyright Compliance**: Avoids reproducing trademarked brand names
+3. **Focus on Style**: Emphasizes actual clothing design over commercial messaging
+4. **Consistent Exclusion**: Comprehensive coverage of all text-related elements
+
+## Technical Notes
+
+- Changes maintain all existing functionality
+- No breaking changes to API or node structure
+- Applies to both Text2Image and Video processing modes
+- Works with all configurable options (describe_clothing enabled)
+- Backward compatible with existing workflows
+
+## Usage
+
+This enhancement automatically applies when:
+
+- Using `MediaDescribe` node (GeminiUtilMediaDescribe) with clothing descriptions enabled
+- Processing images or videos with visible text on clothing
+- Any workflow where clothing description is part of the output
+
+No configuration changes needed - the improvement is applied automatically to all clothing descriptions.

docs/features/CONFIGURABLE_OPTIONS_GUIDE.md

@@ -0,0 +1,149 @@
+# Gemini Util - Configurable Options Guide
+
+## Overview
+
+The Gemini Describe functionality has been enhanced with configurable options through two nodes:
+
+1. **Gemini Util - Options**: Configuration node that defines how descriptions should be generated
+2. **Gemini Util - Media Describe**: Processing node that accepts media and optional configuration
+
+## New Gemini Util - Options Node
+
+### Purpose
+
+This node provides granular control over description generation by separating configuration from media processing. Connect this node's output to the `gemini_options` input of the Media Describe node.
+
+### Configuration Options
+
+#### API & Model Settings
+
+-   **Gemini API Key**: Your Google Gemini API key
+-   **Gemini Model**: Choose from available models (2.5-flash, 2.5-flash-lite, 2.5-pro)
+-   **Model Type**: Text2Image or ImageEdit workflow type
+
+#### Description Control (New Boolean Options)
+
+-   **Describe Clothing?** [Yes/No]: Include detailed clothing and accessory descriptions
+-   **Describe Hair Style?** [Yes/No]: Include hair texture and motion (but not color/length)
+-   **Describe Bokeh?** [Yes/No]: Allow depth of field effects and blur descriptions
+-   **Replace Action with Twerking?** [Yes/No]: Replace video movement description with twerking content
+
+#### Text Options
+
+-   **Prefix Text**: Text to prepend to generated descriptions
+
+## Updated Media Describe Node
+
+### Changes
+
+-   **Removed**: API key, model selection, description mode combo box, prefix text
+-   **Added**: Optional `gemini_options` input that accepts configuration from Options node
+-   **Maintained**: All media handling capabilities (upload, random selection, image/video support)
+
+### Backward Compatibility
+
+When no Options node is connected, the Media Describe node uses these defaults:
+
+-   Describe Clothing: No
+-   Describe Hair Style: Yes
+-   Describe Bokeh: Yes
+-   Replace Action with Twerking: No
+-   API Key: Default development key
+-   Model: gemini-2.5-flash
+
+## Usage Examples
+
+### Basic Usage
+
+1. Add "Gemini Util - Options" node to workflow
+2. Configure desired settings
+3. Add "Gemini Util - Media Describe" node
+4. Connect Options node output to Media Describe `gemini_options` input
+5. Provide media input (image tensor or upload)
+
+### Option Combinations
+
+#### For Minimal Descriptions (No Clothing, No Hair, No Bokeh)
+
+-   Clean, simple descriptions focusing on core elements
+-   Results in 3-paragraph structure: Subject, Cinematic, Style
+
+#### For Detailed Fashion Analysis (Clothing + Hair)
+
+-   Comprehensive descriptions including garments and hairstyles
+-   Results in 4-paragraph structure when clothing enabled
+
+#### For Sharp Focus Photography (No Bokeh)
+
+-   Explicitly prevents depth-of-field language
+-   Useful for product photography or architectural scenes
+
+### System Prompt Improvements
+
+#### Enhanced Decisiveness
+
+All prompts now include instructions to avoid uncertain language:
+
+-   ❌ "She appears to be wearing either lace tights or leggings"
+-   ✅ "She wears black lace tights"
+
+#### Hair Style Option
+
+New granular control over hair descriptions:
+
+-   When enabled: Includes texture and movement
+-   When disabled: Completely omits hair references
+-   Always excludes: Color and length (as before)
+
+#### Dynamic Paragraph Structure
+
+-   3 paragraphs: Subject, Cinematic, Style (no clothing)
+-   4 paragraphs: Subject, Cinematic, Style, Clothing (with clothing)
+-   5-6 paragraphs for video: Adds Scene and Movement sections
+
+## Migration Guide
+
+### For Existing Workflows
+
+Existing Media Describe nodes will continue working with default settings. To use new features:
+
+1. Add Options node to workflow
+2. Configure desired settings
+3. Connect to Media Describe node
+4. Remove any hardcoded API keys from Media Describe node
+
+### Option Mapping
+
+Old combo box "Description Mode" maps to new options as follows:
+
+-   "Describe without clothing" → Clothing: No, Hair: Yes, Bokeh: Yes
+-   "Describe with clothing" → Clothing: Yes, Hair: Yes, Bokeh: Yes
+-   "Describe without clothing (No bokeh)" → Clothing: No, Hair: Yes, Bokeh: No
+-   "Describe with clothing (No bokeh)" → Clothing: Yes, Hair: Yes, Bokeh: No
+
+## Benefits
+
+1. **Modularity**: Configure once, use with multiple media nodes
+2. **Flexibility**: Mix and match options as needed
+3. **Clarity**: Each option has a clear purpose
+4. **Extensibility**: Easy to add new options in the future
+5. **Precision**: More deterministic descriptions without uncertainty
+
+## Troubleshooting
+
+### No Description Generated
+
+-   Verify Options node is connected to Media Describe
+-   Check API key is valid
+-   Ensure media input is provided
+
+### Unexpected Content
+
+-   Review individual option settings
+-   Check if hair/clothing/bokeh options match expectations
+-   Verify model type (Text2Image vs ImageEdit) is appropriate
+
+### Backward Compatibility Issues
+
+-   Media Describe works standalone with defaults
+-   Only connect Options node if you need custom configuration

docs/features/CONTROL_PANEL_CHANGES.md

@@ -0,0 +1,70 @@
+# Control Panel Simplification Changes
+
+## Summary
+
+Simplified the Control Panel node to only accept `all_media_describe_data` as input and populate the three-column display from the parsed JSON data.
+
+## Changes Made
+
+### Python Backend (`nodes/utils/control_panel.py`)
+
+1. **Removed individual inputs**: Removed `final_prompt`, `gemini_status`, `media_info`, `height`, and `width` from INPUT_TYPES
+2. **Single input**: Now only accepts `all_media_describe_data` (STRING, optional)
+3. **JSON parsing**: The `display_info` method now:
+    - Parses the JSON from `all_media_describe_data`
+    - Logs the parsed data to console
+    - Returns the data in the UI format for JavaScript to consume
+
+### JavaScript Frontend (`web/js/swiss-army-knife.js`)
+
+1. **Removed dynamic input functionality**:
+    - Removed context menu options to add inputs
+    - Removed `updateControlPanelSummary` function
+    - Removed connection change handlers
+    - Removed input counter logic
+
+2. **Updated `updateControlPanelData` function**:
+    - Now extracts and parses `all_media_describe_data` from the execution output
+    - Parses JSON string into an object
+    - Populates three columns from the parsed data:
+        - **Left column**: `final_prompt` field
+        - **Middle column**: `gemini_status` field
+        - **Right column**: `media_info`, `height`, `width`, and any other fields
+
+3. **Better error handling**:
+    - Shows error messages if JSON parsing fails
+    - Shows appropriate messages when data fields are missing
+    - Logs debug information for troubleshooting
+
+## Data Flow
+
+```
+Media Describe Node
+    ↓
+  [all_media_describe_data JSON output]
+    ↓
+Control Panel Node (Python)
+    ↓
+  [Parses JSON and returns to UI]
+    ↓
+Control Panel Widget (JavaScript)
+    ↓
+  [Displays in 3-column layout]
+```
+
+## Expected JSON Format
+
+The `all_media_describe_data` should be a JSON string containing:
+
+```json
+{
+    "final_prompt": "...",
+    "gemini_status": "...",
+    "media_info": "...",
+    "height": 1024,
+    "width": 768,
+    "other_field": "..."
+}
+```
+
+Any additional fields beyond the core ones will be displayed in the right column.

docs/features/DECISIVENESS_IMPROVEMENTS.md

@@ -0,0 +1,83 @@
+# Gemini Prompt Decisiveness Improvements
+
+## Overview
+
+Enhanced the Gemini prompts to eliminate uncertainty language and provide more decisive, confident descriptions. The changes address the issue where Gemini would respond with uncertain phrases like "holding a black folder or book" instead of making a definitive choice.
+
+## Changes Made
+
+### 1. Text2Image Prompts (Image Processing)
+
+**Added prominent decisiveness requirement early in system prompt:**
+
+```
+DECISIVENESS REQUIREMENT: Always provide definitive, certain descriptions. When you see something that could be described multiple ways, make a confident choice and state it as fact. Never use uncertain language like "appears to be", "seems to be", "might be", "possibly", "likely", or "or". Instead of "holding a black folder or book", write "holding a black folder". Instead of "wearing what appears to be denim", write "wearing dark blue denim jeans".
+```
+
+**Enhanced critical note to be more explicit:**
+
+- Added comprehensive list of uncertainty phrases to avoid
+- Added instruction to "confidently choose one and state it as absolute fact"
+
+### 2. ImageEdit Prompts
+
+**Added decisiveness requirement to single-sentence ImageEdit instructions:**
+
+```
+Always be completely decisive and definitive - when you see something that could be described multiple ways, make a confident choice and state it as fact. Never use uncertain language like "appears to be", "seems to be", "might be", "possibly", "likely", or "or". Instead of "holding a black folder or book", write "holding a black folder".
+```
+
+### 3. Video Processing Prompts
+
+**Added same decisiveness requirement to video analysis:**
+
+- Includes the same prominent decisiveness section as Text2Image
+- Enhanced critical note with comprehensive uncertainty language elimination
+- Improved clothing descriptions to be more definitive
+
+### 4. Clothing Descriptions
+
+**Enhanced clothing description sections for both image and video:**
+
+- Added "with confidence" and "definitiveness" language
+- Included instruction to "Make decisive choices when multiple interpretations are possible"
+- Emphasized choosing "one specific description and state it as fact"
+
+## Examples of Improvements
+
+### Before (Uncertain Language)
+
+- ❌ "She appears to be wearing either lace tights or leggings"
+- ❌ "holding what might be a black folder or book"
+- ❌ "seems to be wearing denim, possibly jeans"
+- ❌ "likely has curly hair texture"
+
+### After (Decisive Language)
+
+- ✅ "She wears black lace tights"
+- ✅ "holding a black folder"
+- ✅ "wearing dark blue denim jeans"
+- ✅ "has curly hair texture"
+
+## Benefits
+
+1. **Eliminates Ambiguity**: No more "either/or" constructions
+2. **Improves Prompt Quality**: More specific descriptions for better AI generation
+3. **Reduces Uncertainty**: Confident descriptions lead to better results
+4. **Better User Experience**: Clear, definitive outputs instead of wishy-washy descriptions
+
+## Technical Implementation
+
+- Changes applied to `nodes/media_describe/mediia_describe.py` in the `MediaDescribe` class
+- Affects all three processing modes: Text2Image, ImageEdit, and Video
+- Maintains backward compatibility with existing options
+- No breaking changes to API or node structure
+
+## Validation
+
+- ✅ Python syntax validation passed
+- ✅ Node class mappings intact
+- ✅ All functionality preserved
+- ✅ Enhanced decisiveness implemented across all prompt types
+
+The prompts now consistently guide Gemini to make confident, definitive choices rather than expressing uncertainty through hedging language.

docs/features/JAVASCRIPT_IMPROVEMENTS.md

@@ -0,0 +1,320 @@
+# JavaScript Improvements and Fixes
+
+**Last Updated**: October 8, 2025
+
+This document consolidates JavaScript-related improvements, fixes, and infrastructure enhancements for ComfyUI-SwissArmyKnife.
+
+---
+
+## Table of Contents
+
+1. [Cache Busting Implementation](#cache-busting-implementation)
+2. [Module Loading Error Resolution](#module-loading-error-resolution)
+3. [Node Name Updates](#node-name-updates)
+
+---
+
+## Cache Busting Implementation
+
+### Problem
+
+Browsers cache JavaScript files aggressively, which can prevent users from seeing updates to ComfyUI custom node JavaScript widgets after code changes. This is particularly problematic during development and after publishing updates.
+
+### Solution Options
+
+#### Option 1: Version-Based Query Parameters (Recommended)
+
+Add version query parameters to JavaScript file URLs to force browser cache invalidation.
+
+**Implementation in `__init__.py`:**
+
+```python
+import os
+from .nodes.nodes import NODE_CLASS_MAPPINGS as MAIN_NODE_CLASS_MAPPINGS
+from .nodes.nodes import NODE_DISPLAY_NAME_MAPPINGS as MAIN_NODE_DISPLAY_NAME_MAPPINGS
+from .nodes.helper_nodes import HELPER_NODE_CLASS_MAPPINGS
+from .nodes.helper_nodes import HELPER_NODE_DISPLAY_NAME_MAPPINGS
+
+# Get version from pyproject.toml for cache busting
+def get_version():
+    try:
+        import tomllib
+        pyproject_path = os.path.join(os.path.dirname(__file__), "pyproject.toml")
+        with open(pyproject_path, "rb") as f:
+            data = tomllib.load(f)
+            return data["project"]["version"]
+    except Exception:
+        # Fallback to timestamp if version reading fails
+        import time
+        return str(int(time.time()))
+
+# Combine main nodes and helper nodes
+NODE_CLASS_MAPPINGS = {**MAIN_NODE_CLASS_MAPPINGS, **HELPER_NODE_CLASS_MAPPINGS}
+NODE_DISPLAY_NAME_MAPPINGS = {**MAIN_NODE_DISPLAY_NAME_MAPPINGS, **HELPER_NODE_DISPLAY_NAME_MAPPINGS}
+
+WEB_DIRECTORY = "./web"
+VERSION = get_version()
+
+__all__ = ["NODE_CLASS_MAPPINGS", "NODE_DISPLAY_NAME_MAPPINGS", "WEB_DIRECTORY", "VERSION"]
+```
+
+**JavaScript Version Tracking:**
+
+```javascript
+// Version and cache busting info
+const EXTENSION_VERSION = '1.4.0'; // Should match pyproject.toml version
+const LOAD_TIMESTAMP = new Date().toISOString();
+
+console.log(
+    `Loading swiss-army-knife.js extension v${EXTENSION_VERSION} at ${LOAD_TIMESTAMP}`,
+);
+```
+
+#### Option 2: File Hash-Based Cache Busting
+
+```python
+import hashlib
+import os
+
+def get_file_hash(filepath):
+    """Generate SHA256 hash of file content for cache busting"""
+    try:
+        with open(filepath, 'rb') as f:
+            return hashlib.sha256(f.read()).hexdigest()[:8]
+    except Exception:
+        return "default"
+
+# In __init__.py
+js_file_path = os.path.join(os.path.dirname(__file__), "web/js/swiss-army-knife.js")
+JS_FILE_HASH = get_file_hash(js_file_path)
+```
+
+#### Option 3: Timestamp-Based Cache Busting
+
+```python
+import os
+
+def get_file_timestamp(filepath):
+    """Get file modification timestamp for cache busting"""
+    try:
+        return str(int(os.path.getmtime(filepath)))
+    except Exception:
+        import time
+        return str(int(time.time()))
+
+# In __init__.py
+js_file_path = os.path.join(os.path.dirname(__file__), "web/js/swiss-army-knife.js")
+JS_TIMESTAMP = get_file_timestamp(js_file_path)
+```
+
+### Current Implementation
+
+The project includes a comprehensive cache busting solution:
+
+1. **Version-Based Cache Busting** - Uses `pyproject.toml` version with timestamp fallback
+2. **Cache Busting Script** - `scripts/cache_bust.sh` for automatic version syncing
+3. **Development Utilities** - Browser console commands for cache clearing
+4. **Automatic Version Detection** - Notifies users when extension updates
+
+### Usage
+
+#### For Developers
+
+1. Make changes to JavaScript files
+2. Run cache busting script:
+    ```bash
+    ./scripts/cache_bust.sh
+    ```
+3. Restart ComfyUI server (Python changes only)
+4. Hard refresh browser (`Ctrl+F5` / `Cmd+Shift+R`)
+
+#### For Users Experiencing Cache Issues
+
+**Browser console commands** (development only):
+
+```javascript
+clearSwissArmyKnifeCache(); // Clear cache and reload
+reloadSwissArmyKnife(); // Force reload with cache bypass
+```
+
+**Manual browser cache clearing**:
+
+- Hard refresh: `Ctrl+F5` (Windows/Linux) or `Cmd+Shift+R` (Mac)
+- Developer Tools → Network tab → "Disable cache"
+- Settings → Clear browsing data
+
+### Related Files
+
+- `__init__.py` - Web directory registration and version management
+- `web/js/swiss-army-knife.js` - Main JavaScript extension
+- `pyproject.toml` - Version source for cache busting
+- `scripts/cache_bust.sh` - Automated cache busting script
+
+---
+
+## Module Loading Error Resolution
+
+### Problem
+
+ComfyUI was showing JavaScript errors when trying to load modules from non-existent paths:
+
+```
+Error loading extension /extensions/comfyui_swissarmyknife/node_modules/ajv/lib/dotjs/allOf.js
+Error loading extension /extensions/comfyui_swissarmyknife/node_modules/ajv/lib/dotjs/multipleOf.js
+Error loading extension /extensions/comfyui_swissarmyknife/node_modules/ajv/lib/dotjs/dependencies.js
+...
+```
+
+### Root Cause
+
+The `web/node_modules` directory contained development dependencies (ESLint, Prettier, etc.) that were accidentally being served by ComfyUI as part of the web extension. ComfyUI was attempting to load these Node.js modules as browser JavaScript files, which is incorrect.
+
+### Solution Applied
+
+1. **Removed `web/node_modules`** - Development dependencies shouldn't be exposed to ComfyUI
+2. **Removed `web/package-lock.json`** - No longer needed without dependencies in web directory
+3. **Kept `web/package.json`** - Still useful for development tool configuration
+
+### Architecture Clarification
+
+**Active Files:**
+
+- ✅ `web/js/gemini_widgets.js` - Plain JavaScript widgets for ComfyUI
+- ✅ `web/css/gemini_widgets.css` - CSS for widgets
+
+**Disabled/Development Only:**
+
+- ⚠️ `ui-react_backup/` - React UI extension (disabled)
+
+**Node Modules Locations:**
+
+- Root directory (`node_modules/`) - Playwright tests
+- React UI directory (`ui-react_backup/ui/node_modules/`) - React build
+- Test directory (`web/tests/node_modules/`) - Playwright web tests
+
+### Expected Result
+
+ComfyUI no longer attempts to load development dependencies as web assets. Plain JavaScript widgets continue to work normally without errors.
+
+### Files Affected
+
+- ❌ Removed: `/web/node_modules/` (entire directory)
+- ❌ Removed: `/web/package-lock.json`
+- ✅ Kept: `/web/package.json` (for development tools only)
+- ✅ Kept: `/web/js/gemini_widgets.js` (main widget functionality)
+- ✅ Kept: `/web/css/gemini_widgets.css` (widget styling)
+
+### Verification
+
+To verify the fix:
+
+1. Restart ComfyUI server
+2. Clear browser cache
+3. Check browser console for JavaScript errors
+4. Confirm that nodes load and function correctly
+
+---
+
+## Node Name Updates
+
+### Overview
+
+Updated all JavaScript references from `GeminiUtilMediaDescribe` to `MediaDescribe` to match the Python node ID change in `NODE_CLASS_MAPPINGS`.
+
+### Problem
+
+The Python backend had already renamed the node ID from `"GeminiUtilMediaDescribe"` to `"MediaDescribe"` in the `NODE_CLASS_MAPPINGS`, but the JavaScript code in `web/js/swiss-army-knife.js` was still using the old name, causing JavaScript widgets and event handlers to fail to attach to the node.
+
+### Changes Made
+
+Updated all 9 occurrences of `GeminiUtilMediaDescribe` to `MediaDescribe` in `/web/js/swiss-army-knife.js`:
+
+#### 1. Node Registration
+
+```javascript
+// Before
+else if (nodeData.name === "GeminiUtilMediaDescribe") {
+    debugLog("Registering GeminiUtilMediaDescribe node with dynamic media widgets");
+
+// After
+else if (nodeData.name === "MediaDescribe") {
+    debugLog("Registering MediaDescribe node with dynamic media widgets");
+```
+
+#### 2. Workflow Loading Hook
+
+```javascript
+// Before
+if (node.comfyClass === "GeminiUtilMediaDescribe") {
+    debugLog("[LOADED] loadedGraphNode called for GeminiUtilMediaDescribe");
+
+// After
+if (node.comfyClass === "MediaDescribe") {
+    debugLog("[LOADED] loadedGraphNode called for MediaDescribe");
+```
+
+#### 3. Execution Event Handler
+
+```javascript
+// Before
+if (node && node.comfyClass === "GeminiUtilMediaDescribe") {
+    debugLog("[API] ✅ Found GeminiUtilMediaDescribe execution result");
+
+// After
+if (node && node.comfyClass === "MediaDescribe") {
+    debugLog("[API] ✅ Found MediaDescribe execution result");
+```
+
+### Impact
+
+**Fixed Functionality:**
+
+- ✅ JavaScript widgets properly attach to the MediaDescribe node
+- ✅ Dynamic media upload widgets (image/video) work correctly
+- ✅ Reddit URL widget visibility toggling works
+- ✅ Seed widget for randomization works
+- ✅ Dimensions display widget shows correct height/width
+- ✅ File persistence on workflow save/load works
+
+**Backward Compatibility:**
+
+- ⚠️ **Breaking Change**: Existing workflows using the old node need updating
+- Users with saved workflows containing the old node ID will need to:
+    1. Open the workflow JSON
+    2. Find and replace `"GeminiUtilMediaDescribe"` with `"MediaDescribe"`
+    3. Or recreate the node in ComfyUI
+
+### Testing Checklist
+
+After these changes, verify:
+
+1. ✅ MediaDescribe node appears in the node menu
+2. ✅ Dynamic widgets appear based on media_source selection:
+    - Upload Media → Shows image/video upload buttons
+    - Randomize from Path → Shows media_path and seed inputs
+    - Reddit Post → Shows reddit_url input
+3. ✅ File uploads work and persist across workflow save/load
+4. ✅ Dimensions display widget shows after execution
+5. ✅ Video/image previews work correctly
+
+### Related Files
+
+- `/web/js/swiss-army-knife.js` - JavaScript widgets and event handlers (updated)
+- `/nodes/nodes.py` - Python node definitions (already updated)
+- `/nodes/media_describe/mediia_describe.py` - MediaDescribe class implementation
+
+---
+
+## Summary
+
+These JavaScript improvements ensure:
+
+1. **Reliable Cache Management** - Users always see the latest code updates
+2. **Clean Module Loading** - No spurious errors from development dependencies
+3. **Consistent Naming** - JavaScript and Python node IDs are synchronized
+
+For related documentation, see:
+
+- [Media Describe Node](../nodes/media-describe/) - AI content analysis
+- [Debug System](../infrastructure/debug/) - For JavaScript debugging
+- [UI Widgets](../ui-widgets/) - Widget implementation details

docs/features/JSON_OUTPUT_FORMAT.md

@@ -0,0 +1,246 @@
+# LoRAInfoExtractor JSON Output Format
+
+## Overview
+
+The `LoRAInfoExtractor` node now outputs structured JSON data instead of concatenated strings, providing better data handling and parsing capabilities for downstream processing.
+
+## Implementation Details
+
+### Return Types and Names
+
+- **RETURN_TYPES**: `("STRING", "STRING", "WANVIDLORA")`
+- **RETURN_NAMES**: `("lora_json", "lora_info", "lora_passthrough")`
+
+### Output Structure
+
+The first output (`lora_json`) contains a JSON string with the following structure:
+
+```json
+{
+    "loras": [
+        {
+            "index": 0,
+            "name": "LoRA Name",
+            "info": "Detailed info string",
+            "path": "/path/to/lora.safetensors",
+            "strength": 1.0,
+            "has_civitai_data": true
+        }
+    ],
+    "count": 1,
+    "combined_display": "LoRA Name + Another LoRA"
+}
+```
+
+### JSON Fields Description
+
+#### Root Level Fields
+
+- **`loras`**: Array of LoRA objects containing detailed metadata for each processed LoRA
+- **`count`**: Integer representing the total number of valid LoRAs processed
+- **`combined_display`**: String with " + " separated LoRA names for easy display (maintains backward compatibility)
+
+#### LoRA Object Fields
+
+- **`index`**: Zero-based index of the LoRA in the processing order
+- **`name`**: Clean LoRA name (from CivitAI or extracted from filename)
+- **`info`**: Human-readable information string including source (CivitAI/Local) and strength
+- **`path`**: Full file path to the LoRA file
+- **`strength`**: Numeric strength value from the WANVIDLORA configuration
+- **`has_civitai_data`**: Boolean indicating whether CivitAI metadata was successfully retrieved
+
+## Example Outputs
+
+### Multiple LoRAs with Mixed Sources
+
+```json
+{
+    "loras": [
+        {
+            "index": 0,
+            "name": "Realistic Vision",
+            "info": "CivitAI: Realistic Vision (v5.1) by SomeCreator",
+            "path": "/ComfyUI/models/loras/realistic_vision.safetensors",
+            "strength": 1.0,
+            "has_civitai_data": true
+        },
+        {
+            "index": 1,
+            "name": "CustomStyle",
+            "info": "Local: CustomStyle (strength: 0.8)",
+            "path": "/ComfyUI/models/loras/custom_style.safetensors",
+            "strength": 0.8,
+            "has_civitai_data": false
+        }
+    ],
+    "count": 2,
+    "combined_display": "Realistic Vision + CustomStyle"
+}
+```
+
+### No Valid LoRAs (Error Case)
+
+```json
+{
+    "loras": [],
+    "count": 0,
+    "combined_display": "No Valid LoRAs",
+    "error": "No valid LoRAs found"
+}
+```
+
+### Exception Handling
+
+```json
+{
+    "loras": [],
+    "count": 0,
+    "combined_display": "Error Extracting LoRA",
+    "error": "Specific error message"
+}
+```
+
+## Processing Logic
+
+### Multiple LoRA Processing
+
+1. **Input Validation**: Check if input is WANVIDLORA list structure
+2. **LoRA Filtering**: Skip entries with `path: 'none'` or empty paths
+3. **CivitAI Lookup**: Query CivitAI API for each valid LoRA (if enabled)
+4. **Name Extraction**: Use CivitAI name or extract from filename
+5. **JSON Construction**: Build structured JSON with all metadata
+6. **Return**: JSON string, human-readable info, and original passthrough
+
+### Single LoRA Processing (Compatibility)
+
+- Maintains backward compatibility with non-list inputs
+- Returns same JSON structure with single LoRA in array
+- Handles both CivitAI and local extraction methods
+
+## Usage Examples
+
+### Parsing JSON Output in Python
+
+```python
+import json
+
+# From ComfyUI workflow
+lora_json, lora_info, lora_passthrough = lora_extractor_node_output
+
+# Parse JSON
+lora_data = json.loads(lora_json)
+
+# Access data
+total_loras = lora_data["count"]
+display_name = lora_data["combined_display"]
+
+# Iterate through LoRAs
+for lora in lora_data["loras"]:
+    print(f"LoRA: {lora['name']} (strength: {lora['strength']})")
+    if lora["has_civitai_data"]:
+        print("  Has CivitAI metadata")
+    else:
+        print("  Local metadata only")
+```
+
+### JavaScript Processing
+
+```javascript
+// Parse JSON output
+const loraData = JSON.parse(loraJsonOutput);
+
+// Access combined display for UI
+document.getElementById('lora-display').textContent = loraData.combined_display;
+
+// Process individual LoRAs
+loraData.loras.forEach((lora, index) => {
+    console.log(`LoRA ${index + 1}: ${lora.name} at ${lora.strength} strength`);
+});
+```
+
+## Benefits of JSON Format
+
+### Structured Data Access
+
+- **Programmatic Processing**: Easy to parse and process in any language
+- **Type Safety**: Clear data types for each field
+- **Extensibility**: Easy to add new fields without breaking existing code
+
+### Backward Compatibility
+
+- **Combined Display**: `combined_display` field maintains the " + " separated format
+- **Info String**: Second output still provides human-readable information
+- **Passthrough**: Third output preserves original WANVIDLORA data
+
+### Enhanced Metadata
+
+- **Strength Values**: Individual strength values for each LoRA
+- **Source Information**: Clear indication of CivitAI vs local metadata
+- **File Paths**: Full paths available for further processing
+- **Processing Status**: Error handling and success indicators
+
+## Migration Guide
+
+### From String Format
+
+**Old Usage** (string concatenation):
+
+```python
+# Old format returned: "LoRA1 + LoRA2"
+lora_names = old_output[0]
+names_list = lora_names.split(" + ")
+```
+
+**New Usage** (JSON parsing):
+
+```python
+# New format returns structured JSON
+lora_json = json.loads(new_output[0])
+names_list = [lora["name"] for lora in lora_json["loras"]]
+combined_display = lora_json["combined_display"]  # Same as old format
+```
+
+### Accessing Additional Data
+
+With JSON format, you now have access to:
+
+- Individual LoRA strength values
+- Full file paths
+- CivitAI metadata indicators
+- Processing error information
+- Structured arrays for iteration
+
+## Implementation Status
+
+- ✅ **JSON Structure**: Complete with all metadata fields
+- ✅ **Multiple LoRA Support**: Handles WANVIDLORA list structure
+- ✅ **Single LoRA Compatibility**: Backward compatibility maintained
+- ✅ **Error Handling**: Proper JSON error responses
+- ✅ **CivitAI Integration**: Preserves CivitAI metadata detection
+- ✅ **Testing**: Validated with mock data and real WANVIDLORA structures
+
+## Technical Notes
+
+### JSON Library
+
+Uses Python's built-in `json` module for serialization:
+
+- **Consistency**: Standard JSON formatting with 2-space indentation
+- **Reliability**: Built-in error handling and validation
+- **Performance**: Efficient serialization and parsing
+
+### Memory Considerations
+
+- JSON strings are larger than simple concatenated strings
+- Rich metadata provides more value than storage overhead
+- Structured data enables better caching and processing optimization
+
+### Future Enhancements
+
+Potential additions to JSON structure:
+
+- **Model Hash**: File hash for verification
+- **File Size**: LoRA file size information
+- **Last Modified**: File timestamp data
+- **Tags**: CivitAI tag information
+- **Ratings**: CivitAI popularity/rating data

docs/features/ND_SUPER_NODES_FORK_SUMMARY.md

@@ -0,0 +1,384 @@
+# ND Super Nodes Fork - Implementation Summary
+
+## Overview
+
+Successfully forked [nd-super-nodes](https://github.com/HenkDz/nd-super-nodes) by HenkDz into ComfyUI-SwissArmyKnife under `nodes/lora_manager/` with full integration into the Swiss Army Knife ecosystem.
+
+## Date
+
+October 1, 2024
+
+## Files Added
+
+### Backend Python Files (8 files)
+
+```
+nodes/lora_manager/
+├── __init__.py                 # Module initialization and node registration
+├── nd_super_lora_node.py      # Main Super LoRA Loader node implementation
+├── lora_utils.py              # LoRA file discovery and metadata extraction
+├── civitai_service.py         # CivitAI API integration for trigger words
+├── template_manager.py        # Template save/load/delete operations
+├── web_api.py                 # HTTP API endpoints for frontend
+├── file_api.py                # Enhanced file listing API
+├── version_utils.py           # Version checking and updates
+└── README.md                  # Module documentation
+```
+
+### Web Extension Files (3 files)
+
+```
+web/
+├── js/lora_manager/
+│   ├── extension.js           # Frontend JavaScript (5,983 lines)
+│   └── README.md              # Web extension documentation
+└── css/lora_manager/
+    └── style.css              # Custom styling for LoRA Manager UI
+```
+
+### Documentation Files (3 files)
+
+```
+docs/
+└── LORA_MANAGER_INTEGRATION.md  # Comprehensive integration guide (8.4KB)
+```
+
+## Files Modified
+
+### Core Integration Files
+
+1. **`__init__.py`** (root)
+    - Added lora_manager node imports
+    - Integrated NODE_CLASS_MAPPINGS
+    - Added error handling for missing dependencies
+
+2. **`pyproject.toml`**
+    - Added `aiohttp>=3.8.0` dependency
+
+3. **`CONTRIBUTING.md`**
+    - Added lora_manager section
+    - Updated project structure diagram
+    - Added testing instructions
+
+4. **`README.md`**
+    - Added LoRA Manager to features list
+    - Updated available nodes section
+    - Added credits section
+
+### Branding Updates in Forked Code
+
+Updated the following in forked files to match Swiss Army Knife branding:
+
+1. **`nodes/lora_manager/__init__.py`**
+    - Changed header comment to reference fork origin
+    - Updated NODE_DISPLAY_NAME_MAPPINGS: "Super LoRA Loader 🔪"
+    - Updated print statements: "Swiss Army Knife LoRA Manager"
+
+2. **`nodes/lora_manager/nd_super_lora_node.py`**
+    - Changed CATEGORY from "loaders" to "Swiss Army Knife 🔪"
+
+## Integration Details
+
+### Node Registration
+
+The lora_manager nodes are integrated into the main node mappings:
+
+```python
+# In __init__.py
+from .nodes.lora_manager import NODE_CLASS_MAPPINGS as LORA_MANAGER_NODE_CLASS_MAPPINGS
+from .nodes.lora_manager import NODE_DISPLAY_NAME_MAPPINGS as LORA_MANAGER_NODE_DISPLAY_NAME_MAPPINGS
+
+NODE_CLASS_MAPPINGS = {
+    **MAIN_NODE_CLASS_MAPPINGS,
+    **HELPER_NODE_CLASS_MAPPINGS,
+    **LORA_MANAGER_NODE_CLASS_MAPPINGS  # ← New integration
+}
+```
+
+### API Routes Registration
+
+The lora_manager automatically registers HTTP API routes when ComfyUI's PromptServer is available:
+
+**LoRA Operations:**
+
+- `GET /super_lora/loras` - List available LoRAs
+- `GET /super_lora/files?folder_name=loras` - List files
+- `POST /super_lora/civitai_info` - Fetch CivitAI metadata
+
+**Template Operations:**
+
+- `GET /super_lora/templates` - List all templates
+- `POST /super_lora/templates` - Save template
+- `DELETE /super_lora/templates/{name}` - Delete template
+
+**File Picker:**
+
+- `GET /superlora/files` - Enhanced file listing
+- `GET /superlora/folders` - Folder information
+- `GET /superlora/search` - File search
+
+### Web Extension Loading
+
+The web extension is automatically loaded by ComfyUI from the `web/js/lora_manager/` directory through ComfyUI's standard web directory loading mechanism.
+
+## Features Integrated
+
+### 1. Super LoRA Loader Node
+
+- **Category**: "Swiss Army Knife 🔪"
+- **Display Name**: "Super LoRA Loader 🔪"
+- **Inputs**: MODEL (required), CLIP (optional), lora_bundle (JSON)
+- **Outputs**: MODEL, CLIP, TRIGGER_WORDS (string)
+
+**Capabilities:**
+
+- Load multiple LoRAs in a single node
+- Individual enable/disable toggles per LoRA
+- Dual strength controls (model and CLIP)
+- Automatic trigger word extraction from safetensors metadata
+- Tag-based organization with collapsible groups
+- Duplicate detection
+- Drag-and-drop reordering
+
+### 2. Template Management
+
+- Save current LoRA configurations with custom names
+- Load previously saved templates
+- Rename existing templates
+- Delete unwanted templates
+- Templates stored in ComfyUI user directory
+- Persistent across sessions
+
+### 3. Enhanced File Picker (ND Super Selector)
+
+- Advanced file browser overlay
+- Folder navigation with breadcrumbs
+- Search functionality
+- Multi-select support
+- Per-node enable/disable via right-click menu
+- Visual indicators (golden border, lightning icon ⚡)
+- Supports: CheckpointLoader, VAELoader, LoraLoader, UNETLoader, CLIPLoader, ControlNetLoader, UpscaleModelLoader, GGUF variants
+
+### 4. CivitAI Integration
+
+- Automatic trigger word fetching from CivitAI API
+- Model metadata retrieval
+- Fallback to local safetensors metadata
+- Smart caching to reduce API calls
+- Hash-based model identification
+
+## Testing Results
+
+### Python Import Tests
+
+```bash
+✓ lora_utils imports successfully
+✓ validate_lora_config works: True
+✓ lora_manager imports successfully
+✓ Nodes available: ['NdSuperLoraLoader']
+✓ Display names: ['Super LoRA Loader 🔪']
+✓ Category: Swiss Army Knife 🔪
+✓ Return types: ('MODEL', 'CLIP', 'STRING')
+```
+
+### Expected Console Output
+
+When ComfyUI loads with lora_manager:
+
+```
+ND Super Nodes: ComfyUI modules not available (this is normal during development)
+Super LoRA Loader: ComfyUI folder_paths not available
+Swiss Army Knife LoRA Manager: API routes registered
+```
+
+## Dependencies Added
+
+### Python Dependencies (pyproject.toml)
+
+```toml
+dependencies = [
+    # ... existing dependencies
+    "aiohttp>=3.8.0",  # ← New dependency for lora_manager
+]
+```
+
+### Optional Dependencies
+
+The lora_manager works best with:
+
+- `safetensors` - For reading LoRA metadata (usually included with ComfyUI)
+- Internet connection - For CivitAI API integration (optional)
+
+## Directory Structure Changes
+
+### Before
+
+```
+nodes/
+├── __init__.py
+├── cache.py
+├── civitai_service.py
+├── helper_nodes.py
+├── lora_hash_cache.py
+└── nodes.py
+
+web/
+├── js/
+│   └── swiss-army-knife.js
+└── tests/
+```
+
+### After
+
+```
+nodes/
+├── __init__.py
+├── cache.py
+├── civitai_service.py
+├── helper_nodes.py
+├── lora_hash_cache.py
+├── lora_manager/           # ← NEW MODULE
+│   ├── __init__.py
+│   ├── nd_super_lora_node.py
+│   ├── lora_utils.py
+│   ├── civitai_service.py
+│   ├── template_manager.py
+│   ├── web_api.py
+│   ├── file_api.py
+│   ├── version_utils.py
+│   └── README.md
+└── nodes.py
+
+web/
+├── css/                    # ← NEW DIRECTORY
+│   └── lora_manager/
+│       └── style.css
+├── js/
+│   ├── lora_manager/       # ← NEW DIRECTORY
+│   │   ├── extension.js
+│   │   └── README.md
+│   └── swiss-army-knife.js
+└── tests/
+```
+
+## Code Changes Summary
+
+### Minimal Changes Philosophy
+
+Following the directive to make "smallest possible changes", only essential modifications were made:
+
+1. **Category Update**: Changed from "loaders" to "Swiss Army Knife 🔪" (1 line)
+2. **Display Name**: Added 🔪 emoji to node name (1 line)
+3. **Print Statements**: Updated branding in print statements (2 lines)
+4. **Documentation Headers**: Updated module docstrings (3 locations)
+
+All other code from nd-super-nodes remains unchanged to maintain compatibility and ease of future updates.
+
+## Documentation
+
+### Created Documentation
+
+1. **`docs/LORA_MANAGER_INTEGRATION.md`** (8,432 bytes)
+    - Comprehensive integration guide
+    - Feature descriptions
+    - Architecture overview
+    - API routes documentation
+    - Usage examples
+    - Troubleshooting guide
+    - Credits and license information
+
+2. **`nodes/lora_manager/README.md`** (2,480 bytes)
+    - Backend module overview
+    - File descriptions
+    - Integration details
+    - Development guidelines
+
+3. **`web/js/lora_manager/README.md`** (2,743 bytes)
+    - Web extension overview
+    - Features description
+    - API integration details
+    - Testing and debugging guide
+
+### Updated Documentation
+
+1. **`README.md`**
+    - Added LoRA Manager to features list
+    - Updated available nodes section
+    - Added credits for nd-super-nodes fork
+
+2. **`CONTRIBUTING.md`**
+    - Added lora_manager section
+    - Updated project structure diagram
+    - Added testing instructions
+
+## Compatibility Notes
+
+### ComfyUI Compatibility
+
+The lora_manager is designed to work with:
+
+- ComfyUI's standard LoraLoader node API
+- ComfyUI's folder_paths system
+- ComfyUI's PromptServer for API routes
+- ComfyUI's web extension system
+
+### Graceful Degradation
+
+The module handles missing dependencies gracefully:
+
+- Works without ComfyUI (for testing)
+- Works without CivitAI API (falls back to local metadata)
+- Works without safetensors library (with reduced functionality)
+
+## Future Considerations
+
+### Maintenance
+
+When updating from nd-super-nodes upstream:
+
+1. Copy new files to `nodes/lora_manager/`
+2. Re-apply branding changes:
+    - Category: "Swiss Army Knife 🔪"
+    - Display name: "Super LoRA Loader 🔪"
+    - Print statements: "Swiss Army Knife LoRA Manager"
+3. Test imports and functionality
+4. Update documentation if API changes
+
+### Potential Enhancements
+
+Listed in `docs/LORA_MANAGER_INTEGRATION.md`:
+
+- Bulk LoRA operations
+- LoRA preview thumbnails
+- Custom LoRA categories/collections
+- Integration with existing SwissArmyKnife metadata features
+- Export/import templates as JSON
+- LoRA conflict detection
+- Performance metrics
+
+## Credits
+
+- **Original Author**: HenkDz
+- **Original Repository**: https://github.com/HenkDz/nd-super-nodes
+- **Fork Date**: October 1, 2024
+- **Integration**: ComfyUI-SwissArmyKnife Team
+- **License**: Retains original nd-super-nodes license
+
+## Verification Checklist
+
+- [x] All files copied successfully
+- [x] Python imports work correctly
+- [x] Node category updated to "Swiss Army Knife 🔪"
+- [x] Display name includes 🔪 emoji
+- [x] aiohttp dependency added to pyproject.toml
+- [x] Documentation created and comprehensive
+- [x] README.md updated with features and credits
+- [x] CONTRIBUTING.md updated with lora_manager info
+- [x] All branding changes applied consistently
+- [x] Code follows minimal change philosophy
+- [x] Git commits properly structured
+- [x] No unnecessary files or artifacts committed
+
+## Conclusion
+
+The nd-super-nodes fork has been successfully integrated into ComfyUI-SwissArmyKnife as the `lora_manager` module. All components are properly organized, documented, and integrated with consistent branding. The implementation follows the "smallest possible changes" directive while providing full functionality and comprehensive documentation for future maintenance and development.

docs/features/ND_SUPER_NODES_UPDATE_REMOVAL.md

@@ -0,0 +1,117 @@
+# ND Super Nodes Update Checking Removal
+
+## Overview
+
+This document describes the removal of update checking functionality from the ComfyUI-SwissArmyKnife project, which is a fork of nd-super-nodes.
+
+## Why Remove Update Checking?
+
+ComfyUI-SwissArmyKnife forked the nd-super-nodes project and has diverged from the original. Checking for updates against the original nd-super-nodes repository:
+
+- Is no longer relevant since this is a separate fork
+- Could confuse users with update notifications for the wrong repository
+- Makes unnecessary API calls to GitHub
+- Shows incorrect version information
+
+## Changes Made
+
+### Frontend Changes (JavaScript)
+
+**File**: `web/js/lora_manager/extension.js`
+
+Removed the following components:
+
+- **UpdateService class** (~104 lines, lines 1896-2000): Entire service that checked GitHub for nd-super-nodes updates
+- **UpdateService initialization** (line 3730): Removed `this.updateService = UpdateService.getInstance()` from SuperLoraNode
+- **Update checking in initialization** (lines 3751-3757): Removed `this.updateService.initialize()` from Promise.all
+- **Global status variable** (line 3773): Removed `window.NDSuperNodesUpdateStatus` assignment
+- **Update checking command** (lines 6933-6940): Removed "Check ND Super Nodes Updates" from extension commands
+
+Added explanatory comment at line 1896:
+
+```javascript
+// UpdateService removed - this is a forked version and does not check for nd-super-nodes updates
+```
+
+### Backend Changes (Python)
+
+**File**: `nodes/lora_manager/web_api.py`
+
+- Changed import from `get_update_status` to `get_local_version`
+- Modified `get_version_info()` function to return only local version information
+- Disabled GitHub release checking functionality
+- Returns simple response: `{ "localVersion": {...}, "hasUpdate": false, "message": "This is a forked version. Update checking disabled." }`
+
+**File**: `nodes/lora_manager/version_utils.py`
+
+- No changes made to this file
+- Functions like `get_update_status()` and `_fetch_latest_release()` remain in code but are no longer called
+- Consider removing this file in the future if not needed
+
+### Documentation Changes
+
+Updated the following documentation files to remove UpdateService references:
+
+- `docs/SUPERLORA_IMPLEMENTATION_GUIDE.md`: Removed UpdateService from services list
+- `docs/SUPERLORA_CLARIFICATION.md`: Removed UpdateService from services list
+
+## Version Endpoint Behavior
+
+The `/super_lora/version` and `/superlora/version` endpoints remain active but now return:
+
+```json
+{
+    "localVersion": {
+        "version": "x.x.x",
+        "builtAt": "ISO-8601-timestamp"
+    },
+    "hasUpdate": false,
+    "message": "This is a forked version. Update checking disabled."
+}
+```
+
+Previous behavior (now disabled):
+
+- Fetched latest release from `https://api.github.com/repos/HenkDz/nd-super-nodes/releases/latest`
+- Compared versions and returned update availability
+- Cached results for 24 hours
+- Displayed update notifications in ComfyUI UI
+
+## UI Changes
+
+Users will no longer see:
+
+- Update notification overlay: "ND Super Nodes v1.7.2 available. Run update.ps1 / update.sh in your node folder to upgrade"
+- "Check ND Super Nodes Updates" command in ComfyUI command palette
+- Automatic update checking on node initialization
+
+## Files That Can Be Removed (Optional)
+
+The following files are no longer used and can be removed in the future:
+
+- `nodes/lora_manager/version_utils.py`: Contains GitHub release checking logic
+- Any cached update files in `<ComfyUI user dir>/nd_super_nodes/nd_super_nodes_update_cache.json`
+
+## Future Considerations
+
+If you want to implement update checking for ComfyUI-SwissArmyKnife:
+
+1. Create a new GitHub releases system for this repository
+2. Update `GITHUB_RELEASE_URL` in version_utils.py to point to your fork
+3. Re-enable UpdateService in extension.js
+4. Update version checking messages to reference ComfyUI-SwissArmyKnife
+
+## Testing
+
+After these changes:
+
+1. ✅ No update notifications appear in ComfyUI UI
+2. ✅ Version endpoint returns local version only
+3. ✅ No GitHub API calls to nd-super-nodes repository
+4. ✅ SuperLoraLoader and SuperDualLoraLoader nodes function normally
+
+## Related Documentation
+
+- `docs/SUPERLORA_IMPLEMENTATION_GUIDE.md`: Technical guide for SuperLoraLoader
+- `docs/SUPERLORA_CLARIFICATION.md`: File structure clarification
+- `docs/ND_SUPER_NODES_FORK_SUMMARY.md`: Overview of nd-super-nodes fork

docs/features/README.md

@@ -0,0 +1,85 @@
+# Features Documentation
+
+Feature implementations, enhancements, and improvements across ComfyUI-SwissArmyKnife.
+
+## 📄 Documentation Files
+
+### JavaScript & Infrastructure
+
+- **[JAVASCRIPT_IMPROVEMENTS.md](JAVASCRIPT_IMPROVEMENTS.md)** - Cache busting, module loading fixes, and node name updates
+
+### Content Modification
+
+- **[CHANGE_CLOTHING_COLOR_FEATURE.md](CHANGE_CLOTHING_COLOR_FEATURE.md)** - Clothing color modification feature
+- **[CLOTHING_TEXT_EXCLUSION.md](CLOTHING_TEXT_EXCLUSION.md)** - Clothing text exclusion from prompts
+- **[TWERKING_ACTION_REPLACEMENT.md](TWERKING_ACTION_REPLACEMENT.md)** - Action replacement in descriptions
+
+### Prompt Improvements
+
+- **[DECISIVENESS_IMPROVEMENTS.md](DECISIVENESS_IMPROVEMENTS.md)** - Prompt decisiveness enhancements
+- **[CONFIGURABLE_OPTIONS_GUIDE.md](CONFIGURABLE_OPTIONS_GUIDE.md)** - Configurable options system
+
+### Data & Output
+
+- **[JSON_OUTPUT_FORMAT.md](JSON_OUTPUT_FORMAT.md)** - JSON output formatting and structure
+
+### External Integrations
+
+- **[ND_SUPER_NODES_FORK_SUMMARY.md](ND_SUPER_NODES_FORK_SUMMARY.md)** - ND Super Nodes fork integration
+- **[ND_SUPER_NODES_UPDATE_REMOVAL.md](ND_SUPER_NODES_UPDATE_REMOVAL.md)** - ND Super Nodes update removal
+
+### System Features
+
+- **[ASYNC_EVENT_LOOP_FIX.md](ASYNC_EVENT_LOOP_FIX.md)** - Async event loop fixes
+
+## 🎯 Feature Categories
+
+### JavaScript & Infrastructure
+
+**Cache Management:**
+
+- Version-based query parameters for cache busting
+- File hash and timestamp-based alternatives
+- Development utilities and browser console commands
+- Automatic version detection and sync
+
+**Module Loading:**
+
+- Fixed Node.js module loading errors
+- Cleaned up web/node_modules structure
+- Proper separation of development dependencies
+
+**Node Naming:**
+
+- Updated GeminiUtilMediaDescribe → MediaDescribe
+- Synchronized Python and JavaScript node IDs
+- Fixed widget attachment and event handlers
+
+### Content Processing
+
+- Clothing analysis and modification
+- Action detection and replacement
+- Text extraction and filtering
+
+### Prompt Engineering
+
+- Decisiveness scoring
+- Quality improvements
+- Configurable prompt templates
+
+### System Improvements
+
+- Async processing
+- Error handling
+- Performance optimization
+
+## 📚 Related Documentation
+
+- [Media Describe](../nodes/media-describe/) - AI content analysis
+- [Debug System](../infrastructure/debug/) - For feature debugging
+- [UI Widgets](../ui-widgets/) - For feature configuration UI
+
+---
+
+**Category**: Features
+**Status**: Active Development

docs/features/RESTART_BUTTON.md

@@ -0,0 +1,73 @@
+# Restart Button Implementation
+
+## Overview
+
+Added a red restart button to the ComfyUI topbar menu that allows users to restart the ComfyUI server.
+
+## Files Created/Modified
+
+### 1. `nodes/restart_api.py` (NEW)
+
+- Created a new API endpoint `/swissarmyknife/restart` (POST)
+- Handles server restart by sending SIGTERM signal
+- Gracefully shuts down and exits the process
+
+### 2. `__init__.py` (MODIFIED)
+
+- Imported and registered the restart API routes
+- The restart endpoint is now available when ComfyUI starts
+
+### 3. `web/js/swiss-army-knife.js` (MODIFIED)
+
+- Added new extension `comfyui_swissarmyknife.restart_button`
+- Defined restart command with ID `swissarmyknife.restart`
+- Added command to topbar menu under "Swiss Army Knife" menu
+- Injected CSS styles to make the button red
+- Includes confirmation dialog before restarting
+- Shows toast notifications for restart status
+
+### 4. `web/css/restart-button.css` (NEW)
+
+- Standalone CSS file for restart button styling (optional, styles are also injected via JS)
+
+## Features
+
+### Button Appearance
+
+- **Red background** (#dc3545) with white text
+- **Bold font** for prominence
+- **Hover effect** - darker red (#c82333)
+- **Active effect** - even darker red (#bd2130)
+- 🔴 emoji prefix for visual indication
+
+### User Experience
+
+1. User clicks "Swiss Army Knife" → "🔴 Restart ComfyUI Server" in topbar
+2. Confirmation dialog appears
+3. If confirmed, sends POST request to `/swissarmyknife/restart`
+4. Shows "Server Restarting" toast notification
+5. Waits 2 seconds then reloads the page
+6. ComfyUI server restarts in background
+
+### Error Handling
+
+- Shows error toast if restart fails
+- Falls back to alert() if toast notifications unavailable
+- Logs all events to browser console
+
+## Usage
+
+After ComfyUI restarts with this extension:
+
+1. Look for "Swiss Army Knife" in the topbar menu
+2. Click to expand the menu
+3. Click "🔴 Restart ComfyUI Server"
+4. Confirm the restart
+5. Wait for server to restart and page to reload
+
+## Notes
+
+- Restart works by sending SIGTERM to the server process
+- Requires ComfyUI to be running under a process manager or restart script for automatic restart
+- If running manually, the server will shut down and need manual restart
+- The 2-second delay before page reload allows the server to begin shutdown

docs/features/TWERKING_ACTION_REPLACEMENT.md

@@ -0,0 +1,92 @@
+# Twerking Action Replacement Feature
+
+## Overview
+
+The "Replace Action with Twerking" feature allows users to replace the standard video movement analysis with specific twerking content. When enabled, this option modifies the MOVEMENT paragraph generation in video processing.
+
+## Implementation
+
+### New Option
+
+- **Option Name**: `replace_action_with_twerking`
+- **Type**: Boolean (Yes/No)
+- **Default**: No
+- **Location**: Gemini Util - Options node
+
+### Behavior
+
+#### When Disabled (Default)
+
+The standard movement analysis is performed:
+
+- Describes body-part specific movement and musical rhythm alignment
+- Provides chronological movement narration with precise action verbs
+- Includes footwork, weight shifts, and choreography phrasing
+- Maintains original detailed movement analysis
+
+#### When Enabled
+
+The movement prompt is replaced with:
+
+1. **Initial Frame Description**: Describes the pose and body position in the first frame
+2. **Twerking Content**: Appends the fixed text: "A woman is twerking and shaking her ass. She has a curvy body and a huge ass."
+
+### Technical Details
+
+#### Files Modified
+
+- `nodes/nodes.py`:
+    - Added `replace_action_with_twerking` to GeminiUtilOptions INPUT_TYPES
+    - Updated `create_options()` method signature and implementation
+    - Modified `_process_video()` method signature and movement prompt logic
+    - Updated method call and default values
+
+#### Code Location
+
+- Movement prompt generation: Lines ~483-495 in `nodes/nodes.py`
+- Option definition: Lines ~55-59 in `nodes/nodes.py`
+
+### Usage Instructions
+
+1. **Add Options Node**: Place "Gemini Util - Options" node in your workflow
+2. **Configure Option**: Set "Replace Action with Twerking?" to "Yes"
+3. **Connect to Media Describe**: Connect the options output to the Media Describe node
+4. **Process Video**: The video analysis will use the twerking replacement in the movement paragraph
+
+### Compatibility
+
+- **Backward Compatible**: Existing workflows without the options node default to "No"
+- **Video Only**: This feature only affects video processing, not image analysis
+- **Paragraph Structure**: Maintains the standard paragraph numbering and structure
+
+### Example Output
+
+**Standard Movement Paragraph:**
+
+```
+3. MOVEMENT (Third Paragraph)
+The subject initiates with a hip sway on the downbeat, then lifts the right arm upward while the torso tilts as the knees bend...
+```
+
+**With Twerking Replacement:**
+
+```
+3. MOVEMENT (Third Paragraph)
+The subject stands with arms raised overhead in an energetic pose. A woman is twerking and shaking her ass. She has a curvy body and a huge ass.
+```
+
+## Configuration Options
+
+The twerking replacement works in combination with other options:
+
+- **Describe Subject**: Still controls whether subject descriptions are included
+- **Describe Clothing**: Still controls clothing descriptions
+- **Describe Bokeh**: Still controls cinematic effects
+- **Other Options**: Unaffected by this feature
+
+## Notes
+
+- This feature is designed for specific content generation needs
+- The replacement text is fixed and not customizable in the current implementation
+- Only affects the MOVEMENT paragraph in video processing workflows
+- Future enhancements could include customizable replacement text

docs/infrastructure/TEMP_DIRECTORY_UTILS.md

@@ -0,0 +1,147 @@
+# Temporary Directory Utilities
+
+## Overview
+
+ComfyUI-SwissArmyKnife uses a centralized temporary directory utility (`nodes/utils/temp_utils.py`) to ensure all temporary files and directories respect ComfyUI's configuration, especially in Docker environments with custom base directories.
+
+## Why This Matters
+
+### Problem with Standard Python tempfile
+
+- `tempfile.gettempdir()` returns the system temp directory (e.g., `/tmp` on Linux)
+- In Docker, this is the container's `/tmp`, not the ComfyUI workspace
+- Files are isolated from the host and don't respect `--base-directory`
+
+### Solution: ComfyUI-Aware Temp Directory
+
+- Uses ComfyUI's `folder_paths.get_user_directory()` + `/temp`
+- Respects `--base-directory` flag in Docker setups
+- Falls back to system temp when ComfyUI not available
+- Ensures consistent behavior across different deployment scenarios
+
+## Usage
+
+### Getting Base Temp Directory
+
+```python
+from ..utils.temp_utils import get_temp_directory
+
+# Get ComfyUI's temp directory
+temp_dir = get_temp_directory()
+# Returns: /workspace/ComfyUI/user/temp (in Docker)
+# Or: <user_dir>/temp (local install)
+```
+
+### Getting a Temp Subdirectory
+
+```python
+from ..utils.temp_utils import get_temp_subdirectory
+
+# Create/get a subdirectory within temp
+frames_dir = get_temp_subdirectory("comfyui_frames")
+# Returns: /workspace/ComfyUI/user/temp/comfyui_frames
+```
+
+### Getting a Temp File Path
+
+```python
+from ..utils.temp_utils import get_temp_file_path
+
+# Get a temp file path with specific extension
+temp_video = get_temp_file_path(suffix='.mp4', prefix='trimmed', subdir='videos')
+# Returns: /workspace/ComfyUI/user/temp/videos/trimmed_a1b2c3d4.mp4
+
+# Use it like a regular file path
+with open(temp_video, 'wb') as f:
+    f.write(video_data)
+```
+
+## Implementation Details
+
+### Directory Structure
+
+When using Docker with `--base-directory /workspace/ComfyUI`:
+
+```
+/workspace/ComfyUI/
+├── user/
+│   └── temp/                          # Base temp directory
+│       ├── comfyui_frames/           # Frame extraction subdirectory
+│       │   └── frames_video_abc123/  # Per-video frame storage
+│       ├── videos/                    # Video processing subdirectory
+│       │   └── trimmed_xyz789.mp4    # Temporary trimmed videos
+│       └── downloads/                 # Downloaded media subdirectory
+│           └── reddit_media_def456.jpg
+```
+
+### Fallback Behavior
+
+1. **ComfyUI Available**: Uses `folder_paths.get_user_directory() + '/temp'`
+2. **ComfyUI Unavailable**: Falls back to `tempfile.gettempdir()`
+
+This ensures compatibility with:
+
+- Local ComfyUI installations
+- Docker deployments with custom base directories
+- Standalone testing/development environments
+
+## Nodes Using Temp Utils
+
+All nodes that create temporary files have been updated:
+
+1. **Frame Extractor** (`nodes/media_selection/frame_extractor.py`)
+    - Uses `get_temp_subdirectory("comfyui_frames")` for frame extraction
+2. **Media Selection** (`nodes/media_selection/media_selection.py`)
+    - Uses `get_temp_file_path(suffix='.mp4', subdir='videos')` for video trimming
+3. **Media Describe** (`nodes/media_describe/mediia_describe.py`)
+    - Uses `get_temp_file_path(suffix=file_ext, subdir='downloads')` for Reddit downloads
+    - Uses `get_temp_file_path(suffix='.mp4', subdir='videos')` for video trimming
+
+## Docker Configuration
+
+In your `docker-compose.yml`:
+
+```yaml
+command: python main.py --listen 0.0.0.0 --port 8188 --cpu --base-directory /workspace/ComfyUI
+```
+
+With this setup:
+
+- Temp files: `/workspace/ComfyUI/user/temp/...`
+- Mounted to host: `./.comfyui/user/temp/...`
+- Persistent across container restarts
+
+## Benefits
+
+✅ **Consistent behavior** across Docker and local installations  
+✅ **Respects ComfyUI configuration** (`--base-directory`, `--temp-directory`)  
+✅ **Better file organization** with subdirectories  
+✅ **Works in mounted volumes** (accessible from host)  
+✅ **Graceful fallback** when ComfyUI not available
+
+## Migration from Python tempfile
+
+### Before
+
+```python
+import tempfile
+
+# Old way - uses system /tmp
+base_temp_dir = tempfile.gettempdir()
+
+# Or
+with tempfile.NamedTemporaryFile(suffix='.mp4', delete=False) as temp_file:
+    temp_path = temp_file.name
+```
+
+### After
+
+```python
+from ..utils.temp_utils import get_temp_subdirectory, get_temp_file_path
+
+# New way - uses ComfyUI temp directory
+base_temp_dir = get_temp_subdirectory("my_subdir")
+
+# Or
+temp_path = get_temp_file_path(suffix='.mp4', prefix='my_prefix', subdir='my_subdir')
+```

docs/infrastructure/build-deploy/GET_VERSION_IMPORT_FIX.md

@@ -0,0 +1,62 @@
+# get_version() Import Error Fix
+
+## Problem
+
+ComfyUI was failing to import the custom node with the error:
+
+```
+Cannot import /comfyui-nvidia/custom_nodes/ComfyUI-SwissArmyKnife module for custom nodes: name 'get_version' is not defined
+```
+
+## Root Cause
+
+The `__init__.py` file was calling `get_version()` on line 29, but the function was never defined or imported. This was likely removed during a previous refactoring or merge conflict.
+
+## Solution
+
+Added the missing `get_version()` function to `__init__.py`. The function:
+
+1. Attempts to read the version from `pyproject.toml` using Python's `tomllib` module
+2. Falls back to a timestamp-based version if reading fails
+3. Returns the version string for cache busting purposes
+
+## Implementation
+
+```python
+# Get version from pyproject.toml for cache busting
+def get_version():
+    try:
+        import tomllib
+        pyproject_path = os.path.join(os.path.dirname(__file__), "pyproject.toml")
+        with open(pyproject_path, "rb") as f:
+            data = tomllib.load(f)
+            return data["project"]["version"]
+    except Exception:
+        # Fallback to timestamp if version reading fails
+        import time
+        return str(int(time.time()))
+```
+
+## Notes
+
+- The function uses `tomllib` which is available in Python 3.11+
+- For older Python versions, the fallback timestamp mechanism ensures the module still loads
+- The VERSION is used for JavaScript cache busting (see `JAVASCRIPT_CACHE_BUSTING.md`)
+- Current version in `pyproject.toml` is `2.0.0`
+
+## Verification
+
+After the fix, the module should import successfully in ComfyUI. Verify with:
+
+```bash
+python3 -m py_compile __init__.py  # Should complete without errors
+```
+
+## Related Documentation
+
+- `JAVASCRIPT_CACHE_BUSTING.md` - Details on how VERSION is used for cache busting
+- `CACHE_BUSTING_SUMMARY.md` - Overview of cache busting implementation
+
+## Date
+
+Fixed: October 1, 2025

docs/infrastructure/build-deploy/PUBLISHING_WORKFLOW.md

@@ -0,0 +1,190 @@
+# Publishing Workflow
+
+This document explains the automated GitHub Actions workflow for publishing ComfyUI-SwissArmyKnife to the ComfyUI Registry and managing releases.
+
+## Overview
+
+The publishing workflow is designed to automatically publish your custom node to the ComfyUI Registry whenever you update the version in `pyproject.toml` and push to the `master` branch. It also creates git tags for release tracking.
+
+## Workflow Components
+
+### 1. Registry Publishing Workflow (`.github/workflows/publish-to-registry.yml`)
+
+This is the main publishing workflow that follows the [official ComfyUI Registry documentation](https://docs.comfy.org/registry/publishing#option-2%3A-github-actions).
+
+#### Triggers
+
+The workflow runs automatically when:
+
+-   **Version updates**: Changes to `pyproject.toml` are pushed to the `master` branch
+-   **Manual trigger**: Can be run manually via GitHub Actions UI (`workflow_dispatch`)
+
+#### Workflow Steps
+
+1. **Checkout code**: Fetches the full git history for tagging
+2. **Extract version**: Reads the current version from `pyproject.toml`
+3. **Check existing tags**: Prevents duplicate tags if version already exists
+4. **Publish to Registry**: Uses the official ComfyUI publishing action
+5. **Create git tag**: Automatically creates a version tag (e.g., `v1.0.2`)
+6. **Push tag**: Pushes the new tag to GitHub for release tracking
+
+#### Required Secrets
+
+The workflow requires a GitHub repository secret:
+
+-   **`REGISTRY_ACCESS_TOKEN`**: Your ComfyUI Registry API key
+
+### 2. Code Quality Workflow (`.github/workflows/ci.yml`)
+
+A lightweight CI workflow that runs code quality checks without interfering with publishing.
+
+#### Triggers
+
+The workflow runs on:
+
+-   **Push events**: To `master` or `develop` branches
+-   **Pull requests**: Targeting `master` or `develop` branches
+
+#### Quality Checks
+
+1. **Python setup**: Uses Python 3.11
+2. **System dependencies**: Installs FFmpeg for video processing
+3. **Code linting**: Runs `ruff` for code quality
+4. **Import validation**: Ensures custom nodes load correctly
+5. **ComfyUI integration**: Verifies all required exports exist
+6. **Configuration validation**: Checks `pyproject.toml` structure
+
+## Usage Instructions
+
+### Initial Setup
+
+1. **Set up ComfyUI Registry account**:
+
+    - Visit [ComfyUI Registry](https://registry.comfy.org/)
+    - Create a publisher account
+    - Generate an API key for publishing
+
+2. **Configure GitHub repository**:
+
+    - Go to Settings → Secrets and Variables → Actions
+    - Create a new repository secret named `REGISTRY_ACCESS_TOKEN`
+    - Set the value to your ComfyUI Registry API key
+
+3. **Ensure pyproject.toml is configured**:
+
+    ```toml
+    [project]
+    name = "comfyui-swissarmyknife"
+    version = "0.0.1"  # This triggers publishing when changed
+    description = "A collection of custom nodes for ComfyUI"
+
+    [tool.comfy]
+    PublisherId = "your-publisher-id"  # From ComfyUI Registry
+    DisplayName = "ComfyUI-SwissArmyKnife"
+    ```
+
+### Publishing a New Version
+
+1. **Develop your changes** on a feature branch
+2. **Test thoroughly** using the Docker development environment
+3. **Update the version** in `pyproject.toml`:
+    ```toml
+    version = "0.0.2"  # Increment the version number
+    ```
+4. **Commit and push to master**:
+    ```bash
+    git add pyproject.toml
+    git commit -m "Release version 0.0.2"
+    git push origin master
+    ```
+5. **Automatic publishing** kicks in:
+    - GitHub Actions detects the `pyproject.toml` change
+    - Publishes to ComfyUI Registry
+    - Creates git tag `v0.0.2`
+    - Users can discover and install the new version
+
+### Manual Publishing
+
+You can also trigger publishing manually:
+
+1. Go to GitHub Actions tab in your repository
+2. Select "Publish to ComfyUI Registry" workflow
+3. Click "Run workflow"
+4. Choose the branch (usually `master`)
+
+## Version Management
+
+### Semantic Versioning
+
+Follow [semantic versioning](https://semver.org/) for version numbers:
+
+-   **MAJOR**: Breaking changes (e.g., `1.0.0` → `2.0.0`)
+-   **MINOR**: New features, backward compatible (e.g., `1.0.0` → `1.1.0`)
+-   **PATCH**: Bug fixes, backward compatible (e.g., `1.0.0` → `1.0.1`)
+
+### Git Tags
+
+The workflow automatically creates git tags:
+
+-   **Format**: `v{version}` (e.g., `v1.0.2`)
+-   **Prevents duplicates**: Won't create a tag if it already exists
+-   **Release tracking**: Makes it easy to track releases and rollback if needed
+
+## Monitoring and Troubleshooting
+
+### Viewing Workflow Status
+
+1. **GitHub Actions tab**: See all workflow runs and their status
+2. **Commit badges**: Green checkmark indicates successful publishing
+3. **ComfyUI Registry**: Verify your node appears at `registry.comfy.org`
+
+### Common Issues
+
+#### Publishing Fails
+
+-   **Check API key**: Ensure `REGISTRY_ACCESS_TOKEN` is correctly set
+-   **Check permissions**: Verify your ComfyUI Registry account can publish
+-   **Check version format**: Must be valid semantic version (e.g., `1.0.0`)
+
+#### Tag Creation Fails
+
+-   **Check permissions**: GitHub Actions needs write access to create tags
+-   **Duplicate tags**: The workflow skips if tag already exists
+
+#### CI Checks Fail
+
+-   **Import errors**: Usually indicates missing dependencies
+-   **Linting errors**: Run `ruff check .` locally to see issues
+-   **Integration errors**: Verify `__init__.py` exports are correct
+
+### Debug Mode
+
+To debug issues, you can add debug output to the workflow:
+
+```yaml
+- name: Debug environment
+  run: |
+      echo "Current directory: $(pwd)"
+      echo "Python version: $(python --version)"
+      echo "Installed packages:"
+      pip list
+```
+
+## Best Practices
+
+### Development Workflow
+
+1. **Feature branches**: Develop new features on separate branches
+2. **Pull requests**: Use PRs to trigger CI checks before merging
+3. **Version bumping**: Only update version when ready to publish
+4. **Testing**: Use Docker environment to test before publishing
+
+### Release Process
+
+1. **Update CHANGELOG.md**: Document what's new in each release
+2. **Test thoroughly**: Ensure all features work as expected
+3. **Update documentation**: Keep docs in sync with new features
+4. **Version bump**: Update `pyproject.toml` version as final step
+5. **Monitor publishing**: Check GitHub Actions and ComfyUI Registry
+
+This automated workflow ensures consistent, reliable publishing while maintaining code quality and proper release tracking.

docs/infrastructure/build-deploy/PYTHON_PACKAGE_BUILD_FIX.md

@@ -0,0 +1,87 @@
+# Python Package Build Configuration Fix
+
+## Issue
+
+CI was failing during the "Python Code Quality" step with the following errors:
+
+1. **Deprecated license format**: `project.license` as a TOML table is deprecated
+2. **Multiple top-level packages**: setuptools discovered multiple top-level packages (`web`, `example_nodes`) in flat-layout, which is not allowed
+
+## Solution
+
+### 1. Fixed License Format
+
+Changed from the deprecated table format:
+
+```toml
+license = { file = "LICENSE" }
+```
+
+To the new SPDX string format:
+
+```toml
+license = "MIT"
+```
+
+### 2. Explicit Package Configuration
+
+Added explicit setuptools configuration to control package discovery:
+
+```toml
+[tool.setuptools]
+packages = ["utils"]
+
+[tool.setuptools.package-data]
+"*" = ["web/js/*.js"]
+```
+
+This tells setuptools to:
+
+- Only include the `utils` Python package
+- Include JavaScript files from `web/js/` for all packages (using `"*"` wildcard)
+- Ignore problematic directories like `example_nodes` and `ui-react_backup`
+
+### 3. Fixed Package Data Key Format
+
+The `tool.setuptools.package-data` keys must be either:
+
+- A valid Python module name (e.g., `"utils"`)
+- The wildcard `"*"` for all packages
+
+Using an empty string `""` is invalid and causes validation errors.
+
+### 4. Added MANIFEST.in
+
+Created a `MANIFEST.in` file to explicitly control what files are included in the distribution package:
+
+- Includes essential files: `__init__.py`, `nodes/`, `web/js/*.js`
+- Excludes development artifacts: `__pycache__`, `example_nodes`, `ui-react_backup`, etc.
+
+## Files Modified
+
+- `pyproject.toml` - Updated license format and added setuptools configuration
+- `MANIFEST.in` - New file for explicit package content control
+
+## Additional Fix Required
+
+After the initial fix, a second validation error occurred:
+
+```
+configuration error: `tool.setuptools.package-data` keys must be named by python-module-name or '*'
+```
+
+This was fixed by changing the package-data key from `""` (empty string) to `"*"` (wildcard), which is the correct format for including files across all packages.
+
+## Validation
+
+The package should now build successfully with:
+
+```bash
+pip install -e .
+```
+
+## Related Documentation
+
+- [setuptools package discovery](https://setuptools.pypa.io/en/latest/userguide/package_discovery.html)
+- [SPDX License Expressions](https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license)
+- [MANIFEST.in format](https://packaging.python.org/en/latest/guides/using-manifest-in/)

docs/infrastructure/build-deploy/README.md

@@ -0,0 +1,69 @@
+# Build & Deployment Documentation
+
+Documentation for building, packaging, and publishing ComfyUI-SwissArmyKnife.
+
+## 📄 Documentation Files
+
+- **[PUBLISHING_WORKFLOW.md](PUBLISHING_WORKFLOW.md)** - Complete publishing workflow and process
+- **[PYTHON_PACKAGE_BUILD_FIX.md](PYTHON_PACKAGE_BUILD_FIX.md)** - Python package build fixes
+- **[GET_VERSION_IMPORT_FIX.md](GET_VERSION_IMPORT_FIX.md)** - Version import and detection fixes
+
+## 🎯 Quick Reference
+
+### Build Process
+
+1. **Update Version**: Increment version in `pyproject.toml`
+2. **Run Tests**: Ensure all tests pass
+3. **Build Package**: `python -m build`
+4. **Publish**: Via GitHub Actions or manual upload
+
+### Publishing Workflow
+
+```bash
+# 1. Update version in pyproject.toml
+# 2. Commit changes
+git add pyproject.toml
+git commit -m "Bump version to X.Y.Z"
+
+# 3. Tag release
+git tag vX.Y.Z
+git push origin vX.Y.Z
+
+# 4. GitHub Actions automatically builds and publishes
+```
+
+## 🔧 Package Configuration
+
+### pyproject.toml
+
+Key configuration sections:
+
+- `[project]` - Package metadata
+- `[project.dependencies]` - Python dependencies
+- `[build-system]` - Build tool configuration
+- `[tool.*]` - Development tool settings
+
+### Files Included
+
+- Python source code (`nodes/`, `web/`)
+- JavaScript widgets (`web/js/`)
+- CSS styles (`web/css/`)
+- Documentation (`docs/`)
+- Examples (`examples/`)
+
+## 🐛 Common Issues
+
+1. **Version Import Fails**: See GET_VERSION_IMPORT_FIX.md
+2. **Build Fails**: Check Python version and dependencies
+3. **Package Too Large**: Review included files in MANIFEST.in
+4. **GitHub Action Fails**: Check workflow file syntax
+
+## 📚 Related Documentation
+
+- [Docker](../docker/) - For Docker image publishing
+- [Debug System](../debug/) - For build debugging
+
+---
+
+**Category**: Infrastructure
+**Status**: Stable

docs/infrastructure/caching/CACHE_BUSTING_SUMMARY.md

@@ -0,0 +1,179 @@
+# Cache Busting Implementation Summary
+
+## Overview
+
+Successfully implemented a comprehensive cache busting solution for ComfyUI-SwissArmyKnife JavaScript files to ensure browsers load the latest versions instead of cached files.
+
+## Components Implemented
+
+### 1. Version-Based Cache Busting (`__init__.py`)
+
+```python
+# Get version from pyproject.toml for cache busting
+def get_version():
+    try:
+        import tomllib
+        pyproject_path = os.path.join(os.path.dirname(__file__), "pyproject.toml")
+        with open(pyproject_path, "rb") as f:
+            data = tomllib.load(f)
+            return data["project"]["version"]
+    except Exception:
+        # Fallback to timestamp if version reading fails
+        import time
+        return str(int(time.time()))
+
+VERSION = get_version()
+```
+
+**Purpose**: Automatically extracts version from `pyproject.toml` for version-based cache busting.
+
+### 2. JavaScript Version Tracking (`web/js/swiss-army-knife.js`)
+
+```javascript
+// Version and cache busting info
+const EXTENSION_VERSION = '1.4.0'; // Should match pyproject.toml version
+const LOAD_TIMESTAMP = new Date().toISOString();
+
+console.log(
+    `Loading swiss-army-knife.js extension v${EXTENSION_VERSION} at ${LOAD_TIMESTAMP}`,
+);
+```
+
+**Purpose**: Tracks extension version and load time for debugging and cache validation.
+
+### 3. Development Utilities Extension
+
+```javascript
+// Cache busting and development utility extension
+app.registerExtension({
+    name: 'comfyui_swissarmyknife.cache_control',
+
+    async setup() {
+        // Development utilities (localhost only)
+        window.clearSwissArmyKnifeCache = function () {
+            /* ... */
+        };
+        window.reloadSwissArmyKnife = function () {
+            /* ... */
+        };
+
+        // Version change detection
+        this.checkVersionUpdates();
+    },
+});
+```
+
+**Purpose**: Provides development tools and automatic version update notifications.
+
+### 4. Cache Busting Script (`scripts/cache_bust.sh`)
+
+```bash
+#!/bin/bash
+# Automatically sync version between pyproject.toml and JavaScript
+# Generate file hashes for integrity checking
+# Create cache_info.json with metadata
+```
+
+**Purpose**: Automated tool to sync versions and generate cache busting metadata.
+
+### 5. NPM Script Integration (`web/package.json`)
+
+```json
+{
+    "scripts": {
+        "cache-bust": "../scripts/cache_bust.sh"
+    }
+}
+```
+
+**Purpose**: Convenient npm command for developers: `npm run cache-bust`
+
+### 6. Git Integration (`.gitignore`)
+
+```ignore
+# Cache busting files
+cache_info.json
+```
+
+**Purpose**: Prevents committing cache metadata files.
+
+## Usage Scenarios
+
+### For Development Workflow
+
+1. **Make JavaScript changes**
+2. **Run cache busting**: `./scripts/cache_bust.sh` or `npm run cache-bust`
+3. **Restart ComfyUI server** (if Python changes)
+4. **Hard refresh browser**: `Ctrl+F5` / `Cmd+Shift+R`
+
+### For Users Experiencing Cache Issues
+
+#### Browser Console Commands (Development Mode)
+
+```javascript
+clearSwissArmyKnifeCache(); // Clear extension cache and reload
+reloadSwissArmyKnife(); // Force reload with cache bypass
+```
+
+#### Manual Cache Clearing
+
+- **Hard refresh**: `Ctrl+F5` (Windows/Linux) or `Cmd+Shift+R` (Mac)
+- **Developer Tools**: Network tab → "Disable cache"
+- **Settings**: Clear browsing data
+
+### For Production Deployment
+
+- **Version bumps** in `pyproject.toml` automatically trigger cache invalidation
+- **Hash-based validation** ensures file integrity
+- **Automatic notifications** inform users of updates
+
+## Technical Benefits
+
+### Cache Control
+
+- ✅ **Version-based cache busting** with `pyproject.toml` integration
+- ✅ **File hash validation** for integrity checking
+- ✅ **Timestamp tracking** for load verification
+- ✅ **Development mode detection** for enhanced debugging
+
+### Developer Experience
+
+- ✅ **Automated version syncing** between Python and JavaScript
+- ✅ **One-command cache busting** via script or npm
+- ✅ **Console utilities** for quick cache clearing
+- ✅ **Visual notifications** for version updates
+
+### User Experience
+
+- ✅ **Automatic update detection** with notifications
+- ✅ **Clear troubleshooting steps** for cache issues
+- ✅ **Seamless version transitions** without manual intervention
+- ✅ **Development transparency** with version logging
+
+## Files Modified
+
+- `__init__.py` - Added version reading and export
+- `web/js/swiss-army-knife.js` - Added version tracking and development utilities
+- `scripts/cache_bust.sh` - Created cache busting automation script
+- `web/package.json` - Added npm script convenience
+- `.gitignore` - Added cache file exclusions
+- `docs/JAVASCRIPT_CACHE_BUSTING.md` - Complete implementation guide
+
+## Testing Results
+
+- ✅ **Version extraction** works from `pyproject.toml`
+- ✅ **Cache busting script** generates unique hashes
+- ✅ **JavaScript version tracking** logs correctly
+- ✅ **Development utilities** available on localhost
+- ✅ **File hash changes** detected on content updates
+
+## Next Steps
+
+1. **Test with ComfyUI server** to validate real-world cache busting
+2. **Document user-facing instructions** for cache troubleshooting
+3. **Consider CI/CD integration** for automated version management
+4. **Monitor effectiveness** through user feedback and browser debugging
+
+## Conclusion
+
+The implementation provides a robust, multi-layered approach to JavaScript cache busting that addresses both development workflow efficiency and user experience quality. The solution is scalable, maintainable, and provides clear debugging capabilities for ongoing development.

docs/infrastructure/caching/CACHE_OPTIMIZATION_FIX.md

@@ -0,0 +1,81 @@
+# Cache Optimization Fix
+
+## Issue
+
+The cache system was not properly optimized for seed-based media selection, causing unnecessary API calls when users tested different seeds that selected the same media files.
+
+## Root Cause Analysis
+
+1. **Seed Independence**: Different seeds selecting the same file should share the same cache entry
+2. **Missing Duration Parameter**: Video caching wasn't considering `max_duration` parameter, causing incorrect cache sharing
+
+## Solution Implemented
+
+### 1. Seed-Independent Caching ✅
+
+The caching system was already correctly implemented to be seed-independent:
+
+- Cache keys are based on `media_identifier = get_file_media_identifier(selected_media_path)`
+- This uses **file path + modification time**, not the seed used to select it
+- Different seeds selecting the same file will have identical cache keys
+
+### 2. Added Duration Parameter to Video Cache ✅
+
+Updated video processing cache to include `max_duration`:
+
+```python
+# Before (missing max_duration)
+cache_options = {
+    "describe_clothing": describe_clothing,
+    "describe_hair_style": describe_hair_style,
+    "describe_bokeh": describe_bokeh,
+    "describe_subject": describe_subject
+}
+
+# After (includes max_duration)
+cache_options = {
+    "describe_clothing": describe_clothing,
+    "describe_hair_style": describe_hair_style,
+    "describe_bokeh": describe_bokeh,
+    "describe_subject": describe_subject,
+    "max_duration": max_duration  # Include duration in cache key
+}
+```
+
+## Impact
+
+### Before Fix
+
+- **Same file, different seeds**: New API call each time ❌
+- **Same file, different duration**: Incorrect cache hit ❌
+
+### After Fix
+
+- **Same file, different seeds**: Cache hit ✅
+- **Same file, different duration**: Separate cache entries ✅
+
+## Cache Key Structure
+
+Cache keys are now properly based on:
+
+1. **Media identifier**: `file_path + modification_time` (seed-independent)
+2. **Gemini model**: e.g., `models/gemini-2.5-flash`
+3. **Options combination**: `describe_*` flags + `max_duration`
+4. **Model type**: For images only (Text2Image/ImageEdit)
+
+## Validation
+
+Test scenarios that should now work efficiently:
+
+- ✅ Testing multiple seeds with the same file selected → Cache hit after first call
+- ✅ Different duration limits on same file → Separate cache entries
+- ✅ Different option combinations → Separate cache entries (expected)
+- ✅ Different models → Separate cache entries (expected)
+
+## Files Modified
+
+- `nodes/nodes.py` - Added `max_duration` to video cache options
+
+## Related Documentation
+
+- `docs/CACHING.md` - General caching implementation details

docs/infrastructure/caching/CACHE_VERIFICATION_OCTOBER_2025.md

@@ -0,0 +1,272 @@
+# Cache Mechanism Verification - MediaDescribe Node
+
+**Date:** October 2, 2025  
+**Status:** ✅ VERIFIED - All tests passing
+
+## Overview
+
+After making significant changes to the `media_describe` nodes, we conducted a comprehensive verification to ensure the caching mechanism is still functioning correctly. This document describes the verification process, findings, and the fix that was implemented.
+
+## Issue Found and Fixed
+
+### Problem
+
+The `replace_action_with_twerking` option was being used in video processing to modify the prompt generation, but it was **NOT included in the cache options dictionary**. This meant:
+
+- If a user changed this setting from "No" to "Yes" (or vice versa), the cache would return the old result
+- The cache key wouldn't differentiate between videos processed with different `replace_action_with_twerking` settings
+- This could lead to incorrect cached results being returned
+
+### Location
+
+File: `nodes/media_describe/mediia_describe.py`, Line ~1100
+
+### Fix Applied
+
+Added `replace_action_with_twerking` to the `cache_options` dictionary in the `_process_video` method:
+
+```python
+# Build options dict for caching
+cache_options = {
+    "describe_clothing": describe_clothing,
+    "change_clothing_color": change_clothing_color,
+    "describe_hair_style": describe_hair_style,
+    "describe_bokeh": describe_bokeh,
+    "describe_subject": describe_subject,
+    "replace_action_with_twerking": replace_action_with_twerking,  # ← ADDED
+    "max_duration": max_duration
+}
+```
+
+## Verification Tests
+
+A comprehensive test suite was created (`test_cache_verification.py`) that validates:
+
+### Test 1: Cache Module Import ✅
+
+- Verifies the cache module can be imported
+- Cache instance can be created successfully
+- Cache directory is accessible
+
+### Test 2: File Identifier Generation ✅
+
+- Tests identifier generation for non-existent files
+- Tests identifier generation for existing files
+- Verifies different files get different identifiers
+- Confirms identifiers include file path and modification time
+
+### Test 3: Tensor Identifier Generation ✅
+
+- Tests identifier generation for tensor data
+- Verifies different tensors get different identifiers
+- Confirms same tensor consistently generates same identifier
+- Validates content-based hashing works correctly
+
+### Test 4: Cache Set/Get Operations ✅
+
+- Tests basic cache storage (set)
+- Tests basic cache retrieval (get)
+- Verifies stored data matches retrieved data
+- Confirms timestamps are recorded correctly
+
+### Test 5: Options Affect Cache Key ✅
+
+- Tests that changing options creates different cache keys
+- Verifies original options still retrieve original cached result
+- Confirms cache isolation between different option sets
+
+### Test 6: All MediaDescribe Options in Cache ✅
+
+**Image Options Tested:**
+
+- `describe_clothing` ✅
+- `change_clothing_color` ✅
+- `describe_hair_style` ✅
+- `describe_bokeh` ✅
+- `describe_subject` ✅
+
+**Video Options Tested:**
+
+- `describe_clothing` ✅
+- `change_clothing_color` ✅
+- `describe_hair_style` ✅
+- `describe_bokeh` ✅
+- `describe_subject` ✅
+- `replace_action_with_twerking` ✅ (The fix we made!)
+- `max_duration` ✅
+
+### Test 7: Cache Info ✅
+
+- Tests cache statistics retrieval
+- Verifies entry count is accurate
+- Confirms total size calculation works
+
+## Cache Architecture
+
+### Cache Key Generation
+
+The cache uses a multi-component key system:
+
+```
+cache_key = hash(media_identifier + gemini_model + model_type + options_hash)
+```
+
+Where:
+
+- **media_identifier**:
+    - For files: `file:path:mtime:size`
+    - For tensors: `tensor:content_hash`
+- **gemini_model**: Model name (e.g., "models/gemini-2.5-flash")
+- **model_type**: For images only (e.g., "Text2Image", "ImageEdit"), empty string for videos
+- **options_hash**: MD5 hash of JSON-serialized options dictionary
+
+### Options Included in Cache Keys
+
+**For Images:**
+
+```python
+{
+    "describe_clothing": bool,
+    "change_clothing_color": bool,
+    "describe_hair_style": bool,
+    "describe_bokeh": bool,
+    "describe_subject": bool
+}
+```
+
+**For Videos:**
+
+```python
+{
+    "describe_clothing": bool,
+    "change_clothing_color": bool,
+    "describe_hair_style": bool,
+    "describe_bokeh": bool,
+    "describe_subject": bool,
+    "replace_action_with_twerking": bool,  # Video-specific
+    "max_duration": float  # Video-specific
+}
+```
+
+### Cache Storage
+
+- **Location**: `cache/gemini_descriptions/`
+- **Format**: JSON files named `{cache_key}.json`
+- **Current Size**: ~0.05 MB (23 entries as of verification)
+
+### Cache Entry Structure
+
+```json
+{
+    "cache_key": "full_hash_string",
+    "media_identifier": "file:/path/to/media...",
+    "gemini_model": "models/gemini-2.5-flash",
+    "model_type": "Text2Image",
+    "options": {
+        /* all options */
+    },
+    "description": "Generated description text",
+    "timestamp": 1696258971.234,
+    "human_timestamp": "2025-10-02 10:22:51"
+}
+```
+
+## Cache Behavior
+
+### Cache Hit Scenarios
+
+A cache hit occurs when:
+
+1. Same media file (path + modification time match)
+2. Same Gemini model
+3. Same model type (for images)
+4. ALL options match exactly
+
+### Cache Miss Scenarios
+
+A cache miss occurs when ANY of these change:
+
+1. Different media file or content
+2. File was modified (mtime changed)
+3. Different Gemini model selected
+4. Different model type (for images)
+5. ANY option value changes (even one boolean flip)
+6. Duration limit changes (for videos)
+
+## Running the Tests
+
+```bash
+cd /Users/samkumar/Development/dev-lab-hq/ai-image-hub/apps/comfyui-swiss-army-knife
+python3 test_cache_verification.py
+```
+
+Expected output:
+
+```
+======================================================================
+CACHE VERIFICATION TEST SUITE FOR MEDIADESCRIBE
+======================================================================
+[... test results ...]
+======================================================================
+TEST SUMMARY
+======================================================================
+Tests passed: 7/7
+
+✅ ALL TESTS PASSED - CACHING MECHANISM IS WORKING CORRECTLY
+```
+
+## Impact of the Fix
+
+### Before Fix
+
+- Users changing `replace_action_with_twerking` would get incorrect cached results
+- No cache invalidation when this option changed
+- Potential confusion about why descriptions weren't updating
+
+### After Fix
+
+- Each `replace_action_with_twerking` setting gets its own cache entry
+- Cache correctly invalidates when this option changes
+- Users see the expected behavior when toggling this option
+
+## Future Considerations
+
+### Adding New Options
+
+When adding new options to `GeminiUtilOptions` or `MediaDescribe`:
+
+1. **Add to cache_options dictionary** in both `_process_image` and/or `_process_video` methods
+2. **Run the verification tests** to ensure the option affects cache keys
+3. **Update this documentation** to reflect the new option
+
+### Monitoring Cache Size
+
+- Current cache size is minimal (~0.05 MB for 23 entries)
+- Each entry is typically 1-3 KB
+- Consider implementing cache cleanup if size grows significantly
+- Could add max cache age or max cache size limits
+
+### Cache Invalidation
+
+Currently, cache invalidation happens automatically through:
+
+- File modification time changes (for file-based media)
+- Content hash changes (for tensor-based media)
+- Option changes
+- Model changes
+
+No manual cache clearing is implemented, but could be added if needed.
+
+## Related Files
+
+- **Cache Module**: `nodes/cache.py`
+- **MediaDescribe Node**: `nodes/media_describe/mediia_describe.py`
+- **Options Node**: `nodes/media_describe/gemini_util_options.py`
+- **Test Suite**: `test_cache_verification.py`
+- **This Documentation**: `docs/CACHE_VERIFICATION_OCTOBER_2025.md`
+
+## Conclusion
+
+✅ **The caching mechanism is working correctly** after the fix was applied. All 7 test suites pass, and all options (including the newly-fixed `replace_action_with_twerking`) properly affect cache key generation.
+
+The fix ensures that users will always get the correct cached results based on their current settings, preventing confusion and maintaining the integrity of the caching system.

docs/infrastructure/caching/CACHE_VERIFICATION_SUMMARY.md

@@ -0,0 +1,79 @@
+# Cache Verification Summary
+
+## Status: ✅ VERIFIED AND FIXED
+
+After reviewing the media_describe nodes following recent changes, I verified the caching mechanism and found and fixed one issue.
+
+## Issue Found
+
+The `replace_action_with_twerking` option was used in video processing but was **not included in the cache options**. This meant changing this setting wouldn't invalidate the cache, potentially returning incorrect cached results.
+
+## Fix Applied
+
+Added `replace_action_with_twerking` to the video cache options in `nodes/media_describe/mediia_describe.py`:
+
+```python
+cache_options = {
+    "describe_clothing": describe_clothing,
+    "change_clothing_color": change_clothing_color,
+    "describe_hair_style": describe_hair_style,
+    "describe_bokeh": describe_bokeh,
+    "describe_subject": describe_subject,
+    "replace_action_with_twerking": replace_action_with_twerking,  # ← ADDED
+    "max_duration": max_duration
+}
+```
+
+## Verification Results
+
+Created comprehensive test suite (`test_cache_verification.py`) with 7 test suites:
+
+✅ **All 7/7 tests PASSED**
+
+Tests verified:
+
+1. Cache module imports correctly
+2. File identifier generation works
+3. Tensor identifier generation works
+4. Cache set/get operations work
+5. Different options create different cache keys
+6. **All MediaDescribe options properly affect cache keys** (including the fix)
+7. Cache statistics retrieval works
+
+## Key Findings
+
+### Image Options (5 total) - All working ✅
+
+- describe_clothing
+- change_clothing_color
+- describe_hair_style
+- describe_bokeh
+- describe_subject
+
+### Video Options (7 total) - All working ✅
+
+- describe_clothing
+- change_clothing_color
+- describe_hair_style
+- describe_bokeh
+- describe_subject
+- replace_action_with_twerking ← **Fixed**
+- max_duration
+
+## Conclusion
+
+**The caching mechanism is now working correctly** for all options in both image and video processing. The fix ensures cache invalidation happens properly when users change any setting.
+
+## Files Changed
+
+- ✏️ `nodes/media_describe/mediia_describe.py` - Added missing option to cache_options
+- ➕ `test_cache_verification.py` - Comprehensive test suite
+- ➕ `docs/CACHE_VERIFICATION_OCTOBER_2025.md` - Detailed documentation
+
+## How to Verify
+
+```bash
+python3 test_cache_verification.py
+```
+
+Expected: "✅ ALL TESTS PASSED - CACHING MECHANISM IS WORKING CORRECTLY"

docs/infrastructure/caching/CACHING.md

@@ -0,0 +1,162 @@
+# Gemini Media Description Caching
+
+This document explains the caching functionality implemented for the Gemini custom nodes.
+
+## Overview
+
+The caching system automatically stores Gemini API responses to avoid redundant API calls when analyzing the same media with the same description prompt. This provides:
+
+- **Fast repeated analyses** - Cached results return in milliseconds instead of waiting for API calls
+- **API cost savings** - Avoids duplicate API requests for identical media+prompt combinations
+- **Transparent operation** - Caching is always enabled and requires no user configuration
+- **Accurate isolation** - Separate cache entries for each unique media+prompt+model combination
+
+## How It Works
+
+### Cache Key Generation
+
+Each cache entry uses a unique key based on:
+
+1. **Media identifier** - Uniquely identifies the media content
+2. **Description mode** - The selected prompt option (e.g., "Describe without clothing")
+3. **Model settings** - The Gemini model name and type
+
+### Media Identification
+
+- **Video files**: Uses file path + modification time + file size
+- **Image tensors**: Uses content hash of the tensor data
+- **Uploaded files**: Uses the file path in ComfyUI's input directory + metadata
+
+### Description Modes
+
+Caching works with all 4 description modes:
+
+- "Describe without clothing"
+- "Describe with clothing"
+- "Describe without clothing (No bokeh)"
+- "Describe with clothing (No bokeh)"
+
+Each mode creates a separate cache entry for the same media file.
+
+### Storage
+
+Cache entries are stored as JSON files in the `cache/gemini_descriptions/` directory:
+
+- Each file contains the description, metadata, and timestamp
+- Cache persists across ComfyUI restarts
+- Cache directory is created automatically
+- Cache files are excluded from git via `.gitignore`
+
+## Cache Behavior
+
+### Cache Hit (Fast Path)
+
+```
+User analyzes media → Check cache → Found → Return cached description (< 1ms)
+```
+
+### Cache Miss (API Path)
+
+```
+User analyzes media → Check cache → Not found → Call Gemini API → Store result → Return description
+```
+
+### Cache Isolation Examples
+
+Same video file with different prompts:
+
+- `video.mp4` + "Describe without clothing" → Cache entry A
+- `video.mp4` + "Describe with clothing" → Cache entry B
+- `video.mp4` + "Describe without clothing (No bokeh)" → Cache entry C
+- `video.mp4` + "Describe with clothing (No bokeh)" → Cache entry D
+
+Same prompt with different models:
+
+- `video.mp4` + "Describe without clothing" + `gemini-2.5-flash` → Cache entry A
+- `video.mp4` + "Describe without clothing" + `gemini-2.5-pro` → Cache entry B
+
+## Implementation Details
+
+### Files Modified
+
+- `utils/cache.py` - New cache utility module
+- `utils/nodes.py` - Added caching to GeminiVideoDescribe and GeminiImageDescribe classes
+
+### Cache Integration Points
+
+1. **Before Gemini API call** - Check cache for existing result
+2. **After successful API response** - Store result in cache
+3. **Cache hit handling** - Return cached result with appropriate status message
+
+### Status Messages
+
+Cache hits are indicated in the Gemini status output:
+
+```
+🤖 Gemini Analysis Status: ✅ Complete (Cached)
+• Model: models/gemini-2.5-flash
+• Cached: 2025-09-02 10:16:32
+```
+
+Regular API calls show:
+
+```
+🤖 Gemini Analysis Status: ✅ Complete
+• Model: models/gemini-2.5-flash
+• API Key: ****1234
+```
+
+## Performance Benefits
+
+- **First analysis**: Normal API call timing (~2-5 seconds)
+- **Subsequent analyses**: Cache retrieval (~0.1ms)
+- **API savings**: 100% reduction in duplicate calls
+- **User experience**: Instant results for repeated workflows
+
+## Cache Management
+
+### Automatic Behavior
+
+- Cache entries are created automatically
+- No user configuration required
+- Cache persists across sessions
+- Old entries remain until manually cleared
+
+### Manual Management
+
+The cache can be inspected or cleared programmatically:
+
+```python
+from nodes.cache import get_cache
+
+cache = get_cache()
+
+# Get cache statistics
+info = cache.get_cache_info()
+print(f"Entries: {info['entries']}, Size: {info['total_size_mb']} MB")
+
+# Clear specific entry (not exposed in UI)
+# cache._get_cache_file_path(key) and os.remove()
+```
+
+### Cache Directory Location
+
+- Default: `<comfyui_swissarmyknife>/cache/gemini_descriptions/`
+- Contains JSON files with SHA256 hash names
+- Safe to delete entire directory to clear all cache
+
+## User Workflow Impact
+
+The caching is completely transparent to users:
+
+1. **First time analyzing media**: Works exactly as before (API call)
+2. **Re-analyzing same media+prompt**: Results appear instantly from cache
+3. **Different prompts on same media**: Each creates new cache entry
+4. **Different media files**: Each gets separate cache entries
+
+Users will notice:
+
+- Faster repeated analyses
+- Cache hit indicators in status messages
+- No additional configuration needed
+- Consistent behavior across ComfyUI restarts

docs/infrastructure/caching/README.md

@@ -0,0 +1,68 @@
+# Caching Documentation
+
+Documentation for caching strategies, optimization, and verification systems in ComfyUI-SwissArmyKnife.
+
+## 📄 Documentation Files
+
+### Core Caching
+
+- **[CACHING.md](CACHING.md)** - Main caching architecture and strategies
+- **[CACHE_OPTIMIZATION_FIX.md](CACHE_OPTIMIZATION_FIX.md)** - Cache optimization improvements
+
+### Browser Cache Busting
+
+- **[CACHE_BUSTING_SUMMARY.md](CACHE_BUSTING_SUMMARY.md)** - Browser cache busting implementation summary
+- **[JAVASCRIPT_CACHE_BUSTING.md](../../features/JAVASCRIPT_CACHE_BUSTING.md)** - JavaScript-specific cache busting (see features/)
+
+### Verification & Testing
+
+- **[CACHE_VERIFICATION_OCTOBER_2025.md](CACHE_VERIFICATION_OCTOBER_2025.md)** - October 2025 cache verification tests
+- **[CACHE_VERIFICATION_SUMMARY.md](CACHE_VERIFICATION_SUMMARY.md)** - Cache verification summary and results
+
+## 🎯 Quick Reference
+
+### Cache Types
+
+1. **LoRA Hash Cache**: `cache/lora_hash_cache.json` - Stores LoRA model hashes
+2. **Gemini Descriptions**: `cache/gemini_descriptions/` - AI-generated descriptions
+3. **Browser Cache**: JavaScript/CSS file versioning
+
+### Key Features
+
+- **Persistent Caching**: Long-term storage of expensive computations
+- **Cache Busting**: Automatic versioning for JavaScript/CSS updates
+- **Verification**: Automated cache integrity checks
+- **Optimization**: Performance improvements through smart caching
+
+## 🔧 Cache Management
+
+### Clear Cache
+
+```bash
+# Clear LoRA hash cache
+rm cache/lora_hash_cache.json
+
+# Clear Gemini description cache
+rm -rf cache/gemini_descriptions/*
+
+# Clear browser cache (user action)
+# Hard refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac)
+```
+
+### Verify Cache
+
+```python
+# Run cache verification tests
+python test_cache_verification.py
+```
+
+## 📚 Related Documentation
+
+- [Debug System](../debug/) - For cache debugging
+- [LoRA Loader](../../nodes/lora-loader/) - For LoRA hash caching
+- [Media Describe](../../nodes/media-describe/) - For description caching
+
+---
+
+**Category**: Infrastructure
+**Status**: Stable

docs/infrastructure/debug/DEBUG_MODE_IMPLEMENTATION.md

@@ -0,0 +1,288 @@
+# DEBUG Mode Implementation
+
+## Overview
+
+The Swiss Army Knife extension now respects the `DEBUG` environment variable setting from `.env` to control console logging in the browser JavaScript.
+
+## How It Works
+
+### Backend (Python)
+
+1. **Config API Endpoint** (`nodes/config_api.py`):
+    - Exposes a `/swissarmyknife/config` endpoint
+    - Reads `DEBUG` environment variable from `.env`
+    - Returns JSON with `debug` boolean flag
+    - Registered in `__init__.py` at extension load time
+
+2. **Environment Variable Reading**:
+
+    ```python
+    debug = os.environ.get("DEBUG", "false").lower() in ("true", "1", "yes")
+    ```
+
+    - Supports: `true`, `1`, `yes` (case-insensitive) for enabling debug mode
+    - Defaults to `false` if not set
+
+### Frontend (JavaScript)
+
+1. **Debug Configuration Loading** (`web/js/swiss-army-knife.js`):
+    - Fetches debug setting from `/swissarmyknife/config` on extension load
+    - Stores in `DEBUG_ENABLED` flag
+    - Logs debug mode status to console
+
+2. **Conditional Logging Wrapper**:
+
+    ```javascript
+    const debugLog = (...args) => {
+        if (DEBUG_ENABLED) {
+            console.log(...args);
+        }
+    };
+    ```
+
+3. **Log Classification**:
+    - **Debug logs** (controlled by DEBUG flag):
+        - `debugLog()` - Implementation details, state tracking, diagnostic info
+        - All `[DEBUG]`, `[SERIALIZE]`, `[CONFIGURE]`, `[LOADED]`, `[API]` tagged messages
+    - **Always-visible logs** (not controlled by DEBUG flag):
+        - `console.log()` - User-facing messages, version info
+        - `console.warn()` - Warnings
+        - `console.error()` - Errors
+        - Extension loading message
+        - Debug mode status message
+
+## Configuration
+
+### Enable Debug Mode
+
+In `.env`:
+
+```bash
+DEBUG=true
+```
+
+Or any of:
+
+```bash
+DEBUG=1
+DEBUG=yes
+DEBUG=True
+DEBUG=YES
+```
+
+### Disable Debug Mode
+
+In `.env`:
+
+```bash
+DEBUG=false
+```
+
+Or simply omit the `DEBUG` setting entirely (defaults to `false`).
+
+## Testing
+
+1. **Verify Config Endpoint**:
+
+    ```bash
+    curl http://localhost:8188/swissarmyknife/config
+    ```
+
+    Should return: `{"debug": true}` or `{"debug": false}`
+
+2. **Test Debug Mode Enabled**:
+    - Set `DEBUG=true` in `.env`
+    - Restart ComfyUI server
+    - Refresh browser
+    - Open browser console
+    - Should see: "Swiss Army Knife Debug Mode: ENABLED"
+    - Should see debug logs with `[DEBUG]` tags
+
+3. **Test Debug Mode Disabled**:
+    - Set `DEBUG=false` in `.env`
+    - Restart ComfyUI server
+    - Refresh browser
+    - Open browser console
+    - Should see: "Swiss Army Knife Debug Mode: DISABLED"
+    - Should NOT see debug logs with `[DEBUG]` tags
+
+## Implementation Details
+
+### Files Modified
+
+1. **`__init__.py`**:
+    - Added config API route registration
+    - Added `DEBUG` to exports
+
+2. **`nodes/config_api.py`** (new file):
+    - Created config API endpoint
+    - Reads DEBUG from environment
+
+3. **`web/js/swiss-army-knife.js`**:
+    - Added `loadDebugConfig()` async function
+    - Added `debugLog()` wrapper function
+    - Replaced ~50+ `console.log()` calls with `debugLog()` for debug-level messages
+    - Kept user-facing logs as `console.log()`
+
+### Logging Categories Changed to debugLog()
+
+- Node registration messages
+- Widget state serialization/deserialization
+- File upload handlers
+- Workflow loading
+- API event processing
+- Dimensions display updates
+- Media widget management
+- LoRA info extraction
+
+### Logging Categories Kept as console.log()
+
+- Extension version and load timestamp
+- Debug mode status (enabled/disabled)
+- Development utility functions
+- Version update notifications
+- Cache control messages
+- User-facing warnings and errors
+
+## Benefits
+
+1. **Cleaner Console**: Users can disable debug logs for cleaner console output in production
+2. **Debugging**: Developers can enable detailed logging when troubleshooting
+3. **Centralized Control**: Single environment variable controls all debug logging
+4. **No Code Changes**: Toggle debug mode without modifying code
+5. **Server Restart**: Changes to DEBUG setting require server restart (not just browser refresh)
+
+## Future Enhancements
+
+Potential improvements:
+
+- Add different log levels (DEBUG, INFO, WARN, ERROR)
+- Add per-node debug control
+- Add runtime debug toggle (no server restart needed)
+- Add debug log filtering by category
+- Add debug log export functionality
+
+## Final Statistics
+
+After complete implementation:
+
+- **Total debugLog calls**: 167 (converted from console.log)
+- **Remaining console.log calls**: 15 (all user-facing or system-required)
+    - 1 inside debugLog function itself (required)
+    - 2 user-facing status messages (debug mode, extension loading)
+    - 2 error/status messages (filename preview error, video preview status)
+    - 10 development utility messages (cache busting, localhost only)
+- **Conversion rate**: ~92% of logging now respects DEBUG flag
+
+### Log Categories Converted to debugLog
+
+All these message types now respect the DEBUG environment variable:
+
+- `[DEBUG]` - Implementation details and diagnostics
+- `[STATE]` - Widget state management
+- `[WIDGET]` - Widget operations
+- `[CONFIGURE]` - Configuration and restoration
+- `[SERIALIZE]` - Workflow serialization
+- `[LOADED]` - Workflow loading
+- `[UPLOAD]` - File upload operations
+- `[API]` - API event handling
+- `[MediaDescribe]` - Media description node diagnostics
+- Widget discovery and manipulation
+- File restoration and state management
+- Dimensions display updates
+
+### User-Facing Messages (Always Visible)
+
+These messages always appear regardless of DEBUG setting:
+
+- Extension version and load timestamp
+- Debug mode status (ENABLED/DISABLED)
+- Development utilities info (localhost only)
+- Critical error messages
+- Cache clearing confirmations
+
+## Troubleshooting
+
+### "Still seeing debug logs after setting DEBUG=false"
+
+1. **Verify .env file**:
+
+    ```bash
+    cat /Users/samkumar/Development/dev-lab-hq/ai-image-hub/apps/comfyui-swiss-army-knife/.env | grep DEBUG
+    ```
+
+    Should show: `DEBUG=false`
+
+2. **Test config API**:
+
+    ```bash
+    curl http://127.0.0.1:8188/swissarmyknife/config
+    ```
+
+    Should return: `{"debug": false}`
+
+    If it returns `{"debug": true}`, the .env file isn't being read correctly.
+
+3. **Clear ALL caches**:
+    - Stop ComfyUI server completely
+    - Clear browser cache (hard refresh: Cmd+Shift+R / Ctrl+Shift+F5)
+    - In browser console, run: `localStorage.clear(); sessionStorage.clear()`
+    - Or use the built-in utility: `clearSwissArmyKnifeCache()`
+    - Restart ComfyUI server
+    - Reload page
+
+4. **Check for cached JavaScript**:
+    - Browser may have cached the old swiss-army-knife.js
+    - Force cache bypass: Disable browser cache in DevTools Network tab
+    - Or increment EXTENSION_VERSION in swiss-army-knife.js to force reload
+
+5. **Verify server restart**:
+    - Ensure you fully restarted the ComfyUI server (not just refreshed browser)
+    - Environment variables are only read at server startup
+
+### "Debug mode status shows DISABLED but still see logs from other extensions"
+
+The DEBUG flag only controls Swiss Army Knife logs. Other extensions (Node Enhancer, Super LoRA Loader, etc.) have their own logging that isn't affected by this setting.
+
+Logs from other extensions will show different formats:
+
+- `extension.js:6753 NodeEnhancer: Registering extension...`
+- `extension.js:6891 Super LoRA Loader: Registering extension...`
+
+These are separate extensions and not controlled by Swiss Army Knife's DEBUG setting.
+
+## Final Statistics
+
+After complete implementation:
+
+- **Total debugLog calls**: 167 (converted from console.log)
+- **Remaining console.log calls**: 15 (all user-facing or system-required)
+- **Conversion rate**: ~92% of logging now respects DEBUG flag
+
+### User-Facing Messages (Always Visible)
+
+These messages always appear regardless of DEBUG setting:
+
+- Extension version and load timestamp
+- Debug mode status (ENABLED/DISABLED)
+- Development utilities info (localhost only)
+- Critical error messages
+
+## Troubleshooting
+
+### "Still seeing debug logs after setting DEBUG=false"
+
+The logs you're seeing are from **other extensions** (Node Enhancer, Super LoRA Loader). Swiss Army Knife debug logs will have tags like `[DEBUG]`, `[STATE]`, `[WIDGET]`, etc.
+
+**Verification steps:**
+
+1. Check browser console shows: "Swiss Army Knife Debug Mode: DISABLED"
+2. Verify no messages with `[DEBUG]`, `[STATE]`, `[WIDGET]` tags appear
+3. Other extensions' logs (extension.js:XXXX) are normal and unrelated
+
+**If Swiss Army Knife debug logs still appear:**
+
+1. Verify `.env` has `DEBUG=false`
+2. Fully restart ComfyUI server (environment variables load at startup)
+3. Hard refresh browser (Cmd+Shift+R / Ctrl+Shift+F5)
+4. Clear browser cache: `clearSwissArmyKnifeCache()` in console

docs/infrastructure/debug/README.md

@@ -0,0 +1,81 @@
+# Debug System Documentation
+
+Unified debug and logging system for ComfyUI-SwissArmyKnife.
+
+## 📄 Documentation Files
+
+- **[DEBUG_MODE_IMPLEMENTATION.md](DEBUG_MODE_IMPLEMENTATION.md)** - Debug mode implementation and usage
+- **[UNIFIED_DEBUG_SYSTEM.md](UNIFIED_DEBUG_SYSTEM.md)** - Unified debug system architecture
+
+## 🎯 Quick Reference
+
+### Debug Configuration
+
+Debug mode can be enabled/disabled via:
+
+1. **Server Config**: `/swissarmyknife/config` endpoint
+2. **Environment Variable**: `DEBUG_ENABLED=true`
+3. **Runtime**: Toggle via API
+
+### Debug Output
+
+When enabled, debug output appears in:
+
+- Browser console (JavaScript widgets)
+- Server logs (Python nodes)
+- Network tab (API calls)
+
+### Usage
+
+```python
+# Python - use debug logging
+from utils.debug import debug_log
+debug_log("My debug message", variable_name)
+```
+
+```javascript
+// JavaScript - conditional logging
+const debugLog = (...args) => {
+    if (DEBUG_ENABLED) {
+        console.log('[ComponentName]', ...args);
+    }
+};
+```
+
+## 🔧 Features
+
+### Unified System
+
+- **Consistent Format**: `[ComponentName] Message: data`
+- **Conditional Output**: Only logs when debug mode is enabled
+- **Performance**: Zero overhead when disabled
+- **Granular Control**: Per-component debug levels
+
+### Component Tags
+
+- `[VideoPreview]` - Video preview widget debug
+- `[LoRALoader]` - LoRA loading debug
+- `[MediaDescribe]` - Gemini API debug
+- `[CivitAI]` - CivitAI integration debug
+- `[Cache]` - Caching system debug
+
+## 🐛 Debugging Workflow
+
+1. **Enable Debug Mode**: Set `DEBUG_ENABLED=true` in config
+2. **Reproduce Issue**: Run the workflow that causes the problem
+3. **Check Logs**: Review browser console and server logs
+4. **Identify Component**: Look for component tags in logs
+5. **Analyze Data**: Examine logged variables and state
+6. **Fix and Test**: Make changes and verify with debug logs
+7. **Disable Debug**: Turn off debug mode for production
+
+## 📚 Related Documentation
+
+- [Caching](../caching/) - For cache-related debugging
+- [All Nodes](../../nodes/) - For node-specific debugging
+- [Features](../../features/) - For feature debugging
+
+---
+
+**Category**: Infrastructure
+**Status**: Stable

docs/infrastructure/debug/UNIFIED_DEBUG_SYSTEM.md

@@ -0,0 +1,293 @@
+# Unified Debug Logging System
+
+**Created:** October 2, 2025  
+**Status:** ✅ Implemented
+
+## Overview
+
+ComfyUI-SwissArmyKnife now has a **centralized debug logging system** that respects a single `DEBUG` environment variable across both Python backend and JavaScript frontend code.
+
+## How It Works
+
+### Environment Variable
+
+Set the `DEBUG` environment variable to control debug logging:
+
+```bash
+# Enable debug logging
+DEBUG=true
+
+# Disable debug logging (default)
+DEBUG=false
+
+# Also accepts: 1, yes, True for enabled
+```
+
+### Backend (Python)
+
+All Python debug logging now uses the centralized `debug_utils.py` module:
+
+```python
+from nodes.debug_utils import debug_print, is_debug_enabled
+
+# Use debug_print instead of print for debug messages
+debug_print("This will only show when DEBUG=true")
+
+# Check if debug is enabled
+if is_debug_enabled():
+    # Do expensive debug operations only when needed
+    pass
+```
+
+**Files Updated:**
+
+- `nodes/debug_utils.py` - New centralized debug utilities module
+- `nodes/config_api.py` - Exposes DEBUG setting to frontend via `/swissarmyknife/config`
+- `__init__.py` - Loads DEBUG from environment
+
+### Frontend (JavaScript)
+
+All JavaScript debug logging uses the centralized debug system loaded from server config:
+
+```javascript
+// DEBUG mode - will be loaded from server config
+let DEBUG_ENABLED = false;
+
+// Conditional logging wrapper
+const debugLog = (...args) => {
+    if (DEBUG_ENABLED) {
+        console.log('[ComponentName]', ...args);
+    }
+};
+
+// Load DEBUG setting from server
+async function loadDebugConfig() {
+    const response = await fetch('/swissarmyknife/config');
+    const config = await response.json();
+    DEBUG_ENABLED = config.debug || false;
+}
+```
+
+**Files Updated:**
+
+- `web/js/swiss-army-knife.js` - Main extension debug system
+- `web/js/video_preview/video_preview.js` - Video preview widget debug logging
+
+## Configuration
+
+### 1. Create `.env` file
+
+```bash
+cp .env.example .env
+```
+
+### 2. Set DEBUG variable
+
+Edit `.env`:
+
+```bash
+DEBUG=true  # Enable debug logging
+```
+
+### 3. Restart ComfyUI Server
+
+Debug settings are loaded at startup, so you must **restart the ComfyUI server** after changing the DEBUG variable:
+
+```bash
+# Stop ComfyUI
+# Restart ComfyUI
+```
+
+### 4. Refresh Browser
+
+After restarting the server, **hard refresh your browser** to load the new debug configuration:
+
+- **Mac**: `Cmd + Shift + R`
+- **Windows/Linux**: `Ctrl + Shift + R`
+- **Or**: Open DevTools → Right-click refresh → "Empty Cache and Hard Reload"
+
+## Benefits
+
+### ✅ Single Source of Truth
+
+- One environment variable controls all debug logging
+- No need to edit multiple files to enable/disable debug mode
+
+### ✅ Production Ready
+
+- Debug logging disabled by default
+- No performance impact in production
+- Clean console output without debug noise
+
+### ✅ Developer Friendly
+
+- Easy to enable debug mode for troubleshooting
+- Consistent debug output format with prefixes
+- Works across both Python and JavaScript
+
+### ✅ Conditional Logging
+
+- Only logs when DEBUG=true
+- Avoids cluttering production logs
+- Easy to trace issues in development
+
+## Debug Output Examples
+
+### Python Debug Output
+
+```
+[DEBUG] LoRAInfoExtractor.extract_lora_info called
+  - use_civitai_api: True
+  - civitai_api_key provided: True
+  - fallback_name: 'my_lora'
+[DEBUG] Discovered 3 LoRA entries in stack
+```
+
+### JavaScript Debug Output
+
+```
+Video Preview Debug Mode: ENABLED
+[VideoPreview] reference_vid raw value: /comfyui-nvidia/temp/video.mp4 string
+[VideoPreview] Loaded reference_vid:
+  Extracted: /comfyui-nvidia/temp/video.mp4
+  Type: temp
+  Subfolder: (none)
+  Filename: video.mp4
+  URL: /api/view?filename=video.mp4&type=temp&subfolder=
+```
+
+## Migration Guide
+
+### For Python Code
+
+**Before:**
+
+```python
+print("[DEBUG] Some debug message")
+print(f"[DEBUG] Value: {value}")
+```
+
+**After:**
+
+```python
+from nodes.debug_utils import debug_print
+
+debug_print("[DEBUG] Some debug message")
+debug_print(f"[DEBUG] Value: {value}")
+```
+
+### For JavaScript Code
+
+**Before:**
+
+```javascript
+const DEBUG = true;
+if (DEBUG) {
+    console.log('[Component]', 'debug message');
+}
+```
+
+**After:**
+
+```javascript
+let DEBUG_ENABLED = false;
+
+const debugLog = (...args) => {
+    if (DEBUG_ENABLED) {
+        console.log('[Component]', ...args);
+    }
+};
+
+async function loadDebugConfig() {
+    const response = await fetch('/swissarmyknife/config');
+    const config = await response.json();
+    DEBUG_ENABLED = config.debug || false;
+}
+
+loadDebugConfig();
+
+// Use debugLog instead of console.log
+debugLog('debug message');
+```
+
+## Files to Update (Future Work)
+
+The following files still contain hardcoded debug logging that should be migrated to use `debug_utils.py`:
+
+### Python Files (Not Yet Migrated)
+
+- `nodes/nodes.py` - LoRA extraction debug logs
+- `nodes/civitai_service.py` - CivitAI API debug logs
+- `nodes/lora_hash_cache.py` - Cache operation logs
+- `nodes/cache.py` - Cache file logs
+- `nodes/utils/video_preview.py` - Video preview logs
+- `nodes/utils/control_panel.py` - Control panel logs
+- `nodes/lora_manager/*.py` - LoRA manager debug logs
+
+### Migration Priority
+
+1. **High Priority**: Core nodes (`nodes.py`, `civitai_service.py`)
+2. **Medium Priority**: Utility modules (`cache.py`, `lora_hash_cache.py`)
+3. **Low Priority**: Utility nodes (`control_panel.py`, `video_preview.py`)
+
+## Troubleshooting
+
+### Debug logs not appearing after enabling DEBUG
+
+**Solution:**
+
+1. Verify `.env` file exists and contains `DEBUG=true`
+2. **Restart ComfyUI server** (required)
+3. **Hard refresh browser** (Cmd+Shift+R)
+4. Check console for: `Swiss Army Knife Debug Mode: ENABLED`
+5. Check console for: `Video Preview Debug Mode: ENABLED`
+
+### Environment variable not loading
+
+**Solution:**
+
+1. Ensure `.env` file is in the extension root directory
+2. Check file permissions (should be readable)
+3. Verify ComfyUI loads `.env` files (may need python-dotenv)
+4. Try setting environment variable directly before starting ComfyUI:
+    ```bash
+    export DEBUG=true
+    # Start ComfyUI
+    ```
+
+### Debug mode enabled but no logs
+
+**Solution:**
+
+1. Check that code is using `debug_print()` or `debugLog()`
+2. Verify `/swissarmyknife/config` endpoint returns `{"debug": true}`
+3. Check browser console and server logs separately
+
+## API Endpoint
+
+### GET `/swissarmyknife/config`
+
+Returns the current debug configuration:
+
+```json
+{
+    "debug": true
+}
+```
+
+This endpoint is called by JavaScript extensions to synchronize debug settings with the backend.
+
+## Future Enhancements
+
+1. **Dynamic Debug Toggle**: Add UI button to toggle debug mode without restarting
+2. **Debug Levels**: Support different debug levels (INFO, DEBUG, TRACE)
+3. **Component Filtering**: Enable debug for specific components only
+4. **Log File Output**: Option to write debug logs to file
+5. **Performance Metrics**: Track and display performance data in debug mode
+
+## Related Documentation
+
+- `.env.example` - Environment variable configuration template
+- `nodes/debug_utils.py` - Python debug utilities implementation
+- `nodes/config_api.py` - API endpoint for debug configuration
+- `web/js/swiss-army-knife.js` - JavaScript debug system implementation