Redesign webchat as a production operator console

[njfio]

Problem statement

Tau webchat is currently closer to a diagnostics/control page than a production operator console. It mixes debug payloads with user-facing workflows, does not present a cohesive task/transcript/artifact experience, and is not yet a shareable, community-grade surface for operating the agent.

Acceptance criteria

1. Product UX defined

• Define the web application information architecture for chat, tasks, tools, artifacts, memory, cortex, routines, sessions, and share/replay flows.

2. Shared-state dependency honored

• Webchat redesign must explicitly consume the shared operator turn/task state protocol rather than endpoint-specific ad hoc payloads and raw JSON dumps.

3. Interaction workflows defined

• Define prompt submission, live streaming, approvals, interrupts, retries, artifact inspection, memory/cortex visibility, and operator controls.

4. Design system direction defined

• Define a coherent visual/system design direction suitable for a modern community-facing operator product rather than a debug page.

5. Test plan defined

• Define browser and end-to-end tests covering all major pages/views and proving runtime/webchat/dashboard parity on core workflows.

Non-goals

• TUI redesign.
• Swarm orchestration implementation beyond the webchat hooks it depends on.
• Narrow endpoint-by-endpoint cleanup without product-level IA and interaction changes.

[njfio]

Spec branch pushed: 3584-webchat-operator-console-redesign at fe6d3519. Spec link: https://github.com/njfio/Tau/blob/3584-webchat-operator-console-redesign/specs/3584-webchat-production-operator-console.md