Complete chapter details acceptance

Verification Boundary

This acceptance program runs API steps through a manually invoked Mocha suite and uses the pinned console journey catalogue as its oracle. Complete chapter details acceptance defines the scope of its examples.

What This Suite Proves

The suite exercises relevant local implementation behavior, but no complete scenario binding is established in this pass. Its presence is registered without counting it as specification proof.

What It Does Not Prove

Registration supplies no fresh execution result or deployed conformance verdict. Browser behavior, deployed infrastructure and unasserted variants require separate evidence.

Real Dependencies and Test Doubles

PostgreSQL, local Membership services and the suite’s persistence path are real. The business clock and caller fixtures are controlled by the harness. API requests enter the real dispatcher with contexts signed by a test key rather than Platform’s production signer. Platform workspace coordination uses local stand-in rows.

Must Not Be Doubled

The Membership path under examination, transaction behavior and database constraints stay real. Replacing those boundaries would remove the persisted proof the suite is intended to supply.