A merge preview must let an administrator settle differences before execution. Survivor selection, retained communication details and participant effects must describe one consistent proposed result.
Changing participants can invalidate decisions; changing source values or dependent work can invalidate approval. The suite checks these handoffs while retaining consent and participant safeguards. Every sequence remains proposed until one executable selection asserts its full outcome. Existing capability assertions supply evidence for parts of the sequence.
Two compatible run-owned contacts disagree on a retained scalar field.
Steps
Create the plan, override its survivor and inspect the resulting questions.
Expected
The chosen survivor remains selected and the preview exposes the relevant differences.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Contacts have competing e-mail choices, different consent values and overlapping activity links.
Steps
Review scalar and collection decisions, choose retained values and recompute the preview.
Expected
The resolved preview follows the cited checks for consent, communication slots and related links.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
A reviewed working plan contains valid saved decisions.
Steps
Change the participant set, then answer a remaining question and read the preview again.
Expected
Applicable decisions survive and answers belonging to removed participants do not remain effective.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Contact-only and organization-only personas have distinct permission sets.
Steps
Attempt planning for both types and compare the permitted and refused requests.
Expected
A persona can prepare only the type for which it holds the full required permission pair.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
A ready preview has been shown before a dependent task or chosen source value changes.
Steps
Keep the earlier approval material, change the dependent record, submit that earlier approval and then refresh the preview.
Expected
The earlier approval is refused; the new preview makes the changed material available for renewed review.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.