fix-nex-cursor-corruption

Implement: fix new-chat dialog cursor-block "█" corruption (per research-nex-chat)

Metadata

Statusdone
Assignedagent-1799
Agent identity3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3
Modelcodex:gpt-5.5
Created2026-05-02T23:53:57.255303560+00:00
Started2026-05-03T01:04:57.331469477+00:00
Completed2026-05-03T01:21:23.754098520+00:00
Tagsfix,nex,chat,tui,bug, eval-scheduled
Eval score0.79
└ blocking impact0.90
└ completeness0.70
└ constraint fidelity0.70
└ coordination overhead0.85
└ correctness0.80
└ downstream usability0.75
└ efficiency0.85
└ intent fidelity0.44
└ style adherence0.90

Description

Description

Apply the patch proposed by research-nex-chat to eliminate the FULL BLOCK U+2588 cursor glyph from being captured into the endpoint string in the new-chat dialog.

Implement directly — do not decompose further.

File scope (limit to these files)

  • src/tui/viz_viewer/event.rs (dialog input handlers)
  • tests/ (add unit / integration test for the corruption)

DO NOT touch: state.rs (other dialog work), launcher rendering, coordinator/supervisor code.

Validation

  • Failing test written first that reproduces the cursor-glyph capture (per research-nex-chat's repro)
  • Implementation makes the test pass
  • cargo build + cargo test pass with no regressions
  • Manual repro: open wg tui, drive new-chat dialog through the path identified in research, verify endpoint string is clean (no U+2588 or other cursor cells)

Depends on

Required by

Log