integrate-terminallisted

# Integrate Terminal ## Overview Juggler drives terminals *outbound*: given a session it must bring the right window/tab/pane to the foreground, optionally flash a highlight color, and look up whether the session still exists. Each terminal hides these behind a `TerminalBridge`. Adding a terminal means building that bridge plus the addressing path that ties an inbound hook to a real pane, a `TerminalType` case, registration, setup UI, and docs. **Why this skill exists:** terminal integration fails on a different axis than agent integration. An agent integration can fail because the agent fires no useful *events* (inbound). A terminal integration fails because the terminal exposes no way to *control it* (outbound) — or, more subtly, no way for a pane to learn its own id, so an inbound hook can never be routed to a pane. That last gap is invisible until activation is wired up and nothing focuses. This skill front-loads a control-API capability check so those gaps are surfaced and signed off **before** design and code. This is the terminal-side sibling of the `integrate-coding-agent` skill. Same shape (capability matrix → Go/No-Go → design → implement → verify), different critical question: not "what events does it fire?" but "what can Juggler make it do, and how does it address a session?" Do the phases in order. **Do not skip Phase 1, and do not start Phase 2 until the user has signed off on the capability matrix.** ## Phase 1: Control-API Capability Check (MANDATORY — b