Platform commercial link submission and routes

Verification Boundary

The suite sends request-shaped events through the local production dispatcher with signed caller contexts and a test database. Its API boundary is real inside the process; it does not call a deployed endpoint or drive a browser.

What This Suite Proves

Commercial link submission and routes is the inspected subject. The file contains executable engineering checks in the registered lifecycle scope. Those checks have no acceptance binding here; registration preserves their existence without assigning unsupported scenario coverage.

What It Does Not Prove

Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only.

Real Dependencies and Test Doubles

The local provisioning harness keeps the workflow definition, handler, job engine, Platform participants and database real. It replaces workflow execution with the local runner and supplies remote-application, invitation-provider and message-sender doubles. A completed fixture build therefore does not prove a deployed remote build.

Must Not Be Doubled

Keep the production service or persistence function and the database constraints, row policies and guarded removal functions under test real. For dispatcher cases, keep route selection and authorization real as well. Provider and remote-application seams must remain explicit and cannot stand in for deployed cross-application qualification.