mrplex 0.0.3 → 0.2.0

package/README.md

@@ -2,285 +2,247 @@
 
 *Markdown Repos, plexed.*
 
-**Turn ordinary Markdown folders into queryable, versioned, graph-aware knowledge stores — without giving up files.** Your notes stay plain `.md` on disk; agents and humans share the same repository, every write is versioned, and links survive renames.
+mrplex turns a folder of Markdown files into a queryable, versioned knowledge store — without taking your files hostage. Your notes stay ordinary `.md` on disk, readable and editable by any tool you already use. On top of that folder mrplex adds four things a plain directory can't give you:
 
-## Install
+- **Search** over your YAML frontmatter — filter with a small expression language, run full-text search across bodies, and (optionally) rank by meaning.
+- **Versions** — every write is kept, so you can see history, diff two points, and never lose an overwrite to a race.
+- **A link graph** that tracks how your documents connect and survives renames, so moving a file doesn't break the links pointing at it.
+- **One model over three surfaces** — the same store is reachable from the CLI, from an MCP server, and over REST.
 
-Node ≥ 20.11:
+That last point is the reason mrplex exists: it gives an AI agent a way to *explore and maintain* a vault the way a person would — by asking precise questions and following relationships — instead of grepping around and guessing.
 
-```bash
-npm install -g mrplex
-```
-
-Prefer not to install globally? `npx mrplex …` works the same way.
+## Quickstart
 
-Point every command at a database and default repo once (the tour below uses `starship`):
+Install it (Node 20.11 or newer):
 
-```bash
-export MRPLEX_DATABASE=./demo.db
-export MRPLEX_REPO=starship
+```sh
+$ npm install -g mrplex
 ```
 
-Or persist settings in `~/.config/mrplex/config.json`:
+Point it at a folder of Markdown and start asking questions:
 
-```bash
-mrplex config set-database ./demo.db
-mrplex config set-repo starship
+```sh
+$ mrplex repos create notes
+created repo notes
+$ mrplex config set-repo notes          # remember the default; no more -r on every command
+config: repo set
+$ mrplex sync ~/notes --once
+sync notes @ ~/notes: through=v0 actions=128 feed=0
+$ mrplex query --text 'that thing you half remember'
+$path
+---------------------------
+projects/roadmap.md
+meeting-notes/2026-08-12.md
 ```
 
-Each setting resolves **flag → env → config file → default**, so one-off overrides never require editing anything.
-
-> **From a git checkout?** Run `npm install && npm link` (or `npm run cli -- …`). Every `mrplex …` command below is equivalent to `npx mrplex …`.
+That's the whole loop: create a repo, load a folder into it, then query. A repo is just a named collection of documents inside one database (which defaults to `./mrplex.db` — no configuration needed). Any folder of `.md` works, Obsidian vaults included.
 
-## A five-minute tour
+`sync` is two-way. With `--once` it reconciles the folder and the store a single time and exits; drop the flag and it keeps running, watching for changes on both sides. To do that it records a little bookkeeping — two keys, `$version` and `$content_hash` — in each file's frontmatter. That's how a file on disk remembers which stored version it came from, so edits made outside mrplex are matched up correctly on the next sync.
 
-This walkthrough uses the **USS Meridian** — a sample starship knowledge base in [`fixtures/starship/`](fixtures/starship/): crew files, mission records, officer logs, and equipment status, all ordinary Markdown with YAML frontmatter.
+## A guided tour: the USS Meridian
 
-### 1. Sync the sample corpus
+The repository ships a demo vault in `fixtures/starship/` — the crew, missions, logs, and equipment of a fictional survey starship, all short interlinked notes. It's the easiest way to see what the queries actually do.
 
-Clone the repo (for the fixture files), install, and sync the folder into a fresh mrplex repo:
+First copy it out of the checkout and load it. (Copy rather than sync in place: `sync` writes those `$version` tracking keys into the files, and there's no reason to dirty the committed fixture.)
 
-```bash
-git clone https://github.com/usergenic/mrplex
-cd mrplex
-npm install && npm link    # skip if you installed globally above
-
-export MRPLEX_DATABASE=./demo.db
-export MRPLEX_REPO=starship
-
-mrplex repos create starship
-mrplex sync fixtures/starship --once -r starship
+```sh
+$ git clone https://github.com/usergenic/mrplex
+$ cp -r mrplex/fixtures/starship .
+$ mrplex repos create starship
+created repo starship
+$ mrplex config set-repo starship
+config: repo set
+$ mrplex sync starship --once
+sync starship @ starship: through=v0 actions=30 feed=0
 ```
 
-`sync` is the normal way to load a Markdown folder: it pushes local files into the repo, materializes version metadata, and keeps a cursor for two-way updates. Frontmatter values written as repo-root paths (`/crew/foo.md`) and embedded wikilinks/inline links are indexed automatically — no link-config setup step.
+### Ask about your frontmatter
 
-No bootstrap, no token — local mode is full-trust (whoever can run the binary owns the database).
+Filters are written in [CEL](https://cel.dev/) — a small, safe expression language — and evaluated against each document's frontmatter, plus a few built-in fields like `$path` and `$body`. So "what equipment is broken right now?" is a plain boolean expression over the `status` field. Use `-s` (repeatable) to choose which fields come back in the table:
 
-### 2. Query it like data
+```sh
+$ mrplex query --filter 'status == "damaged" || status == "offline"' -s title -s status -s maintainer
+title                         status   maintainer
+----------------------------  -------  -------------------
+Shuttle Corvid                offline  /crew/dax-thorne.md
+Number Three Plasma Manifold  damaged  /crew/bexley-orr.md
+```
 
-Frontmatter is queryable with [CEL](https://github.com/google/cel-spec) filters:
+### Ask about the links between documents
 
-```bash
-# What's broken or offline right now?
-mrplex query --filter 'status == "damaged" || status == "offline"'
+Some questions are about *relationships* rather than fields — "who reports to the captain?" The frontmatter in each crew file has a `reports_to` link, and mrplex indexes those into a graph you can query directly. `$has(target, field)` means "which documents link to `target` through `field`":
 
-# Who reports directly to the captain?
-mrplex query --filter '$has_static("crew/kestrel-vance.md", "reports_to")'
+```sh
+$ mrplex query --filter '$has("crew/kestrel-vance.md", "reports_to")'
+$path
+---------------------
+crew/quill-vasquez.md
+crew/dax-thorne.md
+crew/aria-okonkwo.md
 ```
 
-```text
-PATH                              STATUS
-equipment/plasma-manifold-3.md    damaged
-equipment/shuttle-corvid.md       offline
-…
+### Combine filters, text, and meaning
 
-PATH                    TITLE
-crew/aria-okonkwo.md    Commander Aria Okonkwo
-crew/dax-thorne.md      Lieutenant Commander Dax Thorne
-crew/quill-vasquez.md   Doctor Quill Vasquez
-```
-
-Compose with full-text search — filter, text, and semantic (when configured) all AND together:
+A filter, a full-text search, and a semantic search can all be given at once; results must satisfy all of them (they combine with AND). Here: log entries — `type == "log"` — that also mention "coolant":
 
-```bash
-mrplex query --text 'manifold coolant'
-mrplex query --filter 'type == "mission"' --text 'Halloway'
+```sh
+$ mrplex query --filter 'type == "log"' --text 'coolant'
+$path
+---------------------
+logs/orr-4413-1.md
+logs/thorne-4413-2.md
 ```
 
-### 3. Follow the links as a graph
+By default a query returns just the paths of the matches. You then fetch the full content of only the documents you actually need. This keeps result sets small — which matters a lot when the thing running the query is an agent paying by the token.
+
+### Rename a file without breaking its backlinks
 
-Markdown links, wikilinks, and frontmatter repo-root paths (`/crew/foo.md`) build a derived index bound to document *identity*, so backlinks survive renames. Query membership in CEL:
+This is the payoff of tracking links as a graph. mrplex ties each link to a document's *identity*, not to the path string someone typed. Rename a document and everything that pointed at it still points at it.
 
-```bash
-# Every mission indexed by the mission log MOC
-mrplex query --filter '$in_static("moc/missions.md")'
+`docs mv` moves a document. The `--prev` flag is how mrplex prevents two writers from clobbering each other: you pass the version you're basing your change on, and the write is rejected if someone else moved first (more on that below).
 
-# What touches the damaged plasma manifold? (maintainer field, body links, logs…)
-mrplex query --filter '$has_static("equipment/plasma-manifold-3.md")'
+```sh
+$ V=$(mrplex --json docs get equipment/plasma-manifold-3.md | jq -r .version_id)
+$ mrplex docs mv equipment/manifold-3.md --prev "$V"
+v31
+wrote starship/equipment/manifold-3.md @ v31 (author: mrplex)
 ```
 
-Explore *how* documents connect — neighborhood expansion from a root set:
+Seven documents linked to the old path. Ask the graph who links to the *new* path, and all seven are already there — the relationships followed the document:
 
-```bash
-mrplex graph --roots missions/the-hollow-signal.md --degrees 2 --direction both --render summary
+```sh
+$ mrplex query --filter '$has("equipment/manifold-3.md")'
+$path
+---------------------------
+missions/the-cinder-run.md
+logs/thorne-4413-2.md
+logs/orr-4420-1.md
+logs/orr-4413-1.md
+equipment/coolant-loop-b.md
+crew/dax-thorne.md
+crew/bexley-orr.md
 ```
 
-The missing officer, his mission, the encounter, and the logs that mention him appear as a connected neighborhood — the kind of thread a flat file listing can't give you.
+The graph is correct, but the *link text* those files still contain on disk (`equipment/plasma-manifold-3.md`) is now out of date. `links stale` shows you exactly where, and `links repair` rewrites it for you:
 
-Mermaid for slides or docs:
-
-```bash
-mrplex graph --roots crew/kestrel-vance.md --degrees 2 --direction out --render mermaid
+```sh
+$ mrplex links stale
+crew/bexley-orr.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+crew/dax-thorne.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+equipment/coolant-loop-b.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+logs/orr-4413-1.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+logs/orr-4420-1.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+logs/thorne-4413-2.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+missions/the-cinder-run.md: "equipment/plasma-manifold-3.md" → "equipment/manifold-3.md"
+$ mrplex links repair
+repaired 7 doc(s), skipped 0
 ```
 
-### 4. Change something safely
-
-Every write inserts a new version; nothing is overwritten. Rename a document and the link graph follows its identity:
+### Explore a neighborhood
 
-```bash
-# See current version id, then move the manifold note
-V=$(mrplex --json docs get equipment/plasma-manifold-3.md | jq -r .version_id)
-mrplex docs mv equipment/manifold-3.md --prev "$V"
+`query` finds documents that match. `graph` shows you how a document connects — the links going out of it and coming into it, out to a chosen number of hops. `--render summary` prints it as an indented outline (`→` is a link out, `←` a link in, and the parenthetical is the field the link came from):
 
-# Backlinks still resolve — the graph never broke; link text may need repair
-mrplex query --filter '$has_static("equipment/manifold-3.md")'
-mrplex links stale
+```sh
+$ mrplex graph --roots equipment/manifold-3.md --degrees 1 --render summary
+equipment/manifold-3.md (0)
+  →($body) equipment/coolant-loop-b.md, missions/the-cinder-run.md
+  →(maintainer) crew/bexley-orr.md
+  →(related) equipment/coolant-loop-b.md
+  ←($body) crew/bexley-orr.md, crew/dax-thorne.md, equipment/coolant-loop-b.md, logs/orr-4413-1.md, ...
+... (each neighbor expands the same way, out to the requested degree)
 ```
 
-History and unified diff between any two versions:
+Use `--render mermaid` instead to get a diagram you can paste into any Markdown renderer.
 
-```bash
-mrplex docs history equipment/manifold-3.md
-mrplex docs diff equipment/manifold-3.md --from v1 --to v2
-```
+### Versions, always
 
-Deletion moves a document to a system-namespace path (`:deleted/…`); restore is a normal `docs put` back to user territory.
+Every write appends a new version rather than overwriting — so history is never lost. That's also what makes `--prev` work: it's *optimistic concurrency*. You tell a write which version you started from; if someone else has written in the meantime, yours is rejected and you're handed the current version to reconcile against, instead of silently clobbering their change. Deleting a document moves it aside to `:deleted/…` rather than erasing it, so a delete can be undone with an ordinary write. When you need the record, `docs history` lists a document's versions and `docs diff --from v1 --to v2` shows what changed.
 
-### 5. Connect an agent
+## Connect an agent
 
-CLI, MCP, and REST are surfaces over the same model. Point Cursor (or any MCP client) at your local database:
+The CLI, the MCP server, and the REST API are three doors into the same store. For a database only you touch, the quickest way to give an agent access is MCP over local stdio — for example, in a client's MCP configuration:
 
 ```json
 {
   "mcpServers": {
     "mrplex": {
       "command": "mrplex",
-      "args": ["mcp-stdio", "--unsafe", "--database", "./demo.db"],
-      "env": { "MRPLEX_REPO": "starship" }
+      "args": ["mcp-stdio", "--unsafe", "--database", "./mrplex.db"]
     }
   }
 }
 ```
 
-An agent can now ask relational questions — *"What's broken on the ship, who maintains it, and which missions were affected?"* — and recover structured answers through `query` and `graph` instead of reading every file into context.
+`--unsafe` runs the store with no authentication — every caller has full access. That's an acceptable choice for a private database file on your own machine, and the wrong choice for anything reachable over a network. The next section is what you use instead — when more than one principal is involved, or when you want to guard against a destructive agent mishap.
 
-Serve HTTP for remote clients or Streamable HTTP MCP:
+## Access control
 
-```bash
-mrplex serve --unsafe --port 8321 &
-mrplex --server http://127.0.0.1:8321 query --filter 'status == "missing"'
+When you need real principals — say, an agent that may read and write documents, plus a separate admin identity that can create and delete repos — mrplex generates a starter policy and signing keys for you, so there's no YAML to write by hand:
+
+```sh
+$ mrplex policy create policy.yaml --principal agent
+wrote policy.yaml
+$ mrplex key mint agent --policy policy.yaml     # a day-to-day key for the agent
+$ mrplex serve --policy policy.yaml --audit audit.jsonl
 ```
 
-For shared or networked deployments, run the authenticating shell instead — see [Authentication](#authentication) below. Never expose the raw kernel (`serve --unsafe`) directly to an untrusted network.
+`policy create` takes the filename to write and scaffolds two roles: a `maintainer` (the `--principal` you name) for everyday reads and writes, and an `operator` admin for repo management. `policy check` validates a policy and can print out exactly what a given principal is allowed to do.
 
-## How it works
+You can enforce that policy in three arrangements: embedded in the server (`serve --policy`), in front of the stdio launcher (`mcp-stdio --policy`), or as a standalone proxy ahead of an existing engine (`proxy --policy --upstream`). Edit the file and send the server `SIGHUP` (`kill -HUP`) to reload it without downtime; `mrplex login` signs in through an OIDC device flow. Full details are in [docs/archive/security.md](docs/archive/security.md).
 
-| Concept | What it means |
-|--------|----------------|
-| **Document** | One Markdown file with YAML frontmatter, addressed by repo-relative path |
-| **Version** | Every write appends; `prev_version_id` optimistic concurrency rejects stale writes |
-| **Query** | CEL filters over frontmatter + `$path` / `$body` / `$updated_at` intrinsics; composes with FTS and semantic search |
-| **Link graph** | Derived index over inline links, wikilinks, and frontmatter repo-root paths; `$in`, `$has`, `$backlinks`, `$links` in CEL |
-| **Graph** | BFS neighborhood expansion over the link index — *how* things connect, not just *which* match |
-| **Surfaces** | `mrplex` CLI (local or `--server`), MCP at `/mcp` or `mcp-stdio`, REST at `/repos/{repo}/…` |
-
-Two layers: a **full-trust kernel** (no in-engine auth) and an optional **access-and-identity shell** (API keys, OIDC, per-path write policy, audit log). See [docs/archive/security.md](docs/archive/security.md) for trust boundaries and deployment shapes.
-
-## Features
-
-<details>
-<summary>Full feature list</summary>
-
-- **Versioned Markdown store** — every write inserts; `docs.put` handles in-place update and move; any past state is addressable
-- **Byte-exact frontmatter** — `frontmatter_raw` (verbatim YAML) or `frontmatter` (JSON); exactly one; round-trips are byte-exact via raw
-- **Optimistic concurrency** — stale `prev_version_id` → `stale_prev` with current version returned
-- **Deletion as move** — `:deleted/…` paths; idempotent delete; restore via `docs.put`
-- **Unified diff** — `docs.diff`, REST `/diff`, MCP `docs_diff`, CLI `mrplex docs diff`; `patch(1)`-applicable output
-- **CEL filter queries** — frontmatter fields + `$`-intrinsics; `list()` polymorphism for scalar-or-list fields
-- **Link graph** — inline, wikilink, and frontmatter path extraction (no per-field config); backlinks survive renames; set algebra (`$in("moc/**") && !$in("moc/draft.md")`); `$in_static` for link-only membership; `links stale` / `repair` / `backfill`
-- **Graph exploration** — BFS with direction lens, visibility filter, graph-only `$degrees` intrinsic; CLI `--render summary|yaml|mermaid|json`
-- **Full-text search** — SQLite FTS5 or Postgres `websearch_to_tsquery`; composes with filter via AND
-- **Semantic search** — pluggable `--embedder` hook; chunker + backlog worker; `$semantic_score` in `select`; no hook → `semantic_unavailable`
-- **HTTP surfaces** — MCP (Streamable HTTP + STDIO), REST with `If-Match` / content negotiation / `MOVE`
-- **CLI** — thin MCP client; `--database` local or `--server` remote; identical commands over both
-- **Storage** — SQLite (default) or Postgres+pgvector; same kernel test suite on both
-- **Path policy** — configurable sigils and disallowed chars; NFC + case-insensitive identity, case-preserved storage
-- **Canonical paths** — API responses use slashless repo-relative paths; leading `/` accepted as root alias on input only
-
-Prior design docs in [docs/archive/](docs/archive/) may be out of date where later work supersedes them.
-
-</details>
-
-## Authentication
-
-For anything beyond single-user local use, run the **authenticating shell** — `serve --policy`. It reads declarative YAML (roles, principals, grants, key hashes, OIDC bindings), authenticates each request, and dispatches against a per-principal *guarded* kernel: read visibility narrowed, writes enforced per-path, author derived from the credential, every call audited.
-
-```yaml
-# policy.yaml
-roles:
-  editor:
-    grants:
-      - repo: notes
-        read: "**"
-        write: ["drafts/**", "inbox/**"]
-  operator:
-    grants:
-      - { repo: "*", read: "**", write: "**" }
-    destructive: true
-
-principals:
-  brendan:
-    author: Brendan Baldwin <brendan@example.com>
-    roles: [operator]
-    keys:
-      - sha256:...        # `mrplex key mint brendan --policy policy.yaml`
-  ann:
-    roles: [editor]
-    oidc: { email: ann@example.com }
-```
+One rule worth repeating: never expose `serve --unsafe` to an untrusted network — it is, by definition, an open door.
 
-```bash
-mrplex key mint brendan --policy policy.yaml
-mrplex serve --policy policy.yaml --audit audit.jsonl --port 8321 &
-curl -H "Authorization: Bearer $KEY" http://127.0.0.1:8321/repos
-```
+## How it works
 
-Three deployment shapes — **embedded** (`serve --policy`), **launcher** (`mcp-stdio --policy`), and **fronting proxy** (`proxy --policy --upstream`). Edit the policy and `kill -HUP` to reload grants without restart. OIDC device-flow login via `mrplex login`. Full details in [docs/archive/security.md](docs/archive/security.md).
+mrplex is built from a few concepts:
 
-## Embeddings
+| Concept        | What it is                                                                                 |
+| -------------- | ------------------------------------------------------------------------------------------ |
+| **Document**   | One Markdown file with YAML frontmatter, addressed by its path within a repo               |
+| **Version**    | Every write appends a new one; `--prev` rejects a write based on a stale version           |
+| **Query**      | A CEL filter over frontmatter and `$path` / `$body` / `$updated_at`, combined with full-text and semantic search |
+| **Link graph** | Links from Markdown syntax, wikilinks, and frontmatter paths, tracked by identity so renames don't break them |
+| **Graph walk** | A breadth-first tour of that link graph — *how* documents connect, not just which ones match |
+| **Surfaces**   | The CLI, an MCP server, and a REST API, all over the same store                            |
 
-mrplex never calls an embedding provider itself — wire one with `--embedder` (subprocess command or HTTP URL). For local CPU embeddings:
+Underneath, mrplex is two layers. The **kernel** is the store itself — documents, versions, queries, the graph — and it is full-trust: it has no notion of users, so whoever holds the database file holds everything. Around it is an optional **access-and-identity shell** that adds keys, OIDC, per-path permissions, and an audit log when you need them. The store runs on SQLite by default, or Postgres with pgvector when you want it; the same test suite runs against both, so behavior matches.
 
-```bash
-npm install -g @mrplex/embedder
-export MRPLEX_EMBEDDER=mrplex-embedder   # or: mrplex config set-embedder mrplex-embedder
+## Semantic search
 
-mrplex serve --unsafe --embedder mrplex-embedder
-mrplex embed backfill -r starship
-mrplex query -r starship --semantic 'distress beacon star map'   # uses env/config
-# or per-invocation in local (--database) mode:
-mrplex query -r starship --embedder mrplex-embedder --semantic 'distress beacon star map'
-```
+mrplex never calls an embedding provider on its own — you decide what does the embedding by wiring in a hook. The companion package `@mrplex/embedder` runs a small local model on CPU, which is enough to get started:
 
-Resolution: **flag → `MRPLEX_EMBEDDER` → `mrplex config set-embedder` → unset**. In local mode, `query --embedder` overrides for that call; with `--server`, configure the embedder on the host. See [packages/embedder/README.md](packages/embedder/README.md) for protocol details.
+```sh
+$ npm install -g @mrplex/embedder
+$ mrplex serve --unsafe --embedder mrplex-embedder
+$ mrplex embed backfill                       # embed everything already in the repo
+$ mrplex query --semantic 'distress beacon star map'
+```
 
-## Development
+Point `--embedder` at a command (like the one above) or at an `http(s)://` URL for a remote embedding service. If no hook is configured, a semantic query returns a clear `semantic_unavailable` error rather than silently ranking by nothing. And treat semantic results as a shortlist of candidates worth reading, not a final answer — skim the top hits before you rely on them. The hook protocol is documented in [packages/embedder/README.md](packages/embedder/README.md).
 
-```bash
-npm install
-npm link
-npm test
-npm run typecheck
-npm run lint
-npm run build
-```
+## Configuration
 
-Seed the full dev fixture set (notes + starship):
+Every setting resolves in the same order: a command-line **flag**, then an **environment variable**, then the **config file**, then a built-in default. Save the defaults you're tired of typing:
 
-```bash
-npm run seed -- --database ./mrplex.db
+```sh
+$ mrplex config set-database ./mrplex.db
+$ mrplex config set-author "Ada Lovelace <ada@example.com>"
 ```
 
-CI runs typecheck + lint + tests on Ubuntu & macOS × Node 20 & 22, plus Postgres+pgvector parity. If tests fail with a `NODE_MODULE_VERSION` error from `better-sqlite3`, run `npm rebuild better-sqlite3`.
+The matching environment variables are `MRPLEX_DATABASE`, `MRPLEX_REPO`, `MRPLEX_AUTHOR`, and `MRPLEX_EMBEDDER`.
 
-### Postgres locally
+A note on repo scope: your default repo (from `config set-repo` or `MRPLEX_REPO`) applies to every command, `query` included. To search more than one repo, say so on that command: `query -r` can be repeated and accepts glob patterns, and `-r '*'` searches every repo in the database. The wildcard only works as an explicit flag — a saved default can never quietly widen a search to your whole database.
 
-```bash
-npm run pg:up
-export MRPLEX_DATABASE=postgres://mrplex:mrplex@localhost:5432/mrplex
-mrplex serve --unsafe
+## Development
+
+```sh
+$ npm install && npm link
+$ npm test
+$ npm run typecheck && npm run lint && npm run build
 ```
 
+CI runs typecheck, lint, and tests on Ubuntu and macOS across Node 20 and 22, plus a Postgres + pgvector parity run (`npm run pg:up` starts a local instance). If `better-sqlite3` reports a `NODE_MODULE_VERSION` mismatch, rebuild it with `npm rebuild better-sqlite3`.
+
 ## License
 
 MIT — see [LICENSE](LICENSE).

package/dist/cli/config.d.ts

@@ -18,10 +18,6 @@ export type CliConfig = {
     author?: string;
     /** Default --embedder (command or http(s):// URL). */
     embedder?: string;
-    /** @deprecated Use `embedder`. */
-    embed_url?: string;
-    /** @deprecated Use `embedder`. */
-    embed_cmd?: string;
 };
 export declare function configPath(): string;
 export declare function loadConfig(): CliConfig;

package/dist/cli/config.js.map

@@ -1 +1 @@
-{"version":3,"file":"config.js","sourceRoot":"","sources":["../../src/cli/config.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,SAAS,EAAE,SAAS,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,SAAS,CAAC;AAC5E,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAClC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAgB1C,MAAM,UAAU,UAAU;IACxB,MAAM,SAAS,GAAG,OAAO,CAAC,GAAG,CAAC,eAAe,IAAI,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,CAAC,CAAC;IAC5E,OAAO,IAAI,CAAC,SAAS,EAAE,QAAQ,EAAE,aAAa,CAAC,CAAC;AAClD,CAAC;AAED,MAAM,UAAU,UAAU;IACxB,MAAM,IAAI,GAAG,UAAU,EAAE,CAAC;IAC1B,IAAI,CAAC;QACH,MAAM,IAAI,GAAG,YAAY,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;QACxC,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAY,CAAC;QAC3C,IAAI,OAAO,MAAM,KAAK,QAAQ,IAAI,MAAM,KAAK,IAAI,IAAI,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC;YAC3E,OAAO,EAAE,CAAC;QACZ,CAAC;QACD,OAAO,MAAmB,CAAC;IAC7B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,2EAA2E;QAC3E,IAAK,GAA6B,CAAC,IAAI,KAAK,QAAQ;YAAE,OAAO,EAAE,CAAC;QAChE,OAAO,EAAE,CAAC;IACZ,CAAC;AACH,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAe;IACxC,MAAM,IAAI,GAAG,UAAU,EAAE,CAAC;IAC1B,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IAC9C,aAAa,CAAC,IAAI,EAAE,GAAG,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;IAC3E,IAAI,CAAC;QACH,SAAS,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;IACzB,CAAC;IAAC,MAAM,CAAC;QACP,yDAAyD;IAC3D,CAAC;AACH,CAAC"}
+{"version":3,"file":"config.js","sourceRoot":"","sources":["../../src/cli/config.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,SAAS,EAAE,SAAS,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,SAAS,CAAC;AAC5E,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAClC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAY1C,MAAM,UAAU,UAAU;IACxB,MAAM,SAAS,GAAG,OAAO,CAAC,GAAG,CAAC,eAAe,IAAI,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,CAAC,CAAC;IAC5E,OAAO,IAAI,CAAC,SAAS,EAAE,QAAQ,EAAE,aAAa,CAAC,CAAC;AAClD,CAAC;AAED,MAAM,UAAU,UAAU;IACxB,MAAM,IAAI,GAAG,UAAU,EAAE,CAAC;IAC1B,IAAI,CAAC;QACH,MAAM,IAAI,GAAG,YAAY,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;QACxC,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAY,CAAC;QAC3C,IAAI,OAAO,MAAM,KAAK,QAAQ,IAAI,MAAM,KAAK,IAAI,IAAI,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC;YAC3E,OAAO,EAAE,CAAC;QACZ,CAAC;QACD,OAAO,MAAmB,CAAC;IAC7B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,2EAA2E;QAC3E,IAAK,GAA6B,CAAC,IAAI,KAAK,QAAQ;YAAE,OAAO,EAAE,CAAC;QAChE,OAAO,EAAE,CAAC;IACZ,CAAC;AACH,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAe;IACxC,MAAM,IAAI,GAAG,UAAU,EAAE,CAAC;IAC1B,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IAC9C,aAAa,CAAC,IAAI,EAAE,GAAG,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;IAC3E,IAAI,CAAC;QACH,SAAS,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;IACzB,CAAC;IAAC,MAAM,CAAC;QACP,yDAAyD;IAC3D,CAAC;AACH,CAAC"}