1. The driver set cookie name 'token' but the server uses 'arm_token',
so Playwright always saw the login page instead of the surface.
2. Split "Run All (N suites)" into a "Run All" button + separate
suite count label — count changes over time and shouldn't be
part of the button text.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The test-runner suites load asynchronously — the button only appears
after runners register. Use waitForSelector with 60s timeout instead
of a fixed 3s delay. Dump page text on failure for debugging.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Five package-level test runners validating extension API contracts:
- notes-runner: CRUD, folders, tags, search, backlinks (12 tests)
- chat-runner: conversations, messaging, search (9 tests)
- schedules-runner: CRUD + run (5 tests)
- workflow-runner: definitions, instances, stage progression (5 tests)
- renderer-runner: registry contract, block matching (4 tests)
Runner Result API (in-memory, 3 admin endpoints) stores results
from browser runs for CI consumption. Test-runners surface v0.2.0
posts results after each run and fixes suite prefix matching.
CI integration via Playwright: wait-for-healthy.sh, run-surface-tests.sh,
surface-test-driver.js. New test-runners stage in Gitea CI pipeline.
Verified: 169 passed, 0 failed, 9 warned, 8 skipped on fresh install.
Go handler tests: 4/4 passing.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
