demo: --here, render the TUI in the terminal that ran the demo

--spawn needs tmux or zellij and puts the app in a second pane, which is wrong
when the capture is one terminal. --here launches the TUI through the ./ida-tui
launcher with stdio inherited, so it draws on the terminal you ran the demo
from, then drives it over the socket exactly as before and quits it at the end.

Going through the launcher rather than re-deriving the interpreter keeps the
$IDATUI_PYTHON rules in one place.

Two things this mode has to get right:

- Narration would be drawn over the app, so it is collected and replayed after
  the alternate screen is gone. The operator still sees the full scene list,
  just at the end instead of during.
- The socket is waited for with a deadline that also watches the child, so a
  TUI that dies before it ever listens fails in a second instead of hanging
  until the timeout. Teardown reaps the process (wait, then terminate, then
  kill) and removes the scratch copy on every path.

--here and --spawn are rejected together. Verified: argument handling, the
mutual exclusion, and that the pure suites are unaffected. The end-to-end
--here run is NOT verified here -- it needs a real terminal, which this
environment does not have.

0 files changed, 0 insertions, 0 deletions