--- id: TST-PFM-TNL-087 title: Platform initial import reset kind: integration product_area: platform module: tenant-lifecycle revision: 1 status: draft source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 repository: services-platform files: - modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js implements: - ATS-PFM-TNL-012-09 environment: local implementation_state: implemented latest_result: not-run latest_run_at: null latest_run_ref: null conformance: not-verified estimated_minutes: 5 isolation: >- Run-owned target and comparison workspace records in the prepared test database; owner access is limited to fixture arrangement, independent inspection and cleanup of those records. evidence: - 'services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js' - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/lifecycle/participants - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/lifecycle/reset-participants - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/persistence/tenants - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/reset/reset-tenant - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/persistence/tenant-reset-jobs - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/reset/tenant-reset-workflow - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../services/persistence/tenants - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../deletion-support - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js imports ../../../../../notifications/services/persistence/tenant-purges binding_scope: >- Each implements link names a scenario whose retained cited checks all occur in this file. Partial assertions for other scenarios remain evidence only. partial_scenario_evidence: - scenario: ATS-PFM-TNL-007-06 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses the reset, naming the service and the contract it has to implement provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-011-02 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses a live tenant by name: an initial import loads only an implementation tenant provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-011-03 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#puts the tenant into its loading state - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#changes nothing when the tenant is already loading, so a repeated step is not an error provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-011-05 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#returns it to active, so its own people reach it again provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-02 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses a tenant that is not loading, naming that half of the rule - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses a live tenant, naming the other half - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#records no reset job for any tenant it refused provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-03 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses a confirmation that is not the tenant’s id, and does not say what to type - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses a missing confirmation provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-04 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses the second request as a conflict, naming the job that is running - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses before it asks any participant anything provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-05 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#refuses the reset, naming the service and the contract it has to implement - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#removes nothing at all: a half-reset tenant is the outcome worth refusing for provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-06 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#empties every table of every participant it empties, but the configuration a participant’s own reset keeps - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#keeps every table of every participant it does not empty, row for row - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#keeps the tenant row itself, which is the whole point of a reset provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-07 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#let the other macroservice re-apply its seeds, which is what a reset has and a purge has not provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-08 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#reports one progress event per participant, naming what that participant removed provenance: test scope: partial assertions; no complete scenario implementation claimed - scenario: ATS-PFM-TNL-012-10 references: - >- services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#keeps every table of every participant it does not empty, row for row provenance: test scope: partial assertions; no complete scenario implementation claimed --- # Platform initial import reset ## Verification Boundary The suite invokes production lifecycle services or persistence against its test database. Each fixture and directly called participant belongs to the repository named in the register; this is a local integration boundary. ## What This Suite Proves Initial import reset is the inspected subject. The implements links identify scenarios whose cited checks occur in this file. The original test-title references delimit those checks; partial contributions to other combined scenarios remain evidence only. ## What It Does Not Prove Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only. ## Real Dependencies and Test Doubles The local deletion harness runs the production workflow definition, task handler, job engine and Platform persistence. It advances a controlled clock and supplies recording mail, in-memory storage and ledger, remote-application, search and portal-provider seams. These doubles establish orchestration behavior rather than provider removal. ## Must Not Be Doubled Keep the production service or persistence function and the database constraints, row policies and guarded removal functions under test real. For dispatcher cases, keep route selection and authorization real as well. Provider and remote-application seams must remain explicit and cannot stand in for deployed cross-application qualification.