release: 0.13.0

README.md

@@ -118,7 +118,7 @@ Patchflow does not directly handle editors, persistence or communication.
   - SyncDB/JSONL tables: [src/db-document-immutable.ts](./src/db-document-immutable.ts) (immutable.js) and [src/db-document-immer.ts](./src/db-document-immer.ts) (immer) with indexed queries and string columns that use diff-match-patch for compact history.
 - Adapters: in-memory patch store, file store, presence adapter; easy to plug your own transport.
 - Examples: interactive TCP/file demo in [examples/tcp-session.ts](./examples/tcp-session.ts) and a syncdb demo in [examples/db-immer-session.ts](./examples/db-immer-session.ts).
-- Tests: Jest coverage for patch graph, session, string docs, db docs (both backends), file queueing, presence, cursors, and working copies.
+- Tests: Vitest coverage for patch graph, session, string docs, db docs (both backends), file queueing, presence, cursors, and working copies.
 - Deterministic PatchIds: each patch has an opaque id `time` of the form `<time36>_<client>`, where `time36` is a monotone millisecond timestamp (base36, fixed width) and `client` is a per-session random id (base64url). This avoids logical-time collisions even when the same `userId` commits concurrently from multiple devices/tabs; you no longer need to allocate unique user slots in a fixed 1024-user window. For a hard guarantee, pass an explicit unique `clientId` when constructing each `Session`.
 
 ## Why the DbDocument backends (immutable/immer)?

package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchflow",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "private": false,
   "description": "Lightweight patch-based directed acyclic graph realtime sync core",
   "license": "MIT",