dirsql 0.4.80__tar.gz → 0.4.82__tar.gz

{dirsql-0.4.80 → dirsql-0.4.82}/Cargo.lock

@@ -552,7 +552,7 @@ checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
 
 [[package]]
 name = "dirsql"
-version = "0.4.80"
+version = "0.4.82"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -602,7 +602,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.80"
+version = "0.4.82"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.80 → dirsql-0.4.82}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.80
+Version: 0.4.82
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index

{dirsql-0.4.80 → dirsql-0.4.82}/dirsql/_async.py

@@ -137,7 +137,7 @@ class DirSQL:
             if config_extensions is not None:
                 extensions = [*(extensions or []), *config_extensions]
                 suppress = True
-        return _RustDirSQL(
+        return self._new_core(
             self._root,
             tables=self._tables,
             ignore=self._ignore,
@@ -149,6 +149,9 @@ class DirSQL:
             suppress_config_extensions=suppress,
         )
 
+    def _new_core(self, root, **kwargs):
+        return _RustDirSQL(root, **kwargs)
+
     def _resolved_extensions(self):
         """Resolve each programmatic extension's ``path`` to a loadable file.
 

{dirsql-0.4.80 → dirsql-0.4.82}/dirsql/cli/discover_plugins/with_discovered_plugins.py

@@ -4,24 +4,21 @@ This is the public entry point of the ``discover_plugins`` package (installed =
 active, CLI only; #363/#529). A plugin is an ordinary Python package that
 declares ``[project.entry-points.dirsql]`` naming its top-level module and ships
 a ``dirsql.toml`` fragment there; when installed alongside ``dirsql``, the
-``pip``/``uvx`` launcher discovers it and injects the fragment as a ``-c`` flag
-plus the hidden ``--include-default`` (#604) when the user gave no ``-c``.
+``pip``/``uvx`` launcher discovers it and injects the fragment as a ``-c`` flag.
 Opt out via ``--no-plugin`` / ``DIRSQL_NO_PLUGIN=1``. The compiled binary knows
 nothing about plugins, and the SDK never discovers -- only this CLI launcher.
-The helpers each live in their own module (``user_passed_config``,
-``discovery_disabled``, ``fragment_path``, ``discovered_fragments``).
+The helpers each live in their own module (``discovery_disabled``, ``fragment_path``, ``discovered_fragments``).
 """
 
 from __future__ import annotations
 
 from .discovered_fragments import discovered_fragments
 from .discovery_disabled import NO_PLUGIN_FLAG, discovery_disabled
-from .user_passed_config import user_passed_config
 
 
 def with_discovered_plugins(argv: list[str]) -> list[str]:
     """Return ``argv`` with each installed plugin's fragment appended as ``-c``
-    (plus ``--include-default`` when the user passed no ``-c``). ``--no-plugin``
+    ``--no-plugin``
     / ``DIRSQL_NO_PLUGIN`` skip discovery, consuming the flag. ``init`` and ``context`` take no
     config, so they are left untouched. Raises if a declared plugin is missing its
     module or fragment (the launcher surfaces a clean error).
@@ -40,8 +37,6 @@ def with_discovered_plugins(argv: list[str]) -> list[str]:
     if not fragments:
         return argv
     injected: list[str] = []
-    if not user_passed_config(argv):
-        injected.append("--include-default")
     for fragment in fragments:
         injected.append("-c")
         injected.append(fragment)

{dirsql-0.4.80/packages/rust → dirsql-0.4.82}/docs/howto/write-a-plugin.md

@@ -195,10 +195,9 @@ Discovery is deliberately narrow. Know exactly who does what:
 - **The `uvx`/`pip` launcher injects `-c <fragment>` per installed plugin.**
   Each discovered plugin's fragment is appended after your own `-c` configs, so
   your config still takes ordering precedence
-  ([composing configs](../reference/config.md#composing-multiple-configs)). When
-  you pass no `-c` of your own, the launcher also keeps the
-  shipped starter `records` table (an internal `--include-default`), so plugins
-  **add** tables rather than standing alone. Discovery is **pip/uvx only** for now — the `npx`
+  ([composing configs](../reference/config.md#composing-multiple-configs)). The
+  launcher adds only the plugin's tables and functions; it seeds no `records`
+  table. Discovery is **pip/uvx only** for now — the `npx`
   launcher does not yet discover — and is switched off per invocation with
   [`--no-plugin` or `DIRSQL_NO_PLUGIN=1`](../reference/cli.md#plugins).
 - **The SDK never auto-discovers.** Pass a plugin's config explicitly (the

{dirsql-0.4.80 → dirsql-0.4.82}/docs/reference/cli.md

@@ -465,7 +465,8 @@ installed in the same environment as `dirsql` (`pip install …`, or
 loads its fragment — its tables are queryable with zero config edits.
 Installed = active: there is no enable step and no naming convention. The
 fragment is composed *after* your own `-c` configs (so your config takes
-precedence in ordering), and the shipped starter `records` table is preserved.
+precedence in ordering). A plugin adds its own tables and nothing else: no
+`records` table is seeded.
 
 Discovery is **launcher-only** — the standalone `cargo`-installed binary does no
 discovery, and the SDKs never auto-discover (pass a plugin's config explicitly

{dirsql-0.4.80 → dirsql-0.4.82}/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.80"
+version = "0.4.82"
 # 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.82/packages/python/changelog.d/2026-10-06-plugin-no-default-records.md

@@ -0,0 +1 @@
+**Removed** — an installed plugin no longer seeds a phantom `records` table. The `uvx`/`pip` launcher used to append the hidden `--include-default` whenever it discovered a plugin and the user passed no `-c`, so `SELECT * FROM records` returned one all-NULL row per `**/*.json` file and every query paid a full walk of those files first. A plugin now adds its own tables and functions and nothing else; the internal `--include-default` flag is gone.

{dirsql-0.4.80 → dirsql-0.4.82/packages/python}/docs/howto/write-a-plugin.md

@@ -195,10 +195,9 @@ Discovery is deliberately narrow. Know exactly who does what:
 - **The `uvx`/`pip` launcher injects `-c <fragment>` per installed plugin.**
   Each discovered plugin's fragment is appended after your own `-c` configs, so
   your config still takes ordering precedence
-  ([composing configs](../reference/config.md#composing-multiple-configs)). When
-  you pass no `-c` of your own, the launcher also keeps the
-  shipped starter `records` table (an internal `--include-default`), so plugins
-  **add** tables rather than standing alone. Discovery is **pip/uvx only** for now — the `npx`
+  ([composing configs](../reference/config.md#composing-multiple-configs)). The
+  launcher adds only the plugin's tables and functions; it seeds no `records`
+  table. Discovery is **pip/uvx only** for now — the `npx`
   launcher does not yet discover — and is switched off per invocation with
   [`--no-plugin` or `DIRSQL_NO_PLUGIN=1`](../reference/cli.md#plugins).
 - **The SDK never auto-discovers.** Pass a plugin's config explicitly (the

{dirsql-0.4.80/packages/rust → dirsql-0.4.82/packages/python}/docs/reference/cli.md

@@ -465,7 +465,8 @@ installed in the same environment as `dirsql` (`pip install …`, or
 loads its fragment — its tables are queryable with zero config edits.
 Installed = active: there is no enable step and no naming convention. The
 fragment is composed *after* your own `-c` configs (so your config takes
-precedence in ordering), and the shipped starter `records` table is preserved.
+precedence in ordering). A plugin adds its own tables and nothing else: no
+`records` table is seeded.
 
 Discovery is **launcher-only** — the standalone `cargo`-installed binary does no
 discovery, and the SDKs never auto-discover (pass a plugin's config explicitly

dirsql-0.4.82/packages/python/e2e-attestations/claude-1225-plugin-no-default.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/plugin_discovery_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/extension_package_test.py tests/e2e/cli_version_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1791301754,
+  "exit_code": 0,
+  "commit": "9a556e333ff2cbcbcba2e6eba31a3e14c7aab008",
+  "branch": "claude/1225-plugin-no-default"
+}

dirsql-0.4.82/packages/python/e2e-attestations/claude-1232-anchor-plumbing.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/capture_collision_test.py tests/e2e/declared_table_name_test.py tests/e2e/extension_package_test.py tests/e2e/query_contract_test.py tests/e2e/plugin_discovery_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/fanout_test.py tests/e2e/use_case_transcripts_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/on_file_query_test.py -x -q",
+  "ran_at": 1791302031,
+  "exit_code": 0,
+  "commit": "1746a7286f9b11c9ecb0078ec263e69ecce29d7f",
+  "branch": "claude/1232-anchor-plumbing"
+}

dirsql-0.4.82/packages/python/e2e-attestations/claude-1330-python-dirsql-patch.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/capture_collision_test.py tests/e2e/fanout_test.py tests/e2e/cli_version_test.py tests/e2e/extension_package_test.py tests/e2e/on_file_query_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/plugin_discovery_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1791302200,
+  "exit_code": 0,
+  "commit": "1553e866cb8da7050a1c444833e269c831f6e0a1",
+  "branch": "claude/1330-python-dirsql-patch"
+}

dirsql-0.4.82/packages/python/e2e-attestations/claude-1330-scanner-effects.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/declared_table_name_test.py tests/e2e/use_case_join_test.py -x -q",
+  "ran_at": 1791300931,
+  "exit_code": 0,
+  "commit": "dbe4a7ad92b3f630f0fec40a9e09523babc3b594",
+  "branch": "claude/1330-scanner-effects"
+}

dirsql-0.4.82/packages/python/e2e-attestations/claude-1330-scanner-gitignore.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/glob_speed_gitignore_test.py -x -q",
+  "ran_at": 1791300776,
+  "exit_code": 0,
+  "commit": "bfe83ade86865e07e355567fb96c33cda36a46bb",
+  "branch": "claude/1330-scanner-gitignore"
+}

dirsql-0.4.82/packages/python/e2e-attestations/claude-1330-vtab-read.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/use_case_join_test.py tests/e2e/use_case_transcripts_test.py -x -q",
+  "ran_at": 1791301146,
+  "exit_code": 0,
+  "commit": "89e397ecdff80eb3659c42b1135f70a47705cf37",
+  "branch": "claude/1330-vtab-read"
+}

dirsql-0.4.82/packages/python/migrations.d/2026-10-06-plugin-no-default-records.md

@@ -0,0 +1,30 @@
+### Plugin launcher no longer seeds a `records` table
+
+#### Summary
+
+With a plugin installed, the `uvx`/`pip` launcher used to add the hidden `--include-default`, which seeded a placeholder `records` table (glob `**/*.json`, every row all-NULL) alongside the plugin's tables. It now injects only `-c <fragment>` per plugin. Queries that never named `records` are unaffected and no longer walk every JSON file first; a query that read the placeholder `records` now fails with `no such table: records`.
+
+#### Required changes
+
+| Surface | Before | After |
+| ------- | ------ | ----- |
+| `SELECT count(*) FROM records` with a plugin installed | one row per `*.json` file | `no such table: records` |
+| Want a real `records` table | (placeholder) | define it in your own config and pass it with `-c` |
+
+#### Deprecations removed
+
+The hidden `--include-default` flag (internal, never documented) is removed.
+
+#### Behavior changes without code changes
+
+- Plugin-enabled queries no longer show a `dirsql: indexing N/M files` progress line for files no plugin table matches.
+
+#### Verification
+
+```bash
+cd "$(mktemp -d)"
+echo '{"id":1}' > a.json
+uvx --with dirsql-plugin-embeddings dirsql query "SELECT count(*) FROM records"
+```
+
+Expected: `no such table: records`.

{dirsql-0.4.80 → dirsql-0.4.82}/packages/python/testing-conventions.toml

@@ -14,17 +14,6 @@ extra_scope = ["packages/rust/src", "packages/python/src", "packages/python/test
 fail_under = 100
 branch = true
 
-# The hermetic integration tier is defined by patching the first-party core
-# boundary: `dirsql._async._RustDirSQL` is the PyO3 class, and replacing it is
-# what lets these tests run SQLite-free and native-build-free. There is no
-# third-party target to re-root onto, so `no-first-party-patch` has nothing to
-# say about this seam. Every other patch in both files targets stdlib and stays
-# gated.
-[[python.exempt]]
-path = "tests/integration/hermetic/dirsql_test.py"
-rules = ["no-first-party-patch"]
-reason = "the hermetic tier IS the _RustDirSQL core-boundary patch; no third-party target exists to move it to"
-
 [[python.exempt]]
 path = "tests/integration/hermetic/extensions_test.py"
 rules = ["no-first-party-patch"]

{dirsql-0.4.80 → dirsql-0.4.82}/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.80"
+version = "0.4.82"
 edition.workspace = true
 # Literal `license` (not `license.workspace = true`) because
 # putitoutthere's preflight check reads `[package].license` directly

{dirsql-0.4.80/packages/python → dirsql-0.4.82/packages/rust}/docs/howto/write-a-plugin.md

@@ -195,10 +195,9 @@ Discovery is deliberately narrow. Know exactly who does what:
 - **The `uvx`/`pip` launcher injects `-c <fragment>` per installed plugin.**
   Each discovered plugin's fragment is appended after your own `-c` configs, so
   your config still takes ordering precedence
-  ([composing configs](../reference/config.md#composing-multiple-configs)). When
-  you pass no `-c` of your own, the launcher also keeps the
-  shipped starter `records` table (an internal `--include-default`), so plugins
-  **add** tables rather than standing alone. Discovery is **pip/uvx only** for now — the `npx`
+  ([composing configs](../reference/config.md#composing-multiple-configs)). The
+  launcher adds only the plugin's tables and functions; it seeds no `records`
+  table. Discovery is **pip/uvx only** for now — the `npx`
   launcher does not yet discover — and is switched off per invocation with
   [`--no-plugin` or `DIRSQL_NO_PLUGIN=1`](../reference/cli.md#plugins).
 - **The SDK never auto-discovers.** Pass a plugin's config explicitly (the

{dirsql-0.4.80/packages/python → dirsql-0.4.82/packages/rust}/docs/reference/cli.md

@@ -465,7 +465,8 @@ installed in the same environment as `dirsql` (`pip install …`, or
 loads its fragment — its tables are queryable with zero config edits.
 Installed = active: there is no enable step and no naming convention. The
 fragment is composed *after* your own `-c` configs (so your config takes
-precedence in ordering), and the shipped starter `records` table is preserved.
+precedence in ordering). A plugin adds its own tables and nothing else: no
+`records` table is seeded.
 
 Discovery is **launcher-only** — the standalone `cargo`-installed binary does no
 discovery, and the SDKs never auto-discover (pass a plugin's config explicitly

{dirsql-0.4.80 → dirsql-0.4.82}/packages/rust/src/cli/init.rs

@@ -3,10 +3,8 @@
 //!
 //! `init` does not inspect the target directory at all: it writes
 //! [`super::DEFAULT_CONFIG_TOML`] verbatim -- the escalation scaffold (a named
-//! `[[table]]` with glob, DDL, and a real `on-file` hook) that the
-//! `--include-default` launcher path also seeds from -- so a user always has
-//! a loadable, working config to hand-edit, and the two surfaces can never
-//! drift apart. No LLM, no network, no filesystem walk.
+//! `[[table]]` with glob, DDL, and a real `on-file` hook) -- so a
+//! user always has a loadable, working config to hand-edit. No LLM, no network, no filesystem walk.
 
 use std::path::PathBuf;
 

{dirsql-0.4.80 → dirsql-0.4.82}/packages/rust/src/cli/run.rs

@@ -25,7 +25,7 @@ use super::{
     repl::run_repl,
     serve_with_state, table,
 };
-use crate::{DirSQL, Extension, Row, Table};
+use crate::{DirSQL, Extension};
 use clap::{Args, Parser, Subcommand, ValueEnum};
 use serde_json::Value;
 
@@ -104,17 +104,6 @@ struct ConfigArgs {
     #[arg(short = 'c', long)]
     config: Vec<PathBuf>,
 
-    /// Internal (launcher-only): seed the resolved config set with the shipped
-    /// starter `records` table *before* the `-c` configs, so an explicit `-c`
-    /// composes with it instead of standing alone. `--include-default -c
-    /// <plugin>` yields that table **plus** the plugin's tables — the additive
-    /// composition the plugin launcher (#529) injects for the no-user-`-c`
-    /// case (#604). This is an explicit opt-in, not the implicit no-`-c`
-    /// fallback (which was retired in #636). Hidden from `--help`: it is
-    /// internal plumbing for the launcher, not a documented public flag.
-    #[arg(long = "include-default", hide = true)]
-    include_default: bool,
-
     /// Load a SQLite extension by literal path, overriding a TOML config's
     /// `[[dirsql.extension]]` entries. Repeatable. Format: `<path>` or
     /// `<path>::<entrypoint>`.
@@ -502,23 +491,14 @@ async fn run_server(args: ServerArgs) -> u8 {
 }
 
 fn load_state(cfg: &ConfigArgs, path_table_parser: Option<String>) -> AppState {
-    // Neither a `-c` nor the launcher's `--include-default` -> index the
-    // invocation directory with no named tables. A `./.dirsql.toml` on disk is
-    // NOT consulted (#602); pass it explicitly with `-c` to use it.
-    if cfg.config.is_empty() && !cfg.include_default {
+    // No `-c` -> index the invocation directory with no named tables. A
+    // `./.dirsql.toml` on disk is NOT consulted (#602); pass it explicitly
+    // with `-c` to use it.
+    if cfg.config.is_empty() {
         return load_configless_state(cfg, path_table_parser);
     }
 
     let mut builder = DirSQL::builder();
-    // `--include-default` seeds the shipped starter `records` table before the
-    // `-c` configs, so an explicit config composes with it instead of standing
-    // alone (#604). Programmatic tables sort before config tables in
-    // `resolve`, giving `[starter] ++ [-c]`; a starter-vs-config `records`
-    // collision hits the existing dedup in `compile_matcher`. With no `-c` at
-    // all the flag still applies, yielding just the starter table.
-    if cfg.include_default {
-        builder = builder.table(default_records_table());
-    }
     for config_path in &cfg.config {
         // Canonicalize so config-relative paths (extension libraries, hook
         // working directories) resolve against an absolute parent — `notify`
@@ -616,22 +596,6 @@ fn load_configless_state(cfg: &ConfigArgs, path_table_parser: Option<String>) ->
     }
 }
 
-/// The shipped starter `records` table, parsed from the [`crate::DEFAULT_CONFIG_TOML`]
-/// asset `dirsql init` writes. Used only by the explicit `--include-default`
-/// compose path (#604), which seeds it as a programmatic table *before* the
-/// `-c` configs. There is no implicit no-`-c` fallback (#636).
-fn default_records_table() -> Table {
-    let config = crate::config::load_config_str(crate::DEFAULT_CONFIG_TOML)
-        .expect("DEFAULT_CONFIG_TOML must be valid dirsql config TOML");
-    let table_config = &config.tables[0];
-    Table::new(
-        table_config.name.clone(),
-        table_config.ddl.clone(),
-        table_config.glob.clone(),
-        |_path| vec![Row::new()],
-    )
-}
-
 #[cfg(unix)]
 async fn wait_for_shutdown() -> std::io::Result<()> {
     use tokio::signal::unix::{SignalKind, signal};
@@ -947,29 +911,6 @@ mod tests {
         );
     }
 
-    #[test]
-    fn include_default_defaults_false_without_the_flag() {
-        // Absent -> false: `-c` keeps its replacement semantics unless the
-        // launcher explicitly opts the baked-in default back in (#604).
-        let cli = Cli::parse_from(["dirsql"]);
-        assert!(!cli.common.include_default);
-    }
-
-    #[test]
-    fn include_default_flag_sets_true() {
-        let cli = Cli::parse_from(["dirsql", "--include-default"]);
-        assert!(cli.common.include_default);
-    }
-
-    #[test]
-    fn include_default_parses_after_the_query_subcommand() {
-        // Subcommand-local (#609): the launcher injects it AFTER `query`
-        // alongside `-c <plugin>`.
-        assert!(
-            query_common(&["dirsql", "query", "SELECT 1", "--include-default"]).include_default
-        );
-    }
-
     #[test]
     fn persist_flag_absent_is_none() {
         let cli = Cli::parse_from(["dirsql"]);
@@ -1104,7 +1045,6 @@ mod tests {
         // integration tier.
         let cfg = ConfigArgs {
             config: Vec::new(),
-            include_default: false,
             extension: vec!["/ext/vec0.so::sqlite3_vec_init".to_string()],
             persist: None,
             no_ignore: false,
@@ -1192,12 +1132,4 @@ mod tests {
         ]);
         assert_eq!(code, 2);
     }
-
-    #[test]
-    fn default_records_table_is_built_from_the_shipped_starter_config() {
-        // `--include-default` seeds this table, so a starter config that
-        // stopped parsing would break that flag rather than `dirsql init`.
-        let table = default_records_table();
-        assert!(table.ddl.contains("records"));
-    }
 }

{dirsql-0.4.80 → dirsql-0.4.82}/packages/rust/src/launcher.rs

@@ -94,13 +94,7 @@ mod tests {
     #[test]
     fn collects_a_discovery_injected_fragment_rather_than_the_default() {
         assert_eq!(
-            scan(&[
-                "query",
-                "SELECT 1",
-                "--include-default",
-                "-c",
-                "/frag/dirsql.toml"
-            ]),
+            scan(&["query", "SELECT 1", "-c", "/frag/dirsql.toml"]),
             ["/frag/dirsql.toml"]
         );
     }