v0.9.1 — the first five minutes

Two lines an adopter reads in the first five minutes, both of which said something untrue. Found by installing the published clone in a clean room — isolated HOME, inert supervisor shims — and following the README as written.

doctor denied an enrollment that had just succeeded

The enrollment inventory is drawn only from repositories the capture queue has already seen; doctor never scans your machine, by design. But the queue file exists from the first sweep onward, including sweeps that captured nothing — so a fresh install answered ✅ enrolled repositories: 0 seconds after init printed automatic integration enabled for this worktree. In the clean room: init succeeded, cold start injected 2,833 bytes into the session, and doctor still said 0.

It now reports what it actually knows — no repository captured yet — and names the command that can answer immediately, llmwiki status <repo>.

The README told Claude-only users to run a command they do not have

The llmwiki launcher is installed by the Codex and OpenCode wiring. All four READMEs nonetheless gave llmwiki init /absolute/path as the one activation step, so a Claude-only install meets command not found at exactly that point. Each README now also gives the direct form:

bun ~/llmwiki/src/cli.ts init /absolute/path/to/my-project   # status and disable likewise

(The agent contract in setup_text.md already handled this correctly — only the human-facing docs were wrong.)

---

Upgrading: git pull && ./setup.sh. If you are coming from v0.8.x, the required enrollment step in v0.9.0 still applies.

Verified with 754 tests, tsc --noEmit, and a clean-room install of the published clone: clone → setup → enrollment gate → init → cold-start and per-turn injection → capture sweep → uninstall.