fix: install playwright chromium for US-400 CI

Author: NathanFlurry

.github/workflows/ci.yml

@@ -98,9 +98,20 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-node-modules-${{ env.NODE_VERSION }}-
 
+      - name: Cache Playwright browsers
+        uses: actions/cache@v4
+        with:
+          path: ~/.cache/ms-playwright
+          key: ${{ runner.os }}-playwright-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-playwright-
+
       - name: Install workspace dependencies
         run: pnpm install --frozen-lockfile
 
+      - name: Install Playwright Chromium
+        run: pnpm --dir packages/browser exec playwright install --with-deps chromium
+
       - name: Build registry types package first
         run: pnpm --filter @rivet-dev/agent-os-registry-types build
 

CLAUDE.md

@@ -265,6 +265,7 @@ Each agent type needs:
 - **CI should run both `cargo test --workspace --no-fail-fast` and the ignored sidecar integration suite.** The four slow sidecar isolation tests are intentionally marked `#[ignore]` for local ergonomics, so the workflow needs a dedicated `cargo test -p agent-os-sidecar -- --ignored --test-threads=1` step to keep them covered.
 - **Cache the expensive layers explicitly.** Reuse pnpm store, workspace `node_modules`, and Rust `target/`/cargo caches in CI; otherwise this repo's mixed Rust/TS pipeline gets too slow to iterate on.
 - **CI runners also need the `just` binary.** `packages/dev-shell/test/dev-shell-cli.integration.test.ts` shells out to the repo `justfile`, so GitHub runners must install `just` explicitly or the package test fails with `spawn just ENOENT`.
+- **CI runners also need Playwright's Chromium bundle for `packages/browser`.** The browser package's `test:browser` script launches Playwright against Chromium, so the workflow must install and ideally cache `~/.cache/ms-playwright` or every browser spec fails with `browserType.launch: Executable doesn't exist`.
 - **Cross-crate Rust test helpers must use repo-relative paths, never machine-local absolute paths.** `#[path = "..."]` includes under `crates/*` are compiled on CI runners with different checkout roots, so absolute developer paths like `/home/nathan/...` will break `cargo test --workspace`.
 - **Local CI reproduction:** `git lfs pull && cargo test --workspace --no-fail-fast && cargo test -p agent-os-sidecar -- --ignored --test-threads=1 && cargo build -p agent-os-sidecar && AGENTOS_E2E_NETWORK=1 pnpm test`
 - **Framework**: vitest