Operate Playwright as a system, not a subprocess.

MODULE / 01

From pending to evidence

A run is persisted before dispatch. It waits when capacity is unavailable, starts on a matching workspace worker, and ends as passed, failed, or error.

• Manual and trigger-created runs share the lifecycle
• Job-level concurrency can prevent overlapping runs
• Run artifacts remain connected to the result

MODULE / 02

Runtime variables without hard-coded environments

Project runtime variables provide base URLs and execution context. Secret-aware workers support runtime redaction, while operators remain responsible for preventing sensitive data from entering traces and screenshots.

MODULE / 03

Standard Playwright, operationally visible

Action-level steps, source locations, logs, and timing make browser behavior easier to diagnose without turning the test into a proprietary format.