HQ browser Hq Ai Usage

Verification Boundary

A signed-in browser reads the deployed development service and follows existing records. The route probe can skip when the API is unavailable.

What This Suite Proves

Deployed HQ reads reach request detail. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

The probe checks successful reads and rendering rather than numerical agreement, control writes, captured-body access or complete customer acceptance.

Real Dependencies and Test Doubles

Authentication, the browser, console and development API are real. The suite uses existing seed records and does not double service reads.

Must Not Be Doubled

Retain actual navigation, permission-driven controls and the displayed states under test. A deployed run must retain its real API reads.