(CODUX-227) Document the redesigned Tasks workflow

[numnx]

🧩 Task: Document the redesigned Tasks workflow

Automated task PR opened by Code UX for T04.

📋 Summary

Sprint: Sprint 227 · Production-grade Tasks page redesign · Task: T04

Deliver a production-grade Tasks board with a polished responsive workspace, tidy information-dense cards, dependency rows limited to task identifier and current status, accessible tokenized card action menus, synchronized documentation, and executable dashboard and browser acceptance coverage without changing task data contracts or adding dependencies.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-14 01:55:12 UTC
Finished	2026-07-14 02:06:32 UTC
Duration	11m 20s

📊 Token Usage

Metric	Value
Input tokens	159,365
Cached input tokens	2,589,952
Output tokens	12,260
Total tokens	2,761,577
Invocations	1
Tool calls	26
Active time	6m 41s

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

✅ 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 integrated Tasks redesign accurately for operators and future dashboard contributors after its behavior and acceptance coverage are settled.

## Scope
- `docs/dashboard/design-system-tasks.md`
- `docs/dashboard/dashboard-guide.md`
- `docs-web/user/dashboard/tasks.md`
- Regenerate and verify `docs-web/content/docs/user-dashboard-tasks.mdx` through the repository sync script
- Verify existing Tasks links in `docs/index.md` and `docs/SUMMARY.md`; no new navigation entry is required because this is not a new subsystem

## Implementation Requirements
1. Update the canonical Tasks design-system page with the final board hierarchy, responsive lane rules, compact dependency identifier/status contract, persistent action-menu trigger, grouped menu actions, disabled reasons, focus restoration, and reduced-motion behavior.
2. Replace outdated dashboard-guide statements about a bottom action rail or hover-revealed footer with the implemented menu workflow and describe how the page preserves filtering, sprint scope, optimistic state, QA/CI/runtime metadata, and inline editing.
3. Update the public Tasks guide so users know what each card shows, how blocking tasks are represented, how to open and keyboard-navigate the action menu, where unavailable reasons appear, and how Edit/Delete confirmation behaves.
4. Keep canonical and public descriptions outcome-focused and consistent with the tested implementation; do not claim search, actions, statuses, or visual behavior that the final page does not provide.
5. Run the docs synchronization command so generated MDX matches its source and verify that the existing documentation navigation remains valid.

## Constraints
- This task consumes the final behavior accepted by T03; do not change application code or redefine the implementation from documentation.
- Do not add a new documentation page, edit `docs/SUMMARY.md` or `docs/index.md` unnecessarily, or create a `docs-release/` directory.
- Do not preserve obsolete quick-action-rail guidance, expose private project names, or claim validation commands passed unless they were run by the responsible tasks.

## Verification
- Run `pnpm run sync:docs-web`.
- Run `pnpm run check:docs-web`.
- Confirm `docs/dashboard/design-system-tasks.md`, `docs/dashboard/dashboard-guide.md`, and `docs-web/user/dashboard/tasks.md` consistently describe the compact dependency rows and accessible task action menu, and that the generated MDX is byte-consistent with its source.

🌿 Branch Info

Base: feature/CODUX-227-production-grade-tasks-page-redesign-1
Head: task/feature-codux-22-t04-codex-1ae43191-mrk020c3

---

🤖 Generated by Code UX