(CODUX-117) Add Docs setup control in dashboard

[numnx]

🧩 Task: Add Docs setup control in dashboard

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 188 · Auto Embed docs Setup Agent · Task: T03

Add a Project Setup Agent option to auto-embed relevant repository documentation into the project Knowledge docs library, expose it in dashboard and MCP setup flows, and document the behavior.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-08 18:08:32 UTC
Finished	2026-07-08 18:09:28 UTC
Duration	55s

📊 Token Usage

Metric	Value
Input tokens	91,379
Cached input tokens	1,609,088
Output tokens	13,623
Total tokens	1,714,090
Invocations	2
Tool calls	56
Active time	6m 23s

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

✅ 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 an accessible Docs option button to the dashboard setup flows and include it in setup request payloads when selected.

## Scope
- `dashboard/src/v2/components/ui/AddProjectModal.tsx`
- `dashboard/src/v2/ProjectsPage.tsx`
- `tests/dashboard/v2/add-project-modal.test.tsx`
- `tests/dashboard/v2/projects-page.test.tsx`
- Shared request type re-exported through `dashboard/src/v2/types.ts`

## Implementation Requirements
1. Extend the dashboard setup option state in both `AddProjectModal` and `ProjectsPage` to include `docs: false` by default, keeping docs embedding opt-in unless the operator presses the Docs option.
2. Add a setup option card/button labeled `Docs` with a documentation/knowledge icon from `lucide-preact` and concise copy indicating it embeds repository documentation into Knowledge docs.
3. Ensure the Add Project setup scope step submits `setup.options.docs` correctly when selected and still hides all setup controls for the `new_project` source flow.
4. Ensure the existing-project setup dialog submits `options.docs` through `startProjectSetup` and that any `All` action includes docs while initial defaults keep docs disabled.
5. Preserve existing responsive layout, focus states, `aria-pressed` state, disabled behavior while setup is running, and mobile action stacking.
6. Update dashboard tests to assert the Docs option is rendered in setup flows, omitted from the New Project flow, and included in payloads only when toggled on.

## Constraints
- Do not introduce new UI libraries or external dependencies.
- Do not change project creation, clone, local directory, or New Project payload semantics outside the setup options object.
- Keep button text short enough for the existing setup option grid and maintain keyboard-accessible toggle behavior.
- Do not start setup automatically when the Docs button is toggled; it only changes the setup scope.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/add-project-modal.test.tsx tests/dashboard/v2/projects-page.test.tsx`.
- Run `pnpm run test:dashboard`.
- Success means setup payloads include `docs: true` only after user selection and existing setup UI behavior remains intact.

🌿 Branch Info

Base: feature/CODUX-188-auto-embed-docs-setup-agent
Head: task/feature-codux-188-auto-embed-docs-setup-agent-t03-codex-mrcdxxq5

---

🤖 Generated by Code UX