API lifecycle for AI Usage

Verification Boundary

The suite sends requests through the real in-process dispatcher, route permissions and handlers against a prepared local database. It does not exercise API Gateway or a deployed network.

What This Suite Proves

HQ catalog access requires the staff usage key. Unqualified callers cannot inspect system usage. Windows have preceding comparisons. Customer administrators cannot use the HQ overview. Foreign and absent records are not found. Filters and cursors have bounded results. Routine request reads keep content private. Grant lists derive current window state. Customer keys cannot open staff investigations. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

The suite does not establish browser behavior, deployed routing, live model quality or actual recipient inbox delivery.

Real Dependencies and Test Doubles

The in-process dispatcher, declared routes, signed-context verification, permission evaluation, handlers, module persistence and PostgreSQL are real. The run uses its own signing key rather than production signing material.

Must Not Be Doubled

Retain PostgreSQL constraints, transaction behavior and the production persistence or dispatcher path under test. A scripted provider must not replace accounting or authorization.