dirsql 0.4.81__tar.gz → 0.4.83__tar.gz

{dirsql-0.4.81 → dirsql-0.4.83}/Cargo.lock

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

{dirsql-0.4.81 → dirsql-0.4.83}/PKG-INFO

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

{dirsql-0.4.81 → dirsql-0.4.83}/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.81 → dirsql-0.4.83}/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.81/packages/rust → dirsql-0.4.83}/docs/howto/write-a-plugin.md

@@ -62,7 +62,9 @@ and [`ignore`](../reference/config.md#dirsql-keys).
 There are **no plugin-specific keys and no plugin-specific restrictions**. The
 config schema is content-only: the index root and persistence are
 [runner-owned](../reference/config.md#dirsql-keys) — the root is the directory
-`dirsql` is run from (or an SDK's explicit `root`), persistence is the
+`dirsql` is run from (or an SDK's explicit `root`) and governs path-tables,
+while a fragment's own `[[table]]` globs anchor at the fragment's directory
+(see [glob anchor](../reference/config.md#glob-anchor)); persistence is the
 `--persist [PATH]` flag — decided by whoever runs `dirsql`, never by a config
 file, so a plugin has nothing to say about them. Whatever you can put in your
 own `.dirsql.toml`, a plugin can put in its fragment, and vice-versa.
@@ -86,11 +88,10 @@ matter most for a published plugin:
 - **A hook runs in its declaring config's directory.** For a plugin that is
   the installed fragment's directory — inside **site-packages**. That is a
   read-only, shared location: **run from it, never write to it.** Read the
-  matched files from the absolute paths the hook appends as arguments, and use
-  [`{root}`](../reference/hooks.md#on-file) to reach the user's project
-  directory. Write any cache to `{root}` or a real cache dir,
-  never next to the fragment.
-- **The paths are absolute and `{root}` is the index root**, so a command is
+  matched files from the absolute paths the hook appends as arguments. Write any cache to a real cache dir, never next to
+  the fragment.
+- **The paths are absolute and `{root}` is the table's glob anchor** (the
+  fragment's directory, or the literal prefix of an absolute / `~/` glob), so a command is
   self-sufficient from any working directory — it works whether the plugin
   lives in the project or in site-packages.
 
@@ -195,10 +196,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.81 → dirsql-0.4.83}/docs/reference/cli.md

@@ -244,7 +244,7 @@ Config flags are subcommand-local: pass them after `server`
 
 | Flag | Default | Description |
 |---|---|---|
-| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index is always rooted at the **invocation directory** (the current working directory), regardless of where a config lives — so `--config /elsewhere/.dirsql.toml` still indexes the directory you ran `dirsql server` from. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
+| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index root is the **invocation directory** (the current working directory) and governs path-tables; a config's `[[table]]` globs anchor at **that config's own directory** (see [glob anchor](./config.md#glob-anchor)), so `--config /elsewhere/.dirsql.toml` indexes `/elsewhere`, from any working directory. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
 | `--host <addr>` | `localhost` | Bind address. |
 | `--port <n>` | `7117` | TCP port to bind. |
 | `--persist [<path>]` | off | Keep the SQLite index on disk between runs so a restart only re-parses files that actually changed. Bare `--persist` caches at `<root>/.dirsql/cache.db`; `--persist <path>` caches at `<path>`. Off by default (the index is ephemeral). Also available on [`dirsql query`](#dirsql-query). See [Keep the index across restarts](../howto/persist.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.81/packages/rust → dirsql-0.4.83}/docs/reference/config.md

@@ -14,17 +14,19 @@ with none given [no named tables](./cli.md#configless-mode) are defined (a
 `./.dirsql.toml` on disk is **not** auto-loaded). The [SDKs](./sdk.md) load a
 config via the `config` constructor parameter.
 
-**Path resolution.** Relative paths in the config (`[[dirsql.extension]]`
-`path`) resolve against the config file's parent
-directory. The **index root is not a config concern** — it is decided by the
-runner (the CLI's invocation directory, or an SDK's explicit root), never by
-the config file's location. See [`--config`](./cli.md#flags).
+**Path resolution.** A path written in a config resolves against the config
+file's parent directory: a `[[table]]` `glob` (see [anchoring](#glob-anchor)),
+`ignore`, and `[[dirsql.extension]]` `path`. A config therefore works from any
+working directory. The **index root is not a config concern** — it is decided
+by the runner (the CLI's invocation directory, or an SDK's explicit root) and
+governs only path-tables and programmatic tables. See
+[`--config`](./cli.md#flags).
 
 ## `[dirsql]` keys
 
 | Key | Type | Default | Description |
 |---|---|---|---|
-| `ignore` | array of strings | `[]` | Glob patterns matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Matched files are skipped entirely — excluded from the initial scan and from watch events. |
+| `ignore` | array of strings | `[]` | Glob patterns matched against paths relative to the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. They apply only to this config's `[[table]]` entries (not to path-tables, and not to another config's tables). Matched files are skipped entirely — excluded from the initial scan and from watch events. |
 
 There is no timeout key. `on-file` hook runs are unbounded; to bound one, wrap
 its command in `timeout(1)` (see [Command hooks](./hooks.md#bounding-a-hook)).
@@ -230,7 +232,7 @@ what its required `on-file` command emits — dirsql injects nothing (see
 |---|---|---|
 | `name` | yes | The table's SQL name — the name you query it by. Declared, never derived from `ddl`: dirsql does not read the DDL text. The `ddl` must create a table by this name; if it doesn't, loading fails. |
 | `ddl` | yes | A SQL batch, run verbatim — any number of statements. It must create a table called `name`; that table holds the file rows, and only the columns it declares are kept (keys the `on-file` command emits that are not declared are dropped). The rest of the batch is yours: indexes, virtual tables, triggers. See [Batch `ddl`](#batch-ddl). |
-| `glob` | yes | Glob pattern matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
+| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
 | `on-file` | **yes** | A command run once per table, with every matched file's absolute path appended as a trailing argument; its stdout (one JSON array of row objects) is the table's rows. Must be non-empty. A `[[table]]` with no `on-file` is a load error (see [parse errors](#parse-errors)). See [Command hooks](./hooks.md#on-file). |
 | `strict` | no (default `false`) | When `true`, rows whose keys do not exactly match the declared columns are rejected with an error: extra keys error, and every declared column must be supplied by the `on-file` output. When `false`, extra keys are dropped and missing columns become `NULL`. |
 
@@ -256,6 +258,22 @@ on-file = "uv run python extract_papers.py"
 strict  = true
 ```
 
+### Glob anchor
+
+A table's `glob` is matched beneath its **anchor**, never the index root:
+
+| `glob` starts with | Anchor |
+|---|---|
+| nothing special, or `./` | the config file's directory |
+| `/` (or a drive / UNC root) | the literal directory chain before the first glob character |
+| `~/` | your home directory, then the literal chain |
+| `../` | resolved against the config file's directory, then the literal chain |
+
+So `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes
+`~/.claude/projects` from any working directory, and a shared config elsewhere
+writes `glob = "~/.claude/projects/*/*.jsonl"`. A table's `path` and `dir`
+columns, `{root}`, and `ignore` are all relative to its anchor.
+
 ### Batch `ddl`
 
 `ddl` is handed to SQLite whole, so a table declaration is not limited to one
@@ -346,7 +364,7 @@ dirsql -c ./.dirsql.toml -c ~/team/embeddings.toml -c ./local.toml
 
 The configs load and merge in **argv order**:
 
-- **`[[table]]`, `ignore`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
+- **`[[table]]`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
   entries accumulate** across all configs, in order.
 - **Each config's `on-file` hooks and `[[dirsql.function]]` workers run from
   that config file's own directory** — so a relative command like
@@ -360,7 +378,8 @@ The configs load and merge in **argv order**:
   silent last-writer-wins.
 
 The index [root](./cli.md#flags) is the invocation directory regardless of where
-any config lives. With no `-c`, [no named tables](./cli.md#configless-mode) are
+any config lives; each config's `[[table]]` globs anchor at that config's own
+directory, and its `ignore` applies to its own tables only. With no `-c`, [no named tables](./cli.md#configless-mode) are
 defined (no `./.dirsql.toml` auto-discovery); a single `-c` behaves exactly as
 before.
 

{dirsql-0.4.81 → dirsql-0.4.83}/docs/reference/hooks.md

@@ -42,7 +42,8 @@ relative paths in the command resolve predictably regardless of where
 `dirsql` was launched. A command named by the `--on-file` flag has no config
 file: it runs in the **index root**, the directory `dirsql query` was run in,
 which is also the directory a `./` path-table is relative to. In both forms
-`{root}` is the index root. The command inherits `dirsql`'s environment, so
+`{root}` is where the table's glob is anchored: the index root for `--on-file`,
+the [glob anchor](./config.md#glob-anchor) for a `[[table]]`. The command inherits `dirsql`'s environment, so
 tools like `uvx --with …` / `npx …` resolve their dependencies as usual.
 
 ### stdout protocol
@@ -143,7 +144,7 @@ the path or stat metadata emits it (it has the paths).
 
 | Placeholder | Value |
 |---|---|
-| `{root}` | The index root directory. Derive a root-relative path with `relpath(path, {root})`. |
+| `{root}` | The directory the table's glob is anchored at (the index root for `--on-file`; the config file's directory, or the literal prefix of an absolute / `~/` glob, for a `[[table]]`). Derive an anchor-relative path with `relpath(path, {root})`. |
 
 The matched files' **absolute** paths are not placeholders: they are appended
 to the command as trailing arguments, after everything written in the

{dirsql-0.4.81 → dirsql-0.4.83}/docs/reference/sdk.md

@@ -98,7 +98,9 @@ DirSQL::builder()
 
 Creates a SQLite index over a directory. The index root is the explicit
 `root` when given, else the **process cwd** — the `config` file's location
-never sets the root.
+never sets the root. A config's `[[table]]` globs anchor at the config file's
+own directory instead (see [glob anchor](./config.md#glob-anchor)); `root`
+governs programmatic tables and path-tables.
 
 Constructing with **neither a `config` nor programmatic `tables`** defines
 **no named tables** — the same as the CLI with no
@@ -127,7 +129,9 @@ shortcut was removed in #603 — use
   entries are appended after any programmatic `tables`; its `ignore`
   patterns and `[[dirsql.extension]]` entries are appended likewise. The
   config file does **not** set the index root: with no explicit `root`, the
-  index roots at the process cwd. **Multiple configs merge in order** on
+  index roots at the process cwd. Its `[[table]]` globs anchor at the config
+  file's directory (or at the literal prefix of an absolute / `~/` glob), not
+  at `root`; its `ignore` applies to its own tables only. **Multiple configs merge in order** on
   every SDK — **Python** `config` accepts a `str` or a `list[str]`, the
   **Rust** builder's `.config()` is repeatable (call it once per file), and
   **TypeScript** `config` accepts a `string` or a `string[]`; the configs

{dirsql-0.4.81 → dirsql-0.4.83}/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.81"
+version = "0.4.83"
 # 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.83/packages/python/changelog.d/2026-10-06-config-globs-anchor-at-the-config.md

@@ -0,0 +1,3 @@
+**Changed**
+
+- **A config `[[table]]` `glob` now anchors at its config file's directory, not the index root.** `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes `~/.claude/projects` from any working directory. A glob may also start with `/`, `~/` or `../` (the path-table prefix grammar): it anchors at the literal directory chain before its first glob character. `{root}` in an `on-file` command, a table's `path`/`dir` columns, and `ignore` are all relative to the table's anchor. A config's `ignore` now applies to that config's tables only, no longer to path-tables or to other configs' tables. The index root (cwd, or `root=`) is unchanged and still governs path-tables and programmatic tables. (#1232)

dirsql-0.4.83/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.81 → dirsql-0.4.83/packages/python}/docs/howto/write-a-plugin.md

@@ -62,7 +62,9 @@ and [`ignore`](../reference/config.md#dirsql-keys).
 There are **no plugin-specific keys and no plugin-specific restrictions**. The
 config schema is content-only: the index root and persistence are
 [runner-owned](../reference/config.md#dirsql-keys) — the root is the directory
-`dirsql` is run from (or an SDK's explicit `root`), persistence is the
+`dirsql` is run from (or an SDK's explicit `root`) and governs path-tables,
+while a fragment's own `[[table]]` globs anchor at the fragment's directory
+(see [glob anchor](../reference/config.md#glob-anchor)); persistence is the
 `--persist [PATH]` flag — decided by whoever runs `dirsql`, never by a config
 file, so a plugin has nothing to say about them. Whatever you can put in your
 own `.dirsql.toml`, a plugin can put in its fragment, and vice-versa.
@@ -86,11 +88,10 @@ matter most for a published plugin:
 - **A hook runs in its declaring config's directory.** For a plugin that is
   the installed fragment's directory — inside **site-packages**. That is a
   read-only, shared location: **run from it, never write to it.** Read the
-  matched files from the absolute paths the hook appends as arguments, and use
-  [`{root}`](../reference/hooks.md#on-file) to reach the user's project
-  directory. Write any cache to `{root}` or a real cache dir,
-  never next to the fragment.
-- **The paths are absolute and `{root}` is the index root**, so a command is
+  matched files from the absolute paths the hook appends as arguments. Write any cache to a real cache dir, never next to
+  the fragment.
+- **The paths are absolute and `{root}` is the table's glob anchor** (the
+  fragment's directory, or the literal prefix of an absolute / `~/` glob), so a command is
   self-sufficient from any working directory — it works whether the plugin
   lives in the project or in site-packages.
 
@@ -195,10 +196,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.81/packages/rust → dirsql-0.4.83/packages/python}/docs/reference/cli.md

@@ -244,7 +244,7 @@ Config flags are subcommand-local: pass them after `server`
 
 | Flag | Default | Description |
 |---|---|---|
-| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index is always rooted at the **invocation directory** (the current working directory), regardless of where a config lives — so `--config /elsewhere/.dirsql.toml` still indexes the directory you ran `dirsql server` from. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
+| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index root is the **invocation directory** (the current working directory) and governs path-tables; a config's `[[table]]` globs anchor at **that config's own directory** (see [glob anchor](./config.md#glob-anchor)), so `--config /elsewhere/.dirsql.toml` indexes `/elsewhere`, from any working directory. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
 | `--host <addr>` | `localhost` | Bind address. |
 | `--port <n>` | `7117` | TCP port to bind. |
 | `--persist [<path>]` | off | Keep the SQLite index on disk between runs so a restart only re-parses files that actually changed. Bare `--persist` caches at `<root>/.dirsql/cache.db`; `--persist <path>` caches at `<path>`. Off by default (the index is ephemeral). Also available on [`dirsql query`](#dirsql-query). See [Keep the index across restarts](../howto/persist.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.81 → dirsql-0.4.83/packages/python}/docs/reference/config.md

@@ -14,17 +14,19 @@ with none given [no named tables](./cli.md#configless-mode) are defined (a
 `./.dirsql.toml` on disk is **not** auto-loaded). The [SDKs](./sdk.md) load a
 config via the `config` constructor parameter.
 
-**Path resolution.** Relative paths in the config (`[[dirsql.extension]]`
-`path`) resolve against the config file's parent
-directory. The **index root is not a config concern** — it is decided by the
-runner (the CLI's invocation directory, or an SDK's explicit root), never by
-the config file's location. See [`--config`](./cli.md#flags).
+**Path resolution.** A path written in a config resolves against the config
+file's parent directory: a `[[table]]` `glob` (see [anchoring](#glob-anchor)),
+`ignore`, and `[[dirsql.extension]]` `path`. A config therefore works from any
+working directory. The **index root is not a config concern** — it is decided
+by the runner (the CLI's invocation directory, or an SDK's explicit root) and
+governs only path-tables and programmatic tables. See
+[`--config`](./cli.md#flags).
 
 ## `[dirsql]` keys
 
 | Key | Type | Default | Description |
 |---|---|---|---|
-| `ignore` | array of strings | `[]` | Glob patterns matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Matched files are skipped entirely — excluded from the initial scan and from watch events. |
+| `ignore` | array of strings | `[]` | Glob patterns matched against paths relative to the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. They apply only to this config's `[[table]]` entries (not to path-tables, and not to another config's tables). Matched files are skipped entirely — excluded from the initial scan and from watch events. |
 
 There is no timeout key. `on-file` hook runs are unbounded; to bound one, wrap
 its command in `timeout(1)` (see [Command hooks](./hooks.md#bounding-a-hook)).
@@ -230,7 +232,7 @@ what its required `on-file` command emits — dirsql injects nothing (see
 |---|---|---|
 | `name` | yes | The table's SQL name — the name you query it by. Declared, never derived from `ddl`: dirsql does not read the DDL text. The `ddl` must create a table by this name; if it doesn't, loading fails. |
 | `ddl` | yes | A SQL batch, run verbatim — any number of statements. It must create a table called `name`; that table holds the file rows, and only the columns it declares are kept (keys the `on-file` command emits that are not declared are dropped). The rest of the batch is yours: indexes, virtual tables, triggers. See [Batch `ddl`](#batch-ddl). |
-| `glob` | yes | Glob pattern matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
+| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
 | `on-file` | **yes** | A command run once per table, with every matched file's absolute path appended as a trailing argument; its stdout (one JSON array of row objects) is the table's rows. Must be non-empty. A `[[table]]` with no `on-file` is a load error (see [parse errors](#parse-errors)). See [Command hooks](./hooks.md#on-file). |
 | `strict` | no (default `false`) | When `true`, rows whose keys do not exactly match the declared columns are rejected with an error: extra keys error, and every declared column must be supplied by the `on-file` output. When `false`, extra keys are dropped and missing columns become `NULL`. |
 
@@ -256,6 +258,22 @@ on-file = "uv run python extract_papers.py"
 strict  = true
 ```
 
+### Glob anchor
+
+A table's `glob` is matched beneath its **anchor**, never the index root:
+
+| `glob` starts with | Anchor |
+|---|---|
+| nothing special, or `./` | the config file's directory |
+| `/` (or a drive / UNC root) | the literal directory chain before the first glob character |
+| `~/` | your home directory, then the literal chain |
+| `../` | resolved against the config file's directory, then the literal chain |
+
+So `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes
+`~/.claude/projects` from any working directory, and a shared config elsewhere
+writes `glob = "~/.claude/projects/*/*.jsonl"`. A table's `path` and `dir`
+columns, `{root}`, and `ignore` are all relative to its anchor.
+
 ### Batch `ddl`
 
 `ddl` is handed to SQLite whole, so a table declaration is not limited to one
@@ -346,7 +364,7 @@ dirsql -c ./.dirsql.toml -c ~/team/embeddings.toml -c ./local.toml
 
 The configs load and merge in **argv order**:
 
-- **`[[table]]`, `ignore`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
+- **`[[table]]`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
   entries accumulate** across all configs, in order.
 - **Each config's `on-file` hooks and `[[dirsql.function]]` workers run from
   that config file's own directory** — so a relative command like
@@ -360,7 +378,8 @@ The configs load and merge in **argv order**:
   silent last-writer-wins.
 
 The index [root](./cli.md#flags) is the invocation directory regardless of where
-any config lives. With no `-c`, [no named tables](./cli.md#configless-mode) are
+any config lives; each config's `[[table]]` globs anchor at that config's own
+directory, and its `ignore` applies to its own tables only. With no `-c`, [no named tables](./cli.md#configless-mode) are
 defined (no `./.dirsql.toml` auto-discovery); a single `-c` behaves exactly as
 before.
 

{dirsql-0.4.81/packages/rust → dirsql-0.4.83/packages/python}/docs/reference/hooks.md

@@ -42,7 +42,8 @@ relative paths in the command resolve predictably regardless of where
 `dirsql` was launched. A command named by the `--on-file` flag has no config
 file: it runs in the **index root**, the directory `dirsql query` was run in,
 which is also the directory a `./` path-table is relative to. In both forms
-`{root}` is the index root. The command inherits `dirsql`'s environment, so
+`{root}` is where the table's glob is anchored: the index root for `--on-file`,
+the [glob anchor](./config.md#glob-anchor) for a `[[table]]`. The command inherits `dirsql`'s environment, so
 tools like `uvx --with …` / `npx …` resolve their dependencies as usual.
 
 ### stdout protocol
@@ -143,7 +144,7 @@ the path or stat metadata emits it (it has the paths).
 
 | Placeholder | Value |
 |---|---|
-| `{root}` | The index root directory. Derive a root-relative path with `relpath(path, {root})`. |
+| `{root}` | The directory the table's glob is anchored at (the index root for `--on-file`; the config file's directory, or the literal prefix of an absolute / `~/` glob, for a `[[table]]`). Derive an anchor-relative path with `relpath(path, {root})`. |
 
 The matched files' **absolute** paths are not placeholders: they are appended
 to the command as trailing arguments, after everything written in the

{dirsql-0.4.81/packages/rust → dirsql-0.4.83/packages/python}/docs/reference/sdk.md

@@ -98,7 +98,9 @@ DirSQL::builder()
 
 Creates a SQLite index over a directory. The index root is the explicit
 `root` when given, else the **process cwd** — the `config` file's location
-never sets the root.
+never sets the root. A config's `[[table]]` globs anchor at the config file's
+own directory instead (see [glob anchor](./config.md#glob-anchor)); `root`
+governs programmatic tables and path-tables.
 
 Constructing with **neither a `config` nor programmatic `tables`** defines
 **no named tables** — the same as the CLI with no
@@ -127,7 +129,9 @@ shortcut was removed in #603 — use
   entries are appended after any programmatic `tables`; its `ignore`
   patterns and `[[dirsql.extension]]` entries are appended likewise. The
   config file does **not** set the index root: with no explicit `root`, the
-  index roots at the process cwd. **Multiple configs merge in order** on
+  index roots at the process cwd. Its `[[table]]` globs anchor at the config
+  file's directory (or at the literal prefix of an absolute / `~/` glob), not
+  at `root`; its `ignore` applies to its own tables only. **Multiple configs merge in order** on
   every SDK — **Python** `config` accepts a `str` or a `list[str]`, the
   **Rust** builder's `.config()` is repeatable (call it once per file), and
   **TypeScript** `config` accepts a `string` or a `string[]`; the configs

dirsql-0.4.83/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.83/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.83/packages/python/e2e-attestations/claude-1232-config-anchor.json

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

dirsql-0.4.83/packages/python/e2e-attestations/claude-1232-multi-watch.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": 1791304050,
+  "exit_code": 0,
+  "commit": "8618c31f0280a80e7d09550fdb931c6460741db7",
+  "branch": "claude/1232-multi-watch"
+}

dirsql-0.4.83/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.83/packages/python/e2e-attestations/claude-1330-python-extensions-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": 1791302302,
+  "exit_code": 0,
+  "commit": "97413988a4b984de31f96d190d2164d61279d7c5",
+  "branch": "claude/1330-python-extensions-patch"
+}

dirsql-0.4.83/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.83/packages/python/migrations.d/2026-10-06-config-globs-anchor-at-the-config.md

@@ -0,0 +1,33 @@
+### Config globs anchor at the config file's directory (#1232)
+
+#### Summary
+
+A `[[table]]` `glob` is matched beneath the directory of the config file that wrote it (or, for a `/`, `~/` or `../` glob, beneath its literal prefix), no longer beneath the index root. A config that relied on running from the directory it describes still works when that is also the config's directory; a config kept apart from its data, or one given an explicit root, now indexes the config's directory and needs its globs rewritten.
+
+#### Required changes
+
+| Surface | Before | After |
+| ------- | ------ | ----- |
+| `DirSQL(root="/data", config="/cfg/.dirsql.toml")` with `glob = "**/*.md"` | indexes `/data` | indexes `/cfg`; write `glob = "/data/**/*.md"` to index `/data` |
+| `dirsql -c /cfg/.dirsql.toml` run from `/data` | indexes `/data` | indexes `/cfg` |
+| `ignore` in a config | applied to every table and to path-tables | applies to that config's tables, relative to their anchor |
+| A table over a directory other than the config's | `glob = "docs/*.md"` with the root elsewhere | `glob = "/data/docs/*.md"` or `glob = "~/data/docs/*.md"` |
+| `{root}` in an `on-file` command | the index root | the table's anchor (the config's directory, or the literal prefix of an absolute glob) |
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- A config table's `path` column is relative to its anchor.
+- A programmatic table and a path-table still use the index root.
+
+#### Verification
+
+```bash
+mkdir -p /tmp/cfg/projects/p /tmp/elsewhere
+echo '{}' > /tmp/cfg/projects/p/a.jsonl
+printf '[[table]]\nname = "sessions"\nddl = "CREATE TABLE sessions (n TEXT)"\nglob = "projects/*/*.jsonl"\non-file = "echo [{}]"\n' > /tmp/cfg/.dirsql.toml
+cd /tmp/elsewhere && dirsql query "SELECT COUNT(*) AS n FROM sessions" -c /tmp/cfg/.dirsql.toml   # [{"n":1}]
+```

dirsql-0.4.83/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`.