The category map separates defined scenarios from missing proof. A covered category has a scenario; a binding records inspected test assertions and carries no execution result. State-model completeness and untested interactions remain explicit gaps.
A finalization fault leaves removed data outside ordinary retry. The combined scenario sets up the stated boundary, changes the upstream condition and observes its effect on the dependent outcome. Its steps and assertions are proposed; component tests do not establish this combined execution.
The target and another Websites workspace contain change and template fixtures; removal runs directly through the changes participant.
Steps
Run the target participant to completion and independently read remaining change and template rows in both workspaces.
Expected
The seeded target change and template rows are absent, its inventory is empty and the neighboring workspace is unchanged. This direct-participant check does not establish Platform plan inclusion or CMS removal.
Data
Use separate run-owned target and comparison workspace records created by the cited suite.
16A finalization fault leaves removed data outside ordinary retryinteractionapinegativeproposed
Proves
INV-DOM-PFM-TNL-005-08
Preconditions
A purge reaches workspace removal and a controlled failure occurs before request completion is persisted.
Steps
Commit workspace removal, trigger the failure, settle the purge and attempt ordinary purge retry.
Expected
The workspace stays absent and the unfinished decision remains inspectable. Ordinary retry can refuse the missing workspace; no atomic-completion guarantee is inferred from zero inventory.
Data
Create a separate run-owned workspace for each decision branch and an unaffected comparison workspace. Use a controlled clock, paused task or injected fault at the boundary named in the scenario.