Studio: set up playwright #1770

Parent: #1776

Scope

Set up Playwright as the browser-level e2e runner for Studio (apps/web), reusing the
conventions already in the repo (sdk/typescript/e2e/browser/playwright.config.ts) and the
playwright: resolver already wired in .actrace.yml, so a journey here is citable as a
verify: proof from an acceptance plan.

Candidate journeys (per #1776):

• unauthenticated → login → workspace
• chat send → streamed SSE run → mid-run controls (cancel, steer, approval verdict)
• stale run control refused
• capability-gated schedules empty state
• knowledge inventory
• settings
• global search palette and the shortcuts reference
• connection-lost banner
• a rejected CSRF mutation

CI: a dedicated Playwright job, or an extension of the existing studio job (open question,
see #1776) — cached browsers, traces and screenshots as failure artifacts, same studio
relevance category so it only runs when apps/ changes.

Note

This description was written without deep research into the current apps/web test setup,
the exact shape of .actrace.yml's playwright: resolver, or CI job costs — it may contain
wrong assumptions or choices. Treat it as a starting scope, not a settled plan.

Fully or partially written by an AI agent.