(CODUX-221) Add cross-surface QA and CI acceptance coverage

[numnx]

🧩 Task: Add cross-surface QA and CI acceptance coverage

Automated task PR opened by Code UX for T07.

📋 Summary

Sprint: Sprint 221 · Clarify QA follow-ups and CI status · Task: T07

Clarify QA change requests and CI progress consistently across Sprint, Task, and Live cards by projecting complete QA follow-up metadata, deriving durable CI workflow states from existing execution evidence, and presenting accessible, responsive badges with end-to-end regression coverage and synchronized documentation.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-13 21:18:03 UTC
Finished	2026-07-13 21:19:02 UTC
Duration	1m 0s

📊 Token Usage

Metric	Value
Input tokens	199,199
Cached input tokens	4,683,776
Output tokens	21,962
Total tokens	4,904,937
Invocations	2
Tool calls	39
Active time	16m 5s

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

✅ 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 executable integration coverage proving that the shared QA and CI contracts produce equivalent, accessible outcomes across all three dashboard surfaces.

## Scope
- Create `tests/dashboard/v2/qa-ci-card-status.integration.test.tsx`
- Exercise `dashboard/src/v2/components/tasks/KanbanTaskCard.tsx`, `dashboard/src/v2/components/LiveTaskCard.tsx`, `dashboard/src/v2/components/sprints/SprintCell.tsx`, and `dashboard/src/v2/components/sprints/SprintLedgerRow.tsx`
- Reuse the QA contract from T01, shared components from T02 and T03, and page integrations from T04 through T06

## Implementation Requirements
1. Build a deterministic fixture containing a changes-requested QA review with findings, fix instructions, target task, and at least one follow-up task, plus CI events covering pull-request creation, running checks, check failure, and later recovery.
2. Render the fixture through Task, Live, Sprint gallery, and Sprint ledger card paths and assert consistent labels, blue edit-state QA presentation, red-X CI failure presentation, and workflow-step states.
3. Open the QA details card by keyboard, verify requested-change details, confirm follow-up content is initially collapsed, expand it, and verify the complete specification is reachable without pointer input.
4. Assert that newer successful evidence removes stale failure, active matching attention restores failure, and unrelated task or sprint events never leak across cards.
5. Cover accessible names, focus behavior, Escape dismissal, absence of color-only status communication, and stable rendering when the execution snapshot is replayed unchanged.

## Constraints
- Keep the test deterministic and fully mocked at existing external boundaries; do not invoke Docker, provider CLIs, GitHub, or a live database.
- Do not duplicate component implementation or create a production-only testing hook.
- Keep fixtures generic and do not include real project names or credentials.
- Limit production edits to genuinely necessary integration wiring discovered by the executable test; do not turn this into a review-only task.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/qa-ci-card-status.integration.test.tsx`.
- Run `pnpm run lint`, `pnpm run test:dashboard`, and `pnpm run build`.
- Confirm the same evidence yields equivalent QA and CI semantics on all four card renderings and all keyboard assertions pass.

🌿 Branch Info

Base: feature/CODUX-221-clarify-qa-follow-ups-and-ci-status
Head: task/feature-codux-22-t07-codex-20ebcc89-mrjp5umd

---

🤖 Generated by Code UX