integrate-coding-agentlisted

# Integrate Coding Agent ## Overview Juggler tracks coding-agent sessions by receiving hook events and mapping them to session states (`idle`, `working`, `permission`, `compacting`, plus session create/remove). Adding an agent means building a "bridge": a notify script, an installer, an event mapping, UI, and docs. **Why this skill exists:** a past integration (Antigravity) was fully built before anyone noticed the agent has *no session-start and no session-end events* — a capability gap that reshaped what the integration could do, discovered at the very end. This skill front-loads a prerequisites check so gaps are surfaced and signed off **before** design and code. 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: Prerequisites & Capability Check (MANDATORY — before any design or code) Research the agent from its official documentation. Prefer reading the actual docs over assumptions — if the docs are ambiguous or missing, say so explicitly rather than guessing. Produce the capability matrix in 1d and get sign-off in 1e. ### 1a. Integration mechanism - Does the agent expose a hooks / plugin / event system at all? If not → stop; integration is not possible without one. - Config file: exact path, format (JSON / TOML / etc.), and schema shape. - Is config global, per-project, or both? Juggler installs globally. - Minimum agent version that supports the mechanism. - Is the mechani