Check drafts and account for block overrides: Acceptance Scenarios

Coverage

Required Rule	Acceptance Scenario
`BR-CAP-CRM-DQ-004-01`	`ATS-CRM-DQ-004-01`, `ATS-CRM-DQ-004-07`
`BR-CAP-CRM-DQ-004-02`	`ATS-CRM-DQ-004-01`
`BR-CAP-CRM-DQ-004-04`	`ATS-CRM-DQ-004-02`, `ATS-CRM-DQ-004-07`
`BR-CAP-CRM-DQ-004-05`	`ATS-CRM-DQ-004-03`
`BR-CAP-CRM-DQ-004-06`	`ATS-CRM-DQ-004-04`
`BR-CAP-CRM-DQ-004-07`	`ATS-CRM-DQ-004-04`, `ATS-CRM-DQ-004-05`
`BR-CAP-CRM-DQ-004-08`	`ATS-CRM-DQ-004-05`
`BR-CAP-CRM-DQ-004-10`	`ATS-CRM-DQ-004-06`
`BR-CAP-CRM-DQ-004-13`	`ATS-CRM-DQ-004-08`
`BR-CAP-CRM-DQ-004-11`	No scenario yet; `FND-CRM-DQ-032` records the proof gap.

Show evidence (sources, provenance, origins, pinned commits)

8 scenarios proving CAP-CRM-DQ-004; 8 bound to an existing test.

01 Draft results honor confidence and exclude the edited recordapitest

Proves: BR-CAP-CRM-DQ-004-01 BR-CAP-CRM-DQ-004-02
Preconditions: Prepare many draft look-alikes, its own saved record and a very-high rule floor.
Steps: Request the draft check.
Expected: No more than five ranked matches appear, excluding self and below-floor candidates.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/detection/duplicate-checks.integration.spec.js#answers at most the five a form shows, however many the tenant holds
services-crm:modules/duplicates/tests/integration/services/detection/duplicate-checks.integration.spec.js#does not answer the record itself, a record never being its own duplicate
services-crm:modules/duplicates/tests/integration/services/detection/duplicate-checks.integration.spec.js#answers no record, the pair scoring 70 and the tenant asking for 90
Source: services-crm:modules/duplicates/tests/integration/services/detection/duplicate-checks.integration.spec.js#answers at most the five a form shows, however many the tenant holds

02 Checking does not create review workapitest

Proves: BR-CAP-CRM-DQ-004-04
Preconditions: A draft resembles an existing contact.
Steps: Check the draft and read candidates afterwards.
Expected: The review queue retains its earlier contents.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#writes nothing: the draft is not a record, so the queue is as it was
Source: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#writes nothing: the draft is not a record, so the queue is as it was

03 Draft checking requires duplicate-read authorityapinegativetest

Proves: BR-CAP-CRM-DQ-004-05
Preconditions: Use a caller with no duplicate permission.
Steps: Submit a check request.
Expected: Access is denied.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to a caller with no duplicates permission at all
Source: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to a caller with no duplicates permission at all

04 Overrides validate reasons and commit with creationapinegativetest

Proves: BR-CAP-CRM-DQ-004-06 BR-CAP-CRM-DQ-004-07
Preconditions: A blocking rule refuses the intended create.
Steps: Try absent and blank reasons, no rule, a failing audit write and then a valid override.
Expected: Invalid fields are named, an audit failure leaves no contact and the valid create retains one attributed override record.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#refuses an override with no reason, naming the field
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#refuses an override naming no rule, naming the field
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#leaves no contact behind, the record and its audit sharing one transaction
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#records the override in the create, about the record the create made
Source: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#refuses an override with no reason, naming the field

05 Override records cannot be duplicated or updatedapinegativetest

Proves: BR-CAP-CRM-DQ-004-07 BR-CAP-CRM-DQ-004-08
Preconditions: A record already has a block override.
Steps: Insert another override and attempt an application update.
Expected: Both writes are refused.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#refuses a second override of the same record, a record being created once
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#is not rewritable by the application, which holds no UPDATE on the audit
Source: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-block-overrides.integration.spec.js#refuses a second override of the same record, a record being created once

06 Organization exceptions use the same accountable boundaryapitest

Proves: BR-CAP-CRM-DQ-004-10
Preconditions: Configure an organization blocker and an existing match.
Steps: Create ordinarily, then override with authority and a reason.
Expected: Ordinary creation identifies the blocking match; the authorized exception creates an audited organization.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/organization-block-rules.e2e.spec.js#refuses an ordinary user’s create 409 possible_duplicate, naming the held organization
services-crm:modules/duplicates/tests/e2e/organization-block-rules.e2e.spec.js#audits the override with its reason, its rule and the organization it was let past
Source: services-crm:modules/duplicates/tests/e2e/organization-block-rules.e2e.spec.js#refuses an ordinary user’s create 409 possible_duplicate, naming the held organization

07 The form displays suggestions only for a useful draftbrowsertest

Proves: BR-CAP-CRM-DQ-004-01 BR-CAP-CRM-DQ-004-04
Preconditions: Prepare an existing member.
Steps: Enter matching details, then remove the name.
Expected: Up to five suggestions appear without writes, and the nameless form shows no suggestions.
Data: The existing scenario setup supplies the required records.
Bound to: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0243.spec.ts#CRM-ACC-0243
Source: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0243.spec.ts#CRM-ACC-0243

08 Unsupported check record types are rejectedapinegativetest

Proves: BR-CAP-CRM-DQ-004-13
Preconditions: Use an authorized duplicate reader.
Steps: Request a draft check for an unsupported record type.
Expected: The API returns an invalid-request refusal naming the type.
Data: Use the records and caller described in this scenario.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#refuses a record type detection does not run over, naming the segment (400)
Source: services-crm:modules/duplicates/aws/api/duplicates.routes.ts:objectTypeOf