---
id: TST-PFM-OPS-120
title: Merge participant
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - tests/integration/db/merge-participant.integration.spec.ts
implements:
  - ATS-PFM-OPS-010-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts at
    ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#plans a contact merge
    the kit can prove: no blocker stands in its way
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#plans the one login that
    moves, so the contract check had something to compare
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#answers an apply result
    the contract reads, whose actions name the tables the plan named, the association endpoints and the
    attention rows it moved
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#plans an organization
    merge the kit can prove as well
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#plans no user relink for
    an organization merge, because no Platform column holds an organization a login is
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#derives the columns it
    proved nothing was stranded in from the policy registry
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#moves the subject of an
    item about a merged contact or organization to the survivor
  - >-
    services-platform:tests/integration/db/merge-participant.integration.spec.ts#moves a contact audience
    and an organization audience to the survivors
---

# Merge participant

## Verification Boundary

This suite exercises application licensing through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise merge participant within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.