Platform custom tables

Verification Boundary

The file dispatches requests through the real route table and signed execution contexts against its local fixtures.

What This Suite Proves

Its assertions check custom tables. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

Must Not Be Doubled

Keep the dispatcher, route requirements and the handler behavior named by the assertions real. Review any new substitutions before treating the same acceptance bindings as unchanged.