# Browser evidence and blocker

Captured: 2026-08-02

## Genuine running-browser coverage

The repository's own Playwright configuration created an isolated API, Next application, Chromium browser, and temporary database. `npm run test:e2e` passed 4/4:

1. local login establishes an authenticated session and reaches Dashboard;
2. a saved job is created through the reviewed multi-step UI;
3. the Career Workspace shell renders its heading and explanatory copy;
4. an explicitly published synthetic CV renders anonymously and its PDF response is a real `%PDF-` document.

The Career Workspace assertion proves only the shell rendered; it does not prove every downstream panel loaded. Later direct API checks confirmed that CV-list and application-workspace endpoints fail under default SQLite.

## Interactive browser blocker

The required `browser:control-in-app-browser` skill was selected for the broader manual journey, console, keyboard, responsive, and screenshot review. Its mandatory client module was absent from the installed plugin bundle:

`C:/Users/Cesnimda/.codex/plugins/cache/openai-bundled/browser/26.721.81911/scripts/browser-client.mjs`

Import through the required browser runtime failed with `Module not found`. The skill explicitly forbids substituting standalone Playwright or another browser-control implementation when its client is missing, so the interactive review stopped at that boundary.

## Consequences

- No audit screenshots were captured.
- Browser console/network monitoring beyond the passing repository tests was not performed.
- 375px, 768px, and 1440px viewport checks, keyboard-only navigation, modal focus, reduced motion, dark-theme comparison, back/forward, refresh, multi-tab, and throttled-network checks are blocked.
- Code inspection and component tests are labelled as such; they are not represented as manual browser testing.