npm - rigjs - Versions diffs - 4.0.4 → 4.0.6 - Mend

rigjs 4.0.4 → 4.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (24) hide show

package/.claude/skills/rig-wiki/SKILL.md +61 -28
package/RIG_WIKI_SKILL.md +61 -28
package/built/index.js +178 -178
package/lib/wiki/README.md +19 -15
package/lib/wiki/config.ts +58 -61
package/lib/wiki/daemon/runner.ts +11 -13
package/lib/wiki/fetch.ts +3 -8
package/lib/wiki/index.ts +7 -33
package/lib/wiki/indexCmd.ts +8 -15
package/lib/wiki/ingest.ts +8 -13
package/lib/wiki/init.ts +21 -15
package/lib/wiki/installSkill.ts +68 -20
package/lib/wiki/lint.ts +19 -29
package/lib/wiki/paths.ts +0 -1
package/lib/wiki/query.ts +8 -12
package/lib/wiki/rebuild.ts +17 -28
package/lib/wiki/scan.ts +0 -0
package/lib/wiki/uninstallSkill.ts +43 -17
package/package.json +2 -2
package/scripts/publish.mjs +59 -0
package/skills.md +34 -7
package/lib/wiki/list.ts +0 -69
package/lib/wiki/register.ts +0 -104
package/lib/wiki/unregister.ts +0 -28

package/.claude/skills/rig-wiki/SKILL.md CHANGED Viewed

@@ -15,14 +15,22 @@ metadata:
 **Positioning.** rig wiki is an **agent-facing tool**. Humans don't memorise the CLI; they tell their agent (you) what they want, and you orchestrate `rig wiki *`. Treat any direct user-typed `rig wiki ...` invocation as a fallback — your job is to make raw CLI use unnecessary. Never just hand the user a command and walk away; run it, observe, report.
-You orchestrate `rig wiki *` on behalf of the user. The user speaks in intent; you map to commands. Below is the intent → action table. Resolve the **target wiki** by reading `rig wiki list` once at session start; if none registered, see "Setup" at the bottom.
+## Vault discovery (no registry)
+There is **no global registry**. The active vault is resolved by walking up from the current working directory looking for a `.rig/config.yml`. The directory that contains that file IS the vault.
+This means:
+- **Always `cd` into the project first.** If the user is in some other CWD, change directory before running any `rig wiki *` command.
+- **No `--wiki <name>` flag exists.** Don't try to pass one.
+- **No `rig wiki list`, `register`, or `unregister` commands.** They've been removed.
+- If the user is in a project that has no vault, the next step is `rig wiki init <subdir>` (see "Setup" below).
 ## Intent → command map
 | User intent (any language) | Action |
 |---|---|
 | "把 / record / take notes on / 添加 / 收一下 / 收藏 …" + a URL | `rig wiki fetch <url>` then `rig wiki ingest raw/<resulting-file>` |
-| "…" + a local file path or content paste | Write the content to `<wiki>/raw/YYYY-MM-DD-<kebab-slug>.md` with frontmatter (`source-url`, `fetched-at`, `fetcher: agent-paste`, `content-sha`). Then `rig wiki ingest <that-path>`. |
+| "…" + a local file path or content paste | Write the content to `<vault>/raw/YYYY-MM-DD-<kebab-slug>.md` with frontmatter (`source-url`, `fetched-at`, `fetcher: agent-paste`, `content-sha`). Then `rig wiki ingest <that-path>`. |
 | "ingest / re-process / 重新整理 / 重新 ingest <something>" | `rig wiki ingest <path>` — handles new sources AND re-ingest of modified ones. |
 | "what's new / 有什么变化 / scan / diff" | `rig wiki scan` — surface the NEW / MODIFIED / DELETED / RAW DRIFT report verbatim. |
 | "ingest everything new / 把新东西都收一下" | `rig wiki scan` → for each NEW path → `rig wiki ingest <path>` (one call per file). |
@@ -30,43 +38,70 @@ You orchestrate `rig wiki *` on behalf of the user. The user speaks in intent; y
 | "summarize what we know about X / 总结一下 X" | `rig wiki query "<X>" --synth` — adds a Claude-synthesized paragraph with `[[wikilink]]` citations after the hit list. |
 | "lint / 检查一遍 / what's broken in my wiki" | `rig wiki lint`. Surface the report. Exit code 11 = severe (broken refs / missing source). |
 | "rebuild / 全部重 embed / 换了模型 / 新机器" | `rig wiki rebuild` — full nuclear refresh. Only suggest this when the user mentions a new device or explicitly switching the embed model. |
-| "wiki list / what wikis are registered" | `rig wiki list` |
-Always run from inside the registered project (or pass `--wiki <name>`). If the user is in some other CWD, `cd` to the wiki's project first.
+## Vault layout (flat — no inner `wiki/` subdir)
+```
+<vault>/
+  purpose.md          ← human-authored, never write
+  schema.md           ← human-authored, never write
+  index.md            ← LLM-writable
+  overview.md         ← LLM-writable
+  log.md              ← append-only LLM log
+  reviews.md          ← LLM-writable backlog of human-review items
+  raw/                ← immutable source files (never edit existing)
+  sources/            ← one .md per ingested source — page tree at vault root
+  entities/
+  concepts/
+  synthesis/
+  queries/
+  .rig/config.yml     ← per-vault settings (name, root, include, exclude, …)
+  .gitignore
+```
+Note: there is no `<vault>/wiki/` subdirectory. Page directories (`sources/`, `entities/`, `concepts/`, `synthesis/`, `queries/`) live directly under the vault root.
 ## Argument inference rules
-- **slug** = kebab-case, no dates inside `wiki/`, dates only on `raw/YYYY-MM-DD-*` prefix.
+- **slug** = kebab-case, no dates in page filenames; dates only on `raw/YYYY-MM-DD-*` prefix.
 - **raw filename** = `YYYY-MM-DD-<slug>.md`. Pick today's local date; if filename collides, append `-2`, `-3`.
 - **URL → slug**: last path segment, drop extension, lowercase, replace non-`[a-z0-9-]` with `-`, max 64 chars.
-- **wiki dir name** when initializing: prefer user-stated name; if absent, ask once. Never default to `wiki` or CWD silently.
+- **Default vault dir name** when the user says "init a vault / make a wiki here" without specifying: suggest `rig-wiki` at the project root. Never default silently — confirm the name once.
 ## Hard rules — refuse and explain if violated
 - **Never** edit `raw/`, `purpose.md`, or `schema.md` directly. Those are human-authored. If the user asks you to, tell them to do it manually.
-- **Never** ingest or init at a **hidden path** (any segment starting with `.`) or a **.gitignored** path. rig wiki refuses at the CLI level — it sees these as "the project deliberately doesn't want this in the wiki." Workaround if the user insists: `cp -R <hidden-or-ignored> <wiki>/raw/<slug>/` first, then ingest the copy. Never bypass the guard.
-- **Never** ingest a path outside the wiki's `include[]` scope (anything in `raw/` is always fine; outside that requires the path to be listed in the registered wiki's `include`).
+- **Never** init a vault INSIDE a user-authored data directory (e.g. `personal/wiki/`). The vault dir contaminates the user's source tree. Put the vault at the project root (e.g. `<project>/rig-wiki/`) and point `include[]` at the data dirs via `<vault>/.rig/config.yml`.
+- **Never** init a vault at a **hidden path** (any segment starting with `.`) or a **.gitignored** path. rig wiki refuses at the CLI level.
 - **`rig wiki scan` exit 10 (RAW DRIFT)** = a `raw/` file's bytes changed since last scan. Do NOT auto-fix or re-ingest. Surface to the user as a data-integrity warning.
 - **`rig wiki lint` exit 11** = severe findings. Surface the report path and the top findings; do not auto-fix unless the user asks.
 - **Never** suggest editing `~/.rig/cache/qmd/*.sqlite` or `~/.cache/qmd/`. Those are rebuildable caches.
+## Auto-exclusions (no config needed)
+The scanner skips these automatically — do not waste user time adding them to `exclude`:
+- Any path segment starting with `.` (`.git/`, `.obsidian/`, `.vscode/`, `.DS_Store`, …).
+- Any path matched by the project's `.gitignore`.
+What you DO need to put in `exclude` are content-type filters the user cares about — e.g. `**/*.zip`, `**/*.pdf` if they don't want those in their text wiki.
 ## Common error → recovery
 | Error | What it means | Action |
 |---|---|---|
-| `qmd query failed. Run \`rig wiki index\` first` | No vector index for this wiki | `rig wiki index --wiki <name>` then retry |
-| `no wiki resolved` | CWD is not inside a registered wiki and no `--wiki` flag | Either `cd` into the project or pass `--wiki <name>` |
-| `claude not installed on PATH` (during ingest/synth) | Claude Code CLI missing | Tell the user; suggest `yarn dlx @anthropics/claude-code` or use a non-agent flow |
+| `No rig wiki vault found.` | CWD has no `.rig/config.yml` and no parent does either | `cd` into the vault (or the project that contains one), or run `rig wiki init <subdir>` |
+| `qmd query failed. Run \`rig wiki index\` first` | No vector index for this vault | `rig wiki index`, then retry |
+| `claude not installed on PATH` (during ingest/synth) | Claude Code CLI missing | Tell the user; suggest `yarn dlx @anthropics/claude-code` |
 | Reranker download stalls on first query | CDN cold node, can take ~1 min | Just wait; subsequent queries are instant |
 ## Output handling
-- After running a `rig wiki *` command, **summarise in natural language** what changed. Don't dump raw `rig` output unless the user asks ("show me the raw output"). Examples:
+- After running a `rig wiki *` command, **summarise in natural language** what changed. Don't dump raw `rig` output unless the user asks. Examples:
   - After `rig wiki ingest`: "Wrote 11 pages (1 source, 2 entities, 5 concepts, …). Lint clean."
-  - After `rig wiki query`: cite the top hit by slug `[[wikilink]]` and quote a 1-line snippet; offer to run `--synth` if user wants a paragraph.
+  - After `rig wiki query`: cite the top hit by slug `[[wikilink]]` and quote a 1-line snippet; offer `--synth` for a paragraph.
   - After `rig wiki scan`: "3 new, 1 modified. Want me to ingest them?"
 - For **machine** consumption (chaining): use `--json` on any command. Shape is `{ ok, code, data?, error? }`.
-- **Long ingest** (Claude two-step CoT): expect 1–3 minutes. Tell the user once at the start; don't ping them mid-run.
+- **Long ingest** (Claude two-step CoT): expect 1–3 minutes per source. Tell the user once at the start; don't ping them mid-run.
 - **First-run model download** (embed model on first `ingest` / `index`, reranker on first `query`): each is ~610MB from the rig CDN — usually under a minute. Mention it the first time, then forget.
 ## When NOT to use this skill
@@ -76,38 +111,36 @@ Always run from inside the registered project (or pass `--wiki <name>`). If the
 - User is talking about a different knowledge system (Obsidian-only, Notion, etc.).
 - Task is unrelated to personal knowledge capture (e.g. code search → use `grep`).
-## Setup — if no wiki is registered
+## Setup — if no vault is found
-`rig wiki list` shows zero entries → ask the user **once** (don't list multiple defaults; pick one suggestion and confirm):
+`rig wiki scan` (or any command) reports `No rig wiki vault found.` → ask the user **once** (don't list multiple defaults; pick one suggestion and confirm):
-> "No wiki registered here. Want me to init one under `knowledge/`? (or pick another subdir name)"
+> "No vault here. Want me to init one as `rig-wiki/` at the project root? (or pick another path)"
 Then orchestrate without further prompting:
 ```bash
-rig wiki init <subdir>          # REQUIRED — fails if path missing or hidden/gitignored
-rig wiki register <subdir>
+rig wiki init rig-wiki    # creates <project>/rig-wiki/ with templates + .rig/config.yml
 ```
-After init, **pause and ask the user to edit `<subdir>/purpose.md`** (one-time human scoping — define what this wiki is for, in/out of scope). Don't write purpose.md yourself; it's the only human-authored anchor for everything downstream.
+After init, **pause and ask the user to edit `<vault>/purpose.md`** (one-time human scoping — define what this wiki is for, in/out of scope). Don't write purpose.md yourself; it's the only human-authored anchor for everything downstream.
-If the user describes a scan scope that differs from the defaults (e.g. "include every md file in the parent dir but ignore zip files"), translate that into edits to `<subdir>/.rig/config.yml` — that's the per-vault settings file (`name`, `root`, `include`, `exclude`, `schedule`, `ingestRules`). The vault is self-contained: nothing about its identity or scope lives outside its own directory.
+If the user describes a scan scope that differs from the defaults (e.g. "include every md file in `personal/` but ignore zip files"), translate that into edits to `<vault>/.rig/config.yml`. Fields: `name`, optional `root` (relative scan base, default `..`), `include[]`, `exclude[]`, `schedule`, `ingestRules`. The vault is self-contained — nothing about its identity or scope lives outside its own directory.
-## Configuration model (read once, then forget)
+## Configuration files
-Two layers, both YAML:
+Two YAML files, both optional except where noted:
-- `~/.rig/config.yml` — rig-global prefs only (default agent, qmd toggle, log rotation). Touched by `rig wiki agent use`.
-- `~/.rig/wikis.yml` — registry. **Just a flat list of vault paths** for discovery. No per-wiki settings here.
-- `<vault>/.rig/config.yml` — **the only place per-vault settings live.** `name`, optional `root` (relative scan base, default `..`), `include[]`, `exclude[]`, `schedule`, `ingestRules`. Created automatically by `init`. Safe to edit by hand.
+- `~/.rig/config.yml` — rig-global prefs (default agent, qmd toggle, log rotation). Touched by `rig wiki agent use`.
+- `<vault>/.rig/config.yml` — **the only place per-vault settings live.** Auto-created by `rig wiki init`. Safe to edit by hand.
-Never edit `~/.rig/wikis.yml` to change a wiki's name, scope, or schedule — those belong in the vault. Never invent a `package.rig.json5` wiki block; that file is unrelated to rig wiki (legacy rig CICD only).
+No global registry. No `package.rig.json5` wiki block (that file is for legacy rig CICD, unrelated).
 ## Architecture (read once, then forget)
 - Vector-only retrieval: Qwen3-Embedding-0.6B (~610MB) + Qwen3-Reranker-0.6B (~610MB), both CDN-mirrored at `assets.terncloud.com/rig/models/`.
 - Models auto-downloaded on first use into `~/.cache/qmd/models/`; subsequent runs are instant.
-- Per-wiki SQLite at `~/.rig/cache/qmd/<wiki>.sqlite` (sqlite-vec extension). `.gitignore`'d by default.
+- Per-vault SQLite at `~/.rig/cache/qmd/<vault-name>.sqlite` (sqlite-vec extension). `.gitignore`'d by default.
 - `ingest` triggers incremental embed at the end — no need to manually call `index` in routine use.
 - macOS-only in v1.

package/RIG_WIKI_SKILL.md CHANGED Viewed

@@ -15,14 +15,22 @@ metadata:
 **Positioning.** rig wiki is an **agent-facing tool**. Humans don't memorise the CLI; they tell their agent (you) what they want, and you orchestrate `rig wiki *`. Treat any direct user-typed `rig wiki ...` invocation as a fallback — your job is to make raw CLI use unnecessary. Never just hand the user a command and walk away; run it, observe, report.
-You orchestrate `rig wiki *` on behalf of the user. The user speaks in intent; you map to commands. Below is the intent → action table. Resolve the **target wiki** by reading `rig wiki list` once at session start; if none registered, see "Setup" at the bottom.
+## Vault discovery (no registry)
+There is **no global registry**. The active vault is resolved by walking up from the current working directory looking for a `.rig/config.yml`. The directory that contains that file IS the vault.
+This means:
+- **Always `cd` into the project first.** If the user is in some other CWD, change directory before running any `rig wiki *` command.
+- **No `--wiki <name>` flag exists.** Don't try to pass one.
+- **No `rig wiki list`, `register`, or `unregister` commands.** They've been removed.
+- If the user is in a project that has no vault, the next step is `rig wiki init <subdir>` (see "Setup" below).
 ## Intent → command map
 | User intent (any language) | Action |
 |---|---|
 | "把 / record / take notes on / 添加 / 收一下 / 收藏 …" + a URL | `rig wiki fetch <url>` then `rig wiki ingest raw/<resulting-file>` |
-| "…" + a local file path or content paste | Write the content to `<wiki>/raw/YYYY-MM-DD-<kebab-slug>.md` with frontmatter (`source-url`, `fetched-at`, `fetcher: agent-paste`, `content-sha`). Then `rig wiki ingest <that-path>`. |
+| "…" + a local file path or content paste | Write the content to `<vault>/raw/YYYY-MM-DD-<kebab-slug>.md` with frontmatter (`source-url`, `fetched-at`, `fetcher: agent-paste`, `content-sha`). Then `rig wiki ingest <that-path>`. |
 | "ingest / re-process / 重新整理 / 重新 ingest <something>" | `rig wiki ingest <path>` — handles new sources AND re-ingest of modified ones. |
 | "what's new / 有什么变化 / scan / diff" | `rig wiki scan` — surface the NEW / MODIFIED / DELETED / RAW DRIFT report verbatim. |
 | "ingest everything new / 把新东西都收一下" | `rig wiki scan` → for each NEW path → `rig wiki ingest <path>` (one call per file). |
@@ -30,43 +38,70 @@ You orchestrate `rig wiki *` on behalf of the user. The user speaks in intent; y
 | "summarize what we know about X / 总结一下 X" | `rig wiki query "<X>" --synth` — adds a Claude-synthesized paragraph with `[[wikilink]]` citations after the hit list. |
 | "lint / 检查一遍 / what's broken in my wiki" | `rig wiki lint`. Surface the report. Exit code 11 = severe (broken refs / missing source). |
 | "rebuild / 全部重 embed / 换了模型 / 新机器" | `rig wiki rebuild` — full nuclear refresh. Only suggest this when the user mentions a new device or explicitly switching the embed model. |
-| "wiki list / what wikis are registered" | `rig wiki list` |
-Always run from inside the registered project (or pass `--wiki <name>`). If the user is in some other CWD, `cd` to the wiki's project first.
+## Vault layout (flat — no inner `wiki/` subdir)
+```
+<vault>/
+  purpose.md          ← human-authored, never write
+  schema.md           ← human-authored, never write
+  index.md            ← LLM-writable
+  overview.md         ← LLM-writable
+  log.md              ← append-only LLM log
+  reviews.md          ← LLM-writable backlog of human-review items
+  raw/                ← immutable source files (never edit existing)
+  sources/            ← one .md per ingested source — page tree at vault root
+  entities/
+  concepts/
+  synthesis/
+  queries/
+  .rig/config.yml     ← per-vault settings (name, root, include, exclude, …)
+  .gitignore
+```
+Note: there is no `<vault>/wiki/` subdirectory. Page directories (`sources/`, `entities/`, `concepts/`, `synthesis/`, `queries/`) live directly under the vault root.
 ## Argument inference rules
-- **slug** = kebab-case, no dates inside `wiki/`, dates only on `raw/YYYY-MM-DD-*` prefix.
+- **slug** = kebab-case, no dates in page filenames; dates only on `raw/YYYY-MM-DD-*` prefix.
 - **raw filename** = `YYYY-MM-DD-<slug>.md`. Pick today's local date; if filename collides, append `-2`, `-3`.
 - **URL → slug**: last path segment, drop extension, lowercase, replace non-`[a-z0-9-]` with `-`, max 64 chars.
-- **wiki dir name** when initializing: prefer user-stated name; if absent, ask once. Never default to `wiki` or CWD silently.
+- **Default vault dir name** when the user says "init a vault / make a wiki here" without specifying: suggest `rig-wiki` at the project root. Never default silently — confirm the name once.
 ## Hard rules — refuse and explain if violated
 - **Never** edit `raw/`, `purpose.md`, or `schema.md` directly. Those are human-authored. If the user asks you to, tell them to do it manually.
-- **Never** ingest or init at a **hidden path** (any segment starting with `.`) or a **.gitignored** path. rig wiki refuses at the CLI level — it sees these as "the project deliberately doesn't want this in the wiki." Workaround if the user insists: `cp -R <hidden-or-ignored> <wiki>/raw/<slug>/` first, then ingest the copy. Never bypass the guard.
-- **Never** ingest a path outside the wiki's `include[]` scope (anything in `raw/` is always fine; outside that requires the path to be listed in the registered wiki's `include`).
+- **Never** init a vault INSIDE a user-authored data directory (e.g. `personal/wiki/`). The vault dir contaminates the user's source tree. Put the vault at the project root (e.g. `<project>/rig-wiki/`) and point `include[]` at the data dirs via `<vault>/.rig/config.yml`.
+- **Never** init a vault at a **hidden path** (any segment starting with `.`) or a **.gitignored** path. rig wiki refuses at the CLI level.
 - **`rig wiki scan` exit 10 (RAW DRIFT)** = a `raw/` file's bytes changed since last scan. Do NOT auto-fix or re-ingest. Surface to the user as a data-integrity warning.
 - **`rig wiki lint` exit 11** = severe findings. Surface the report path and the top findings; do not auto-fix unless the user asks.
 - **Never** suggest editing `~/.rig/cache/qmd/*.sqlite` or `~/.cache/qmd/`. Those are rebuildable caches.
+## Auto-exclusions (no config needed)
+The scanner skips these automatically — do not waste user time adding them to `exclude`:
+- Any path segment starting with `.` (`.git/`, `.obsidian/`, `.vscode/`, `.DS_Store`, …).
+- Any path matched by the project's `.gitignore`.
+What you DO need to put in `exclude` are content-type filters the user cares about — e.g. `**/*.zip`, `**/*.pdf` if they don't want those in their text wiki.
 ## Common error → recovery
 | Error | What it means | Action |
 |---|---|---|
-| `qmd query failed. Run \`rig wiki index\` first` | No vector index for this wiki | `rig wiki index --wiki <name>` then retry |
-| `no wiki resolved` | CWD is not inside a registered wiki and no `--wiki` flag | Either `cd` into the project or pass `--wiki <name>` |
-| `claude not installed on PATH` (during ingest/synth) | Claude Code CLI missing | Tell the user; suggest `yarn dlx @anthropics/claude-code` or use a non-agent flow |
+| `No rig wiki vault found.` | CWD has no `.rig/config.yml` and no parent does either | `cd` into the vault (or the project that contains one), or run `rig wiki init <subdir>` |
+| `qmd query failed. Run \`rig wiki index\` first` | No vector index for this vault | `rig wiki index`, then retry |
+| `claude not installed on PATH` (during ingest/synth) | Claude Code CLI missing | Tell the user; suggest `yarn dlx @anthropics/claude-code` |
 | Reranker download stalls on first query | CDN cold node, can take ~1 min | Just wait; subsequent queries are instant |
 ## Output handling
-- After running a `rig wiki *` command, **summarise in natural language** what changed. Don't dump raw `rig` output unless the user asks ("show me the raw output"). Examples:
+- After running a `rig wiki *` command, **summarise in natural language** what changed. Don't dump raw `rig` output unless the user asks. Examples:
   - After `rig wiki ingest`: "Wrote 11 pages (1 source, 2 entities, 5 concepts, …). Lint clean."
-  - After `rig wiki query`: cite the top hit by slug `[[wikilink]]` and quote a 1-line snippet; offer to run `--synth` if user wants a paragraph.
+  - After `rig wiki query`: cite the top hit by slug `[[wikilink]]` and quote a 1-line snippet; offer `--synth` for a paragraph.
   - After `rig wiki scan`: "3 new, 1 modified. Want me to ingest them?"
 - For **machine** consumption (chaining): use `--json` on any command. Shape is `{ ok, code, data?, error? }`.
-- **Long ingest** (Claude two-step CoT): expect 1–3 minutes. Tell the user once at the start; don't ping them mid-run.
+- **Long ingest** (Claude two-step CoT): expect 1–3 minutes per source. Tell the user once at the start; don't ping them mid-run.
 - **First-run model download** (embed model on first `ingest` / `index`, reranker on first `query`): each is ~610MB from the rig CDN — usually under a minute. Mention it the first time, then forget.
 ## When NOT to use this skill
@@ -76,38 +111,36 @@ Always run from inside the registered project (or pass `--wiki <name>`). If the
 - User is talking about a different knowledge system (Obsidian-only, Notion, etc.).
 - Task is unrelated to personal knowledge capture (e.g. code search → use `grep`).
-## Setup — if no wiki is registered
+## Setup — if no vault is found
-`rig wiki list` shows zero entries → ask the user **once** (don't list multiple defaults; pick one suggestion and confirm):
+`rig wiki scan` (or any command) reports `No rig wiki vault found.` → ask the user **once** (don't list multiple defaults; pick one suggestion and confirm):
-> "No wiki registered here. Want me to init one under `knowledge/`? (or pick another subdir name)"
+> "No vault here. Want me to init one as `rig-wiki/` at the project root? (or pick another path)"
 Then orchestrate without further prompting:
 ```bash
-rig wiki init <subdir>          # REQUIRED — fails if path missing or hidden/gitignored
-rig wiki register <subdir>
+rig wiki init rig-wiki    # creates <project>/rig-wiki/ with templates + .rig/config.yml
 ```
-After init, **pause and ask the user to edit `<subdir>/purpose.md`** (one-time human scoping — define what this wiki is for, in/out of scope). Don't write purpose.md yourself; it's the only human-authored anchor for everything downstream.
+After init, **pause and ask the user to edit `<vault>/purpose.md`** (one-time human scoping — define what this wiki is for, in/out of scope). Don't write purpose.md yourself; it's the only human-authored anchor for everything downstream.
-If the user describes a scan scope that differs from the defaults (e.g. "include every md file in the parent dir but ignore zip files"), translate that into edits to `<subdir>/.rig/config.yml` — that's the per-vault settings file (`name`, `root`, `include`, `exclude`, `schedule`, `ingestRules`). The vault is self-contained: nothing about its identity or scope lives outside its own directory.
+If the user describes a scan scope that differs from the defaults (e.g. "include every md file in `personal/` but ignore zip files"), translate that into edits to `<vault>/.rig/config.yml`. Fields: `name`, optional `root` (relative scan base, default `..`), `include[]`, `exclude[]`, `schedule`, `ingestRules`. The vault is self-contained — nothing about its identity or scope lives outside its own directory.
-## Configuration model (read once, then forget)
+## Configuration files
-Two layers, both YAML:
+Two YAML files, both optional except where noted:
-- `~/.rig/config.yml` — rig-global prefs only (default agent, qmd toggle, log rotation). Touched by `rig wiki agent use`.
-- `~/.rig/wikis.yml` — registry. **Just a flat list of vault paths** for discovery. No per-wiki settings here.
-- `<vault>/.rig/config.yml` — **the only place per-vault settings live.** `name`, optional `root` (relative scan base, default `..`), `include[]`, `exclude[]`, `schedule`, `ingestRules`. Created automatically by `init`. Safe to edit by hand.
+- `~/.rig/config.yml` — rig-global prefs (default agent, qmd toggle, log rotation). Touched by `rig wiki agent use`.
+- `<vault>/.rig/config.yml` — **the only place per-vault settings live.** Auto-created by `rig wiki init`. Safe to edit by hand.
-Never edit `~/.rig/wikis.yml` to change a wiki's name, scope, or schedule — those belong in the vault. Never invent a `package.rig.json5` wiki block; that file is unrelated to rig wiki (legacy rig CICD only).
+No global registry. No `package.rig.json5` wiki block (that file is for legacy rig CICD, unrelated).
 ## Architecture (read once, then forget)
 - Vector-only retrieval: Qwen3-Embedding-0.6B (~610MB) + Qwen3-Reranker-0.6B (~610MB), both CDN-mirrored at `assets.terncloud.com/rig/models/`.
 - Models auto-downloaded on first use into `~/.cache/qmd/models/`; subsequent runs are instant.
-- Per-wiki SQLite at `~/.rig/cache/qmd/<wiki>.sqlite` (sqlite-vec extension). `.gitignore`'d by default.
+- Per-vault SQLite at `~/.rig/cache/qmd/<vault-name>.sqlite` (sqlite-vec extension). `.gitignore`'d by default.
 - `ingest` triggers incremental embed at the end — no need to manually call `index` in routine use.
 - macOS-only in v1.