@aitne-sh/aitne 0.1.5 → 0.1.7

package/agent-assets/docs/guides/maintain-wiki-health.md

@@ -0,0 +1,168 @@
+---
+schema_version: 1
+slug: guides/maintain-wiki-health
+title: Maintain Wiki Health
+id: maintain-wiki-health
+aliases:
+  - "!lint"
+  - wiki health
+  - wiki lint
+  - wiki orphans
+  - wiki taxonomy candidates
+category: guides
+summary: |
+  How to run `!lint`, read the health report, act on action items,
+  and review taxonomy candidates the wiki agent surfaces for owner
+  approval before promoting them.
+section: maintain-wiki-health
+tags:
+  - guide
+  - wiki
+  - health
+status: stable
+ask_examples:
+  - How do I run a wiki health check?
+  - What does the wiki health report contain?
+  - Where do I see the latest health report?
+  - How often should I run !lint?
+  - What is a taxonomy candidate?
+locale: en-US
+created: 2026-05-12
+updated: 2026-05-12
+related:
+  - features/wiki/overview
+  - features/wiki/commands
+  - guides/explore-with-trace-and-connect
+ui_anchors:
+  - /wiki
+  - /wiki/timeline
+  - /settings/wiki
+---
+
+# Maintain Wiki Health
+
+The wiki is a living artifact. Notes accumulate, sources drift,
+slugs collide, and the taxonomy slowly diverges from the vocabulary
+your raw notes actually use. `!lint` is the periodic audit pass
+that surfaces all of this in one report — without changing your
+notes itself.
+
+## When to Run
+
+`!lint` is cheap (Sonnet medium tier, default $0.50 envelope) and
+non-destructive. Run it whenever you want a snapshot of wiki
+health. A practical cadence:
+
+- **Weekly**, after a busy ingest week, to catch orphans early.
+- **Before promoting a candidate** to the taxonomy or graduating
+  an inbox note — you want the audit fresh.
+- **After a bulk import** (Phase 2 migration or a backlog
+  `!ingest` batch) to verify the merge didn't introduce drift.
+
+You don't need to schedule `!lint`; send it from a DM:
+
+```
+!lint
+```
+
+The wiki agent replies with the workspace name and tells you the
+report will land at `90_meta/health/<today>.md`.
+
+## What the Report Contains
+
+The report is a Markdown file at `90_meta/health/<YYYY-MM-DD>.md`
+with a fixed section order:
+
+1. **Summary** — one-line tallies (`3 orphans, 1 broken link, 2
+   taxonomy candidates`).
+2. **Action items** — concrete fixes you can take, each naming
+   the affected file and the proposed change.
+3. **Orphans** — wiki notes with no incoming links.
+4. **Broken wikilinks** — `[[slug]]` references pointing at files
+   that no longer exist.
+5. **Missing frontmatter** — notes that don't satisfy the schema
+   in `90_meta/schemas/`.
+6. **Stale content** — wiki notes whose newest source link is
+   older than 90 days.
+7. **Term inconsistencies** — slugs that look like the same
+   concept under different names.
+8. **Taxonomy candidates** — recurring concepts that aren't yet
+   in `90_meta/taxonomy.md` (three or more raw notes, or two or
+   more wiki notes).
+9. **Index drift** — `20_wiki/_index.md` mismatches against disk.
+
+Empty sections render as `_(none)_` so a diff between two reports
+makes the change visible.
+
+## Reading the Report on the Dashboard
+
+Open **My Life → Wiki → Timeline & health** (`/wiki/timeline`). The
+page is also reachable from a button at the top of `/settings/wiki`,
+and the legacy `/settings/wiki/timeline` URL redirects here so old
+bookmarks still work. The most-recent report is parsed and rendered
+with:
+
+- A coloured date badge.
+- The `## Summary` bullets.
+- The `## Action items` list (this is the part you actually act on).
+- A "View full report" expander showing the raw Markdown for
+  every section.
+
+The same page hosts the activity timeline (see below) so you can
+correlate a health finding with the ingest / compile / ask runs
+that produced the state.
+
+## Acting on Action Items
+
+The audit never modifies content layers itself. For each action
+item:
+
+- **Orphan** → either link the note from `20_wiki/_index.md` and
+  related notes, or archive it. From a DM you can run `!ask` to
+  decide whether the note's content has been superseded.
+- **Broken wikilink** → edit the linking note via `!compile` (so a
+  fresh `wiki.compile` resolves the reference) or trace the
+  history with `!trace` to recover what the missing target used
+  to be.
+- **Stale content** → re-ingest authoritative sources with `!ingest`,
+  then run `!compile` to re-synthesize.
+- **Term inconsistencies** → decide on the canonical slug, then
+  update `90_meta/taxonomy.md` manually so future ingests pick the
+  right name.
+
+## Taxonomy Candidates
+
+When `!lint` finds a concept appearing repeatedly that isn't yet
+in the taxonomy, it appends a `# Candidates` section to
+`90_meta/taxonomy.md`:
+
+```
+# Candidates
+- quantum-computing — referenced by 4 raw / 0 wiki
+- formal-methods — referenced by 3 raw / 1 wiki
+```
+
+**The wiki agent never promotes a candidate into the main `##
+Topics` section itself.** Promotion is an owner act because once a
+slug is canonical, every future ingest and compile pass will route
+toward it. To promote, edit `90_meta/taxonomy.md` directly:
+
+1. Move the candidate line into the `## Topics` section.
+2. Delete the corresponding line from `# Candidates`.
+3. Optionally add aliases for spelling variants the raw notes use.
+
+The next `!compile` will reconcile existing notes against the new
+canonical slug.
+
+## Where the Report Lives
+
+The report is a regular wiki file written via the standard
+chokepoint, so:
+
+- It's visible to `!ask` (you can literally ask "what did the last
+  lint find?").
+- The DM read-only surface (`/api/wiki/.../files/90_meta/health/...`)
+  serves it back to a DM-agent for follow-up questions.
+- Internal-mode workspaces snapshot the previous version into
+  `.snapshots/` before each rewrite; external-mode relies on your
+  git or cloud sync.

package/agent-assets/docs/guides/multiple-wikis-for-multiple-domains.md

@@ -0,0 +1,192 @@
+---
+schema_version: 1
+slug: guides/multiple-wikis-for-multiple-domains
+title: Multiple Wikis for Multiple Domains
+id: multiple-wikis-for-multiple-domains
+category: guides
+summary: |
+  Run more than one wiki workspace inside the same daemon. Address
+  them from DMs with `@<workspace>`, manage them independently from
+  /settings/wiki, and keep their file trees isolated on disk.
+section: multiple-wikis-for-multiple-domains
+tags:
+  - guide
+  - wiki
+  - multi-workspace
+status: stable
+ask_examples:
+  - How do I run multiple wikis?
+  - How do I target a specific wiki from a DM?
+  - What does `@research` do before a wiki command?
+locale: en-US
+created: 2026-05-12
+updated: 2026-05-12
+related:
+  - features/wiki/overview
+  - features/wiki/commands
+  - guides/build-your-wiki
+  - guides/use-an-existing-obsidian-vault
+---
+
+# Multiple Wikis for Multiple Domains
+
+Phase 5 lifted Aitne's single-workspace ceiling. If you keep distinct
+knowledge bases — say, a research vault, a parenting journal, and an
+ops runbook — you can run each as its own wiki workspace inside the
+same daemon. The DM agent routes commands per workspace; the file
+trees never overlap.
+
+## Why you might want this
+
+- **Topic isolation.** A query against your research wiki should not
+  pull from your parenting journal. Separate workspaces give you
+  separate `_index.md` and `20_wiki/` trees so the agent never has to
+  filter across domains.
+- **Different audiences.** A workspace synced via Obsidian to a shared
+  iCloud folder for a team is governed differently from a private
+  workspace in `$PA_DATA_DIR`. Per-workspace settings handle the
+  asymmetry.
+- **Different cadences.** A "current project" wiki gets multiple
+  ingests per day; a long-term commonplace book may compile weekly.
+  Per-workspace dispatch / cost / approval thresholds let you tune
+  each.
+
+## Creating a second workspace
+
+1. Open `/settings/wiki`. You will see your current (default)
+   workspace.
+2. Scroll to **Add Workspace** (Phase 5 surface). Choose either:
+   - **Internal**, which lives under `$PA_DATA_DIR/wiki-<name>/`. Best
+     for private notes you never sync to another device.
+   - **External**, which points at an existing folder on disk (your
+     Obsidian vault, an iCloud-synced directory, a git working copy).
+3. Pick a unique `name` (lowercase letters, digits, `.`, `_`, `-`). The
+   name is what you address from DMs.
+4. The wizard probes the candidate path against §2.1.1 collision rules
+   — it refuses to nest a wiki inside your primary vault, the data
+   directory, or another active wiki. Iterate until the probe is green.
+5. Click **Create**. The vault skeleton (`00_inbox/`, `10_raw/`,
+   `20_wiki/`, `30_outputs/`, `90_meta/`) is seeded and the workspace
+   joins the active set.
+
+## Addressing a workspace from DMs
+
+Every wiki bang command accepts an optional `@<workspace>` token
+immediately after the bang:
+
+    !ingest @research https://arxiv.org/abs/2401.02954
+    !compile @research full
+    !ask @research what did I conclude about retrieval-augmented LMs?
+    !lint @parenting
+    !trace @ops "incident 2026-05-02"
+    !connect @research "diffusion models" "score matching"
+
+Omit `@<workspace>` and the command targets the default workspace
+(the one named `default`, set during initial setup).
+
+The `@<token>` syntax is parsed before the command's own argument
+parser sees the rest, so you can keep using multi-word topics and
+comma-separated arguments verbatim.
+
+## What the agent sees per workspace
+
+Each session is materialised against a single workspace's tree. The
+`wiki-vault-rules` skill loaded for the session names that workspace's
+language, dispatch mode, layer invariants, and frontmatter
+conventions. Layer authorisation in the daemon API is workspace-scoped
+— a `wiki.ask` session against `@research` cannot reach into
+`@parenting`'s `10_raw/` even if the agent attempts it.
+
+## `!wiki` status with multiple workspaces
+
+`!wiki` (no token) lists every active workspace in a compact form:
+
+    3 active wiki workspaces:
+    - `default` (default) — 12r/8w/3o (internal)
+    - `research` — 84r/41w/12o (external)
+    - `parenting` — 7r/2w/0o (external)
+
+    Target a non-default workspace with `@<name>` (e.g. `!ask @research <question>`).
+
+`r/w/o` are raw / wiki / output counts. The `(default)` marker tells
+you which workspace `!ask` (with no `@`) will route to.
+
+## Configuring each workspace independently
+
+`/settings/wiki` shows a workspace picker at the top once you have
+more than one. Each workspace's panel carries its own:
+
+- language (`en`, `ja`, …)
+- dispatch mode (parallel / serial) and concurrency cap
+- write strategy (`fs` / `cli` / `auto`) — external mode only
+- full-compile approval threshold (USD)
+- git pre-compile auto-commit toggle (external git vaults only)
+- bridge feature gate + measurement mode + min confidence (Phase 5)
+- DM-agent bridge write toggle
+
+`POST /api/backends/apply-defaults` re-seeds the per-process backend /
+model / budget rows but leaves the per-workspace columns alone — those
+are operator preferences, not install defaults.
+
+## Per-workspace `/settings/models` rows
+
+`/settings/models` lists the wiki process keys
+(`wiki.ingest_url`, `wiki.compile`, `wiki.ask`, `wiki.lint`,
+`wiki.trace`, `wiki.connect`) once each. The backend / model / budget
+bound to each key applies across all workspaces — they share the
+binding because the daemon resolves the row by process key, not by
+workspace.
+
+If you need a research vault on Opus 4.7 and a parenting journal on
+Haiku 4.5 at the same time, the supported path today is:
+
+- Bind `wiki.ask` to medium-tier Sonnet (a sensible cross-workspace
+  default).
+- Use the workspace-aware `!ask @research` for the research vault and
+  rely on per-workspace token budgets via the cost ceiling.
+
+A future enhancement is per-workspace model bindings; the present
+shape was chosen to keep `/settings/models` legible without a
+workspace dimension.
+
+## Archiving a workspace
+
+The dashboard's **Archive** button on a workspace card flips its
+`active` column to `0`. Archived workspaces:
+
+- disappear from `!wiki` listings,
+- reject all daemon API requests with `wiki_not_enabled`,
+- drop out of `/search` and `/index`,
+- keep their files on disk (you can re-activate later with no data
+  loss),
+- have their `fts_wiki` rows cleared eagerly so a same-id re-enable
+  re-indexes from disk.
+
+`DELETE /wiki/workspaces/:name` removes the row entirely (filesystem
+contents are preserved — the daemon never deletes vault content). Use
+this when you are sure you will not re-enable.
+
+## Path collision rules (recap)
+
+Two active wiki workspaces cannot point at overlapping paths. Neither
+can overlap:
+
+- `primaryVaultPath` — your reactive-memory vault (`knowledge/`,
+  `today.md`, etc.).
+- `externalObsidianVaultPath` — your owner-facing Obsidian vault.
+- `$PA_DATA_DIR` — the daemon's data home.
+
+The wizard's pre-create probe enforces this; PATCH cannot widen past
+it. If you want to migrate a workspace to a new disk location, archive
+the old row, create a fresh row pointing at the new path, then
+manually copy the vault contents.
+
+## See also
+
+- `docs/design/23-wiki-builder.md` — Phase summary table for the
+  overall wiki feature.
+- `docs/design/appendices/wiki-external-vault.md` — write strategy,
+  iCloud handling, snapshot exclusion.
+- `docs/design/appendices/wiki-bridge-mechanism.md` — Phase 5 bridge
+  capture from DMs into a workspace's raw layer.
+- `docs/user/features/wiki/commands.md` — full bang command reference.

package/agent-assets/docs/guides/pause-the-agent.md

@@ -23,6 +23,7 @@ created: 2026-04-25
 updated: 2026-04-25
 related:
   - features/operations/quiet-hours
+  - features/messaging/bang-commands
   - concepts/routines
 ---
 
@@ -39,15 +40,19 @@ losing your install.
 
 ## Steps
 
-1. **Disable the hourly check** from `/settings/routines` — toggle
+1. **For a short pause from your phone**: DM `!stop` to the agent on
+   any paired messaging app. Autonomous work pauses immediately; the
+   daemon keeps running so you can `!start` to resume. See
+   [Bang Commands](../features/messaging/bang-commands.md).
+2. **Disable the hourly check** from `/settings/routines` — toggle
    `hourlyCheckEnabled` off. Morning, evening, weekly, and monthly
    reviews fire at fixed times in code, so they cannot be toggled
    from the dashboard; the most reliable mute is `pa stop`.
-2. **Set an extended quiet hours window** on `/settings/schedule` —
+3. **Set an extended quiet hours window** on `/settings/schedule` —
    e.g. `quietHoursStart: "00:00"`, `quietHoursEnd: "23:59"`. Both
    fields take an `HH:MM` string. This silences notifications while
    keeping routines running.
-3. **Optionally** stop the daemon entirely with `pa stop`. This is
+4. **Optionally** stop the daemon entirely with `pa stop`. This is
    the only way to fully suppress the fixed-schedule routines.
 
 ## Verification
@@ -62,4 +67,6 @@ losing your install.
 
 ## Related
 
+- [Bang Commands](../features/messaging/bang-commands.md) — `!stop` /
+  `!start` from any paired DM.
 - [Quiet Hours](../features/operations/quiet-hours.md)

package/agent-assets/docs/guides/use-an-existing-obsidian-vault.md

@@ -0,0 +1,156 @@
+---
+schema_version: 1
+slug: guides/use-an-existing-obsidian-vault
+title: Use an Existing Obsidian Vault
+id: use-an-existing-obsidian-vault
+aliases:
+  - external wiki
+  - obsidian vault as wiki
+  - external mode
+category: guides
+summary: |
+  Point Aitne's wiki at an Obsidian vault you already maintain. The
+  setup wizard probes the path, classifies the layout, and walks you
+  through Adopt vs Migrate vs Split.
+section: use-an-existing-obsidian-vault
+tags:
+  - guide
+  - wiki
+  - obsidian
+status: stable
+ask_examples:
+  - Can the wiki use my existing Obsidian vault?
+  - How does the iCloud-sandbox fallback work?
+  - What does Adopt vs Migrate mean?
+locale: en-US
+created: 2026-05-12
+updated: 2026-05-12
+related:
+  - features/wiki/overview
+  - guides/build-your-wiki
+  - guides/budget-and-cost-for-wiki
+  - troubleshooting/wiki-write-failed
+---
+
+# Use an Existing Obsidian Vault
+
+## Goal
+
+Aitne can point the wiki subsystem at a vault you already maintain
+in Obsidian, instead of creating its own at `$PA_DATA_DIR/wiki`.
+This is "external mode", and the setup wizard walks you through
+three decisions: **probe**, **classify**, then **Adopt vs Migrate
+vs Split**.
+
+## Step 1 — Open Settings → Wiki
+
+Click **Setup → Settings → Wiki** in the dashboard sidebar (or open
+`/wiki` and follow the **Enable Wiki** button — both land on the same
+page). If you have no workspace yet, the page shows two CTAs:
+
+- **Enable Internal Workspace** — uses the daemon-owned root.
+- **Probe & Create External** — points at the path you choose with
+  the folder picker.
+
+### Picking the path
+
+The path field uses your OS-native folder dialog so you do not have
+to type the path by hand or worry about typos:
+
+- **macOS** — Finder's "choose folder" sheet opens.
+- **Windows** — File Explorer's folder picker opens.
+- **Linux** — one of `zenity`, `kdialog`, or `yad` opens (whichever
+  is installed on your system).
+
+If you prefer to paste a path you already have on the clipboard, the
+text field accepts that too — typing or pasting and clicking the
+folder button are equivalent. Aitne refuses paths that overlap
+`dataDir`, your primary vault, or the external Obsidian vault path so
+two writers never claim the same files.
+
+### Inline validation banner
+
+Once you pick a directory, Aitne immediately calls `GET /api/fs/probe`
+and renders a banner under the input. The banner has three severity
+levels:
+
+- **Error (red)** — save is blocked. The most common cause is a
+  collision with another vault (primary, external Obsidian, dataDir,
+  or another wiki workspace); the second is a path under a system
+  prefix (`/etc`, `/var`, `/usr`, …) or matching a known secret-file
+  pattern (`.ssh`, `.env`, `Library/Keychains`, …).
+- **Warning (amber)** — save is allowed but something needs your
+  attention. The most common case is "directory is not writable from
+  the daemon" — Aitne will fall back to the Obsidian CLI at runtime,
+  and you should leave Obsidian running.
+- **Info (blue)** — nothing wrong. Used for "directory will be
+  created on save" (the path does not exist yet) and for "Obsidian
+  vault detected" / "existing LLM-Wiki layout detected" hints. When
+  an existing wiki layout is detected, the wizard will surface the
+  Adopt / Migrate decision in Step 3.
+
+The **Probe & Create External** button is greyed out while the banner
+is an error so you cannot fire a workspace-create that the daemon
+already knows will fail.
+
+## Step 2 — Probe Classifies the Vault
+
+The wizard calls `POST /api/wiki/workspaces/probe` and one of three
+classifications comes back:
+
+- **empty** — no markdown files anywhere. Aitne creates the layered
+  skeleton (`00_inbox/`, `10_raw/`, `20_wiki/`, `30_outputs/`,
+  `90_meta/`) and seeds `90_meta/taxonomy.md` + the schema templates.
+- **partial** — fewer than two layer directories. This usually means
+  the directory holds unrelated notes. The wizard nudges you to
+  inspect before continuing so Aitne does not silently take over a
+  foreign vault.
+- **wiki** — two or more layer directories. The wizard surfaces
+  schema deltas and the top `type:` values it detected, then offers
+  Adopt / Migrate / Split.
+
+## Step 3 — Adopt / Migrate / Split
+
+| Option | What it does |
+|---|---|
+| **Adopt** | Keeps your existing schema and subdirectory layout verbatim. Aitne's wiki agent gets a workspace-specific addendum so it follows your conventions. |
+| **Migrate** | Flattens type-based subdirectories (`20_wiki/concepts/x.md → 20_wiki/x.md`) and renames legacy frontmatter keys (`topic → title`, `source_url → url`, …) to Aitne's Bases-era schema. Always writes a backup mirror under `90_meta/health/pre-migrate-<date>/` first. |
+| **Split** | Refuses to touch the existing vault and creates a sibling workspace instead. Available once multi-workspace lands. |
+
+When you pick **Migrate**, the dashboard renders the plan — files
+that will be moved, frontmatter renames per file, slug collisions to
+resolve — before any write hits disk. Apply only once the plan looks
+right; the report lands at `90_meta/health/import-<date>.md`.
+
+## Step 4 — First Compile
+
+After the workspace is created (and migrated, if you chose that
+path), you can:
+
+- Run `!compile` for an incremental compile of any pre-existing raw
+  notes.
+- Run `!compile full` for a one-shot full rebuild — but check the
+  cost estimate banner first. Above the per-workspace threshold
+  (default $2.00) the command queues an approval in the dashboard
+  rather than spending autonomously.
+
+If your external vault is also a git repo, Aitne automatically
+commits a `pre-compile snapshot` on a clean working tree before
+`!compile full` so you can roll back if the result surprises you. A
+dirty tree refuses the operation entirely — commit or stash first.
+
+## iCloud-Sandboxed Vaults
+
+When Aitne's direct filesystem writes return `EPERM` (typical for
+iCloud and other sandboxed locations), the daemon falls back to the
+official Obsidian CLI. Requirements:
+
+- Obsidian 1.12 or later installed.
+- **Settings → General → Command line interface** enabled inside
+  Obsidian.
+- The Obsidian app must be running (the CLI talks to the live
+  process).
+
+The resolved write strategy is persisted into the workspace row so
+the probe only runs once. The dashboard write-strategy dropdown lets
+you pin `fs` or `cli` explicitly when you trust your own answer.

package/agent-assets/docs/reference/cli-commands.md

@@ -31,6 +31,7 @@ keywords:
 related:
   - guides/install-and-run
   - guides/reinstall-cleanly
+  - features/wiki/commands
 ---
 
 # CLI Commands
@@ -50,7 +51,7 @@ tables below show both forms.
 |---|---|
 | `aitne start` / `pnpm start` | Build (if stale), then launch daemon + dashboard in the background. |
 | `aitne stop` / `pnpm stop` | Graceful shutdown (SIGTERM → SIGKILL after 10s) of both processes. |
-| `aitne restart` / `pnpm restart` | `stop` then `start`. `--clean-context` wipes `context/` after a tarball backup. |
+| `aitne restart` | `stop` then `start`. `--clean-context` wipes `context/` after a tarball backup. (Prefer the bin over `pnpm restart` / `npm restart`: those run the npm `stop` → `restart` → `start` lifecycle, which would re-fire each step.) |
 | `aitne status` / `pnpm status` | PIDs, uptime, integrations, today's spend, last action timestamp, next scheduled item. |
 | `aitne dev` / `pnpm dev` | Foreground mode — runs the daemon + dashboard with full stdio. |
 
@@ -86,6 +87,28 @@ tables below show both forms.
 | `pnpm lint` | Run eslint per package. |
 | `pnpm clean` | Remove `node_modules`, `dist`, `.buildstamp`. |
 
+## Wiki bang commands
+
+Sent as DMs from a paired channel, not from the shell. Every command
+accepts an optional `@<workspace>` token immediately after the bang to
+target a non-default workspace. See
+[Wiki Commands](../features/wiki/commands.md) for the full reference
+and the cost-gate / approval semantics.
+
+| Command | What it does |
+|---|---|
+| `!ingest [@<ws>] <url> [url...]` | Capture one or more URLs into the workspace's `10_raw/` layer. Caps at 10 URLs per batch; parallel or serial fan-out per the workspace's dispatch mode. |
+| `!compile [@<ws>]` | Incremental compile — synthesises only raw notes touched since the last run into `20_wiki/`. |
+| `!compile [@<ws>] --preview` | Dry-run touch list (added / modified / unchanged) plus cost and ETA. No agent session runs. Alias: `--dry-run`. |
+| `!compile [@<ws>] full` | Full rebuild. Cost-gated: estimates above the per-workspace threshold queue a dashboard approval. On a clean external git vault, an automatic pre-compile snapshot is committed first. |
+| `!compile [@<ws>] full --preview` | Dry-run of the full rebuild. |
+| `!ask [@<ws>] <question>` | Cited answer from the workspace, written to `30_outputs/`. |
+| `!lint [@<ws>]` | Audit orphans, broken links, schema drift, taxonomy candidates, stale notes. Writes `90_meta/health/<YYYY-MM-DD>.md`. |
+| `!trace [@<ws>] <topic>` | Reconstruct how an idea has evolved across `10_raw` / `20_wiki` / `30_outputs`. |
+| `!connect [@<ws>] <A>, <B>` | Find shared structure and bridges between two areas. |
+| `!wiki` | Workspace status (per-workspace counts when multiple are active). |
+| `!wiki help` | Wiki command list. |
+
 ## Environment overrides
 
 | Variable | Default | What it controls |