Retained assignment API compatibility

Verification Boundary

This retained compatibility suite is included in the current service test commands. Its legacy-shaped inputs pass through adapters to the current regional implementation, so the register counts it as executable regional evidence.

What This Suite Proves

The linked source assertions contribute checks for moving the deciding address changes placement. 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

The compatibility harness translates older SDK and storage calls into the current local test infrastructure. Regional persistence and PostgreSQL supply stored outcomes, while legacy clients and transport are adapters rather than deployed services.

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.