control-cli

# Control CLI Exercise an interactive terminal program through a small, repeatable harness. Prefer a repository-native demo or test harness; only assemble a temporary PTY or terminal session when the project has no suitable one. ## Harness Loop 1. Identify the command, smallest fixture, expected ready marker, and cleanup condition. 2. Discover existing package scripts, PTY helpers, expect scripts, demo recorders, or TUI tests. 3. Launch in an isolated environment with deterministic variables and local disposable data. 4. Capture the initial screen or transcript. 5. Send one action at a time and wait for a concrete prompt or screen marker. 6. Capture the resulting transcript and any requested profile artifact. 7. Stop the process and remove temporary sessions, ports, and profiles. On Windows, prefer the project's own test runner or a checked-in Python/Node probe. Use ConPTY or an already-installed PTY helper when available; do not add a dependency just to run a one-off probe. On other systems, `tmux`, `pty`, or a repository-supported terminal harness may be appropriate. ## Evidence For a bug fix or regression, run the same deterministic interaction against the baseline and treatment and pass the captures to `verify-this`. For a hang, keep the last screen, process exit state, timeout, and a stack/CPU sample when available. For memory growth, use equal repetitions and record before/after snapshots or a bounded allocation metric. Prefer stable text markers and acc...