--- id: TST-PFM-SEC-119 title: Resend staff invitation database and service checks kind: integration product_area: platform module: security revision: 2 status: draft source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 repository: services-platform files: - >- modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js implements: - ATS-PFM-SEC-016-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: Use the prepared test database and suite-owned fixture rows; retain shared seed records. assertion_evidence: - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#security: resending a staff member’s invitation - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#the staff member who never got their invitation - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#writes a new invitation rather than reissuing the one that was outstanding - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#supersedes the one invitation that was outstanding, and says so - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#leaves the staff member with both invitations on record, newest first - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#answers that the new invitation’s e-mail went, and when it expires - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#sends it to the staff member’s own address, and answers no token anybody could read - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#makes the sign-in account the first invitation never got as far as - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#leaves the staff member invited, since nothing has been accepted yet - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#audits the resend as every lifecycle operation is audited - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#the link already in the staff member’s inbox - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is dead, and says it was superseded - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is dead where the new link works, so it is the link and not the person that was refused - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#anybody who is not a staff member - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is not found, so the route reports nothing about who exists - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#had a live invitation to resend, which is why the refusal is about who they are - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is sent nothing: a second link crossed the SES seam for the staff member and none for them - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#leaves nothing on their trail: who they are is decided before any operation on them - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#a staff member who has already accepted - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is refused, and told to reset the password instead of inviting the person again - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is still active, with the invitation it accepted under left as it was - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#is sent nothing - provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js#records the refusal on the staff member’s trail dependency_evidence: >- The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls Cognito, message delivery, the clock at the declared seams; those collaborators remain outside its live proof. evidence: - >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js - >- 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 dependency_review: provenance: test source: >- services-platform:modules/security/tests/integration/services/invitations/resend-staff-invitation.integration.spec.js explicit_no_doubles: false identified_double_boundaries: - Cognito - message delivery - the clock --- # Resend staff invitation database and service checks ## Verification Boundary The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for resend staff invitation. ## 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 prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls Cognito, message delivery, the clock at the declared seams; those collaborators remain outside its live proof. ## Must Not Be Doubled Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.