Part of QA PAR-457. Create sprint QA launch week with Starts 2026-10-19 and Ends 2026-10-25 on 2026-10-18. Sprints list correctly groups it under Upcoming and says Starts in 1 day. Sprint detail shows an Active badge beside the same Starts in 1 day message. Analytics then titles a panel 'Sprint burndown — QA launch week' but renders 'No active sprint with dates.' Product confuses lifecycle state (not closed) with actually running now. Expected consistent Upcoming/Current/Closed terminology and a burndown empty state that explains the sprint hasn't started. Reproduced at 390×844; URLs /w/design-qa-20261018/sprints/12a88a57-62ec-4aa8-b130-444997f0c239 and /analytics. Evidence: sprints-12a88a57-62ec-4aa8-b130-444997f0c239-mobile.png, analytics-mobile.png.
Implemented in the dependent QA stack: https://github.com/ParadauxIO/taskl.ie/pull/97
Combined verification passed: full API suite (1,306 tests), web lint and TypeScript, unit suite (1,211 passed; one existing skip), 483 Chromium story checks, and the production Next.js/CSS build. Desktop/mobile component evidence and a flow diagram are attached where applicable; server-rendered screenshot gaps and GitHub rollout prerequisites are explicit in the PR.
Awaiting review and merge; production application code has not been deployed by this task.