(CODUX-224) Document repaired cinematic activity

[numnx]

🧩 Task: Document repaired cinematic activity

Automated task PR opened by Code UX for T04.

📋 Summary

Sprint: Sprint 224 · Repair 3D agent activity feedback · Task: T04

Repair the existing 3D Chat stage so matching active Project Manager invocations drive cycling avatar tools and a transient animated bubble showing the latest eligible invocation assistant message, in-progress status, and unique tool count; improve large-screen response sizing, typography, and thought-to-avatar spacing; and cover lifecycle, reduced-motion, responsive, stale-response, and fetch-failure behavior with dashboard tests and synchronized documentation.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-13 22:55:13 UTC
Finished	2026-07-13 23:01:10 UTC
Duration	5m 57s

📊 Token Usage

Metric	Value
Input tokens	138,072
Cached input tokens	2,506,496
Output tokens	12,362
Total tokens	2,656,930
Invocations	1
Tool calls	28
Active time	5m 24s

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

✅ 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
Document how 3D Chat derives transient invocation feedback, scopes Project Manager activity, animates tools and progress bubbles, and degrades safely across failures, reduced motion, and responsive layouts.

## Scope
- Edit `docs/dashboard/design-system-chat.md`
- Edit `docs/architecture/chat-thread-runtime.md`
- Edit `docs-web/user/dashboard/chat.md`
- Edit `docs-web/architecture/virtual-workers.md`
- Regenerate and verify `docs-web/content/docs/user-dashboard-chat.mdx`
- Regenerate and verify `docs-web/content/docs/architecture-virtual-workers.mdx`

## Implementation Requirements
1. Describe that only a running `dashboard_reply` or `worker_reply` invocation matching the resolved Project Manager preset drives foreground tools and the transient progress bubble, while unrelated running work remains a background cue.
2. Explain that the bubble displays the latest eligible persisted assistant interim message, explicit in-progress status, and a deduplicated tool-call count, and that it remains separate from the durable thread transcript and final reply.
3. Document refresh and cleanup behavior for zero-message startup, transcript updates, terminal state, invocation/project/thread changes, stale responses, and non-fatal transcript-fetch failures.
4. Record the reduced-motion fallback and large-screen sizing, typography, overflow, and thought-bubble spacing expectations, including the requirement that visible text remains the authoritative activity signal.
5. Run the repository documentation generator so published MDX mirrors the edited `docs-web` sources, then verify that generated output is clean and linked through the existing chat and virtual-worker entries.

## Constraints
- Document only behavior implemented and verified by T03; do not claim backend streaming, delivery guarantees, or tests that do not exist.
- Keep canonical `docs/` and published `docs-web/` guidance consistent without creating a `docs-release/` directory.
- Do not add new index or summary entries because this work extends existing documented subsystems rather than introducing a new page.
- Do not expose real project names, transcript contents, credentials, or provider secrets in examples.

## Verification
- Run `pnpm run sync:docs-web` followed by `pnpm run check:docs-web`.
- Run `pnpm exec vitest run tests/backend/services/docs-web-catalog-service.test.ts`.
- Confirm the canonical design/runtime documentation and generated public chat/virtual-worker pages agree on ownership, interim-message selection, tool counting, lifecycle cleanup, reduced motion, and responsive behavior.

🌿 Branch Info

Base: feature/CODUX-224-repair-3d-agent-activity-feedback
Head: task/feature-codux-22-t04-codex-582fe0dd-mrjtlqcx

---

🤖 Generated by Code UX