Starlight QA

Purpose

Prove that the supported journey works on the candidate revision, not merely that a page renders.

When it fires

• A web, mobile-web, API, installer, or marketplace flow is ready for verification.
• Responsive, accessibility, network, or state regressions are possible.
• A preview must be checked before merge or production.

Inputs

• Exact candidate URL or revision and supported environments.
• Critical journeys, expected outcomes, and side-effect boundaries.
• Test accounts or fixtures explicitly approved for the run.
• Accessibility, performance, and browser support requirements.