(CODUX-108) Document custom dashboard workflow

[numnx]

🧩 Task: Document custom dashboard workflow

Automated task PR opened by Code UX for T07.

📋 Summary

Sprint: Sprint 185 · Add Custom Data Dashboards · Task: T07

Add a project-scoped Custom Dashboards system where the Project Manager agent can create dashboard bundles, validate them in detached Docker sessions connected to Code UX data, and publish only validated dashboards into the main dashboard UI.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 15:44:37 UTC
Finished	2026-07-07 15:45:45 UTC
Duration	1m 7s

📊 Token Usage

Metric	Value
Input tokens	150,415
Cached input tokens	3,253,888
Output tokens	17,444
Total tokens	3,421,747
Invocations	3
Tool calls	68
Active time	9m 15s

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

✅ 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 the Custom Dashboards feature in the canonical docs and user docs, including the agent workflow, API/MCP surface, validation gate, detached runtime, and rollback expectations.

## Scope
- Create `docs/dashboard/custom-dashboards.md`
- Edit `docs/dashboard/dashboard-guide.md`
- Edit `docs/mcp/tools-and-contracts.md`
- Edit `docs/architecture/system-overview.md` if the new runtime service is part of the architecture overview
- Edit `docs/index.md`
- Edit `docs/SUMMARY.md`
- Create `docs-web/user/dashboard/custom-dashboards.md`
- Edit `docs-web/user/index.md` and relevant docs-web navigation/index files if they list dashboard pages

## Implementation Requirements
1. Document how users ask the Project Manager for a custom dashboard, review drafts, run detached validation, inspect logs, publish validated revisions, and archive/rollback safely.
2. Document the data-source node graph model at a user level: Code UX dashboard data, stats/telemetry, integrations metadata, external APIs, and unavailable-source behavior.
3. Document the backend/API/MCP contracts at a developer level, including route names, `manage_custom_dashboards` actions, publish gating, and validation session lifecycle.
4. Link the new docs from `docs/index.md`, `docs/SUMMARY.md`, and docs-web user navigation so the page is discoverable.
5. Keep claims aligned with implemented behavior from T01-T06 and do not claim validation checks pass unless the feature actually enforces them.

## Constraints
- Do not edit release notes or create release-management content.
- Do not describe unimplemented data connectors as fully available; distinguish placeholders from working Code UX data sources.
- Keep docs concise, user-facing where appropriate, and consistent with existing dashboard docs style.

## Verification
- Run `pnpm run lint` if TypeScript files were touched indirectly; otherwise run `pnpm run build` only if docs tooling is tied to the build.
- Manually verify links in `docs/index.md`, `docs/SUMMARY.md`, and docs-web user pages point to existing files.
- Success means canonical docs and docs-web both explain the custom dashboard workflow and all added links resolve.

🌿 Branch Info

Base: feature/CODUX-185-add-custom-data-dashboards
Head: task/feature-codux-185-add-custom-data-dashboards-t07-codex-mrat6ndq

---

🤖 Generated by Code UX