What problem does it solve? Adding a new trigger type to Windmill touches dozens of files across the Rust backend, Svelte frontend, TypeScript CLI, OpenAPI spec, and AI system prompts, and missing any one of them causes silent regressions like dropped syncs, broken capture buttons, or lost workspace forks. ## Core Features & Use Cases - Complete file checklist: Enumerates every file that must change, from SQLx migrations and the windmill-trigger-{kind} crate to sidebar entries, icons, and hardcoded trigger-kind arrays in ACL, offboarding, and trash modules. - Reference implementations: Points to GCP, Kafka, and Azure triggers as concrete patterns for push, pull, and streaming integrations. - Validation workflow: Provides exact cargo check, ./update_sqlx.sh, and npm run check:fast commands plus a final pre-PR checklist. - Use Case: When implementing a new Azure Event Grid trigger, follow the checklist to wire the database migration, feature-gated API routes, capture endpoint, CLI sync support, and frontend editor without missing the KINDS array length or OpenAPI enums. ## Quick Start Ask the AI to walk through the adding-a-trigger checklist to scaffold a new trigger kind such as MQTT across the Windmill backend, frontend, and CLI.