fix: polish dashboard status, chat, and controls

[numnx]

What changed

• Refined the 3D chat stage so assistant replies are narrower, smaller, and farther right; the thinking cue sits above the agent and animated work tools remain visible for the full awaited reply.
• Made the workflow badge use realtime task evidence on Overview Active Streams, and show a red Human needed state only for explicit open/claimed human-owned attention with no worker assignment.
• Removed duplicate failed-sprint alarm chrome and separated the workflow overlay into an independent Delivery flow card, floating arrow, and QA review card.
• Disabled the Nodes Workflow and Dashboard chat quick actions by default behind dedicated feature flags.
• Defaulted imported, new-local, and new-remote projects to None for both Tech Stack Guidance and Styleguide.
• Migrated all production dashboard single-choice fields to AvantgardeSelect, including disabled-option keyboard handling and focus-restoration support.
• Top-aligned the Settings category pane and right-hand controls in linked setting rows.
• Updated canonical and public documentation plus focused regression coverage for each behavior.

Why

Several dashboard surfaces were deriving presentation from incomplete or transient state: Overview did not project the same realtime CI evidence as Tasks and Live, chat tool animation depended on invocation feedback arriving, and broad intervention summaries could be mistaken for human-only attention. Native selects and centered Settings rows also produced inconsistent dark-mode and layout behavior. This change centralizes those presentation rules and removes duplicate or ambiguous status UI.

Validation

• pnpm run ci — passed
  • quality guardrails
  • dependency audit (no known vulnerabilities)
  • strict typecheck/lint
  • backend coverage: 5,779 passed, 7 skipped
  • dashboard suite: 2,294 passed, 1 skipped
  • server and dashboard production builds
• pnpm run check:docs-web — passed
• git diff --check — passed
• Runtime health: /health returned all components UP; dashboard root returned HTTP 200.
• Visual browser verification at 1600×1000 confirmed the Settings pane and linked right-side controls compute to top alignment.

Risk and rollback

• Risk is concentrated in shared dashboard presentation and select primitives; cross-surface and keyboard regressions cover the changed contracts.
• The dedicated quick-action flags remain opt-in, so rollback can disable them without reverting underlying Nodes or Custom Dashboard surfaces.
• Full rollback is the revert of commit 13f91f278.