Local regional API lifecycle

Verification Boundary

The suite invokes the local API harness and reads persisted results in the test database. It verifies regional route handling without a deployed gateway.

What This Suite Proves

The linked source assertions contribute checks for identifier validation preserves the legacy grammar; blank names prevent creation; reads are workspace-specific; references block removal; unused regions can be removed permanently; unsaved configuration returns defaults; assignment can start with empty coverage; criteria lists require valid bounded content; rule normalization removes unrelated criteria; postal restrictions use valid country codes; omitted rules preserve the list; insertion supports append and earlier placement; deletion closes the position gap; reorder requires the complete distinct set; enabled assignment tolerates removal of its final rule; rule reads cannot cross workspaces; preview explains the winning rule; preview leaves policy unchanged; preview is read-authorized work; an address is required for preview; preview explains lack of coverage; placement is a reaction to committed creation; request processing and continuation share the run; recalculation applies changed coverage; history and individual reads expose progress; run reads cannot cross workspaces; authentication and workspace access are required; read permits listing but cannot create rules. A scenario spanning several files relies on those assertions together; this file supplies only its named checks.

What It Does Not Prove

The register establishes neither a current passing run nor verified conformance. Unbound scenarios, broader feature chains and the delegated infrastructure beyond this execution boundary remain unproved.

Real Dependencies and Test Doubles

PostgreSQL and the regional persistence under assertion are real. The suite supplies test execution contexts and fixtures; a local API harness replaces deployed transport where applicable.

Must Not Be Doubled

Regional matching, regional persistence and the stored values under assertion must remain real. A substitute answer for these dependencies cannot qualify the linked regional outcomes.