---
id: TST-PFM-SEC-036
title: Invitation flow unit checks
kind: unit
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - lib/auth/__tests__/invitation-flow.test.ts
implements:
  - ATS-PFM-SEC-005-10
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: The suite owns its input fixtures and installed doubles.
assertion_evidence:
  - provenance: test
    source: 'react-console:lib/auth/__tests__/invitation-flow.test.ts#invitation flow'
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#starts by loading and asks for a link
      when there is no token
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#tells a malformed token the same
      thing the backend tells an unknown one
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#is ready to accept when nobody else
      is signed in
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#refuses to accept while another
      account is on screen, and offers to sign out
  - provenance: test
    source: 'react-console:lib/auth/__tests__/invitation-flow.test.ts#refusals'
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#gives ${refusal} its own screen with
      its own wording
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#offers a retry only when the
      invitation itself may be fine
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#ignores a retry on a refusal that
      cannot be retried
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#reads anything it does not recognise
      as the neutral refusal
  - provenance: test
    source: 'react-console:lib/auth/__tests__/invitation-flow.test.ts#accepting'
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#keeps a rejected password on the
      form, where the field is
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#moves a dead invitation off the form
      and onto its own screen
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#leaves a network failure on the form
      so the retry is just pressing the button again
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#ends accepted, and stays busy on the
      way to the console
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#ignores events that do not belong to
      the state they arrive in
  - provenance: test
    source: >-
      react-console:lib/auth/__tests__/invitation-flow.test.ts#is busy exactly while something is in
      flight
dependency_evidence: >-
  The test imports the authentication helper and supplies its inputs in-process. Browser storage,
  environment values or fetch responses are fixtures where the file replaces them; these checks do
  not call a live identity provider.
evidence:
  - 'react-console:lib/auth/__tests__/invitation-flow.test.ts'
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
---
# Invitation flow unit checks

## Verification Boundary

The file evaluates production helpers with controlled inputs in-process. The assertion references identify the source checks for invitation flow.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The test imports the authentication helper and supplies its inputs in-process. Browser storage, environment values or fetch responses are fixtures where the file replaces them; these checks do not call a live identity provider.

## Must Not Be Doubled

Keep the production helper, schema, matcher or declaration under examination real. Substituting the decision itself would remove the behavior the assertions exercise.