dirsql 0.4.31 → 0.4.33

package/docs/reference/cli.md

@@ -483,6 +483,24 @@ dirsql: indexed 41231 files in 3m12s
 
 stdout is untouched — it carries the query result and nothing else.
 
+A query gets the same treatment when it calls a
+[worker-backed function](./config.md#dirsql-function). Those cost one round
+trip per row, so a query that calls one over a whole corpus is the slowest
+thing dirsql does:
+
+```
+dirsql: running 9204 worker calls
+```
+
+and, when the query ends:
+
+```
+dirsql: ran 41231 worker calls in 2m41s
+```
+
+A query that calls no worker prints nothing, whatever the setting — the
+reporting only ever speaks when there is something to report.
+
 By default this is **terminal-only, and only for work slow enough to wonder
 about**: a phase that finishes in under half a second prints nothing at all,
 and a run whose stderr is a pipe or a file prints nothing regardless of how

package/docs/reference/config.md

@@ -133,6 +133,11 @@ process alive for the rest of the invocation, sending it every subsequent
 call — one process total, never one per row or per file. The worker is torn
 down when the invocation ends.
 
+A query paying per-row round trips reports them on stderr while it runs
+(`dirsql: running 9204 worker calls`), on the same terms as every other
+[progress line](./cli.md#progress-reporting): terminal-only by default, silent
+on a pipe, and gone before the result is printed.
+
 The `timeout` bounds each **round-trip call**, not the query: a query that
 calls the function on 10 000 rows is 10 000 individually timed calls. A call
 that times out, or a worker that crashes or closes its pipes, fails the query

package/docs/reference/sdk.md

@@ -408,6 +408,10 @@ one summary of what each cost:
 dirsql: indexed 41231 files in 3m12s
 ```
 
+A `query` that calls a worker-backed function is reported the same way, as a
+running count of round trips (`dirsql: running 9204 worker calls`) — the shape
+`dirsql-plugin-embeddings` produces when it embeds a corpus one row at a time.
+
 This is terminal-only by default, and only for a phase that runs longer than
 half a second — a program whose stderr is a pipe, a file, or a log collector
 sees nothing, whatever the scan costs. Set `DIRSQL_PROGRESS=never` to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.31",
+  "version": "0.4.33",
   "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.31",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.31",
-    "@dirsql/lib-darwin-x64": "0.4.31",
-    "@dirsql/lib-darwin-arm64": "0.4.31",
-    "@dirsql/lib-win32-x64-msvc": "0.4.31"
+    "@dirsql/lib-linux-x64-gnu": "0.4.33",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.33",
+    "@dirsql/lib-darwin-x64": "0.4.33",
+    "@dirsql/lib-darwin-arm64": "0.4.33",
+    "@dirsql/lib-win32-x64-msvc": "0.4.33"
   }
 }