lorentz 966376e6b6 fix(analyzer): import worker from analyze route to trigger auto-start ... worker.ts has a self-init side effect on module load, but nothing in the shipped code imported it — so jobs queued but no worker ran. Adding a side-effect import to the analyze route handler; Next.js eagerly loads route modules at boot to build the routing manifest, so this runs once per server process. Confirmed live: [ANALYZER-WORKER] starting log line fires on container start. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-29 11:21:10 -04:00
..
analyses/[id]	feat(analyzer): phase 7 — share-via-email	2026-04-29 11:03:11 -04:00
jobs/[jobId]	feat: AI ticket analyzer (phases 1-6)	2026-04-29 10:59:40 -04:00
needs-review	feat: AI ticket analyzer (phases 1-6)	2026-04-29 10:59:40 -04:00
tickets/[ticketNumber]	fix(analyzer): import worker from analyze route to trigger auto-start	2026-04-29 11:21:10 -04:00