The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | createMergePlan | Prepare the two-contact plan and settle its questions. | CAP-CRM-DQ-012 | The preview becomes ready. | test |
| 2 | /console/{tenantId}/crm/contacts/{id}/edit | As a coordinator, edit the absorbed contact and attach a task. | CAP-CRM-ENT-004 | The ordinary edit succeeds. | test |
| 3 | executeMergePlan | Submit the earlier approval before refreshing. | CAP-CRM-DQ-016 | Execution returns the changed preview and stale details without queuing work. | test services-crm:modules/merges/tests/integration/services/merges/approval-binding.integration.spec.js#refuses an execution that submits no hash too, because the stored plan is the one last shown |
| 4 | getMergePlan | Inspect the returned preview and differences. | CAP-CRM-DQ-013 | The edited participant and new task are visible for renewed review. | observed |
| 5 | executeMergePlan | Confirm the revised preview. | CAP-CRM-DQ-016 | The job moves the task that the administrator reviewed. | test services-crm:modules/merges/tests/integration/services/merges/approval-binding.integration.spec.js#executes once the plan is looked at again and confirmed, moving the task the reviewer saw |
| 6 | updateContact | Attempt another coordinator save from the old participant screen. | CAP-CRM-DQ-018 | The service identifies the survivor and does not write an absorbed record. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | A chosen value changes on its source record. | Inspect the replacement source value and pending confirmation. | The administrator confirms it or selects another offered value. | test services-crm:modules/merges/tests/integration/services/merges/approval-binding.integration.spec.js#refuses to execute until the new value is confirmed, naming the conflict and what changed |
| alternate | 1 | A colleague refreshes the same working plan. | An older-version answer receives a conflict. | The author reloads and submits against the current preview. | test |
| failure | 5 | Another merge shares a participant and runs concurrently. | One combination succeeds and the other reports already merged. | The shared record is absorbed only once. | test |
| failure | 2 | The coordinator deletes a participant. | Planning reports the absent record and the approved attempt cannot complete. | No combination is applied. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | Approval identifies moved dependent rows and versions, preventing an unseen added task from moving under the earlier preview. | test services-crm:modules/merges/tests/integration/services/merges/approval-binding.integration.spec.js#leaves the late task on the record it was created on |
02 | A display-label rename alone does not invalidate merge approval. | test |
End-to-end policy: required: Browser review and concurrent service edits jointly determine whether stale approval and renewed confirmation are communicated correctly.