Import paths standardized and realtime docs reorganized
Trigger.dev documentation now includes AI-assisted setup prompts, standardized import paths, and reorganized realtime docs that clearly explain the difference between run status updates and streaming AI output.
Trigger.dev documentation has been updated with clearer import paths, restructured realtime sections, and new AI-assisted setup instructions. The most significant change removes all @trigger.dev/sdk/v3 imports from the writing-tasks.mdc cursor rule, standardizing on @trigger.dev/sdk — developers no longer need the v3 suffix to import task, schedules, or runs. The realtime documentation has been reorganized to clearly distinguish between "Run updates" (status, metadata, and tag changes via Electric SQL) and "Streaming" (continuous data like AI tokens from tasks). Added FAQ sections address common questions around progress bars, AI streaming, and WebSocket requirements. A new "Set up with AI" section provides a copy-paste prompt that AI coding assistants (Claude Code, Cursor, Copilot) can use to automatically configure Trigger.dev in existing projects, dramatically lowering the onboarding barrier for developers using AI tools.