[Feature]: Evaluate phased migration from neo-neo-bblessed to OpenTUI React #590
Description
Is your feature request related to a problem? Please describe.
The current `neo-neo-bblessed` stack keeps the TUI working but makes rich terminal rendering and layout expensive to maintain.
Describe the solution you'd like
Evaluate a phased move to OpenTUI React so we keep the current keyboard-first experience while improving terminal-native Markdown, tables, code blocks, and the path to Mermaid/rich content.
Additional context
Start with one prototype behind a flag (likely task detail), validate performance and standalone binary packaging, then only migrate further if it clearly beats the current stack. This is a concrete follow-up to #298.