Changed membership configuration during checkout

Verification Boundary

The suite runs an acceptance journey through the in-process API composition with signed contexts, enforcement and PostgreSQL.

What This Suite Proves

The suite contains executable checks at the boundary described above. Its current assertions do not map to a complete authored scenario, so it receives no invented proof binding.

What It Does Not Prove

An in-process pass does not qualify deployed network calls, queues, schedules or the member’s full browser journey. Registration records existing code and leaves execution and conformance unverified.

Real Dependencies and Test Doubles

The API dispatcher, enforcement and PostgreSQL remain real. Test signing keys, controlled business dates, fixture owner rows and any recording partner ports replace deployed dependencies.

Must Not Be Doubled

Keep the prepared database, workspace boundary, exercised owner constraints and the business operation under test real. A partner double cannot substitute for the Membership write this suite claims to exercise.