Regional route permission declarations
Verification Boundary
The suite exercises regional calculations, declarations or console components with test inputs. Its assertions do not establish deployed service behavior.
What This Suite Proves
The linked source assertions contribute checks for delete authority is separate from edit authority; preview is read-authorized work; start authority uses the admin-tier key; route declarations identify the required authority; bulk work requires both regional keys; the hosted import surface contains twelve operations. 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
Test inputs, execution contexts, request clients or component dependencies are supplied by the suite. Database persistence and deployed transport are outside this boundary.
Must Not Be Doubled
The calculation, permission declaration or console behavior under assertion must remain the real implementation.