libretto-readonly

## How Libretto Read-Only Works - Use this skill when the browser session must stay strictly read-only. - Libretto stores read-only vs write-access on the session itself. - The primary inspection tools are `snapshot` and `readonly-exec`. - `readonly-exec` reuses Libretto's normal execution pipeline, but it only exposes read-only helpers and denies mutating Playwright methods. - Only a user can change the session mode for an existing session. Never change a session's mode on your own — the user must change it themselves manually. ## Working Rules - Announce which session you are using and what page you are inspecting. - Do not use `exec`, `run`, or any direct Playwright action that could change browser or application state. - Do not click, type, submit forms, navigate, upload files, dispatch DOM events, or send non-GET requests. - Prefer `snapshot` first when the visible page state is unclear. - Use `readonly-exec` for focused inspection: titles, HTML, locator text, counts, visibility checks, and GET requests. - Keep snippets small and purpose-built. Do not run multiple `readonly-exec` commands at the same time. - Close disposable sessions before your final response once inspection is complete. Open browsers keep consuming local or hosted resources. - End with diagnosis and handoff guidance, not an attempted in-browser repair. ## Commands ### `connect` - Use `connect` to attach to an existing CDP endpoint for a preserved browser session. - Use `--read-only` when creating...