foldkit-cms-drizzle 0.1.0 → 0.1.1

package/README.md

@@ -6,12 +6,9 @@ unpublished work in three tables beside your own, and it is where the **audience
 boundary** is enforced: who is not an author is refused entries, drafts and
 revisions outright, and sees of your content only what is published.
 
-> **Status: every operation.** Saving and discarding a draft, publishing and
-> unpublishing, scheduling, archiving, restoring a revision, the worklist, an
-> entry's derived state, and the boundary. In-app preview and an example are what
-> is left of [the design](../../docs/design/cms-DESIGN.md#13-build-order).
-> Not on npm. SQLite and Postgres; MySQL has no `returning`, which the conflict
-> rule needs.
+Supports SQLite and Postgres. The conflict check requires `returning`, so this
+adapter does not support MySQL. The [CMS example](../../examples/cms/README.md)
+includes the server, in-app preview, and a browser mode over an in-memory database.
 
 ## What it owns
 
@@ -47,7 +44,13 @@ pnpm add effect drizzle-orm foldkit-cms foldkit-cms-drizzle foldkit-remote-drizz
 
 ## Example
 
-```ts
+The following is **wiring pseudocode**: `Blog`, `Posts`, `posts`, `isAuthor`,
+and the insert/update handlers belong to your application. Use
+[the runnable server](../../examples/cms/src/server.ts) for complete handlers,
+a database layer, and transaction setup. `sqliteTables()` describes tables;
+include them in your migrations before running the server.
+
+```text
 import { CmsServer, Transaction, published, sqliteTables } from 'foldkit-cms-drizzle'
 
 const cmsTables = sqliteTables() // or pgTables(); add them to your schema and migrations
@@ -88,6 +91,19 @@ RemoteServer.make({
 - **`create` and `update` go to the CMS, not to `RemoteServer.make`.** Registered
   there too, they are a way to publish with no draft, no revision and no `allow`.
 
+## Verify the audience boundary
+
+Before connecting the editor, exercise the same content read as an author and
+as a visitor. An author may see working content; a visitor must see only rows
+allowed by the binding's `visible` rule. Repeat through a relation and a query,
+not just a direct id read. CMS state and allowed actions are separate from the
+identity established by your HTTP or RPC authentication.
+
+For the first write, save a draft and read the public row again: it must be
+unchanged. Publishing should then update the row, append a revision, and remove
+the draft within the supplied transaction. A scheduled time alone executes
+nothing; your host must call `cms.due` as described below.
+
 ## Saving a draft
 
 `CmsSaveDraft` writes the working copy, valid or not. The client names something

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foldkit-cms-drizzle",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "The server half of foldkit-cms over Drizzle: the entries, drafts and revisions tables, the draft operations with their conflict rule, the worklist query, and the audience boundary between a visitor and an author.",
   "keywords": [
     "foldkit",
@@ -39,11 +39,11 @@
   ],
   "dependencies": {
     "drizzle-orm": "1.0.0-rc.4",
-    "foldkit-cms": "0.1.0",
-    "foldkit-remote": "0.5.0",
-    "foldkit-remote-server": "0.5.0",
-    "foldkit-remote-drizzle": "0.5.0",
-    "foldkit-entity": "0.2.0"
+    "foldkit-cms": "0.1.1",
+    "foldkit-entity": "0.3.0",
+    "foldkit-remote": "0.6.0",
+    "foldkit-remote-drizzle": "0.6.0",
+    "foldkit-remote-server": "0.6.0"
   },
   "peerDependencies": {
     "effect": "^4.0.0-rc.112"
@@ -54,8 +54,8 @@
     "tsdown": "^0.23.0",
     "typescript": "5.9.3",
     "foldkit-bundle": "0.2.0",
-    "foldkit-form": "0.1.1",
-    "foldkit-surface": "0.3.0"
+    "foldkit-surface": "0.4.0",
+    "foldkit-form": "0.1.2"
   },
   "scripts": {
     "build": "tsdown",