Each scenario names the guarantee it proves. Category coverage describes specified cases; executable bindings retain their narrower assertion boundaries. Lifecycle coverage remains a gap wherever guards and effects lack independent verification.
Accept messages for two eligible recipients, then suppress one before claiming it and throttle the other once. Run the send consumer, retry after backoff, report delivery and inspect attempts and final outcomes.
The interaction case combines the producing, processing and reading outcomes named in its frontmatter. It remains proposed until an executable suite performs that complete sequence.
Coverage
Rulecovered
Transitiongap: FND-PFM-NOT-079
Validationcovered
Permissioncovered
Edgecovered
Failurecovered
Boundarycovered
Concurrencycovered
Invariantcovered
Interactioncovered
Test Scenarios
15 scenarios proving CAP-PFM-NOT-018; 14 bound to an existing test.
01Dispatch committed pointers with recoverable claimsconcurrencyapitest
Pointer rows in two workspaces, more than one batch.
Steps
Dispatch accepted pointers, reject one queue publish, compete two runs and end a run at its time budget.
Expected
Acknowledged pointers publish in ascending creation order and are deleted; refused work returns later. Exclusive concurrent claims prevent duplicate taking, and time-limited remaining work waits for another run.
Prepare a request of three recipients and a throttling provider.
Steps
Throttle the initial receive, allow recovery, and exhaust a different request's recipient on its final receive.
Expected
Throttled drafts return with backoff and eligible sends complete in the retry fixture. At exhaustion the refused message fails and the item goes to dead-letter handling; remaining drafts are attempted only while invocation time remains.
Accept messages for two eligible recipients, then suppress one before claiming it and throttle the other once.
Steps
Run the send consumer, retry after backoff, report delivery and inspect attempts and final outcomes.
Expected
The newly protected message has no provider attempt. The other message submits through the retry path and retains provider delivery separately from dispatch state.
Data
A suite-owned workspace, named staff accounts and unique occurrence keys; external adapters record attempts without shared writes.
Prepare current request pointers, send items, earlier camel-case items, legacy message items and malformed input.
Steps
Serialize and parse each item shape using the communication queue helpers.
Expected
Current and supported earlier item shapes round-trip into the current contract. The parser identifies legacy message work and returns no supported item for malformed or unknown-version input.