(CODUX-148) Wire typed app actions into dashboard chat

[numnx]

🧩 Task: Wire typed app actions into dashboard chat

Automated task PR opened by Code UX for T04.

📋 Summary

Sprint: Sprint 205 · 3d Chat Quickactions · Task: T04

Make idle 3D Chat quickactions catalog-driven, responsively distributed, guidance-aware, and safe to show only for freshly initialized new projects where required.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-11 03:41:10 UTC
Finished	2026-07-11 03:52:01 UTC
Duration	10m 51s

📊 Token Usage

Metric	Value
Input tokens	131,196
Cached input tokens	4,698,880
Output tokens	14,050
Total tokens	4,844,126
Invocations	1
Tool calls	60
Active time	10m 16s

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

✅ 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
Update dashboard chat data flow to post all five app quickactions as typed detached-planning requests and render their progress labels consistently.

## Scope
- `dashboard/src/v2/hooks/use-chat-thread-data.ts`
- `dashboard/src/v2/lib/chat-widget-view-models.ts`
- `dashboard/src/v2/components/chat/widgets/AppCreationProgressWidget.tsx` if presentation changes are needed
- `tests/dashboard/v2/use-chat-page-data.test.tsx`
- `tests/dashboard/v2/chat-message-bubbles.test.tsx`
- Relevant colocated chat component tests

## Implementation Requirements
1. Replace Web/Desktop-only handler maps with the shared catalog, so `handleCreateAppQuickaction` accepts all five kinds, posts the correct body, template ID, stack summary, request ID, and guidance selection, and remains independent of composer text/history.
2. Extend app-progress metadata normalization and labels for Online Shop, Portfolio, and Game while retaining the existing Web/Desktop progress stages, status copy, stack summary, suggestion tags, and malformed-metadata fallbacks.
3. Keep the existing Threads-mode Create Web/Desktop controls compatible as a two-item subset of the expanded protocol and preserve optimistic message-cache behavior and error focus recovery.
4. Add tests that assert all five payloads, action-specific guidance, no composer-history writes, progress labels, and backward-compatible Web/Desktop rendering.

## Constraints
- Reuse the shared catalog and existing typed connection contracts; do not create a second dashboard-only kind map.
- Do not add frontend optimistic invocation records or change thread follow-up semantics.
- Keep app-progress widgets as adjuncts to normal chat bubbles rather than replacing transcript content.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/use-chat-page-data.test.tsx tests/dashboard/v2/chat-message-bubbles.test.tsx`.
- Confirm all five payloads reach `postConversationMessage` with the expected template and guidance selection and render readable app-kind labels.

🌿 Branch Info

Base: feature/CODUX-205-3d-chat-quickactions
Head: task/feature-codux-20-t04-codex-2b145151-mrfthymr

---

🤖 Generated by Code UX