tui-iteration-selector — Workgraph live mirror

Metadata

Status	done
Assigned	`agent-48`
Agent identity	`f51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e`
Created	2026-04-26T16:47:34.157367371+00:00
Started	2026-04-26T16:48:08.233538556+00:00
Completed	2026-04-26T17:10:20.307413572+00:00
Tags	`eval-scheduled`
Eval score	0.80
└ blocking impact	0.82
└ completeness	0.75
└ coordination overhead	0.85
└ correctness	0.82
└ downstream usability	0.80
└ efficiency	0.80
└ intent fidelity	0.73
└ style adherence	0.85

Description

User reports: 'we are unable to select which iteration using the mouse. only with keyboard. we should be able to click on the triangles in the tui that are associated with the iteration to switch iteration.'

Pattern: somewhere in the TUI (probably the chat tab or task viewer for cycle/iteration tasks) there are visual triangle markers indicating cycle iterations. They respond to keyboard nav (arrow keys?) but NOT to mouse click. Should be clickable to jump directly to that iteration's view.

Spec

Identify the iteration triangle widget (grep for the unicode triangle char ▼ ▲ ◀ ▶ in src/tui — or check viz_viewer/state.rs for cycle iteration UI)
Wire mouse click handler so clicking a triangle switches to that iteration view
Existing keyboard nav stays — this is additive, not replacement
Hover state (if feasible) to indicate clickability

Files likely to touch

src/tui/viz_viewer/state.rs (mouse event routing, iteration selector state)
src/tui/mod.rs or wherever iteration UI is rendered
src/commands/tui_pty.rs (mouse event capture)

Validation

Failing test first: test_iteration_triangle_click_switches_iteration
Implementation makes test pass
cargo build + cargo test pass with no regressions
Manual smoke (live):
- Open wg tui on a task with cycle iterations
- Click a triangle marker → view switches to that iteration
- Keyboard nav (arrow keys / j/k) still works as before

## Description

User reports: 'we are unable to select which iteration using the mouse. only with keyboard. we should be able to click on the triangles in the tui that are associated with the iteration to switch iteration.'

Pattern: somewhere in the TUI (probably the chat tab or task viewer for cycle/iteration tasks) there are visual triangle markers indicating cycle iterations. They respond to keyboard nav (arrow keys?) but NOT to mouse click. Should be clickable to jump directly to that iteration's view.

### Spec

- Identify the iteration triangle widget (grep for the unicode triangle char ▼ ▲ ◀ ▶ in src/tui — or check viz_viewer/state.rs for cycle iteration UI)
- Wire mouse click handler so clicking a triangle switches to that iteration view
- Existing keyboard nav stays — this is additive, not replacement
- Hover state (if feasible) to indicate clickability

### Files likely to touch

- src/tui/viz_viewer/state.rs (mouse event routing, iteration selector state)
- src/tui/mod.rs or wherever iteration UI is rendered
- src/commands/tui_pty.rs (mouse event capture)

## Validation

- [ ] Failing test first: test_iteration_triangle_click_switches_iteration
- [ ] Implementation makes test pass
- [ ] cargo build + cargo test pass with no regressions
- [ ] Manual smoke (live):
  - Open wg tui on a task with cycle iterations
  - Click a triangle marker → view switches to that iteration
  - Keyboard nav (arrow keys / j/k) still works as before

Depends on

done .assign-tui-iteration-selector

Required by

(none)

Log

2026-04-26T16:47:34.156224876+00:00 Task paused
2026-04-26T16:47:49.294802010+00:00 Task published
2026-04-26T16:48:08.074792527+00:00 Lightweight assignment: agent=Careful Programmer (f5143935), exec_mode=full, context_scope=task, reason=Programmer role with Careful tradeoff is ideal for TUI state management and mouse/keyboard event integration requiring precise attention to detail.
2026-04-26T16:48:08.233540921+00:00 Spawned by coordinator --executor claude --model claude-opus-4-6
2026-04-26T16:48:15.796321374+00:00 Starting work: investigating iteration triangle UI in TUI
2026-04-26T16:53:06.549082058+00:00 Root cause: tab bar iter nav uses Alignment::Right but click handler assumes left-aligned text. Positions are off by 1+ col. Also uses == instead of ranges.
2026-04-26T17:09:18.206106016+00:00 Implementation complete: fixed tab bar iter nav click (right-aligned text offset + range-based zones), fixed detail header click (correct padding math + handle_iteration_change), added 6 unit tests for zone logic
2026-04-26T17:10:12.627336977+00:00 Committed: 12ab3ffd0 — pushed to remote
2026-04-26T17:10:12.646890929+00:00 Validated: cargo build passes, cargo test 2784 pass (6 pre-existing failures unrelated to changes)
2026-04-26T17:10:20.307421437+00:00 Task marked as done