Domain-journey preconditions and empty API read

Verification Boundary

The browser and API clients use the deployed development console and services with run-owned records. Skipped fixture steps do not count as executed behavior.

What This Suite Proves

The suite creates a unit and checks an empty product list. It records all database steps as skipped and supplies no domain rollback proof.

What It Does Not Prove

All domain database steps are skipped. The empty API list is an empty-fixture observation and supplies no rollback or common-record save proof.

Real Dependencies and Test Doubles

The console, signed personas and development APIs are real dependencies. The run supplies its own unit, chart and records; unavailable infrastructure can skip a walk.

Must Not Be Doubled

Do not replace authentication, service responses, persistence, posting or workspace isolation with browser stubs when claiming a deployed lifecycle result.