(CODUX-221) Integrate QA and CI badges into Live cards

[numnx]

🧩 Task: Integrate QA and CI badges into Live cards

Automated task PR opened by Code UX for T05.

📋 Summary

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

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 19:48:19 UTC
Finished	2026-07-13 20:07:26 UTC
Duration	19m 7s

📊 Token Usage

Metric	Value
Input tokens	215,955
Cached input tokens	10,870,528
Output tokens	25,457
Total tokens	11,111,940
Invocations	1
Tool calls	92
Active time	18m 25s

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

✅ 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 the shared CI indicator to Live task cards and preserve the upgraded QA details experience throughout active, reconnecting, and completed sessions.

## Scope
- Edit `dashboard/src/v2/LiveSessionPage.tsx`
- Edit `dashboard/src/v2/lib/live-session-view-model.ts`
- Edit `dashboard/src/v2/lib/live-task-runtime.ts`
- Edit `dashboard/src/v2/components/LiveTaskCard.tsx`
- Edit `tests/dashboard/v2/components/ui/live-task-card.test.tsx`
- Edit `tests/dashboard/v2/live-page-status-regression.test.tsx`
- Verify `tests/dashboard/v2/lib/live-session-view-model.test.ts`
- Consume `SprintReviewBadge` from T03 and CI derivation/component exports from T02

## Implementation Requirements
1. Index and scope recent execution events and active CI attention items by sprint and task when constructing Live task card data, reusing persisted snapshot data already loaded by `LiveSessionPage`.
2. Derive and pass a stable task CI presentation to `LiveTaskCard`, including merge-indicator fallback when no richer gate event exists.
3. Render `CiStatusBadge` whenever CI owns the task's current progression or failure, even if the general task phase is running or pending, and avoid duplicate or contradictory merge and status badges.
4. Keep `SprintReviewBadge` wired to the complete T01 summary so requested-change instructions and collapsed follow-up task specifications remain available after restart or reconnect.
5. Preserve event feeds, invocation summaries, prompt disclosures, selection, and task controls while adding concise screen-reader status text and responsive badge wrapping.
6. Add regression tests for live updates, persisted snapshot replay, reconnect with unchanged data, active-attention failure, newer success, unrelated task events, QA disclosure behavior, and existing Live controls.

## Constraints
- Do not create new polling or websocket channels; use the existing execution snapshot and runtime subtask projections.
- Do not treat a temporary disconnect or absent event list as CI failure.
- Keep derivation in the shared helper and avoid page-local CI state mappings.
- Preserve current event ordering and content-stable memoization behavior.
- Do not edit Task, Sprint, or documentation files owned by T04, T06, and T08.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/components/ui/live-task-card.test.tsx tests/dashboard/v2/live-page-status-regression.test.tsx tests/dashboard/v2/lib/live-session-view-model.test.ts`.
- Run `pnpm run lint`, `pnpm run test:dashboard`, and `pnpm run build`.
- Load `http://localhost:4444`, inspect a Live session at desktop and mobile widths, and confirm CI and QA state remains correct through snapshot refresh while existing disclosures and controls still work.

🌿 Branch Info

Base: feature/CODUX-221-clarify-qa-follow-ups-and-ci-status
Head: task/feature-codux-22-t05-codex-ac18cfc3-mrjmxf4g

---

🤖 Generated by Code UX