Interface PlanContext

The page's current URL; request paths resolve against it.

Action default when a step omits timeoutMs.

The authoritative origin gate for request steps.

validateStates also checks request origins before Chromium launches, but against the state's configured URL, while a path resolves at runtime against the live pageUrl — a script that clicks through to another origin first resolves against one the pre-launch pass never saw. The gate therefore has to be applied where the resolution happens, which is here; the pre-launch check is a convenience that fails the run early.

The predicate takes the resolved URL rather than its hostname so both gates can be the same isAllowedOrigin comparison — scheme, host and port — and a states file that validated cannot be widened at runtime.

Omitted, no gate is applied: planning is a pure function, and a caller that plans without driving a page is not making a request. The driver never omits it — see createScriptedStateRunner, which falls back to a same-origin-as-the-page gate when its own option is unset.