snapback4 0.0.6 → 0.0.7

package/README.md

@@ -206,7 +206,11 @@ The horizon `last N by index` bounds what a device acquires per group;
 older rows are online-only, and a device's read past them says
 `complete: false`. Joining a group delivers its rows; leaving it delivers
 one scope tombstone, and the table's `retain` says what the device keeps.
-A table without `sync` is online-only: its queries run on the server.
+What it keeps under `delivered-history` it can still read locally through
+a query without a membership `require` (the server refuses the same query
+once the membership is gone, so a "history" query answers on the device
+and is empty online). A table without `sync` is online-only: its queries
+run on the server.
 
 ## 4. The client
 
@@ -308,7 +312,8 @@ flips the link.
 - **`snapback4 run <op> '<json args>' --as alice [--json]`** runs one
   operation against the local store and prints the result and the meter.
 - **`snapback4 test [--fixture dir] [--as persona]`** loads a fixture
-  (one `<table>.jsonl` per table), runs every query as each persona with
+  (one `<table>.jsonl` per table) into a fresh store in memory (without a
+  fixture, the project's dev store), runs every query as each persona with
   arguments derived from the data (a reference is the table's first row,
   a principal the persona, a text the shortest that fits), prints the
   meters beside the ceilings and the arguments it used, and names any

package/dist/replica/interpreter.d.ts

@@ -91,7 +91,12 @@ export declare class Interpreter {
      * counted. */
     private visibility;
     private ruleTrue;
-    /** The read rule for one row, with probes over the replica. */
+    /** Whether the viewer may read a held row. A synced table's rows are
+     * the partition: the server delivered each under the read rule and
+     * withdrew what it revoked, so what the device holds it may read — and
+     * what `retain delivered-history` kept after a leave stays readable here
+     * even though the server now refuses it. Only an online-only table's
+     * rows (none, unless predicted) meet the rule on the device. */
     readable(table: string, row: Row): Promise<boolean>;
     private rule;
     private permitted;

package/dist/replica/interpreter.js

@@ -703,9 +703,17 @@ export class Interpreter {
             default: return false;
         }
     }
-    /** The read rule for one row, with probes over the replica. */
+    /** Whether the viewer may read a held row. A synced table's rows are
+     * the partition: the server delivered each under the read rule and
+     * withdrew what it revoked, so what the device holds it may read — and
+     * what `retain delivered-history` kept after a leave stays readable here
+     * even though the server now refuses it. Only an online-only table's
+     * rows (none, unless predicted) meet the rule on the device. */
     async readable(table, row) {
-        const rule = this.schema.tables[table].rules.read;
+        const definition = this.schema.tables[table];
+        if (definition?.sync)
+            return true;
+        const rule = definition.rules.read;
         return this.rule(rule, undefined, row, false);
     }
     async rule(rule, old, next, insert) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snapback4",
-  "version": "0.0.6",
+  "version": "0.0.7",
   "type": "module",
   "description": "Snapback 4: the card (contract), the online and local-first clients (IndexedDB, SQLite), React hooks, sign-in, a labelled mock, and the `snapback4` CLI. LLP 3000.",
   "bin": {
@@ -42,7 +42,7 @@
     "README.md"
   ],
   "optionalDependencies": {
-    "snapback4-darwin-arm64": "0.0.6"
+    "snapback4-darwin-arm64": "0.0.7"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json",