wiki-savelisted

> 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-save — session close-out (warm, human-present) Close the session by filing **THIS session's** work into durable knowledge, **right here (warm context)**, and keep the **reading input (L0) fresh**. This is the primary integration path — warm, human-present, not an unattended cron. **Minutes, not tens of minutes**: close-out latency is what makes people abandon a wiki (the maintenance-burden rule), so this pass is strictly O(this session). Everything heavier — the transcript backlog, the gap queue, topic re-distillation — belongs to the periodic **`/wiki-deep`** de