implement-tui-visual

Implement: TUI visual treatment differentiates .chat-* vs .coordinator-*

Metadata

Statusdone
Assignedagent-743
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Modelclaude:sonnet
Created2026-04-27T16:01:48.090421670+00:00
Started2026-04-27T16:15:31.424042133+00:00
Completed2026-04-27T16:40:25.586723274+00:00
Tagstui,chat-redesign,visual, eval-scheduled

Description

Description

In the TUI, '.chat-' tasks are first-class chat agents. '.coordinator-' tasks are legacy/deprecated and should look visually distinct so users (and we) can tell them apart at a glance during the deprecation window.

Apply different visual treatment in:

  • Tab labels (tab bar)
  • Graph viewer node rendering
  • Task list / status views
  • Anywhere a chat task id is rendered

Suggested treatment (adjust based on existing palette):

  • '.chat-*' → primary/accent color, full opacity, bold-ish
  • '.coordinator-*' → muted/dim color (grey or desaturated), maybe with a 'legacy' marker or strikethrough

The styling should be minimal — a single style helper that maps task-id-prefix → style — not a sprinkle of conditionals across the rendering code.

Validation

  • Failing test first: a tab/node rendered for '.coordinator-N' has a different style than one for '.chat-N' (assert via style attrs in unit test)
  • Style helper is a single function/lookup, not duplicated logic
  • Live-smoke: open a graph containing both '.coordinator-3' and '.chat-1', visually verify they look different in:
    • tab bar (if both happen to be open as tabs)
    • graph viewer
    • status/list views
  • cargo build + cargo test pass

Depends on

Required by

Log