The coverage map distinguishes specified examples from missing proof. A covered category means an expected case is specified; executable bindings and their run results remain separate evidence. Each required rule has a proof link or an explicit coverage finding in the structured rule ledger.
Merge leaves local dues and settlement work on the source. Prepare source dues and financial settings, merge the source, inspect the returned follow-up list and reread the source facets.
Clearing a local profile exposes program fallback. Save different local and program ordering-profile choices; resolve the sales context, clear the local choice and resolve again.
Coverage
Rulecovered
Transitionnot-applicable
Validationcovered
Permissioncovered
Edgecovered
Failuregap: FND-MBR-STR-061
Boundarygap: FND-MBR-STR-061
Concurrencycovered
Invariantcovered
Interactioncovered
Test Scenarios
9 scenarios proving CAP-MBR-STR-008; 6 bound to an existing test.
01Dues extensions require the appropriate productvalidationapinegativetest
services-membership:modules/structure/tests/integration/services/persistence/organizational-units.integration.spec.ts#organizational units in the database › merge › moves the children under the survivor, marks the unit merged and lists what it left,services-membership:modules/structure/services/persistence/organizational-unit-dues-products.ts:createDuesProduct,services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#not_moved: the dues product, the settings, the legal-entity link
08Clearing a local profile exposes program fallbackinteractionapiproposed
An isolated workspace contains the records and current versions needed for the case.
Steps
Save different local and program ordering-profile choices; resolve the sales context, clear the local choice and resolve again.
Expected
The local choice is used first and the program choice is used after clearing.
Data
Separate fixture records for the accepted and refused operations.
Source
services-membership:docs/migrations/packages-as-products/README.md#Ordering profiles (added the same day, from Commerce's decision Andrew approved at about 15:45 UTC),services-membership:docs/migrations/packages-as-products/README.md#Ordering profiles (added the same day, from Commerce's decision Andrew approved at about 15:45 UTC)
09Workspace authority gates this capabilitypermissionapinegativeproposed
An isolated workspace contains the records and current versions needed for the case.
Steps
Exercise the capability’s exposed operations with its read-only and management callers, then repeat with application access removed, an unlicensed workspace and an unavailable workspace.
Expected
Each named operation requires its declared authority; admission failures occur before any record or calculated result is exposed.
Data
Separate fixture records for the accepted and refused operations.
Source
services-membership:tests/unit/route-authorization.spec.ts#route authorization: every Membership operation names its permission › requires membership.structure.read of every structure read and membership.structure.manage of every change,services-membership:modules/configuration/aws/api/configuration.routes.ts:configurationModuleRoutes,services-membership:tests/e2e/terms-api.e2e.spec.ts#the terms API, end to end in process › refuses a caller who holds no key in the tenant