dirsql 0.3.101__tar.gz → 0.3.119__tar.gz

{dirsql-0.3.101 → dirsql-0.3.119}/Cargo.lock

@@ -500,7 +500,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.3.101"
+version = "0.3.119"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.3.101 → dirsql-0.3.119}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.3.101
+Version: 0.3.119
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index
 Author: Kevin Scott

dirsql-0.3.119/dirsql/cli/discover_plugins/discovered_fragments.py

@@ -0,0 +1,18 @@
+"""Discover installed plugins' fragment paths, ordered by entry-point name."""
+
+from __future__ import annotations
+
+from importlib import metadata
+
+from .fragment_path import fragment_path
+
+ENTRY_POINT_GROUP = "dirsql"
+
+
+def discovered_fragments() -> list[str]:
+    """Fragment paths for every installed plugin, ordered by entry-point name
+    (deterministic, so a running server's ``-c`` list is reproducible)."""
+    entry_points = sorted(
+        metadata.entry_points(group=ENTRY_POINT_GROUP), key=lambda ep: ep.name
+    )
+    return [fragment_path(ep.value) for ep in entry_points]

dirsql-0.3.119/dirsql/cli/discover_plugins/discovery_disabled.py

@@ -0,0 +1,14 @@
+"""Whether plugin discovery is opted out (flag or env var)."""
+
+from __future__ import annotations
+
+import os
+
+NO_PLUGIN_FLAG = "--no-plugin"
+NO_PLUGIN_ENV = "DIRSQL_NO_PLUGIN"
+
+
+def discovery_disabled(argv: list[str]) -> bool:
+    """True when discovery is opted out via ``--no-plugin`` or
+    ``DIRSQL_NO_PLUGIN``."""
+    return NO_PLUGIN_FLAG in argv or bool(os.environ.get(NO_PLUGIN_ENV))

dirsql-0.3.119/dirsql/cli/discover_plugins/fragment_path.py

@@ -0,0 +1,25 @@
+"""Resolve a plugin module's shipped ``dirsql.toml`` fragment path."""
+
+from __future__ import annotations
+
+from importlib import resources
+
+FRAGMENT_NAME = "dirsql.toml"
+
+
+def fragment_path(module_name: str) -> str:
+    """Absolute path to a plugin module's shipped ``dirsql.toml``. Raises a
+    clear error naming the plugin when the module or the fragment is missing --
+    never a silent skip."""
+    try:
+        fragment = resources.files(module_name).joinpath(FRAGMENT_NAME)
+    except ModuleNotFoundError as exc:
+        raise ValueError(
+            f"dirsql plugin module {module_name!r} is not importable: {exc}"
+        ) from exc
+    if not fragment.is_file():
+        raise ValueError(
+            f"dirsql plugin {module_name!r} ships no {FRAGMENT_NAME} fragment "
+            f"(expected at {fragment})"
+        )
+    return str(fragment)

dirsql-0.3.119/dirsql/cli/discover_plugins/user_passed_config.py

@@ -0,0 +1,15 @@
+"""Whether the user's argv already names a config file."""
+
+from __future__ import annotations
+
+
+def user_passed_config(argv: list[str]) -> bool:
+    """True when argv already names a ``-c`` / ``--config`` file -- the user's
+    own config is the base, so the baked-in default is not re-added."""
+    for arg in argv:
+        # `--config` naturally fails `startswith("-c")` (it starts with `--`),
+        # so the three clauses are disjoint: bare/attached short `-c`, long
+        # `--config`, and the `--config=<value>` form.
+        if arg == "--config" or arg.startswith("--config=") or arg.startswith("-c"):
+            return True
+    return False

dirsql-0.3.119/dirsql/cli/discover_plugins/with_discovered_plugins.py

@@ -0,0 +1,48 @@
+"""Rewrite argv to activate installed plugins (the discovery orchestrator).
+
+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``.
+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``).
+"""
+
+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``
+    / ``DIRSQL_NO_PLUGIN`` skip discovery, consuming the flag. ``init`` takes no
+    config, so it is left untouched. Raises if a declared plugin is missing its
+    module or fragment (the launcher surfaces a clean error).
+
+    Appending is safe because config flags are subcommand-local (#609): the
+    user's own ``-c`` sits after the ``query`` subcommand (or at top level in
+    server mode), so the injected flags land in the same clap context and
+    accumulate with it -- plugins merge after the user's config, preserving
+    user-first order.
+    """
+    if discovery_disabled(argv):
+        return [a for a in argv if a != NO_PLUGIN_FLAG]
+    if argv and argv[0] == "init":
+        return argv
+    fragments = discovered_fragments()
+    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)
+    return [*argv, *injected]

{dirsql-0.3.101 → dirsql-0.3.119}/dirsql/cli/main.py

@@ -9,6 +9,7 @@ import subprocess
 import sys
 
 from .binary_path import binary_path
+from .discover_plugins.with_discovered_plugins import with_discovered_plugins
 from .is_windows import is_windows
 from .resolve_config_extensions import with_resolved_extensions
 
@@ -23,9 +24,12 @@ def main(argv: list[str] | None = None) -> int:
         print(f"dirsql: {exc}", file=sys.stderr)
         return 1
 
-    # Resolve any package-name extensions in a TOML config here (the binary
-    # can't) and pass them as `--extension` flags; a no-op otherwise.
+    # Discover installed plugins (CLI only) and inject their config fragments as
+    # `-c` flags before resolving extensions; then resolve any package-name
+    # extensions in a TOML config here (the binary can't) as `--extension`
+    # flags. Both are no-ops when nothing applies.
     try:
+        argv = with_discovered_plugins(argv)
         argv = with_resolved_extensions(argv)
     except Exception as exc:
         print(f"dirsql: {exc}", file=sys.stderr)

{dirsql-0.3.101 → dirsql-0.3.119}/docs/.vitepress/config.ts

@@ -37,6 +37,7 @@ export default defineConfig({
         {
           text: 'How-to Guides',
           items: [
+            { text: 'Query files without a config', link: '/howto/query-without-config' },
             { text: 'Define tables for your files', link: '/howto/define-tables' },
             { text: 'Derive columns from file paths', link: '/howto/columns-from-paths' },
             { text: 'Extract rows from file contents', link: '/howto/extract-from-contents' },
@@ -45,6 +46,7 @@ export default defineConfig({
             { text: 'Load a SQLite extension', link: '/howto/load-extension' },
             { text: 'Keep the index across restarts', link: '/howto/persist' },
             { text: 'React to file changes', link: '/howto/react-to-changes' },
+            { text: 'Write a plugin', link: '/howto/write-a-plugin' },
             { text: 'Embed dirsql in your application', link: '/howto/embed' }
           ]
         },
@@ -55,6 +57,7 @@ export default defineConfig({
             { text: 'Configuration File', link: '/reference/config' },
             { text: 'Command Hooks', link: '/reference/hooks' },
             { text: 'Virtual Columns & Glob Captures', link: '/reference/columns' },
+            { text: 'Path-tables', link: '/reference/path-tables' },
             { text: 'HTTP API', link: '/reference/http-api' },
             { text: 'SDK', link: '/reference/sdk' },
             { text: 'Migrations', link: '/migrations' }

{dirsql-0.3.101 → dirsql-0.3.119}/docs/getting-started.md

@@ -9,6 +9,10 @@ a SQL database you can query over HTTP — without writing any code. You will:
 
 It takes about five minutes.
 
+`dirsql` only ever reads your files — it never writes, moves, or changes
+them — so it is safe to point at a real directory of your own once you are
+done here. See [Read-only by design](./explanation#read-only-by-design).
+
 **You need:** a terminal with `curl` and [`jq`](https://jqlang.org/), and
 Node ≥ 20.11 (for `npx`). Every `npx dirsql` step below also has a `uvx`
 tab that behaves identically, if you prefer Python tooling
@@ -16,33 +20,23 @@ tab that behaves identically, if you prefer Python tooling
 
 ## 1. Create three files
 
-Make a working directory with two subfolders — one per note author:
+Paste this whole block into your terminal. It makes a working directory
+with a subfolder per note author and writes three tiny markdown notes:
 
 ```bash
 mkdir -p my-notes/notes/alice my-notes/notes/bob
 cd my-notes
-```
-
-Create the three notes by pasting each block exactly as shown:
-
-```bash
 cat > notes/alice/welcome.md <<'EOF'
 # Welcome
 
 Start here. This folder is about to become a database.
 EOF
-```
-
-```bash
 cat > notes/alice/ideas.md <<'EOF'
 # Ideas
 
 - query files with SQL
 - watch for changes
 EOF
-```
-
-```bash
 cat > notes/bob/reading-list.md <<'EOF'
 # Reading list
 
@@ -50,6 +44,9 @@ cat > notes/bob/reading-list.md <<'EOF'
 EOF
 ```
 
+(Any directory of files works with `dirsql` — the rest of this tutorial
+assumes exactly these three so your output matches ours.)
+
 Check that all three files are in place:
 
 ```bash
@@ -91,14 +88,15 @@ open a **second terminal** for the next step.
 
 ## 3. Query your files
 
-You gave `dirsql` no configuration, so it serves a single default table
-named `files` ([zero-config mode](./reference/cli.md#zero-config-mode)).
-Ask it how many rows it has:
+You gave `dirsql` no configuration, so no named tables exist. Query the
+filesystem directly with a [path-table](./reference/path-tables.md) — a
+quoted path where a table name goes. `'./'` means everything under the
+index root. Ask it how many files there are:
 
 ```bash
 curl -s http://localhost:7117/query \
   -H 'content-type: application/json' \
-  -d '{"sql":"SELECT COUNT(*) AS files FROM files"}'
+  -d '{"sql":"SELECT COUNT(*) AS files FROM \'./\'"}'
 ```
 
 ```
@@ -112,7 +110,7 @@ through `jq` to pretty-print. Now select some columns:
 ```bash
 curl -s http://localhost:7117/query \
   -H 'content-type: application/json' \
-  -d '{"sql":"SELECT path, size FROM files ORDER BY path"}' \
+  -d '{"sql":"SELECT path, size FROM \'./\' ORDER BY path"}' \
   | jq
 ```
 
@@ -167,16 +165,18 @@ Two keys define the table:
 ## 5. Restart and query the new shape
 
 Config is read at startup, so go back to the **first terminal**, stop the
-server with `Ctrl-C`, and start it again:
+server with `Ctrl-C`, and start it again — this time pointing `dirsql` at
+your config with `-c` (`dirsql` does not auto-load a `.dirsql.toml` from the
+current directory; you always pass it explicitly):
 
 ::: code-group
 
 ```bash [npm]
-npx dirsql
+npx dirsql -c .dirsql.toml
 ```
 
 ```bash [PyPI]
-uvx dirsql
+uvx dirsql -c .dirsql.toml
 ```
 
 :::
@@ -185,9 +185,8 @@ uvx dirsql
 Running at localhost:7117
 ```
 
-This time `dirsql` found your `.dirsql.toml` and served the `notes` table
-you defined instead of the default `files` table. Query it from the second
-terminal:
+This time `dirsql` loaded your `.dirsql.toml` and served the `notes` table
+you defined. Query it from the second terminal:
 
 ```bash
 curl -s http://localhost:7117/query \

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/columns-from-paths.md

@@ -29,8 +29,11 @@ within one path segment) are in
 
 ## 2. Query the captured columns
 
+Pass the config with [`-c`](../reference/cli.md#flags) (`dirsql` does not
+auto-load a `.dirsql.toml` from the current directory):
+
 ```bash
-dirsql query "SELECT year, month, basename FROM photos ORDER BY year, month"
+dirsql query "SELECT year, month, basename FROM photos ORDER BY year, month" -c ./.dirsql.toml
 ```
 
 ```json
@@ -40,7 +43,7 @@ dirsql query "SELECT year, month, basename FROM photos ORDER BY year, month"
 Captures are real SQL columns, so aggregation works:
 
 ```bash
-dirsql query "SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"
+dirsql query "SELECT year, COUNT(*) AS photos FROM photos GROUP BY year" -c ./.dirsql.toml
 ```
 
 ```json

{dirsql-0.3.101 → dirsql-0.3.119}/docs/howto/define-tables.md

@@ -2,8 +2,8 @@
 
 Map a glob of files to a named SQL table so you query exactly the files you
 care about, with exactly the columns you care about — instead of the
-catch-all `files` table that [zero-config mode](../reference/cli.md#zero-config-mode)
-serves.
+ad-hoc [path-tables](../reference/path-tables.md)
+[configless mode](../reference/cli.md#configless-mode) leaves you with.
 
 ## 1. Create a config next to your files
 
@@ -26,10 +26,12 @@ glob = "posts/**/*.md"
 
 ## 2. Query the table
 
-Each matched file is one row:
+Pass the config with [`-c`](../reference/cli.md#flags) — `dirsql` does not
+auto-load a `.dirsql.toml` from the current directory. Each matched file is
+one row:
 
 ```bash
-dirsql query "SELECT path, size FROM posts ORDER BY path"
+dirsql query "SELECT path, size FROM posts ORDER BY path" -c ./.dirsql.toml
 ```
 
 ```json
@@ -37,8 +39,7 @@ dirsql query "SELECT path, size FROM posts ORDER BY path"
 ```
 
 Files that don't match the glob (a `README.txt` next to `posts/`, say) are
-simply not in the table. Once a config file exists, it fully replaces the
-zero-config default — only the tables you define are served.
+simply not in the table. Only the tables you define are served.
 
 ## Multiple tables
 

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/extract-from-contents.md

@@ -31,8 +31,11 @@ by every hook.
 
 ## 2. Query the extracted columns
 
+Pass the config with [`-c`](../reference/cli.md#flags) (`dirsql` does not
+auto-load a `.dirsql.toml` from the current directory):
+
 ```bash
-dirsql query "SELECT title, author, year, path FROM books ORDER BY year"
+dirsql query "SELECT title, author, year, path FROM books ORDER BY year" -c ./.dirsql.toml
 ```
 
 ```json
@@ -57,7 +60,7 @@ on-file = "jq -c -s '.' {path}"
 ```
 
 ```bash
-dirsql query "SELECT event, user FROM events"
+dirsql query "SELECT event, user FROM events" -c ./.dirsql.toml
 ```
 
 ```json

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/load-extension.md

@@ -23,10 +23,11 @@ overrides the init symbol when it doesn't match the filename-derived
 default — `sqlite-vec` is exactly such a case
 ([reference](../reference/config.md#dirsql-extension)).
 
-The extension's functions are callable:
+The extension's functions are callable (pass the config with
+[`-c`](../reference/cli.md#flags) so its `[[dirsql.extension]]` entry loads):
 
 ```bash
-dirsql query "SELECT vec_version() AS vec_version"
+dirsql query "SELECT vec_version() AS vec_version" -c ./.dirsql.toml
 ```
 
 ```json
@@ -52,7 +53,7 @@ entrypoint = "sqlite3_vec_init"
 ```
 
 ```bash
-uvx --with sqlite-vec dirsql
+uvx --with sqlite-vec dirsql -c ./.dirsql.toml
 ```
 
 **Node (`npx dirsql`, TypeScript SDK).** Use the *npm package name* — but

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/persist.md

@@ -41,7 +41,9 @@ large. Add it to `.gitignore`:
 
 The top-level `.dirsql/` directory is reserved for `dirsql`'s metadata and
 is never scanned as data, so the cache can't index itself
-([config reference](../reference/config.md#dirsql-keys)).
+([config reference](../reference/config.md#dirsql-keys)). While running,
+`dirsql` also creates transient `cache.db-wal` and `cache.db-shm` sidecar
+files next to the cache; the `.dirsql/` ignore already covers all three.
 
 ## What survives, what rebuilds
 
@@ -57,6 +59,13 @@ Persistence is a startup-time optimization, not a change in meaning: the
 database remains a derived view of your files, and queries return the same
 rows either way ([how `dirsql` thinks](../explanation.md)).
 
+### Durability
+
+The cache favors throughput over durability: it opens in WAL journal mode
+with `synchronous=NORMAL`. On power loss the most recent cache updates may
+be lost, but the file cannot corrupt — the next startup reconciles and
+re-parses anything missing.
+
 ## Embedding `dirsql`?
 
 The SDK constructors expose the same switch as `persist` / `persistPath`

dirsql-0.3.119/docs/howto/query-without-config.md

@@ -0,0 +1,69 @@
+# Query files without a config
+
+You have a directory and a question about the files in it. You want an answer
+now — not a `.dirsql.toml`, not a schema, not a setup step. Point `dirsql` at
+the directory and write a path where a table name goes.
+
+## 1. Run a query against the directory
+
+No config, no install ceremony — `uvx` (or `npx`) fetches and runs `dirsql`,
+rooted at the directory you run it from:
+
+```bash
+uvx dirsql query "SELECT basename, size FROM './' ORDER BY size DESC LIMIT 5"
+```
+
+```json
+[
+  {"basename":"video.mp4","size":84213770},
+  {"basename":"archive.zip","size":9123400},
+  {"basename":"notes.md","size":40213},
+  {"basename":"todo.md","size":1200},
+  {"basename":"README.md","size":840}
+]
+```
+
+`'./'` stands in for a table you never declared. `dirsql` scans the directory
+live and hands SQLite one row per file — this is a
+[path-table](../reference/path-tables.md). Because there is no `-c`, there are
+**no named tables** at all; the path *is* the query
+([configless mode](../reference/cli.md#configless-mode)).
+
+## 2. Ask about content, not just names
+
+Every file exposes the seven [stat columns](../reference/columns.md) (`path`,
+`basename`, `dir`, `ext`, `size`, `mtime`, `ctime`) plus a hidden `content`
+column. `content` is read only when you name it, so filtering on it is cheap
+until you actually ask:
+
+```bash
+uvx dirsql query "SELECT path FROM './docs/**/*.md' WHERE content LIKE '%deprecated%'"
+```
+
+The `./` prefix is required. A bare glob is rejected with a hint rather than
+silently guessed:
+
+```
+uvx dirsql query "SELECT * FROM '**/*.md'"
+-- no such table: **/*.md; did you mean './**/*.md'?
+```
+
+## 3. Graduate to a named table when it pays off
+
+A path-table re-scans the filesystem on every query — perfect for a one-off
+question over a few hundred files, wasteful for a large tree you query
+repeatedly. When that day comes, [declare a table](./define-tables.md): it is
+indexed once, kept fresh by the watcher, and can persist across restarts. The
+zero-config query is the floor; a named table is the escalation path — nothing
+you write here has to be thrown away to get there.
+
+## Notes
+
+- The same query works from the SDK: construct `DirSQL` with neither a
+  `config` nor `tables` and call `query("SELECT * FROM './'")`
+  ([SDK reference](../reference/sdk.md)).
+- Paths outside the root resolve too — `'/var/log/*.log'`, `'../notes'`,
+  `'~/notes/*.md'` — reporting absolute paths
+  ([path-tables reference](../reference/path-tables.md#paths-outside-the-index-root)).
+- `node_modules/` and `.git/` are skipped by default so a bare `'./'` does not
+  drown in machinery ([skip rules](../reference/path-tables.md#skip-rules)).

{dirsql-0.3.101/packages/python → dirsql-0.3.119}/docs/howto/react-to-changes.md

@@ -5,10 +5,21 @@ change — and [`GET /events`](../reference/http-api.md#get-events) pushes
 every row-level change to you as it happens. No polling, no diffing on your
 side.
 
+Row events are emitted for **named tables**, so this flow needs a config —
+[path-tables](../reference/path-tables.md) are scanned per query and are not
+watched. Define one next to your files:
+
+```toml
+# .dirsql.toml
+[[table]]
+ddl  = "CREATE TABLE files (path TEXT, basename TEXT, dir TEXT, ext TEXT, size INTEGER, mtime INTEGER, ctime INTEGER)"
+glob = "**/*"
+```
+
 ## 1. Open the stream
 
-With the server running (`npx dirsql` / `uvx dirsql`), subscribe from
-another terminal:
+With the server running (`npx dirsql -c ./.dirsql.toml` /
+`uvx dirsql -c ./.dirsql.toml`), subscribe from another terminal:
 
 ```bash
 curl -N http://localhost:7117/events

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/search-by-meaning.md

@@ -7,6 +7,13 @@ into semantic search: a SQLite vector extension for the distance math, an
 index time, and a [`pre-query`](../reference/hooks.md#pre-query) command to
 embed each question at query time.
 
+::: tip Just want it working?
+[`dirsql-plugin-embeddings`](https://pypi.org/project/dirsql-plugin-embeddings/)
+packages exactly what this guide builds, ready to install:
+`uvx --with dirsql-plugin-embeddings dirsql`. Keep reading to see how it's
+built — the same three pieces, from scratch.
+:::
+
 ## How the pieces fit
 
 1. **[`[[dirsql.extension]]`](../reference/config.md#dirsql-extension)**
@@ -103,10 +110,12 @@ runtime — and the literal-path alternative that works everywhere — are in
 
 Run with `sqlite-vec` available to the launcher's environment. The initial
 scan runs `embed.py` once per note, then the query argument goes straight to
-`pre-query`, exactly as a `POST /query` body would:
+`pre-query`, exactly as a `POST /query` body would. Pass the config with
+[`-c`](../reference/cli.md#flags) — `dirsql` does not auto-load a
+`.dirsql.toml` from the current directory:
 
 ```bash
-uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}'
+uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}' -c ./.dirsql.toml
 ```
 
 ```json
@@ -114,7 +123,7 @@ uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}'
 ```
 
 ```bash
-uvx --with sqlite-vec dirsql query '{"q": "reviewing code on github"}'
+uvx --with sqlite-vec dirsql query '{"q": "reviewing code on github"}' -c ./.dirsql.toml
 ```
 
 ```json

{dirsql-0.3.101/packages/rust → dirsql-0.3.119}/docs/howto/skip-files.md

@@ -31,8 +31,11 @@ ignored file never reaches any table — even one whose glob would match it.
 
 ## 2. Confirm what made it in
 
+Pass the config with [`-c`](../reference/cli.md#flags) (`dirsql` does not
+auto-load a `.dirsql.toml` from the current directory):
+
 ```bash
-dirsql query "SELECT path FROM notes ORDER BY path"
+dirsql query "SELECT path FROM notes ORDER BY path" -c ./.dirsql.toml
 ```
 
 ```json
@@ -42,7 +45,7 @@ dirsql query "SELECT path FROM notes ORDER BY path"
 ## Notes
 
 - `ignore` lives in a config file, so it needs one:
-  [zero-config mode](../reference/cli.md#zero-config-mode) indexes
+  [configless mode](../reference/cli.md#configless-mode) indexes
   everything with no ignores.
 - The top-level `.dirsql/` directory is always excluded, ignore list or
   not — it is reserved for `dirsql`'s own metadata