wiki-doctorlisted

> Engine invocation — resolve it ONCE, in this order, and use the first that exists: > 1. `bun "<plugin-root>/src/cli.ts"`, where `<plugin-root>` is the directory TWO levels above > this skill's base directory (skills/<name>/ → plugin root). This is the plugin and clone > install — the normal case. Stop here when that file exists. > 2. `bun "$LLMWIKI_ROOT/src/cli.ts"` when `LLMWIKI_ROOT` is set — a host that copied this > skill folder OUT of the plugin (OpenClaw, Hermes, `skills add`) leaves step 1 pointing at > that host's skills directory, not at an engine. > 3. `llmwiki` on PATH — the launcher `setup.sh` writes to `~/.local/bin`, or the npm bin. > > If none of the three resolve, say so once and stop. Do NOT guess a path: the engine writes > into a repository, and a guessed root writes into the wrong one. Every `llmwiki …` or > engine-CLI reference below means the invocation you resolved here. # /wiki-doctor — repair the active installation and this repository's wiki Make the active llmwiki wiring and the current repository's `docs/wiki/` operational and trustworthy. This workflow runs two distinct checks in order: `llmwiki doctor` for the machine-level installation, then `llmwiki wiki-doctor` plus an evidence-aware agent repair pass for the current project. $ARGUMENTS ## Safety boundary - The CLI owns safe, deterministic repairs only: missing skeleton files/directories, the the rebuildable index (engine-held; `llmwiki state-path <repo>`), citation/link g