Cover dashboard sprint workflows (codex)

[numnx]

🧩 Task: Cover dashboard sprint workflows

Automated task PR opened by Code UX for T02.

📋 Summary

Sprint: Sprint 169 · Testsuite: e2e · Task: T02

Greatly expand Code UX end-to-end coverage with a deterministic cross-platform Playwright harness, product-focused dashboard workflows, filesystem save/upload checks, runtime invocation assertions, and fake-CLI sprint orchestration scenarios for full runs plus start/stop/retry controls.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 10:02:02 UTC
Finished	2026-07-07 10:24:33 UTC
Duration	22m 31s

📊 Token Usage

Metric	Value
Input tokens	298,948
Cached input tokens	9,718,656
Output tokens	23,061
Total tokens	10,040,665
Invocations	1
Tool calls	109
Active time	21m 43s

Included usage estimate (subscription/local login): $7.05

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Add product-level Playwright tests for the dashboard flows users use before orchestration: selecting a project, creating a sprint, creating tasks, navigating core pages, and confirming the sprint ledger remains accessible on desktop and mobile.

## Scope
- New `tests/e2e/dashboard-workflows.spec.ts`
- `tests/e2e/accessibility-smoke.spec.ts`
- `tests/e2e/sprint-ledger-responsive.spec.ts`
- `tests/e2e/helpers/e2e-fixtures.ts` from T01 as a read/reuse dependency
- Dashboard routes `/`, `/projects`, `/sprints`, `/tasks`, `/agents`, `/stats`, `/scheduler`, `/config`, `/memory`, `/browser`, `/files`

## Implementation Requirements
1. Use the fixture helpers from T01 to complete onboarding, create an isolated local git project, and select it before browser navigation.
2. Add a dashboard workflow spec that creates a draft sprint from the UI, adds at least two tasks through the visible dashboard controls, verifies dependency/status labels where exposed, and confirms the created records are returned by `/api/projects/:projectId/sprints` and `/api/projects/:projectId/tasks`.
3. Update the existing accessibility smoke spec to use isolated fixture setup and assert no first-run overlay or tour blocks keyboard navigation.
4. Tighten the sprint ledger responsive test so it uses a known isolated sprint fixture instead of relying on whatever shared server state already exists.
5. Add route navigation assertions that each core dashboard route renders a stable page landmark or heading and records no unhandled `pageerror` events.
6. Remove arbitrary fixed waits where Playwright can wait for specific locators, URLs, API responses, or hidden loading states.

## Constraints
- Do not trigger planning or provider execution in this task; keep created sprints/tasks in draft or idle state.
- Do not edit orchestration, provider, or backend service code beyond reusing helpers created by T01.
- Keep selectors user-facing where practical: roles, labels, headings, and stable `data-testid` only when the UI already provides them or when adding one is necessary.
- Avoid sharing mutable sprint/project state with other e2e specs.

## Verification
- Run `pnpm run build`.
- Run `pnpm run test:e2e -- tests/e2e/dashboard-workflows.spec.ts tests/e2e/accessibility-smoke.spec.ts tests/e2e/sprint-ledger-responsive.spec.ts`.
- Success means the UI workflows pass on the local Playwright server, create only isolated fixture data, and report no unhandled browser errors.

🌿 Branch Info

Base: feature/CODUX-169-testsuite-e2e
Head: task/feature-codux-169-testsuite-e2e-t02-codex-mrahce1r

---

🤖 Generated by Code UX