project-librarian 0.5.4 → 0.5.6

package/README.md

@@ -5,7 +5,7 @@
 [![Node.js](https://img.shields.io/badge/Node.js-%3E%3D22.13-brightgreen.svg)](https://nodejs.org/)
 [![Code evidence index](https://img.shields.io/badge/code%20evidence-node%3Asqlite-blue.svg)](https://nodejs.org/api/sqlite.html)
 
-**Give every AI coding agent the same durable memory of your project.** Project Librarian keeps a compact, repo-local planning wiki — plus an optional code-evidence index — that Codex, Claude Code, Cursor, and Gemini CLI read at session start, so they stop rediscovering your codebase from scratch every time.
+**Give every AI coding agent the same durable memory of your project.** Project Librarian keeps a compact, repo-local planning wiki, plus an optional code-evidence index, that Codex, Claude Code, Cursor, and Gemini CLI can read at session start.
 
 Languages: [English](README.md) | [한국어](README.ko.md)
 
@@ -13,7 +13,7 @@ Languages: [English](README.md) | [한국어](README.ko.md)
 
 Most users should ask their coding agent to run Project Librarian rather than run lifecycle commands by hand.
 
-Install the reusable skill files once, or ask an agent with shell access to do it:
+Install the reusable skill files once:
 
 ```bash
 npx project-librarian@latest install --scope user --agents all
@@ -25,23 +25,23 @@ Then ask Codex, Claude Code, Cursor, or Gemini CLI from the target repository:
 - "Use Project Librarian to migrate the existing docs/wiki content."
 - "Search the Project Librarian wiki for authentication decisions."
 
-The installed skill tells the agent to resolve the local runner and execute the right command from the project root. Prefer a project-local install only when you want that runner stored inside the target repository's agent setup:
+The installed skill resolves the local runner and executes the right command from the project root. Use a project-local install only when you want the runner stored inside that repository's agent setup:
 
 ```bash
 npx project-librarian@latest install --scope project --agents all
 ```
 
-`install` copies the reusable runner and skill files. The agent-run lifecycle command is what creates or updates `AGENTS.md`, agent hooks, `wiki/`, git hook files, diagnostics, and optional code-evidence support. `install-skill` remains supported as a compatibility alias.
+`install` copies reusable runner and skill files only. The agent-run lifecycle command creates or updates `AGENTS.md`, agent hooks, `wiki/`, git hook files, diagnostics, and optional code-evidence support. `install-skill` remains a compatibility alias.
 
 ## Update
 
-To refresh an existing Project Librarian setup without migrating the wiki, run the latest package from the repository root:
+To refresh an existing setup without migrating the wiki, run:
 
 ```bash
 npx project-librarian@latest update
 ```
 
-That updates managed setup files, agent hooks, wiki operating/meta files, and existing project-scoped Project Librarian skill copies for the selected agent surfaces. It preserves the current `wiki/` and rejects migration flags, so it will not rename the wiki to `wiki_legacy*`.
+That updates managed setup files, agent hooks, wiki operating/meta files, and existing project-scoped skill copies. It preserves the current `wiki/` and rejects migration flags, so it will not rename the wiki to `wiki_legacy*`.
 
 Use `--agents` when you intentionally want to add or refresh a specific project surface:
 
@@ -56,108 +56,92 @@ User-scoped skill installs are global agent tooling and are not changed by a pro
 npx project-librarian@latest install --scope user --agents all
 ```
 
-## Highlights
-
-- **Small first read.** Session-start hooks inject only `wiki/startup.md` and `wiki/index.md`; agents route to deeper pages on demand instead of grepping the whole repo cold.
-- **One setup, four agents.** Codex, Claude Code, Cursor, and Gemini CLI share the same wiki-first contract, hooks, and rules.
-- **Structured wiki writing.** New project content is classified through `wiki/meta/document-taxonomy.md` before it is written or consolidated, so PRDs, policies, UX, data, APIs, QA, release, and operations notes do not collapse into one catch-all page.
-- **Inspectable wiki graph.** `--wiki-visualize` writes a self-contained HTML graph under `.project-wiki/`, showing page types, router depth, backlinks, and decision references without adding to startup context.
-- **Measured, not hand-wavy.** Every performance claim comes from hermetic Codex benchmarks — and the cases where it costs *more* are shown right next to the wins.
-- **Local session handoff.** `--handoff-save` writes generated resume notes under `.project-wiki/session/`; startup hooks only point to it, so rolling execution memory does not become canonical wiki truth.
-- **Optional code evidence.** A regenerable SQLite index plus answer-shaped MCP tools answer impact, ownership, and workspace-graph questions, with zero extra runtime dependencies.
-- **Safe to re-run.** Bootstrap is idempotent and preservation-first; diagnostics flag broken routes, unreachable pages, and stale truth before they mislead an agent.
-
 ## Why It Exists
 
 LLM coding agents waste context and tool calls when every session starts by rediscovering the project: reading old chats, scanning markdown, grepping source, and guessing which files matter.
 
-Project Librarian gives agents two local sources of truth:
+Project Librarian gives agents a small first read and reliable routes to deeper truth:
 
 | Surface | What It Gives The Agent |
 | --- | --- |
-| `wiki/startup.md` + `wiki/index.md` | A compact session-start summary and router, so only the relevant planning pages are read. |
-| `wiki/canonical/`, `wiki/roadmaps/`, `wiki/plans/`, and `wiki/decisions/` | Current truth stays in canonical pages, broad future work stays in roadmaps, detailed execution stays in plans, and durable rationale stays in decisions. |
-| `wiki/meta/document-taxonomy.md` | A service-lifecycle classification map that tells agents where PRD, policy, UX, data, engineering, QA, release, and operations truth should live. |
-| `.codex/`, `.claude/`, `.cursor/`, and `.gemini/` hooks | Automatic startup context for Codex, Claude Code, Cursor, and Gemini CLI without loading the full wiki. |
-| `GEMINI.md` and `.cursor/rules/` | Gemini CLI and Cursor instruction files that route agents to the same compact wiki-first contract. |
-| `.project-wiki/code-evidence.sqlite` | Regenerable code evidence for files, symbols, imports, routes, ownership, workspace graph, reports, and impact checks. |
-| `.project-wiki/session/last-handoff.md` | Optional generated local handoff for the last session's goal, state, blockers, next actions, decisions, commands, and verification. It is reference data, not project truth. |
-| `.project-wiki/wiki-graph.html` | Optional static wiki graph visualizer with derived concept types, router reachability, links, backlinks, and decision references. |
-| Diagnostics and migration modes | Link checks, quality checks, migration inboxes, stale-signal reports, and issue drafts when the workflow exposes a problem. |
+| `wiki/startup.md` + `wiki/index.md` | A compact session-start summary and router, so only relevant planning pages are read. |
+| `wiki/canonical/`, `wiki/roadmaps/`, `wiki/plans/`, `wiki/decisions/` | Current truth, future scope, execution plans, and durable rationale stay separated. |
+| Agent hooks and rules | Codex, Claude Code, Cursor, and Gemini CLI start from the same wiki-first contract. |
+| `.project-wiki/code-evidence.sqlite` | Optional, regenerable code evidence for impact, ownership, routes, symbols, imports, and workspace graph questions. |
+| Diagnostics and migration modes | Link checks, quality checks, migration review files, stale-signal reports, and issue drafts. |
 
 The core idea is not "write more docs." It is "keep the first agent read small, then give it reliable routes to deeper project truth and code evidence."
 
-The taxonomy is a routing aid, not a mandate to create every possible document. It is strongest for service and product development. Library, infrastructure, research, or other non-service projects can use only the relevant slices and leave the rest as intentionally unused categories instead of forcing artificial pages.
+## Highlights
 
-## Benchmark Results
+- **Small first read.** Startup hooks inject only `wiki/startup.md` and `wiki/index.md`; agents route to deeper pages on demand.
+- **One setup, four agents.** Codex, Claude Code, Cursor, and Gemini CLI share the same repo-local memory contract.
+- **Structured wiki writing.** New project content is classified before it is written or consolidated, so PRDs, policies, UX, data, APIs, QA, release, and operations notes do not collapse into one catch-all page.
+- **Inspectable wiki graph.** `--wiki-visualize` writes a static HTML graph under `.project-wiki/` without adding to startup context.
+- **Measured claims.** Benchmark wins and losses are published together, with claim boundaries attached.
+- **Local session handoff.** `--handoff-save` stores generated resume notes under `.project-wiki/session/` without turning execution memory into canonical project truth.
+- **Optional code evidence.** A SQLite index plus answer-shaped MCP tools answer expensive traversal questions on large repositories without adding an MCP SDK dependency.
+- **Safe to re-run.** Bootstrap is idempotent and preservation-first.
 
-These numbers are maintainer release evidence, not a blanket promise. Every value is real Codex JSONL usage and local wall-clock time (ChatGPT/Codex auth, `gpt-5.5`), measured hermetically — isolated Codex home, allowlist-only environment, clean tree, post-run fixture validation — with 3 measured runs plus 1 warmup per scenario against an `organic` control that has no Project Librarian.
+## Common Requests
 
-In the tables below, **"less" / "more"** compares cost-weighted tokens against that control, and **"faster" / "slower"** compares wall-clock time. (Cost-weighted = uncached input + 0.1 × cached input + output + reasoning output; cached resends are discounted, and raw merged totals would unfairly penalize any tool that adds a turn.) The wiki-routing track and the code-graph track are measured and reported separately — a win on one never backs a claim about the other. Generated benchmark reports under `benchmarks/reports/llm/` are ignored by default; maintainers should commit deliberate release baselines only when they are meant to support a public claim. Reproduce a release candidate with:
+Ask your agent for the outcome you want; the installed skill maps the request to the local runner.
 
-```bash
-npm run benchmark:release:preview
-npm run benchmark:release -- --allow-codex-run
-```
+| Goal | Ask The Agent |
+| --- | --- |
+| Create or update the wiki | "Use Project Librarian to set up or update this repository's planning wiki." |
+| Update without migration | "Update this repository's Project Librarian setup without migrating the wiki." |
+| Migrate existing docs/wiki content | "Use Project Librarian to migrate the existing docs/wiki content." |
+| Run diagnostics | "Run Project Librarian diagnostics." |
+| Search project memory | "Search the Project Librarian wiki for authentication decisions." |
+| Build code evidence | "Build Project Librarian code evidence for `src`." |
+| Inspect code impact | "Show Project Librarian impact evidence for `healthHandler`." |
+| Save a handoff | "Save a Project Librarian session handoff for the current work." |
 
-Measured release runs stream `[benchmark:progress]` lines to stderr for the scenario count, expected Codex exec total, current exec ordinal, phase, prompt id, exit status, elapsed time, and raw JSONL path. stdout stays reserved for the final JSON result.
+See [Usage](docs/usage.md) for install scopes, runner paths, generated files, migration behavior, and the full agent-request table.
 
-### Wiki track (planning-doc routing)
+## Benchmarks
 
-Cost-weighted tokens, Project Librarian vs control:
+These numbers are maintainer release evidence, not a blanket promise. Every value is real Codex JSONL usage and local wall-clock time, measured hermetically against an `organic` control with no Project Librarian. The wiki-routing track and the code-graph track are measured separately; a win on one never backs a claim about the other.
 
-| Scale | decision_lookup | aggregation | multi_session (2nd session) |
+Wiki track, cost-weighted tokens vs control:
+
+| Scale | decision_lookup | aggregation | multi_session |
 | --- | --- | --- | --- |
 | Small | 14.4% less | 81.0% more | 22.0% less |
 | Medium | 52.0% less | 19.0% less | 54.1% less |
 | Large | 71.1% less | 29.0% less | 71.8% less |
 
-Latest synthetic wiki-track release candidate: 2026-06-19, `gpt-5.5`, 42 scenarios, 3 measured runs plus 1 warmup each. The overall claim gate **passed**: 42/42 scenarios passed correctness, all 42 scenarios were claimable, and every corpus gate met the 3-run minimum. The release claim is still bounded to the synthetic wiki-routing track and the listed task families; it is not a claim about code-graph behavior, real repositories, every agent surface, or every question shape. Published boundaries remain visible: small `aggregation` still costs 81.0% more with the wiki, small `release_policy` costs 9.4% more in the full report, and `aggregation` stays slower at every scale even when token cost drops.
-
-### Code-graph track (code evidence index, real repositories)
+Latest synthetic wiki-routing track release candidate: 2026-06-19, `gpt-5.5`, 42 scenarios, 3 measured runs plus 1 warmup each. The overall claim gate **passed**. This is bounded to the synthetic wiki-routing track and listed task families; it is not a claim about code-graph behavior, real repositories, every agent surface, or every question shape.
 
-Measured on two SHA-pinned open-source repositories with hand-authored answer keys and the answer-shaped MCP tools injected into the hermetic Codex home. The claim gate passed with 30/30 runs correct after two evaluator false positives were fixed and the report was re-scored from raw JSONL; recompute-from-raw is the standing audit policy. Cost-weighted tokens, Project Librarian vs control:
+Code-graph track, cost-weighted tokens vs control:
 
 | Question | excalidraw (~1.2k files) | backstage (~11.8k files) |
 | --- | --- | --- |
 | impact_trace | 117% more | **27.7% less** |
 | workspace_graph | 106% more | 2.6% less |
-| ownership_lookup | — | 99% more |
-
-The claim is a scale crossover, and the losses are published next to the win: on the 11.8k-file repository the tool wins the expensive traversal question (impact_trace 27.7% fewer cost-weighted tokens, 24.5% fewer scan bytes) and breaks even on the workspace graph, but everything loses on the small repository and cheap lookups (CODEOWNERS ownership) lose at every measured scale. In short, the code-evidence index pays off only on genuinely large repositories for expensive-traversal questions — exactly what the CLI's scale-aware gates encode: below ~5k indexable files, `--code-index` asks for explicit acknowledgement and bootstrap skips MCP auto-registration, citing these measurements.
+| ownership_lookup | - | 99% more |
 
-### What the benchmark names mean
+The code-evidence index pays off only on genuinely large repositories for expensive traversal questions. Below ~5k indexable files, `--code-index` halts unless `--acknowledge-small-repo` is passed, and bootstrap skips MCP auto-registration unless an existing `.project-wiki` SQLite index shows the user already opted in.
 
-Repositories under test:
+Before citing `--code-report`, `--code-impact`, `--code-context-pack`, or MCP tool output as current code-structure evidence, run `project-librarian --code-status` or MCP `code_status` and require `stale_files: 0`. Stale reports are pointers for rebuild, not authoritative project truth.
 
-- **excalidraw** — a real open-source whiteboard/diagramming app (~1.2k files); the small-repo data point.
-- **backstage** — Spotify's open-source developer-portal platform (~11.8k files); the large-repo data point.
+See [Benchmark Evidence](docs/benchmarks.md) for methodology, task-family definitions, reproduction commands, and the published losses.
 
-Question types (task families):
+## Documentation
 
-- **decision_lookup** — find the latest project decision and its date from the wiki.
-- **aggregation** — answer a question whose facts are scattered across several pages and must be synthesized.
-- **multi_session** — a second session on the same project, measuring whether the durable wiki helps the next session, not just the first.
-- **impact_trace** — "if this module changes, what else is affected?": trace the full set of direct and indirect importers.
-- **ownership_lookup** — "who owns this file?": resolve the owner by CODEOWNERS last-match precedence.
-- **workspace_graph** — "what does this package depend on across the monorepo?": the workspace/package dependency graph.
+| Document | Use It For |
+| --- | --- |
+| [Usage](docs/usage.md) | Install scopes, runner paths, generated files, migration, and common agent requests. |
+| [Code Evidence](docs/code-evidence.md) | MCP server behavior, freshness contract, scale gate, language support, and native helper policy. |
+| [CLI Reference](docs/cli-reference.md) | Complete command and option reference. |
+| [Benchmark Evidence](docs/benchmarks.md) | Public benchmark claims, limits, and maintainer benchmark commands. |
+| [Maintainer Guide](docs/maintainer.md) | Development, release readiness, trusted publishing, and benchmark operations. |
+| [Contributing](CONTRIBUTING.md) | Local contribution workflow and verification expectations. |
+| [Security Policy](SECURITY.md) | Supported versions, private reporting, and supply-chain boundary. |
 
 ## Install Details
 
-Use this section when you need to choose an install scope or target agent. Use `npx` for initial skill installation or for an explicit registry-version project update:
-
-```bash
-npx project-librarian@latest install --scope user --agents all
-```
-
-Install into the current repository instead:
-
-```bash
-npx project-librarian@latest install --scope project --agents all
-```
-
-`install` copies reusable skill files only. It does not create or update `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `wiki/`, `.cursor/rules/`, `.cursor/hooks.json`, `.gemini/settings.json`, `.codex/hooks.json`, or `.claude/settings.json`. `install-skill` remains supported as a compatibility alias.
-
 | Situation | Command |
 | --- | --- |
 | Install globally for all supported agents | `npx project-librarian@latest install --scope user --agents all` |
@@ -168,294 +152,7 @@ npx project-librarian@latest install --scope project --agents all
 | Install only Gemini CLI | `npx project-librarian@latest install --agents gemini` |
 | Preview install output | `npx project-librarian@latest install --scope project --agents all --dry-run` |
 
-`--agents` also accepts comma-separated values such as `codex,claude,cursor,gemini`. `all` targets every supported agent. `--scope` accepts `user` or `project`.
-
-The project setup/update runner also accepts `--agents`. Fresh setup defaults to all supported agent surfaces only when no project-scoped Project Librarian skill install is present. If the repository already has project-scoped skills such as `.codex/skills/project-librarian/` and `.claude/skills/project-librarian/`, the first setup uses that installed agent set by default. Existing non-migration updates preserve the agent surfaces already present in the repository, so a repo that has only Codex and Claude files will not gain Cursor or Gemini files on a plain update. Use `project-librarian update --agents cursor` or `project-librarian update --agents all` when you intentionally want to add newly supported surfaces; unlisted surfaces are not deleted.
-
-`project-librarian update` also syncs any project-scoped Project Librarian skill installs that already exist for the selected surfaces from the currently running package. This means `npx project-librarian@latest update` can refresh the repository's managed setup, hooks, wiki meta files, and existing project-scoped skill copies without migration. It does not create new project-scoped skill installs by default and does not update user-scoped skill installs; use `install --scope user` for that.
-
-## Runner Paths
-
-These paths are mainly for agents and automation. After installation, agents should run the installed local copy with `node`, not `npx`. This avoids network access and unpinned package execution in restricted agent environments.
-
-| Installation | Runner |
-| --- | --- |
-| Project-scoped Codex skill | `node .codex/skills/project-librarian/dist/init-project-wiki.js` |
-| Project-scoped Claude skill | `node .claude/skills/project-librarian/dist/init-project-wiki.js` |
-| Project-scoped Cursor skill | `node .cursor/skills/project-librarian/dist/init-project-wiki.js` |
-| Project-scoped Gemini skill | `node .gemini/skills/project-librarian/dist/init-project-wiki.js` |
-| User-scoped Codex skill | `node ~/.codex/skills/project-librarian/dist/init-project-wiki.js` |
-| User-scoped Claude skill | `node ~/.claude/skills/project-librarian/dist/init-project-wiki.js` |
-| User-scoped Cursor skill | `node ~/.cursor/skills/project-librarian/dist/init-project-wiki.js` |
-| User-scoped Gemini skill | `node ~/.gemini/skills/project-librarian/dist/init-project-wiki.js` |
-
-## Common Agent Requests
-
-Ask your agent for the outcome you want; the skill maps the request to the local runner internally.
-
-Wiki setup and maintenance:
-
-| Goal | Ask The Agent | Internal Action |
-| --- | --- | --- |
-| Create or update the wiki | "Use Project Librarian to set up or update this repository's planning wiki." | `[init]` |
-| Update existing setup without migration | "Update this repository's Project Librarian setup without migrating the wiki." | `update` |
-| Update from the npm latest package without migration | "Run the latest Project Librarian update for this repository without migrating the wiki." | `npx project-librarian@latest update` |
-| Add a specific agent surface to an existing setup | "Add the Cursor Project Librarian surface without migrating the wiki." | `update --agents cursor` |
-| Migrate existing docs/wiki content | "Use Project Librarian to migrate the existing docs/wiki content." | `--migrate` |
-| Validate generated setup | "Run Project Librarian validation." | `--lint` |
-| Check links and document quality | "Run Project Librarian diagnostics." | `--doctor` |
-| Refresh generated routing before diagnostics | "Refresh Project Librarian routing and then run diagnostics." | `--doctor --fix` |
-| Search project wiki content | "Search the Project Librarian wiki for authentication decisions." | `--query "authentication decisions"` |
-| Show backlinks and decision citations for a page | "Show Project Librarian wiki impact for decisions/release-policy." | `--wiki-impact "decisions/release-policy"` |
-| Generate a wiki graph visualizer | "Generate the Project Librarian wiki graph visualizer." | `--wiki-visualize` |
-| Capture a candidate note | "Capture this as a Project Librarian candidate note: <details>." | `--capture-inbox --title "Candidate" --content "Details"` |
-| Save a session handoff | "Save a Project Librarian session handoff for the current work." | `--handoff-save --goal "..." --state "..." --next "..."` |
-| Resume from a handoff | "Show the last Project Librarian session handoff." | `--handoff-show` |
-| Promote handoff candidates | "Promote the last Project Librarian handoff to the wiki inbox." | `--handoff-promote-inbox` |
-| Opt in to full handoff injection | "Enable the Project Librarian full handoff injection experiment." | `--handoff-injection-enable` |
-| Report stale or unresolved wiki pages | "Check Project Librarian for stale or unresolved pages." | `--prune-check` |
-| Report only higher-signal stale or unresolved wiki pages | "Check Project Librarian for strict stale or unresolved pages." | `--prune-check --prune-check-strict` |
-| Install hook files without changing git config | "Set up Project Librarian hook files without changing git config." | `--no-git-config` |
-
-Code evidence:
-
-| Goal | Ask The Agent | Internal Action |
-| --- | --- | --- |
-| Build the default evidence cache | "Build Project Librarian code evidence for `src`." | `--code-index --code-scope src` |
-| Build multiple scopes | "Build Project Librarian code evidence for `src` and `packages/api`." | `--code-index --code-scope src --code-scope packages/api` |
-| Require incremental update | "Update the Project Librarian code evidence index incrementally." | `--code-index --incremental` |
-| Force a full rebuild | "Fully rebuild the Project Librarian code evidence index." | `--code-index --code-index-full` |
-| Use optional Tree-sitter backend | "Build Project Librarian code evidence with the Tree-sitter parser." | `--code-index --code-parser tree-sitter` |
-| Inspect cache compatibility | "Inspect Project Librarian code evidence cache health." | `--code-index-health` |
-| Show cache status | "Show Project Librarian code evidence status." | `--code-status` |
-| List indexed files | "List files in the Project Librarian code evidence index." | `--code-files` |
-| Print architecture and ownership report | "Show the Project Librarian code report." | `--code-report` |
-| Print one report section | "Show the routes section of the Project Librarian code report." | `--code-report --code-report-section routes` |
-| Inspect impact evidence | "Show Project Librarian impact evidence for `healthHandler`." | `--code-impact healthHandler` |
-| Build a context pack | "Build a Project Librarian context pack for `healthHandler`." | `--code-context-pack healthHandler` |
-| Search indexed symbols | "Search Project Librarian code evidence for symbol `Auth`." | `--code-search-symbol Auth` |
-| Run conservative read-only SQL | "Run a read-only Project Librarian code evidence query for file paths." | `--code-query "select path from files order by path"` |
-
-Only one code evidence mode can run at a time. `--incremental`, `--code-index-full`, and `--code-parser` are valid only with `--code-index`.
-
-## What Gets Installed
-
-Fresh setup installs the supported agent surfaces below unless you pass `--agents` or the repository already has project-scoped Project Librarian skills for a narrower agent set. Existing non-migration updates preserve the detected surface set by default and update only those selected surfaces plus the common wiki/git-hook files.
-
-Project instruction files:
-
-- `AGENTS.md`
-- `CLAUDE.md`
-- `GEMINI.md`
-- `wiki/AGENTS.md`
-- `.cursor/rules/project-librarian.mdc`
-
-Startup hooks:
-
-- `.codex/hooks.json`
-- `.codex/hooks/wiki-session-start.js`
-- `.claude/settings.json`
-- `.claude/hooks/wiki-session-start.js`
-- `.cursor/hooks.json`
-- `.cursor/hooks/wiki-session-start.js`
-- `.gemini/settings.json`
-- `.gemini/hooks/wiki-session-start.js`
-
-Git hook files:
-
-- `.githooks/prepare-commit-msg`
-- `.githooks/wiki-commit-trailers.js`
-
-Wiki directories:
-
-- `wiki/canonical/`
-- `wiki/roadmaps/`
-- `wiki/plans/`
-- `wiki/decisions/`
-- `wiki/inbox/`
-- `wiki/meta/`
-- `wiki/sources/`
-- `wiki/migration/`
-
-Seed wiki pages and routers:
-
-- `wiki/startup.md`
-- `wiki/index.md`
-- `wiki/meta/document-taxonomy.md`
-
-Empty project pages such as `canonical/project-brief.md`, `canonical/open-questions.md`, `canonical/assumptions.md`, `canonical/risks.md`, and ADR templates are not created until there is real content to store. The router can discover them later with `--refresh-index`. During migration, form-only legacy templates are recorded as skipped in `wiki/migration/inventory.md` instead of becoming review rows or new wiki pages.
-
-MCP server registration (preservation-first merge into `mcpServers`):
-
-- `.mcp.json` (Claude Code)
-- `.cursor/mcp.json` (Cursor)
-- `.gemini/settings.json` `mcpServers` (Gemini CLI)
-
-Disposable code evidence cache:
-
-- `.project-wiki/code-evidence.sqlite`
-
-## Code Evidence MCP Server
-
-`project-librarian mcp` runs a hand-rolled stdio MCP server (JSON-RPC 2.0 over newline-delimited JSON, no extra runtime dependencies) that serves the existing `.project-wiki` code-evidence index read-only. It exposes answer-shaped tools — `code_context_pack`, `code_impact`, `code_ownership` (CODEOWNERS last-match precedence), `code_workspace_graph`, `code_search`, and `code_status` — whose responses lead with a one-line answer, follow with compact path/symbol/signature evidence, cap each reply, and prepend a warning when `code_status` reports the index is stale.
-
-The server also exposes fixed resources — `project-librarian://wiki/startup`, `project-librarian://wiki/index`, and `project-librarian://code/status` — plus prompt templates for wiki taxonomy updates, code impact traces, maintenance improvement reviews, and retrieval quality reviews. Resource reads come from a fixed URI registry rather than arbitrary filesystem paths.
-
-Bootstrap registers the server for Claude Code (`.mcp.json`), Cursor (`.cursor/mcp.json`), and Gemini CLI (`mcpServers` in `.gemini/settings.json`), preserving any existing servers and keys and reporting `exists` on a re-run. When the repository contains a local runner the registration uses `node <runner> mcp`; otherwise it uses the installed `project-librarian mcp` binary.
-
-Codex registers MCP servers at the user level only (`codex mcp add`), so bootstrap does not write a project-level Codex MCP config. To use the server with Codex, run it once per machine:
-
-```bash
-codex mcp add project-librarian -- node .codex/skills/project-librarian/dist/init-project-wiki.js mcp
-```
-
-## How It Works
-
-1. Bootstrap creates a preservation-first wiki structure and marker-bounded agent instruction sections.
-2. Session-start hooks inject only `wiki/startup.md` and `wiki/index.md`, with character budgets.
-3. Bootstrap avoids empty form-only project pages; focused canonical, decision, source, and meta pages are created when content actually exists.
-4. Detailed planning truth stays in canonical, decision, source, and meta pages that agents read on demand.
-5. New project-planning content is classified through `wiki/meta/document-taxonomy.md` before it is written or consolidated, keeping upstream/downstream document relationships visible.
-6. `--refresh-index` routes newly discovered wiki pages; large route sets are split into `wiki/indexes/auto-*.md` scoped routers.
-7. `--code-index` creates a disposable SQLite evidence cache under `.project-wiki/`.
-8. `--code-report`, `--code-impact`, `--code-context-pack`, `--code-search-symbol`, and `--code-query` expose code-backed evidence for planning updates.
-9. Read-only wiki consumers share a concept read model that derives user-facing page types from paths and frontmatter without rewriting the canonical wiki schema.
-10. Wiki producers keep writing the canonical markdown/YAML schema, while read-only consumers such as diagnostics, MCP, and the visualizer use derived projections instead of mutating source documents.
-11. `--wiki-visualize` writes a static graph artifact to `.project-wiki/`, reusing the wiki graph and concept read model instead of introducing a database or server.
-12. Diagnostics report broken links, duplicate routes, orphan pages, stale pages, missing TL;DRs, evidence gaps, and migration policy violations.
-
-Migration is intentionally review-first. `--migrate` preserves an existing `wiki/` as `wiki_legacy*`, skips form-only/template legacy files, splits mixed legacy pages into meaning units, classifies each unit through the document taxonomy, and writes review files under `wiki/migration/`:
-
-- `inventory.md` records migratable legacy markdown files, file-level classification, and form-only/template files skipped from semantic migration.
-- `unit-map.md` records each heading, paragraph, list item, table row, and code block with its suggested taxonomy area and target page.
-- `split-plan.md` groups those units by suggested new wiki target, so one legacy page that mixes API specs, features, UX, QA, policy, or operations can be rewritten into separate files.
-- `coverage.md` is the editable status ledger for each unit: pending, adopted, merged, superseded, rejected, resolved, or needs-human-review.
-- `verification.md` and `review.md` summarize coverage and semantic completion after `--review-migration`.
-
-`--migration-lint` validates that `coverage.md`, `unit-map.md`, and `split-plan.md` still account for the current migration batch, including duplicate/stale unit IDs, invalid storage/confidence/status values, split count drift, target drift, and old coverage-table schemas. When a legacy page has units that point to multiple targets, `--review-migration` will not let a file-level inbox status complete every unit; unit-level coverage must be resolved instead.
-
-Retained or copied legacy content is acceptable when it fits the new wiki policy and structure; the new wiki must not depend on citing `wiki_legacy*`.
-
-## Language Support Matrix
-
-The matrix lists languages with implemented symbol/import extraction. Other recognized extensions are inventory-only. Default mode uses `typescript-ast`, `python-light`, `go-light`, config extraction, and inventory rows. `--code-parser tree-sitter` switches supported source files to `tree-sitter-*` profiles.
-
-| Language | Extensions | Default extraction | Tree-sitter extraction | Indexed evidence |
-| --- | --- | --- | --- | --- |
-| TypeScript | `.ts`, `.tsx`, `.cts`, `.mts` | `typescript-ast` | `tree-sitter-typescript`, `tree-sitter-tsx` | functions, classes, methods, variables, interfaces, types, enums, imports, exports, calls, common HTTP routes |
-| JavaScript | `.js`, `.jsx`, `.cjs`, `.mjs` | `typescript-ast` | `tree-sitter-javascript` | functions, classes, methods, variables, imports, exports, `require()` calls, calls, common HTTP routes |
-| Python | `.py` | `python-light` | `tree-sitter-python` | functions, classes, `import`, `from ... import` |
-| Go | `.go` | `go-light` | `tree-sitter-go` | functions, methods, types, consts, vars, single imports, import blocks |
-| Rust | `.rs` | inventory-only | `tree-sitter-rust` | functions, structs, enums, traits, impls, `use` imports |
-| Java | `.java` | inventory-only | `tree-sitter-java` | classes, interfaces, enums, methods, imports |
-| PHP | `.php` | inventory-only | `tree-sitter-php` | functions, classes, interfaces, traits, methods, namespace uses |
-| Kotlin | `.kt`, `.kts` | inventory-only | `tree-sitter-kotlin` | functions, classes, objects, imports |
-| Swift | `.swift` | inventory-only | `tree-sitter-swift` | functions, classes, structs, protocols, enums, imports |
-| C | `.c`, `.h` | inventory-only | `tree-sitter-c` | functions, structs, enums, includes |
-| C++ | `.cc`, `.cpp`, `.cxx`, `.hpp`, `.hh`, `.hxx` | inventory-only | `tree-sitter-cpp` | functions, classes/structs, namespaces, enums, includes/usings |
-| C# | `.cs` | inventory-only | `tree-sitter-csharp` | classes, interfaces, structs, enums, methods, usings |
-
-Recognized but inventory-only extensions include `.rb`, `.vue`, and `.css`. Config files (`.json`, `.yaml`, `.yml`, `.toml`, `.env.example`, `package.json`, `tsconfig.json`, `Dockerfile`, and `Makefile`) are indexed as configuration or inventory evidence.
-
-## CLI Reference
-
-Use the resolved local runner for automation or direct CLI execution:
-
-```bash
-node .codex/skills/project-librarian/dist/init-project-wiki.js [init|update] [options]
-node .codex/skills/project-librarian/dist/init-project-wiki.js install [--scope user|project] [--agents codex|claude|cursor|gemini|all]
-```
-
-`install-skill` remains a compatibility alias for `install`.
-
-`update` is the explicit existing-project update command. It rejects `--migrate` and `--adopt-existing`; use top-level `--migrate` when legacy docs or wiki content should be preserved into `wiki_legacy*` and reviewed. When project-scoped Project Librarian skill installs already exist for the selected agent surfaces, `update` copies the current package's reusable skill files into those project skill directories before refreshing the managed setup.
-
-Important options:
-
-| Option | Purpose |
-| --- | --- |
-| `--migrate`, `--adopt-existing` | Preserve an existing wiki as `wiki_legacy*`, create migration inboxes, and generate unit-map/split-plan/coverage review files. |
-| `--lint` | Validate generated setup without editing files. |
-| `--link-check` | Report broken wiki links, duplicate routes, orphan pages, and pages the startup router cannot reach within the depth budget. |
-| `--quality-check` | Report stale, conflicting, and low-quality wiki document signals. |
-| `--doctor` | Run lint, link-check, and quality-check together. |
-| `--doctor --fix` | Safely refresh generated index routing before diagnostics. |
-| `--migration-lint` | Validate migration coverage, unit-map, split-plan, and review scaffolding separately from normal lint. |
-| `--migration-quality-check` | Report migration policy/structure signals separately from normal quality-check. |
-| `--migration-doctor` | Run migration-lint and migration-quality-check together. |
-| `--query <terms>` | Search wiki paths, metadata, titles, and bodies; answer-first output with per-page TL;DR lines under a hard size cap. |
-| `--wiki-impact <page-or-term>` | Show wiki backlinks, `decision_ref` citations, outgoing links, and router depth for matching pages. |
-| `--wiki-visualize` | Write a self-contained static wiki graph visualizer to `.project-wiki/wiki-graph.html`. |
-| `--wiki-visualize-out <path>` | With `--wiki-visualize`, write to a custom repository-relative path under `.project-wiki/`. |
-| `--refresh-index` | Update generated auto-discovered wiki routing. |
-| `--capture-inbox --title <title> --content <content>` | Append a candidate note to the wiki inbox. |
-| `--handoff-save --goal <goal> --state <state> --next <action>` | Save generated local session handoff state under `.project-wiki/session/`. Repeat `--next`, `--decision`, `--blocked`, `--open-question`, and `--verification` as needed. |
-| `--handoff-show`, `--handoff-status`, `--handoff-clear` | Print, inspect, or remove generated session handoff state. Startup hooks mention the handoff when it exists but do not inject the full file by default. |
-| `--handoff-promote-inbox` | Append selected generated handoff facts to `wiki/inbox/project-candidates.md` as a pending candidate. It does not write canonical, plan, or decision pages. |
-| `--handoff-injection-enable`, `--handoff-injection-disable`, `--handoff-injection-status` | Opt in, opt out, or inspect the capped full handoff injection experiment. Default startup behavior remains pointer-only. |
-| `--issue-draft --issue-title <title>` | Print a read-only GitHub issue body draft for problems or side effects. |
-| `--issue-create --issue-title <title>` | Create a GitHub issue through `gh` after explicit user approval. |
-| `--glossary-init` | Create and route the optional glossary page. |
-| `--prune-check` | Report active pages with stale or unresolved lifecycle signals. |
-| `--prune-check --prune-check-strict` | Omit pages selected only because their `updated` date is older than today. |
-| `--review-migration`, `--semantic-migrate` | Sync migration coverage and inbox statuses into migration review files. |
-| `--no-git-config` | Install hook files without changing `git core.hooksPath`. |
-| `--code-index` | Build the disposable code evidence index. |
-| `--code-index-health` | Inspect code evidence cache compatibility and print rebuild guidance without writing. |
-| `--code-report` | Print architecture and ownership summaries from the evidence index. |
-| `--code-report-section <section>` | Print one section: `coverage`, `ownership`, `languages`, `parsers`, `workspaces`, `workspace-graph`, `routes`, `hotspots`, `configs`, or `edges`. |
-| `--code-impact <term>` | Show file, symbol, route, import, edge, and owner impact evidence. |
-| `--code-context-pack <term>` | Print a budgeted first-pass context pack with structural file, symbol, route, import, edge, and ownership evidence. |
-| `--code-search-symbol <term>` | Search indexed symbols. |
-| `--code-query <sql>` | Run conservative read-only SQL over the evidence index. |
-
-## Development
-
-The source is TypeScript. The committed `dist/` directory is the compiled JavaScript used by the npm binary and installed skill copies.
-
-```bash
-npm install
-npm run typecheck
-npm run build
-npm run check:dist
-npm test
-npm run test:coverage
-npm run benchmark:llm:raw-audit
-npm run benchmark:llm:delta-analysis
-npm run benchmark:claim-ledger
-npm run release:check
-npm pack --dry-run
-```
-
-When editing TypeScript under `src/`, rebuild before committing so `dist/` stays current. `npm run check:dist` verifies that the checked-in generated files still match the latest build output.
-
-`npm run test:coverage` uses Node's native test coverage with conservative line, branch, and function thresholds so coverage is a regression gate, not only a report.
-
-`npm run release:check` is a local-only maintainer gate: it runs tests, native Node coverage, benchmark parser smoke, the real-corpus offline demo, benchmark release preview, benchmark claim-ledger classification, raw hygiene audit, package dry-run inspection, dist executable/parity checks, and README benchmark-claim boundary checks. It never publishes, never deletes raw benchmark artifacts, and never launches a measured Codex benchmark.
-
-Treat a green `release:check` as a reproducible release-readiness bundle, not a runtime guarantee: it proves those local gates on the current checkout, including that the package dry run stays inside the expected publish boundary (`agents/`, `dist/`, `LICENSE`, `README.md`, `README.ko.md`, and `SKILL.md`) and excludes source files, tests, repo-local wiki/workflow state, raw benchmark output, and local caches.
-
-Publishing is handled by `.github/workflows/publish.yml` after a GitHub Release is published. The workflow targets the protected `npm-publish` GitHub Environment, uses npm trusted publishing through GitHub OIDC (`id-token: write`) and `npm publish --access public`, and generates npm provenance automatically; it must not use `NODE_AUTH_TOKEN` or npm token secrets, and release-critical first-party GitHub Actions are pinned to full commit SHAs. `release:check` verifies this workflow contract locally.
-
-Trusted publishing and npm provenance prove the package was published through that GitHub OIDC workflow. They do not prove benchmark correctness, code-evidence freshness in an end-user repository, or a security audit; those remain separate evidence tracks.
-
-Maintainer benchmark commands live in [benchmarks/README.md](benchmarks/README.md). They are for release evidence and public claim validation, not normal end-user setup.
-
-For code-evidence runtime/storage checks, `npm run perf:code-efficiency` generates 3k/10k/50k fixtures and writes `benchmarks/reports/code-performance-efficiency/current.json` plus `.md`. Command timings include CLI startup and freshness checks; the `query_groups` section reports direct DB timings for representative file/symbol/route/import/edge queries. The report also measures checked-in `mixed-monorepo`, `web-service`, `python-cli`, and `docs-heavy` corpora separately from synthetic scale fixtures.
-
-Measured LLM benchmark runs automatically prune stale prior raw run directories and isolated Codex homes older than 1 day, then prune the current run's homes even on claimable-run failure; raw JSONL, stderr, reports, and manifests remain for runs inside the retention window. Old ignored raw output can still be audited with the dry-run-first helper before deleting retained isolated Codex homes:
-
-```bash
-npm run benchmark:llm:raw-audit -- --older-than-days 14
-npm run benchmark:llm:prune-raw -- --older-than-days 14
-npm run benchmark:llm:prune-raw -- --older-than-days 14 --execute
-```
-
-`npm run benchmark:llm:delta-analysis` reads the checked-in measured LLM report and ranks cost-weighted regressions without launching Codex. Add `-- --include-traces` to include representative raw JSONL command traces and classify broad-search/router-read drivers. It is the first diagnostic stop for weak cells such as small-scale aggregation before adding new benchmark claims.
-
-Measured LLM runs default to `--scenario-order run-major-balanced`: each measured run index executes all selected scenarios, reversing the order on alternating repetitions so with/without pairs are not grouped by condition across repeated runs. Use `--scenario-order scenario-major` only when reproducing older scenario-grouped diagnostics.
-
-`npm run typecheck:ts7` is an opt-in TypeScript 7 RC compatibility probe. It uses `npx` and is intentionally outside `test`, `release:check`, and CI gates until the compiler API and this project's TypeScript extractor have a measured parity record.
+`--agents` also accepts comma-separated values such as `codex,claude,cursor,gemini`. `all` targets every supported agent. `--scope` accepts `user` or `project`. Direct CLI and automation details are in [CLI Reference](docs/cli-reference.md).
 
 ## Inspiration
 

package/dist/args.js

@@ -1,7 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.codeIndexMode = exports.acknowledgeSmallRepoMode = exports.noGitConfigMode = exports.reviewMigrationMode = exports.pruneCheckStrictMode = exports.pruneCheckMode = exports.captureInboxMode = exports.refreshIndexMode = exports.issueDraftMode = exports.issueCreateMode = exports.handoffVerification = exports.handoffStatusMode = exports.handoffState = exports.handoffShowMode = exports.handoffSaveMode = exports.handoffPromoteInboxMode = exports.handoffInjectionStatusMode = exports.handoffInjectionEnableMode = exports.handoffInjectionDisableMode = exports.handoffOpenQuestions = exports.handoffNextActions = exports.handoffLastSuccessCommand = exports.handoffLastFailureCommand = exports.handoffInputMode = exports.handoffGoal = exports.handoffDecisions = exports.handoffClearMode = exports.handoffBlocked = exports.glossaryMode = exports.fixMode = exports.doctorMode = exports.qualityCheckMode = exports.linkCheckMode = exports.migrationQualityCheckMode = exports.migrationLintMode = exports.migrationDoctorMode = exports.lintMode = exports.migrateMode = exports.invalidAgentTargets = exports.missingValueOptions = exports.unexpectedValueOptions = exports.unknownOptions = exports.args = exports.commandArgs = exports.command = exports.unknownCommand = exports.helpMode = exports.agentTargets = exports.parsedArgs = exports.rawArgs = void 0;
-exports.issueDraftTitle = exports.issueBodyFile = exports.captureCategory = exports.captureContent = exports.captureTitle = exports.codeIndexScopes = exports.codeParser = exports.codeIndexOutput = exports.codeSearchSymbol = exports.codeReportSection = exports.codeQuerySql = exports.codeImpactTarget = exports.codeContextPackTarget = exports.wikiVisualizeOutput = exports.wikiVisualizeMode = exports.wikiImpactTarget = exports.wikiImpactMode = exports.queryTerm = exports.codeSearchSymbolMode = exports.codeQueryMode = exports.codeImpactMode = exports.codeParserMode = exports.codeContextPackMode = exports.codeFilesMode = exports.codeStatusMode = exports.codeReportMode = exports.codeIndexHealthMode = exports.codeIndexFullMode = exports.codeIndexIncrementalMode = void 0;
+exports.issueDraftTitle = exports.issueBodyFile = exports.captureCategory = exports.captureContent = exports.captureTitle = exports.codeIndexScopes = exports.codeParser = exports.codeIndexOutput = exports.codeSearchSymbol = exports.codeReportSection = exports.codeQuerySql = exports.codeImpactTarget = exports.codeContextPackTarget = exports.wikiVisualizeOutput = exports.wikiVisualizeMode = exports.wikiImpactTarget = exports.wikiImpactMode = exports.queryTerm = exports.codeSearchSymbolMode = exports.codeQueryMode = exports.codeImpactMode = exports.codeParserMode = exports.codeContextPackMode = exports.codeFilesMode = exports.codeStatusMode = exports.codeReportMode = exports.codeIndexHealthMode = exports.codeIndexFullMode = exports.codeIndexIncrementalMode = exports.codeIndexEngineMode = exports.codeIndexEngine = void 0;
 exports.parseArgs = parseArgs;
 exports.argValue = argValue;
 exports.argValues = argValues;
@@ -18,6 +18,7 @@ const flagDefinitions = [
     { name: "--code-files", value: "none", aliases: ["--code-evidence-files"] },
     { name: "--code-impact", value: "value", aliases: ["--code-evidence-impact"] },
     { name: "--code-index", value: "none", aliases: ["--code-evidence-index"] },
+    { name: "--code-index-engine", value: "value", aliases: ["--code-evidence-index-engine"] },
     { name: "--code-index-full", value: "none", aliases: ["--code-evidence-index-full"] },
     { name: "--code-index-health", value: "none" },
     { name: "--code-index-incremental", value: "none", aliases: ["--incremental", "--code-incremental", "--code-evidence-index-incremental"] },
@@ -179,6 +180,8 @@ function parseArgs(argv) {
         codeFilesMode: hasAnyFlag("--code-files"),
         codeImpactMode: hasAnyFlag("--code-impact"),
         codeImpactTarget,
+        codeIndexEngine: argValueFromAny("--code-index-engine") || "auto",
+        codeIndexEngineMode: hasAnyFlag("--code-index-engine"),
         codeIndexFullMode: hasAnyFlag("--code-index-full"),
         codeIndexHealthMode: args.has("--code-index-health"),
         codeIndexIncrementalMode: hasAnyFlag("--code-index-incremental"),
@@ -302,6 +305,8 @@ exports.reviewMigrationMode = exports.parsedArgs.reviewMigrationMode;
 exports.noGitConfigMode = exports.parsedArgs.noGitConfigMode;
 exports.acknowledgeSmallRepoMode = exports.parsedArgs.acknowledgeSmallRepoMode;
 exports.codeIndexMode = exports.parsedArgs.codeIndexMode;
+exports.codeIndexEngine = exports.parsedArgs.codeIndexEngine;
+exports.codeIndexEngineMode = exports.parsedArgs.codeIndexEngineMode;
 exports.codeIndexIncrementalMode = exports.parsedArgs.codeIndexIncrementalMode;
 exports.codeIndexFullMode = exports.parsedArgs.codeIndexFullMode;
 exports.codeIndexHealthMode = exports.parsedArgs.codeIndexHealthMode;