What problem does it solve? Upgrading an existing TypeScript codebase from Inngest SDK v3 to v4 involves many breaking changes—moved triggers, removed EventSchemas, relocated serve options, rewritten step.invoke calls, and a new realtime API—and mixed v3/v4 usage causes confusing runtime errors. ## Core Features & Use Cases - Usage Detection: Scans the repository with ripgrep to classify it as v3-only, mixed v3/v4, or mostly migrated before editing. - Ordered Mechanical Migration: Applies changes in a controlled sequence covering package versions, client construction, serve options, createFunction triggers, eventType/staticSchema schemas, step.invoke references, realtime APIs, and checkpointing. - Verification Workflow: Runs typechecks, tests, and the Inngest dev server to confirm function discovery and event delivery. - Use Case: A team upgrades to inngest@4 and hits "signing key required" errors and broken @inngest/realtime imports; this skill walks through each breaking change and verifies the result. ## Quick Start Ask the assistant to upgrade this repository from Inngest v3 to v4 and fix any mixed v3/v4 API usage.