@saasicat/spec 0.2.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,59 @@
+# @saasicat/spec
+
+Language-neutral spec of the SaaS platform — JSON Schemas, OpenAPI and
+acceptance test scenarios.
+
+## Contents
+
+| File                                    | Purpose                                           |
+| --------------------------------------- | ------------------------------------------------- |
+| `schemas/admin-manifest.schema.json`    | UI discovery projection of an app                 |
+| `schemas/plan-catalog.schema.json`      | App identity config format (`config/saas.yaml`)   |
+| `schemas/promo-code.schema.json`        | Promo code format incl. redemption lifecycle      |
+| `schemas/audit-event.schema.json`       | Audit log entry format                            |
+| `admin-api.openapi.yaml`                | NORMATIVE REST contract of the SuperAdmin backend |
+| `acceptance/`                           | HTTP test scenarios (stubs; runner planned)       |
+| `index.js` / `index.cjs` / `index.d.ts` | Re-exports for JS/TS consumers                    |
+
+## Usage
+
+In a consuming backend:
+
+```ts
+import { adminManifestSchema, planCatalogSchema } from '@saasicat/spec';
+import Ajv2020 from 'ajv/dist/2020';
+
+const ajv = new Ajv2020({ strict: false, allErrors: true });
+const validateManifest = ajv.compile(adminManifestSchema);
+const validateCatalog = ajv.compile(planCatalogSchema);
+
+if (!validateManifest(myManifest)) console.error(validateManifest.errors);
+if (!validateCatalog(mySaasYaml)) console.error(validateCatalog.errors);
+```
+
+Reading acceptance test scenarios as YAML:
+
+```ts
+// in the acceptance test runner (planned)
+import * as fs from 'node:fs';
+import * as path from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { glob } from 'glob';
+
+const specRoot = path.dirname(fileURLToPath(import.meta.resolve('@saasicat/spec/index.js')));
+const scenarios = await glob('acceptance/**/*.yaml', { cwd: specRoot, absolute: true });
+```
+
+```bash
+pnpm add @saasicat/spec
+```
+
+## Binding principles
+
+- **Language-neutral:** no TS code, no runtime logic. Only JSON Schemas,
+  YAML OpenAPI and JSON/YAML acceptance scenarios.
+- **No domain truth:** the schema describes the _format_, not the data.
+  App identity content lives in the consumer's `config/saas.yaml`; plans
+  live in the DB, curated via the SuperAdmin UI.
+- **`schemaVersion` is required** in every top-level schema. Major bumps
+  break — that is allowed, but must be documented in a migration note.

package/acceptance/README.md

@@ -0,0 +1,62 @@
+# Acceptance Test Scenarios
+
+HTTP-based black-box tests that run against **every** implementation of the
+SaaS platform (reference implementation: `@saasicat/nest`).
+This makes the OpenAPI contract from `admin-api.openapi.yaml` not just a
+document, but an executable set of guarantees.
+
+## Format
+
+Each scenario is a YAML file with the structure:
+
+```yaml
+scenario: 'Kurzbeschreibung des Verhaltens (1 Satz)'
+description: |
+    Längere Beschreibung — was wird hier abgesichert, warum ist es wichtig.
+    Verweise auf SPEC-Sektion oder offene Frage.
+
+setup: # state setup via Admin API calls
+    - createTenant: { slug: '...', email: '...' }
+    - createPromoCode: { code: '...', ... }
+
+when: # the action under test
+    - redeemPromoCode: { code: '...', tenantSlug: '...' }
+
+then: # expected HTTP response
+    status: 200
+    body:
+        # JSON pattern; AnyOf, contains, etc. allowed
+```
+
+## Test Runner
+
+An acceptance test runner (planned) reads each scenario, boots a test
+server, and verifies `setup` → `when` → `then` sequentially.
+
+## Scenario Backlog
+
+| Area            | Scenario                                                                                            | Status  |
+| --------------- | --------------------------------------------------------------------------------------------------- | ------- |
+| `manifest/`     | Public boot is retrievable without auth and contains **only** branding                              | 🟡 stub |
+| `manifest/`     | Full manifest requires SUPER_ADMIN, otherwise 403                                                   | 🟡 stub |
+| `manifest/`     | manifestHash stable across two boots                                                                | 🔴      |
+| `manifest/`     | ETag match returns 304                                                                              | 🔴      |
+| `promo/`        | First-time-customers-only rejects a second redemption                                               | 🟡 stub |
+| `promo/`        | Allow-zero-invoice false blocks a 100% discount                                                     | 🔴      |
+| `promo/`        | Code with `valueType=PERCENT, value>100` is rejected                                                | 🔴      |
+| `plan-version/` | Publish does not touch `Subscription.planVersionId` of existing tenants (P1 guarantee from SPEC §6) | 🟡 stub |
+| `plan-version/` | Regressive version requires tenant opt-in                                                           | 🔴      |
+| `plan-version/` | 6-week notification cron sends mail to affected subscriptions                                       | 🔴      |
+| `tenant/`       | Suspend → 403 for tenant login + audit entry with reason                                            | 🟡 stub |
+| `tenant/`       | Suspend without MFA header → 401 MFA_REQUIRED                                                       | 🔴      |
+| `mfa/`          | TOTP verify with a good code → 200, with a bad one → 401                                            | 🟡 stub |
+| `mfa/`          | System rejects MFA skip via env flag in production                                                  | 🔴      |
+
+🟡 = Stub file present, but the test runner does not process it yet
+🔴 = Yet to be written
+
+## Convention
+
+- **Scenario language:** English (wire format, language-neutral).
+- **Comments:** German is allowed, as they serve a documentation purpose.
+- **Data:** do not use real emails / slugs — `test-*` prefixes.

package/acceptance/manifest/full-manifest-requires-super-admin.yaml

@@ -0,0 +1,43 @@
+scenario: 'Full manifest endpoint requires SUPER_ADMIN role'
+description: |
+    GET /api/v1/admin/manifest MUST:
+      - 401 without JWT
+      - 403 with JWT but role != SUPER_ADMIN
+      - 200 with SUPER_ADMIN JWT
+    The manifest is never a security source, but the endpoint itself is
+    worth protecting (it exposes capabilities, endpoints, page list).
+    Spec: SPEC §10.4.
+
+setup:
+    - createTenant: { slug: 'test-acme', email: 'owner@test-acme.example' }
+    - createUser:
+          { tenantSlug: 'test-acme', email: 'tenant-admin@test-acme.example', role: 'TENANT_ADMIN' }
+    - createUser: { email: 'super@platform.example', role: 'SUPER_ADMIN' }
+
+cases:
+    - name: 'anonymous'
+      request:
+          method: GET
+          path: /api/v1/admin/manifest
+      then:
+          status: 401
+
+    - name: 'tenant-admin'
+      request:
+          method: GET
+          path: /api/v1/admin/manifest
+          auth: { as: 'tenant-admin@test-acme.example' }
+      then:
+          status: 403
+
+    - name: 'super-admin'
+      request:
+          method: GET
+          path: /api/v1/admin/manifest
+          auth: { as: 'super@platform.example' }
+      then:
+          status: 200
+          headers:
+              ETag: { matches: '^"?sha256-[A-Za-z0-9+/=_-]+"?$' }
+              Cache-Control: { contains: 'private' }
+          bodyMustValidateAgainstSchema: admin-manifest.schema.json

package/acceptance/manifest/public-boot-no-auth.yaml

@@ -0,0 +1,40 @@
+scenario: 'Public-Boot is reachable without auth and contains only branding'
+description: |
+    Pre-login boot (/api/v1/admin/boot) MUST be reachable without a Bearer token
+    and return only branding fields. Never Capabilities, pages, or endpoints.
+    Spec: SPEC §10.4 + admin-api.openapi.yaml.
+
+setup: []
+
+when:
+    - request:
+          method: GET
+          path: /api/v1/admin/boot
+          # No Authorization header
+
+then:
+    status: 200
+    bodyShape:
+        type: object
+        required: [project]
+        additionalProperties: false
+        properties:
+            project:
+                type: object
+                required: [key, displayName]
+                additionalProperties: false
+                properties:
+                    key: { type: string }
+                    displayName: { type: string }
+                    logoUrl: { type: string }
+                    environment: { type: string, enum: [production, staging, development] }
+    # Defense-in-depth check: explicitly confirm that the critical
+    # fields do NOT appear (even though additionalProperties: false
+    # implies it — the test should still fail clearly on schema drift).
+    bodyMustNotContain:
+        - capabilities
+        - navigation
+        - dashboard
+        - tenants
+        - audit
+        - planCatalogSnapshot

package/acceptance/mfa/totp-verify-good-and-bad-code.yaml

@@ -0,0 +1,57 @@
+scenario: 'TOTP-Verify accepts good code, rejects bad code'
+description: |
+    MFA mechanics. SuperAdmin has a registered TOTP secret. For
+    MFA-required endpoints the X-Mfa-Code is verified via @levminer/speakeasy
+    (Nest) or pyotp (Django). Spec: SPEC §10.5.
+
+setup:
+    - createUser:
+          email: 'super@platform.example'
+          role: 'SUPER_ADMIN'
+    - enrollMfa:
+          email: 'super@platform.example'
+          # In the test the TOTP secret is deterministic via mock RNG; the
+          # acceptance runner knows the secret and can generate valid
+          # codes.
+
+cases:
+    - name: 'valid TOTP code'
+      request:
+          method: POST
+          path: /api/v1/admin/tenants/test-mandant/suspend
+          auth: { as: 'super@platform.example' }
+          headers:
+              X-Mfa-Code: '{{generateTotpFor: super@platform.example}}'
+          body: { reason: 'test reason' }
+      pre:
+          - createTenant: { slug: 'test-mandant', email: 'x@test-mandant.example' }
+      then:
+          status: 200
+
+    - name: 'invalid TOTP code'
+      request:
+          method: POST
+          path: /api/v1/admin/tenants/test-mandant/suspend
+          auth: { as: 'super@platform.example' }
+          headers:
+              X-Mfa-Code: '000000'
+          body: { reason: 'test reason' }
+      pre:
+          - createTenant: { slug: 'test-mandant-2', email: 'y@test-mandant-2.example' }
+      then:
+          status: 401
+          body:
+              code: 'MFA_FAILED'
+
+    - name: 'missing TOTP header'
+      request:
+          method: POST
+          path: /api/v1/admin/tenants/test-mandant-3/suspend
+          auth: { as: 'super@platform.example' }
+          body: { reason: 'test reason' }
+      pre:
+          - createTenant: { slug: 'test-mandant-3', email: 'z@test-mandant-3.example' }
+      then:
+          status: 401
+          body:
+              code: 'MFA_REQUIRED'

package/acceptance/plan-version/publish-does-not-touch-bestand.yaml

@@ -0,0 +1,62 @@
+scenario: 'Plan-Version publish does not modify existing Subscription.planVersionId'
+description: |
+    P1 guarantee from SPEC §6: When a new plan version is published,
+    `Subscription.planVersionId` of the existing tenants is NOT touched.
+    Only publishedAt of the new version + supersededAt of the old version
+    are written. Migration runs exclusively through the
+    notification + renewal cron with a 6-week lead time.
+
+    This is the core guarantee for grandfathering protection. If this
+    test goes red, the implementation violates that contract protection.
+
+setup:
+    - createTenant:
+          slug: 'test-bestand'
+          email: 'owner@test-bestand.example'
+          planId: 'STANDARD'
+          billingCycle: MONTHLY
+    - assertSubscriptionVersion:
+          tenantSlug: 'test-bestand'
+          version: 1 # initial version
+    - storeAs:
+          key: 'originalPlanVersionId'
+          from: 'tenant.subscription.planVersionId'
+          tenantSlug: 'test-bestand'
+
+when:
+    # SUPER_ADMIN publishes a new version — e.g. with a price increase.
+    - createPlanVersionDraft:
+          planId: 'STANDARD'
+          changes:
+              monthlyNet: { from: 24.90, to: 29.90 }
+          changeNote: 'Q2 price increase'
+    - publishPlanVersion:
+          planId: 'STANDARD'
+          mfaCode: '{{validTotpFromAdmin}}'
+
+then:
+    # Existing subscription remains unchanged.
+    - assertSubscription:
+          tenantSlug: 'test-bestand'
+          planVersionId: '{{originalPlanVersionId}}' # ← same value as before publish
+    # The tenant keeps paying the old price.
+    - assertSubscriptionPriceMonthlyNet:
+          tenantSlug: 'test-bestand'
+          value: 24.90
+    # pendingPlanVersion fields are not yet set (the notification cron
+    # has not run yet).
+    - assertSubscription:
+          tenantSlug: 'test-bestand'
+          pendingPlanVersionId: null
+          pendingPlanVersionEffectiveAt: null
+
+    # Catalog: the old version has supersededAt, the new one has publishedAt.
+    - assertPlanVersion:
+          planId: 'STANDARD'
+          version: 1
+          supersededAt: { isNotNull: true }
+    - assertPlanVersion:
+          planId: 'STANDARD'
+          version: 2
+          publishedAt: { isNotNull: true }
+          supersededAt: null

package/acceptance/promo/first-time-only-blocks-second-redemption.yaml

@@ -0,0 +1,40 @@
+scenario: 'PromoCode with firstTimeCustomersOnly rejects second redemption from same email domain'
+description: |
+    When a code has firstTimeCustomersOnly=true, each email domain may redeem it
+    at most once. Second redemption → 422 FIRST_TIME_ONLY.
+
+setup:
+    - createPromoCode:
+          code: 'WELCOME25'
+          valueType: PERCENT
+          value: 25
+          durationType: ONCE
+          firstTimeCustomersOnly: true
+    - createTenant:
+          slug: 'test-a'
+          email: 'ada@example.com'
+          planId: 'STARTER' # consumer-specific; acceptance runner maps to a matching marketed plan
+    - redeemPromoCode:
+          code: 'WELCOME25'
+          tenantSlug: 'test-a'
+
+when:
+    # Second creation with a different domain — should work.
+    # But a second one with the same domain (sub.example.com) must block,
+    # if the implementation deduplicates by email domain.
+    - createTenant:
+          slug: 'test-a-second'
+          email: 'bob@example.com'
+          planId: 'STARTER'
+    - request:
+          method: POST
+          path: /api/v1/admin/promo-codes/redeem
+          body:
+              code: 'WELCOME25'
+              tenantSlug: 'test-a-second'
+
+then:
+    status: 422
+    body:
+        code: 'PROMO_FIRST_TIME_ONLY'
+        message: { type: string }

package/acceptance/tenant/suspend-creates-audit-and-blocks-login.yaml

@@ -0,0 +1,69 @@
+scenario: 'Tenant suspend writes audit log and blocks subsequent tenant-user login'
+description: |
+    Standard SuperAdmin action. Required behavior:
+      - 401 without MFA header (MfaGuard)
+      - 200 with valid MFA + reason
+      - AuditLog entry with action=TENANT_SUSPEND, actorTag=web:..., reason
+      - Subsequent login of a tenant user → 403 or 401 (tenant is suspended)
+
+    Spec: SPEC §10 + admin-api.openapi.yaml /tenants/{slug}/suspend.
+
+setup:
+    - createTenant:
+          slug: 'test-suspended'
+          email: 'owner@test-suspended.example'
+    - createUser:
+          tenantSlug: 'test-suspended'
+          email: 'user@test-suspended.example'
+          role: 'TENANT_USER'
+          password: 'test-password-123'
+
+cases:
+    - name: 'without MFA header'
+      request:
+          method: POST
+          path: /api/v1/admin/tenants/test-suspended/suspend
+          auth: { as: 'super@platform.example' }
+          body: { reason: 'Outstanding invoices' }
+      then:
+          status: 401
+          body:
+              code: 'MFA_REQUIRED'
+
+    - name: 'with valid MFA'
+      request:
+          method: POST
+          path: /api/v1/admin/tenants/test-suspended/suspend
+          auth: { as: 'super@platform.example' }
+          headers:
+              X-Mfa-Code: '{{validTotpFromAdmin}}'
+          body: { reason: 'Outstanding invoices over 90 days' }
+      then:
+          status: 200
+
+    - name: 'tenant-user can no longer log in'
+      request:
+          method: POST
+          path: /api/auth/login
+          body:
+              email: 'user@test-suspended.example'
+              password: 'test-password-123'
+      then:
+          status: 401
+          body:
+              code: { matches: 'TENANT_(SUSPENDED|INACTIVE)' }
+
+    - name: 'audit log contains the suspension'
+      request:
+          method: GET
+          path: /api/v1/admin/audit?entity=Tenant&action=TENANT_SUSPEND
+          auth: { as: 'super@platform.example' }
+      then:
+          status: 200
+          bodyContains:
+              items:
+                  - action: TENANT_SUSPEND
+                    entity: Tenant
+                    actorTag: { matches: "^web:super@platform\\.example:" }
+                    changes:
+                        reason: 'Outstanding invoices over 90 days'