---
id: TST-MBR-STR-097
title: 'Grace, lapse and a later rejoin'
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/s04-lapse-and-rejoin.e2e.spec.ts
implements:
  - ATS-MBR-STR-016-03
  - ATS-MBR-STR-016-05
  - ATS-MBR-STR-016-06
  - FAS-MBR-STR-05-03
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/s04-lapse-and-rejoin.e2e.spec.ts'
bindings:
  - scenario: ATS-MBR-STR-016-03
    source: >-
      services-membership:tests/e2e/s04-lapse-and-rejoin.e2e.spec.ts#scenario 4: lapse, drop and rejoin
      through a staff term › answers grace the day after the term ended and lapsed once the 60 days are
      over
    provenance: test
  - scenario: ATS-MBR-STR-016-05
    source: >-
      services-membership:tests/e2e/s04-lapse-and-rejoin.e2e.spec.ts#scenario 4: lapse, drop and rejoin
      through a staff term › answers two continuity episodes
    provenance: test
  - scenario: ATS-MBR-STR-016-06
    source: >-
      services-membership:tests/e2e/s04-lapse-and-rejoin.e2e.spec.ts#scenario 4: lapse, drop and rejoin
      through a staff term › keeps the original join date and restarts continuity at the rejoin (a gap of
      437 days is more than 60)
    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/s04-lapse-and-rejoin.e2e.spec.ts'
---

# Grace, lapse and a later rejoin

## Verification Boundary

This suite runs public API operations through the local dispatcher and checks the resulting records and responses. Grace, lapse and a later rejoin 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.