implement-rename-remaining

Implement: rename remaining 'coordinator' surfaces to 'chat'

Metadata

Statusdone
Assignedagent-744
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Modelclaude:sonnet
Created2026-04-27T16:01:17.769036780+00:00
Started2026-04-27T16:15:32.125229516+00:00
Completed2026-04-27T16:43:50.501659043+00:00
Tagstui,chat-redesign,naming, eval-scheduled

Description

Description

Sweep remaining user-visible 'coordinator' strings to 'chat' wherever it refers to the chat-agent role-noun (NOT the activity 'coordination', which is fine per CLAUDE.md).

Targets identified by research-tui-chat:

  • New chat ids: must be '.chat-N', not '.coordinator-N'
  • TUI display strings, tab labels, status lines, dialog titles
  • Display names like 'wg-workgraph-coordinator-3' → 'wg-workgraph-chat-3'
  • On-disk paths if research finds any (e.g. .workgraph/chat/coordinator-N/)

Run 'wg migrate chat-rename' if research finds graph data still using old ids. If gaps exist in the migration itself, fix the migration (or add a follow-up migration step) so it covers all current sources.

CRITICAL: the legacy aliases on CLI flags / config keys / IPC commands stay (per CLAUDE.md deprecation policy). Only user-visible strings + new chat creation ids need to change.

Validation

  • Failing test first: creating a new chat produces id '.chat-N', never '.coordinator-N'
  • grep -r 'coordinator-' src/tui/ returns no user-visible string matches (only legacy alias / migration code)
  • Display name format is 'wg--chat-N' for new chats
  • Existing graphs with '.coordinator-N' tasks still work (deprecation aliases honored) — verify via test
  • 'wg migrate chat-rename' on a sample graph with legacy ids produces a clean rename
  • cargo build + cargo test pass
  • Live-smoke: launch TUI, create a chat, observe display name + tab label both say 'chat' not 'coordinator'

Depends on

Required by

Log