dirsql 0.4.34 → 0.4.35

package/docs/reference/cli.md

@@ -498,6 +498,24 @@ and, when the query ends:
 dirsql: ran 41231 worker calls in 2m41s
 ```
 
+A worker that keeps a cache of its own can say so per response
+(`{"meta": {"cached": true}}` — see [Worker
+protocol](./config.md#worker-protocol)), and those round trips are then split
+out, because the number that answers *"will this be fast next time"* is not
+the total:
+
+```
+dirsql: running 9204 worker calls (8811 cached)
+dirsql: ran 41231 worker calls in 2m41s (38104 cached)
+```
+
+Both figures count **worker round trips, not rows**. A function declared
+`deterministic = true` lets SQLite reuse one answer for identical arguments
+within a query, so repeated content never reaches the worker at all and both
+numbers sit below the row count on a corpus with duplicates. The split covers
+only what the worker itself reports serving from cache. A worker that sends no
+`meta` gets the unsplit line above, not a `(0 cached)`.
+
 A query that calls no worker prints nothing, whatever the setting — the
 reporting only ever speaks when there is something to report.
 

package/docs/reference/config.md

@@ -161,6 +161,15 @@ request line in, one response line out, per call:
   JSON-text vectors) — or `{"err": "message"}`, which **fails the query**
   with that message. An `{"err": ...}` response leaves the healthy worker
   running; only transport failures (timeout, crash) recycle it.
+- **Optional `"meta"`**, alongside `"ok"`: a second top-level object carrying
+  facts about how the answer was produced rather than what it is. One key is
+  read today — `{"ok": [...], "meta": {"cached": true}}` says the worker
+  answered from a cache of its own, which dirsql reports as the `(N cached)`
+  split on its [worker-call progress line](./cli.md#progress-reporting). The
+  field is **optional and advisory**: a worker that omits it is a worker that
+  reports no cache hits, keys dirsql does not recognize are ignored (they
+  always have been), and a `meta` of an unexpected shape is ignored too rather
+  than failing a query over a progress counter.
 - **stderr passes through** to `dirsql`'s stderr, so a worker's progress
   bars and download logs reach the terminal.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.34",
+  "version": "0.4.35",
   "description": "Ephemeral SQL index over a local directory",
   "license": "MIT",
   "repository": "https://github.com/thekevinscott/dirsql",
@@ -213,10 +213,10 @@
     ]
   },
   "optionalDependencies": {
-    "@dirsql/lib-linux-x64-gnu": "0.4.34",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.34",
-    "@dirsql/lib-darwin-x64": "0.4.34",
-    "@dirsql/lib-darwin-arm64": "0.4.34",
-    "@dirsql/lib-win32-x64-msvc": "0.4.34"
+    "@dirsql/lib-linux-x64-gnu": "0.4.35",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.35",
+    "@dirsql/lib-darwin-x64": "0.4.35",
+    "@dirsql/lib-darwin-arm64": "0.4.35",
+    "@dirsql/lib-win32-x64-msvc": "0.4.35"
   }
 }