Execution model

Requests without browser capabilities use the bounded HTTP engine. It validates every initial and redirect URL, shapes headers and cookies, applies a total timeout and response-size ceiling, then extracts and asserts.

Browser runs are persisted before queue submission. Workers acquire the job, create an attempt, open an isolated context, apply profile/state/interception, navigate, execute actions in order, capture/extract/assert, persist artifacts and result, and release the context.

An assertion failure means execution_status: completed and test_status: failed. A crash or navigation failure means execution_status: failed; conflating these would hide whether the product ran correctly.