Platform existing-workspace initialization

Verification Boundary

The suite invokes production lifecycle services or persistence against its test database. Each fixture and directly called participant belongs to the repository named in the register; this is a local integration boundary.

What This Suite Proves

Existing-workspace initialization is the inspected subject. The inspected engineering checks remain available in the register. Some may contribute partial assertions to capability scenarios, but the file is not claimed to implement any complete scenario; the unbound inventory records that remaining mapping work.

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.