@saasicat/spec 0.27.0 → 1.0.0-rc.0

package/acceptance/plan-version/{publish-does-not-touch-bestand.yaml → publish-does-not-touch-existing-contracts.yaml}

@@ -11,17 +11,17 @@ description: |
 
 setup:
     - createTenant:
-          slug: 'test-bestand'
-          email: 'owner@test-bestand.example'
+          slug: 'test-existing-contracts'
+          email: 'owner@test-existing-contracts.example'
           planId: 'STANDARD'
           billingCycle: MONTHLY
     - assertSubscriptionVersion:
-          tenantSlug: 'test-bestand'
+          tenantSlug: 'test-existing-contracts'
           version: 1 # initial version
     - storeAs:
           key: 'originalPlanVersionId'
           from: 'tenant.subscription.planVersionId'
-          tenantSlug: 'test-bestand'
+          tenantSlug: 'test-existing-contracts'
 
 when:
     # SUPER_ADMIN publishes a new version — e.g. with a price increase.
@@ -37,16 +37,16 @@ when:
 then:
     # Existing subscription remains unchanged.
     - assertSubscription:
-          tenantSlug: 'test-bestand'
+          tenantSlug: 'test-existing-contracts'
           planVersionId: '{{originalPlanVersionId}}' # ← same value as before publish
     # The tenant keeps paying the old price.
     - assertSubscriptionPriceMonthlyNet:
-          tenantSlug: 'test-bestand'
+          tenantSlug: 'test-existing-contracts'
           value: 24.90
     # pendingPlanVersion fields are not yet set (the notification cron
     # has not run yet).
     - assertSubscription:
-          tenantSlug: 'test-bestand'
+          tenantSlug: 'test-existing-contracts'
           pendingPlanVersionId: null
           pendingPlanVersionEffectiveAt: null
 

package/admin-api.openapi.yaml

@@ -5,7 +5,7 @@ openapi: 3.1.0
 #
 # NORMATIVE contract for the SuperAdmin backend. Every implementation
 # (reference: @saasicat/nest) MUST fulfill this contract. Acceptance tests
-# in saas-platform-spec/acceptance/ validate implementations against exactly
+# in acceptance/ validate implementations against exactly
 # these endpoints.
 #
 # Path convention (see SPEC §8.1): All admin endpoints live under
@@ -660,7 +660,7 @@ paths:
 
     # ────────────────────────────────────────────────────────
     # Catalog V2 — Plan/Bundle/Marketing/Promotion + Discovery
-    # (CatalogModule, saas-platform-nest/src/catalog/*; DTO = SSOT for schemas)
+    # (CatalogModule, packages/nest/src/catalog/*; DTO = SSOT for schemas)
     # ────────────────────────────────────────────────────────
 
     # ── Plans ──
@@ -1240,7 +1240,7 @@ components:
             schema: { type: string, pattern: '^[a-z0-9][a-z0-9-]{1,62}[a-z0-9]$' }
 
     schemas:
-        # ────────── Catalog V2 (DTO = SSOT: saas-platform-nest/src/catalog/dto/*) ──────────
+        # ────────── Catalog V2 (DTO = SSOT: packages/nest/src/catalog/dto/*) ──────────
         CatalogPlanCreate:
             type: object
             required: [projectKey, planKey, label]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@saasicat/spec",
-  "version": "0.27.0",
+  "version": "1.0.0-rc.0",
   "description": "Language-neutral spec of the SaaS platform: JSON Schemas, OpenAPI contract, Prisma fragments, acceptance scenarios.",
   "type": "module",
   "main": "./index.cjs",
@@ -53,7 +53,7 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/uelker70/saasicat.git",
-    "directory": "packages/saas-platform-spec"
+    "directory": "packages/spec"
   },
   "bugs": {
     "url": "https://github.com/uelker70/saasicat/issues"

package/prisma-fragments/09-pending-registration.prisma

@@ -15,9 +15,9 @@
 // the reference implementation, whose tables already live under the Prisma
 // default names — a subsequent `@@map` would only force a table rename.
 //
-// Contract: saas-platform-types/registration.types.ts (PendingRegistration,
+// Contract: @saasicat/types (src/registration.types.ts) (PendingRegistration,
 //           PendingRegistrationRepository, PaymentEventLog).
-// Service logic: saas-platform-nest/registration/PendingRegistrationService.
+// Service logic: @saasicat/nest/registration (PendingRegistrationService).
 
 // Multi-step registration flow: status of a PendingRegistration
 // between sign-up-data capture (step 1) and final activation

package/prisma-fragments/README.md

@@ -5,7 +5,7 @@ related:
     - ../schemas/plan-catalog.schema.json
     - ../schemas/promo-code.schema.json
     - ../schemas/audit-event.schema.json
-    - ../../saas-platform-types/src/subscription.types.ts
+    - ../../types/src/subscription.types.ts
 ---
 
 # Prisma Fragments

package/sql/constraints.postgres.sql

@@ -1,5 +1,5 @@
 -- =============================================================================
--- SaaSicat — normative PostgreSQL constraints the Prisma DSL cannot express.
+-- SaaSiCat — normative PostgreSQL constraints the Prisma DSL cannot express.
 -- =============================================================================
 --
 -- Consumers add these statements to their SQL migration after creating the

package/sql/reference-schema.postgres.sql

@@ -1,5 +1,5 @@
 -- =============================================================================
--- SaaSicat — PostgreSQL reference schema (DERIVED ARTIFACT).
+-- SaaSiCat — PostgreSQL reference schema (DERIVED ARTIFACT).
 -- =============================================================================
 --
 -- Generated via `pnpm run gen:sql` from the prisma-fragments:
@@ -790,7 +790,7 @@ ALTER TABLE "subscription_bundles" ADD CONSTRAINT "subscription_bundles_subscrip
 ALTER TABLE "subscription_bundles" ADD CONSTRAINT "subscription_bundles_bundleVersionId_fkey" FOREIGN KEY ("bundleVersionId") REFERENCES "bundle_versions"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
 
 -- =============================================================================
--- SaaSicat — normative PostgreSQL constraints the Prisma DSL cannot express.
+-- SaaSiCat — normative PostgreSQL constraints the Prisma DSL cannot express.
 -- =============================================================================
 --
 -- Consumers add these statements to their SQL migration after creating the