HQ browser Hq Ai Usage

Verification Boundary

The browser exercises HQ screens against fixture-backed responses.

What This Suite Proves

Routine request reads keep content private. Console role controls remain distinct. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

Mocked responses do not establish ledger agreement, model execution, delivered notices or customer isolation.

Real Dependencies and Test Doubles

The browser and console rendering are real; HQ service responses and identities are fixtures.

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.