managed-provider-cli

# Managed Provider CLI Use this skill when a task touches how Longhouse starts, observes, steers, or repairs provider CLIs. The core rule: Longhouse manages session control, not provider binary distribution. ## Mental Model - **Provider CLI**: an upstream executable the user installs separately, such as `claude`, `codex`, or `agy`. - **Managed session**: Longhouse owns the control path. It does not imply Longhouse owns, vendors, pins, patches, or updates the provider binary. - **Unmanaged session**: Longhouse ingests or discovers a bare provider CLI session but does not own a live control path. - **Machine Agent**: `longhouse-engine`; ships local events, owns runtime hooks/state, and may run provider-specific bridge processes. - **Runtime Host**: FastAPI/web/database product runtime. It stores session state and exposes `/api/agents/*`. ## Provider Paths ### Claude - `longhouse claude` relies on Claude's native channel/MCP/stdin control path. - Claude channel send, interrupt, and active-turn steer are first-class local control operations. Steer uses `claude-channel send --meta intent=steer` and Runtime Host must gate explicit `intent=steer` on a fresh active runtime phase; idle channel injection is not steer. - Machine Agent remote launch uses the `claude.launch` support bit and must run stock Claude under a PTY wrapper with `--dangerously-load-development-channels server:longhouse-channel` and wait for Claude channel state before Runtime Host records the lau...