Effective definitions and workspace context integration
Verification Boundary
CRM effective-definition resolution, Platform-owned layout reads, workspace context reads and shared list-page behavior cross real local database seams.
What This Suite Proves
The tests establish selection of the stored form or layout assignment, validation of assignment references and source-aware workspace calendar reads. Shared list-page tests exercise paging at the local service adapter. Workspace lifecycle reads distinguish operational workspaces from those being deleted; ephemeral-copy tests exercise the copy-specific stored premise.
What It Does Not Prove
This boundary does not prove Platform provisioning, deletion orchestration or a complete console form. It does not prove a deployed explorer query. The workspace-context reads are supporting contracts, and their inclusion does not transfer Platform ownership of the workspace lifecycle to Entities.
Level and Rationale
Resolution requires actual assignments and definitions; supplied form answers would conceal mismatched purpose or workspace ownership. Fresh context reads are essential when Platform changes a calendar or state after a prior request. Real local tables establish that CRM observes the changed source rather than cached state.
Real Dependencies and Test Doubles
CRM query functions and PostgreSQL are real. The prepared database holds the Platform-side reference tables and local stand-ins used by CRM. These fixtures establish the consumer contract; they do not certify the deployed producer or every published form-engine behavior.
Must Not Be Doubled
Keep the assignment validation and referenced definitions real. Do not replace the workspace-state read when proving changed state is observed. Shared list-page tests must preserve the production paging adapter rather than return a preassembled page.
Fixtures and Isolation
The group owns the definitions and context fixtures it introduces. Copy tests use scope-owned ephemeral destinations. Platform seed rows provide controlled premises, and teardown follows the source-declared cleanup; serial execution prevents temporary producer-table changes from affecting another group.
Determinism and Retries
Fixtures state the expected calendar zones, state vocabulary and page limits. They compare fresh reads after a source change. This register adds no automatic retries or performance threshold, because neither would prove the actual ownership and reference contracts.
How It Runs
Run the command in the frontmatter from the service repository after preparing the test database. It selects every file in this aggregate register under the repository Mocha bootstrap and runs serially. This is the aggregate selection of the integration gate; the complete repository integration command includes other modules and is wider than this register.
Coverage Gaps
This register is a local consumer integration boundary. Cross-module lifecycle and deployed form-rendering proof remain with Platform and browser suites. The component pass still owes a precise allocation of these consumers and their operational controls; no broad Platform control claim is inferred here.