e2e-session-test

# cctop end-to-end session test Verify a real session flows all the way through: ``` agent in a terminal → cctop hooks → ~/.cctop/sessions/<pid>.json → panel card ``` A good smoke test after touching hooks, the session schema, or the panel. ## Capabilities, not tools Harness-agnostic — it needs three generic capabilities. Use your environment's equivalent; don't assume a specific tool: - **run shell commands** - **capture a screenshot** of the screen (or fall back to the `screencapture` CLI) - **view an image** you captured ## Create the session with a CLI agent in a terminal Drive a CLI agent (`claude` / `codex` / `opencode` / `pi`) in a terminal window — it's a real session and one shell command starts it. Don't try to puppet a *desktop* agent's GUI: if it's the app hosting you, screen capture hides its window and you can't confirm input landed (see `references/troubleshooting.md`). Requires a cctop build with the `cctop://` URL scheme (ships with this skill). ## Steps (run from the repo root) ```bash # 1. Baseline — note the PIDs .claude/skills/e2e-session-test/scripts/cctop-sessions.sh # 2. Create a session — opens a terminal running the agent, waits for it to register .claude/skills/e2e-session-test/scripts/launch-cli-session.sh claude ~/projects/cctop # 3. Verify — a new PID entry with the right source (cc/codex/opencode/pi) appears .claude/skills/e2e-session-test/scripts/cctop-sessions.sh # 4. Summon the panel open cctop://toggle ``` Then **capture a scre...