SGraph-AI__Service__Playwright

Code-derived reference of the FULL sg-playwright capability surface — every HTTP endpoint, its request/response schema and field defaults, and every one of the 25 declarative step verbs with their parameters and enums. Trigger when you need the EXACT shape of a request or response, the complete list of endpoints/step actions, a field's default value or type, which probe verbs /inspect allows, or you are building/extending a client or the default "Try it out" test page and need a checkable field-by-field map. This is the lookup table; for task-oriented "how do I drive a browser over HTTP" recipes and the auth-header split use the companion skill `use-sg-playwright`. Source of truth is the code under `sg_compute_specs/playwright/core/` at v0.2.63 — not capabilities.json (frozen at v0.1.29) nor the reality doc (stale on endpoint count). file_path:line references included so every claim is verifiable.

Drive the SG/Playwright browser-automation service over HTTP — navigate pages, run scripted multi-step sequences, take screenshots/PDFs, extract DOM/text/HTML, batch-probe one page from many angles, or hold a stateful browser session. Trigger when the user asks to "navigate to a URL", "take a screenshot of a page", "scrape a page", "fill a form on a site", "extract the DOM from", "render a PDF of", "click a button on", "drive a browser", or any phrasing that means "remote-control a real Chromium instance through the sg-playwright API". The launching operator gives you a HOST (the FQDN of an ephemeral sg-compute EC2 / a /pw vault proxy) and a TOKEN; every call is HTTP — you hold no browser yourself. CRITICAL on auth: use `x-sgraph-access-token: ${TOKEN}` for `${HOST}/pw/...` (the proxied production path) and `X-API-Key: ${TOKEN}` for direct stack access — sending the wrong header gets 401 on every call.