---
id: TST-MBR-STR-099
title: Chapter consolidation and membership continuation
kind: api-lifecycle
product_area: membership
module: structure
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-membership
files:
  - tests/e2e/s13-unit-merge.e2e.spec.ts
implements:
  - ATS-MBR-STR-003-04
  - ATS-MBR-STR-004-02
  - ATS-MBR-STR-003-08
  - ATS-MBR-STR-004-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: A uniquely named local workspace and its seeded records; the suite owns its fixture data and cleanup.
evidence:
  - 'services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts'
bindings:
  - scenario: ATS-MBR-STR-003-04
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah
      into Atlanta › merges Savannah, counting one affiliation moved and one ended on the survivor
    provenance: test
  - scenario: ATS-MBR-STR-003-04
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah
      into Atlanta › ends Pat’s Savannah affiliation yesterday and continues it in Atlanta as primary
      from today
    provenance: test
  - scenario: ATS-MBR-STR-003-04
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah
      into Atlanta › keeps Jo’s Atlanta affiliation and ends her Savannah one yesterday
    provenance: test
  - scenario: ATS-MBR-STR-003-04
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah
      into Atlanta › lists Jo and Pat on Atlanta’s roster today, and no one on Savannah’s
    provenance: test
  - scenario: ATS-MBR-STR-004-02
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah
      into Atlanta › refuses to delete Savannah while affiliations name it (unit_has_affiliations)
    provenance: test
  - scenario: ATS-MBR-STR-003-08
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#refuses to delete Savannah while
      affiliations name it (unit_has_affiliations)
    provenance: test
  - scenario: ATS-MBR-STR-004-07
    source: >-
      services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#refuses to delete Savannah while
      affiliations name it (unit_has_affiliations)
    provenance: test
invocation: 'npm run test:e2e'
coverage_limit: >-
  Bindings identify the concrete cases executed in this file. A compound specification may also depend on
  other registered suites or remain partly proposed; registration is not a passing execution result.
provenance: test
source:
  - 'services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts'
---

# Chapter consolidation and membership continuation

## Verification Boundary

This suite runs public API operations through the local dispatcher and checks the resulting records and responses. Chapter consolidation and membership continuation defines the scope of its examples.

## What This Suite Proves

The suite executes the concrete examples named by its binding ledger. Those examples contribute to the linked capability or feature scenarios within the boundary of the test assertions.

## What It Does Not Prove

Registration supplies no fresh execution result or deployed conformance verdict. Browser behavior, deployed infrastructure and unasserted variants require separate evidence.

## Real Dependencies and Test Doubles

PostgreSQL, local Membership services and the suite’s persistence path are real. The business clock and caller fixtures are controlled by the harness. API requests enter the real dispatcher with contexts signed by a test key rather than Platform’s production signer.

## Must Not Be Doubled

The Membership path under examination, transaction behavior and database constraints stay real. Replacing those boundaries would remove the persisted proof the suite is intended to supply.