How it fits together

Where the CLI, runner, browser adaptor, Keys adaptor, and reporting sit relative to your app, CI, and providers.

At a high level:

Your app — the system under test (UI, APIs, agents).
Testing CLI / CI job — loads restormel-testing.yaml, validates against MVP rules, starts runs, emits exit codes.
Runner — coordinates goals, retries, success criteria, verdicts, and artefact writes.
Browser adaptor — Playwright (MVP) for real browser execution.
Keys adaptor — resolves logical model references to provider execution; aligns with your Keys project.
Providers / gateways — unchanged; Keys stays the control layer for resolve policy.

Canonical env and key vocabulary for Keys lives in Keys docs—start at Keys integration or the full dashboard journey Keys + Testing onboarding.