### terminal platform (enabled)
- **Use for**: CLI / REPL / shell / full-screen TUI scenarios driven through a PTY.
- **Server**: `terminal-devtools` · **scenario tools**: the `tdt_scenario-*` tools
  (`tdt_scenario-add` / `-update` / `-delete` / `-list` / `-search` / `-run`).
- **Store**: project → `.ironbee/scenarios/tdt`, global → `~/.ironbee/scenarios/tdt` (the
  server's `SCENARIOS_DIR`; you pass `scope`, the server resolves the path).
- Scenario **scripts** call this platform's tools via `callTool('<bare-tool>', {...})` — discover
  the available `tdt_*` tool names from your connected MCP tool schemas; don't guess.

**What to test & how — capture the SAME evidence the verifier would** (a scenario runs FOR
verification, so its script must collect what the terminal cycle collects). In the script:
1. Pick an **evidence path** for the changed code area:
   - **Run-evidence path** — run the one-shot command with `tdt_pty_run` (`returnOutput: true`); put the
     returned output AND exit code in your result. Confirm the output is what the change should produce
     AND the exit code is expected (`0` for success, or the specific non-zero code an error/flag path
     returns) — a command that prints the right text but exits non-zero is a fail.
   - **Interactive-evidence path** — spawn the program with `tdt_pty_start` (returns a `paneId`), drive it
     with `tdt_interaction_send-keys` (tmux key syntax — `Enter`, `C-c`, `Up`, `Tab`) and/or
     `tdt_interaction_send-text` (literal text), **synchronize with `tdt_sync_wait-for`** (block until the
     expected output appears — prefer this over fixed delays), then capture with `tdt_content_capture`
     (`returnOutput: true`; `mode: stream` for line-oriented REPLs/shells with an incremental `since`
     cursor, `mode: screen` for full-screen TUIs) and put the captured output in your result. Stop the
     pane with `tdt_pty_stop` when done. Auxiliary helpers (NOT evidence): `tdt_sync_wait-for-idle`,
     `tdt_content_get-cursor`, `tdt_pty_resize` / `tdt_pty_signal` / `tdt_pty_list`.

`return` the evidence — the command output + exit code, or the captured REPL / TUI output — **plus
explicit pass/fail assertions**. That returned result is what `/ironbee-verify scenario:<name>` reads to
judge whether the terminal flow behaved correctly.
**`terminal-devtools` is for terminal programs only (CLI / REPL / shell / TUI).**