Test Lumen

Outcome

Each completion claim is backed by a test at the real ownership boundary rather than a narrower proxy.

Prerequisites

Bootstrap the repository and start Docker. Identify the normal, failure, restart, duplicate, cross-workspace, cancellation, budget, secret, artifact, and recovery paths that apply to the change.

Steps

1. Run the owning unit or contract test while iterating.
2. Run integration tests against migrated PostgreSQL and real filesystem artifact bytes.
3. Use deterministic providers for ordinary CI; gate live providers separately.
4. Use Playwright only for actual browser behavior, including keyboard, accessibility, viewport, motion, console, network, and screenshot state.
5. Run chaos and recovery tests at the process/provider boundary being claimed.
6. Run pnpm check before integration.

Verify

Inspect what each test asserts. A green command is insufficient if its fixtures never exercise the named requirement. Save exact commands, environment, results, and honest limits in execution evidence.

Recover

When a test fails, preserve the first failure, reproduce narrowly, and fix the owning path. Do not weaken a gate, skip the case, or declare a delegate's report to be proof.

Next task

Apply the design system.