dirsql 0.4.34__tar.gz → 0.4.36__tar.gz

{dirsql-0.4.34 → dirsql-0.4.36}/Cargo.lock

@@ -540,7 +540,7 @@ checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
 
 [[package]]
 name = "dirsql"
-version = "0.4.34"
+version = "0.4.36"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -583,7 +583,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.34"
+version = "0.4.36"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.34 → dirsql-0.4.36}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.34
+Version: 0.4.36
 Requires-Dist: tomli>=2 ; python_full_version < '3.11'
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory

dirsql-0.4.36/dirsql/cli/config_paths_from_argv.py

@@ -0,0 +1,28 @@
+"""Config-path extraction from the launcher's argv.
+
+Every config flag occurrence counts -- ``-c``/``--config`` are repeatable,
+and plugin discovery injects fragments as additional ``-c`` flags -- so the
+scan collects them all, in argv order.
+"""
+
+from __future__ import annotations
+
+
+def config_paths_from_argv(argv: list[str]) -> list[str]:
+    """Every config value in argv, in order (``--config X``, ``--config=X``,
+    ``-c X``, ``-c=X``, ``-cX``), or the default when none are given."""
+    paths: list[str] = []
+    i = 0
+    while i < len(argv):
+        a = argv[i]
+        if a == "--config" or a == "-c":
+            # A bare trailing flag (no following value) yields "".
+            paths.append(next(iter(argv[i + 1 :]), ""))
+            i += 2
+            continue
+        if a.startswith("--config="):
+            paths.append(a[len("--config=") :])
+        elif a.startswith("-c"):
+            paths.append(a[len("-c") :].removeprefix("="))
+        i += 1
+    return paths or ["./.dirsql.toml"]

{dirsql-0.4.34 → dirsql-0.4.36}/dirsql/cli/resolve_config_extensions.py

@@ -8,10 +8,6 @@ extensions and this launcher passes the resolved literal paths to the binary
 via repeatable ``--extension`` flags; the binary then loads those and ignores
 the configs' own extension entries.
 
-Every config flag occurrence counts -- ``-c``/``--config`` are repeatable,
-and plugin discovery injects fragments as additional ``-c`` flags -- so the
-scan collects them all, in argv order.
-
 Native-language configs (``.py`` / ``.js`` / ``.mjs`` / ``.cjs``) are untouched:
 the binary dispatches those to ``dirsql interpret``, whose handshake already
 carries resolved paths.
@@ -20,32 +16,13 @@ carries resolved paths.
 from __future__ import annotations
 
 from ..resolve_config_extensions import resolve_configs_extension_specs
+from .config_paths_from_argv import config_paths_from_argv
 
 # Config extensions the binary dispatches to `dirsql interpret`; never
 # pre-resolved here (that path resolves via the handshake).
 _NATIVE_SUFFIXES = (".py", ".js", ".mjs", ".cjs")
 
 
-def _config_paths_from_argv(argv: list[str]) -> list[str]:
-    """Every config value in argv, in order (``--config X``, ``--config=X``,
-    ``-c X``, ``-c=X``, ``-cX``), or the default when none are given."""
-    paths: list[str] = []
-    i = 0
-    while i < len(argv):
-        a = argv[i]
-        if a == "--config" or a == "-c":
-            # A bare trailing flag (no following value) yields "".
-            paths.append(next(iter(argv[i + 1 :]), ""))
-            i += 2
-            continue
-        if a.startswith("--config="):
-            paths.append(a[len("--config=") :])
-        elif a.startswith("-c"):
-            paths.append(a[len("-c") :].removeprefix("="))
-        i += 1
-    return paths or ["./.dirsql.toml"]
-
-
 def with_resolved_extensions(argv: list[str]) -> list[str]:
     """Return ``argv`` plus ``--extension`` flags when a TOML config names an
     extension by package name; otherwise return ``argv`` unchanged. Raises if a
@@ -53,7 +30,7 @@ def with_resolved_extensions(argv: list[str]) -> list[str]:
     if argv and argv[0] == "init":
         return argv
     config_paths = [
-        p for p in _config_paths_from_argv(argv) if not p.endswith(_NATIVE_SUFFIXES)
+        p for p in config_paths_from_argv(argv) if not p.endswith(_NATIVE_SUFFIXES)
     ]
     if not config_paths:
         return argv

{dirsql-0.4.34 → dirsql-0.4.36}/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.
 

{dirsql-0.4.34/packages/rust → dirsql-0.4.36}/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.
 

{dirsql-0.4.34 → dirsql-0.4.36}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.4.34"
+version = "0.4.36"
 # abi3 note: the `abi3-py310` pyo3 feature (below) builds ONE stable-ABI
 # `cp310-abi3` wheel per platform that loads on every CPython >= 3.10
 # (matching `pyproject.toml`'s `requires-python = ">=3.10"`), instead of

dirsql-0.4.36/packages/python/changelog.d/2026-09-04-config-paths-from-argv-module.md

@@ -0,0 +1,3 @@
+**Changed**
+
+- **The launcher's argv config-path scan moved to its own module.** `config_paths_from_argv` now lives in `dirsql/cli/config_paths_from_argv.py`; `with_resolved_extensions` imports it. Internal reorganisation with no change to the published API or CLI behavior, mirroring the TypeScript launcher. (#1042)

{dirsql-0.4.34/packages/rust → dirsql-0.4.36/packages/python}/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.
 

{dirsql-0.4.34 → dirsql-0.4.36/packages/python}/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.
 

dirsql-0.4.36/packages/python/e2e-attestations/claude-tackle-1034-cachesplit.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1788557530,
+  "exit_code": 0,
+  "commit": "97fdc1dfbdf490f71bd2067d8be66a50dce22bcb",
+  "branch": "claude/tackle-1034-cachesplit"
+}

dirsql-0.4.36/packages/python/e2e-attestations/claude-tackle-1042-py12.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1788565282,
+  "exit_code": 0,
+  "commit": "9257c5204b6cf9b491cf5487aedbf026c5255338",
+  "branch": "claude/tackle-1042-py12"
+}

{dirsql-0.4.34 → dirsql-0.4.36}/packages/python/testing-conventions.toml

@@ -10,7 +10,7 @@
 extra_scope = ["packages/rust/src", "packages/python/src"]
 
 [python]
-one_function_per_file = { max_lines = 100 }
+one_function_per_file = { max_lines = 15 }
 
 # Same floor as the root file, which this lane no longer reads.
 [python.coverage]

{dirsql-0.4.34 → dirsql-0.4.36}/packages/rust/Cargo.toml

@@ -6,7 +6,7 @@ description = "Ephemeral SQL index over a local directory"
 # version stays for the binding crates (publish = false). The literal
 # intentionally lags the published version: putitoutthere rewrites it to
 # the planned release version at build time and never commits it back.
-version = "0.4.34"
+version = "0.4.36"
 edition.workspace = true
 # Literal `license` (not `license.workspace = true`) because
 # putitoutthere's preflight check reads `[package].license` directly

{dirsql-0.4.34/packages/python → dirsql-0.4.36/packages/rust}/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.
 

{dirsql-0.4.34/packages/python → dirsql-0.4.36/packages/rust}/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.