debug-live-applisted

# Debugging a live Chimaera Chimaera's runtime bugs (terminal state, reconnect, resize, previews, agent launch) reproduce **against the real daemon + UI**, not in unit tests. This skill is how you observe one. Bring the app up with the **develop** skill (`chimaerad-isolated` preview), then read it with the `preview_*` tools. ## Read the three surfaces | Want to see… | Tool | Notes | |---|---|---| | What the **daemon** did | `preview_logs` (`level: error` to filter) | Rust `tracing` goes to the daemon's stderr; this is your server log. | | A **client** error | `preview_console_logs` (`level: error`) | JS exceptions, failed sockets, Svelte warnings. | | **API / WS** traffic | `preview_network` (`filter: failed`) | Every `/api/v1/*` call with status; pass a `requestId` to read a response body. | | The **rendered** state | `preview_snapshot` (structure) / `preview_screenshot` (visual) | Snapshot is text — better for asserting content/roles than a screenshot. | | A **CSS** value | `preview_inspect` (specific properties) | More reliable than eyeballing a screenshot. | Use `preview_eval` for one-off inspection/repro (`window.location.reload()`, read a store value) — never to *implement* a change; edit source and reload. ## Reproduce a failure 1. Bring up `chimaerad-isolated`; navigate the preview to the token URL from `preview_logs` (serve mode has no `/dev/manifest` auto-auth — the token rides the `#token=` fragment). 2. Drive the exact path that breaks (open a folder,