@saasicat/persistence-testing 1.0.0-rc.1 → 1.0.0-rc.10

package/README.md

@@ -1,5 +1,7 @@
 # @saasicat/persistence-testing
 
+## What this is
+
 The executable persistence contract for SaaSiCat adapters. One `node:test`
 suite that every adapter (Prisma and Drizzle ship today, TypeORM plugs into
 the same harness) must pass **against a real database** — this is what makes
@@ -20,12 +22,27 @@ Verified scenarios:
 - one promo redemption per subscription (unique guard)
 - audit write → query roundtrip incl. `actorTag` wildcard filters
 - MFA secret roundtrip
+- the applied settings: one row per installation, replaced only by a writer that
+  read its current fingerprint — so replicas starting together record one change,
+  concurrently — with the change and the record it supersedes landing together;
+  changes listed in the order they were recorded, acknowledged once
 
 Scenario groups gate on declared capabilities and provided slices; a
 gated-off group reports as **skipped with reason** — coverage gaps stay
 visible, never silent. Roadmap scenarios (subscription contracts, reference
 migrations N→N+1) are registered as visible skips until the slices ship.
 
+## What this is not
+
+Not a test framework and not a set of fixtures for your application. It is one
+executable contract: the suite an adapter must pass before it can claim to
+implement the ports.
+
+Not runnable without a database. The semantics it checks — row locks, rollback,
+atomic promo redemption, tenant isolation — are exactly the ones an in-memory
+double cannot have, so it needs a real PostgreSQL and says so when it does not
+find one.
+
 ## Usage
 
 ```js
@@ -33,7 +50,6 @@ import { persistenceAdapterContract } from '@saasicat/persistence-testing';
 
 persistenceAdapterContract({
     name: 'adapter-drizzle @ postgres',
-    projectKey: 'my-app',
     create: async () => ({
         adapter: {
             capabilities: { transactions: true, pessimisticLocking: true /* … */ },
@@ -64,3 +80,9 @@ fixture writes are schema-specific. See
 In-memory fakes must not be used to "verify" an adapter — they cannot
 emulate lock semantics (declare `pessimisticLocking: false` and the lock
 scenarios gate off, visibly).
+
+## Next
+
+- [Ports and adapters](../../docs/explanation/adr/0007-ports-and-adapters.md) — what a port promises
+- [Test coverage](../../docs/explanation/test-coverage.md) — what this contract reaches, and what it
+  does not

package/dist/.build-stamp

@@ -1 +1 @@
-3cc958a7edaf66125690f779f6808fab5dac7ffdf3a50fbf18f4342d7b4fe490
+d69349b8cf05ccfcfe7ed640927a191c987f4b842414f43eea7b3e496a919fa9