verify-applisted

# Verifying a Chimaera change Chimaera's verification culture is explicit: **features are driven live before they land, not just unit-tested.** Terminal state, reconnect semantics, resize, and agent integrations have repeatedly had bugs that pass tests but break against the real thing. Your PR should say what you ran and what you observed. ## 1. Tests + lints first (necessary, not sufficient) ```sh just check # cargo fmt --check + clippy -D warnings + cargo test --workspace npm --prefix web-ui run check # svelte-check, if you touched the UI npm --prefix web-ui run test # targeted reducer/unit coverage npm --prefix web-ui run build # production bundle and generated assets ``` `crates/chimaera-pty` has real PTY tests (`tests.rs`, `snapshot.rs`) — extend them when you change terminal state or snapshotting. ## 2. Drive the real flow Bring up the dev loop (see the **develop** skill), then exercise the *actual* path you changed. Use the `preview_*` tooling to observe: `preview_snapshot` for structure/content, `preview_console_logs` + `preview_logs` for errors, `preview_network` for API/WS traffic, `preview_screenshot` for proof. Match the exercise to what you touched: - **Terminal / PTY** — spawn a session, type, scroll. Then **kill the socket and reattach**: the exact screen must come back (scrollback, colors, cursor, title), no lost bytes. Reattach from a second tab at a **different window size**. - **Resize / resync** — change the divider drag