(CODUX-104) Queue follow-up direction for app sprints

[numnx]

🧩 Task: Queue follow-up direction for app sprints

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 172 · Quickactions Create App · Task: T03

Add chat quickactions for Create Desktop App and Create Web App that launch planning immediately, show a rich progress widget, and capture follow-up direction into the generated sprint once planning is editable.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 10:35:25 UTC
Finished	2026-07-07 10:37:46 UTC
Duration	2m 21s

📊 Token Usage

Metric	Value
Input tokens	156,098
Cached input tokens	4,993,792
Output tokens	24,073
Total tokens	5,173,963
Invocations	2
Tool calls	84
Active time	16m 4s

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
Persist follow-up direction from the same chat thread during create-app planning and apply it to the created sprint once planning has finished enough for the sprint to be edited.

## Scope
- src/contracts/connection-chat-types.ts
- src/services/chat-thread-runtime-service.ts
- src/repositories/project-management-repository.ts only if an existing sprint update method is insufficient
- tests/backend/services/chat-thread-runtime-service.test.ts
- tests/backend/server/dashboard-chat-api.test.ts as needed
- Consume the runtimeState quickaction fields created by T02

## Implementation Requirements
1. Extend the quickaction runtime state with active sprint id, app kind, planning status, and queued follow-up entries containing message id, bodyMarkdown, and createdAt.
2. When a user posts a normal chat message in a thread with an active create-app quickaction whose sprint has no planned tasks yet, store the message as a queued follow-up, mark it processed, and post a concise system acknowledgement that the direction will be applied after planning.
3. When the detached planning promise from T02 completes, read any queued follow-ups from the thread runtime state and append them to the sprint goal or originalPrompt using a clearly delimited section such as “Additional direction from chat”.
4. If a follow-up arrives after the sprint already has tasks, append it immediately and post a system message confirming the sprint direction was updated.
5. Update the app progress widget metadata status to completed or failed when detached planning resolves or rejects, and clear only the active planning marker while retaining durable sprint id context.

## Constraints
- Do not modify task prompts or generated subtasks directly in this task; append user direction to the sprint-level editable context only.
- Do not mark failed dashboard messages as processed.
- Preserve normal provider chat for threads without an active create-app quickaction.
- Avoid polling loops in the frontend for this behavior; the backend detached planning completion should perform the append.

## Verification
- pnpm run test:backend -- tests/backend/services/chat-thread-runtime-service.test.ts
- pnpm run test:backend -- tests/backend/server/dashboard-chat-api.test.ts
- pnpm run lint
- Success means follow-ups before planning completion are queued then appended after completion, follow-ups after task creation append immediately, and failed planning updates widget metadata without losing queued user text.

🌿 Branch Info

Base: feature/CODUX-172-quickactions-create-app
Head: task/feature-codux-172-quickactions-create-app-t03-codex-mrahup7k

---

🤖 Generated by Code UX