@cairnkeep/cli 2.15.4 → 2.17.0

package/README.md

@@ -4,620 +4,115 @@
 [![npm](https://img.shields.io/npm/v/@cairnkeep/cli)](https://www.npmjs.com/package/@cairnkeep/cli)
 [![license](https://img.shields.io/npm/l/@cairnkeep/cli)](LICENSE)
 
-> A durable, harness-agnostic **memory + context layer** for coding agents.
-
-A *cairn* is a stack of stones left as a trail marker for whoever follows; a
-*keep* is where you store what matters. **Cairnkeep** is where coding agents
-stack durable memory — decisions, pitfalls, patterns — and follow the trail
-across sessions, projects, and harnesses (Claude Code, Codex CLI, OpenCode,
-Kimi Code, Qwen Code, Pi, and other MCP clients).
-
-## Five-minute start
-
-For Codex CLI, Cairnkeep can install the complete project-local memory wiring
-in one command:
+> Durable, local-first memory and context for coding agents.
+
+Cairnkeep helps coding agents carry project context across sessions and
+harnesses. It stores decisions, constraints, patterns, and lessons in
+project-scoped memory, then gives agents a bounded protocol for finding and
+verifying that context without turning memory into an authority or an
+autonomous agent runtime.
+
+## Why Cairnkeep?
+
+- **Continuity across sessions.** Recall project decisions and recurring
+  failures instead of rediscovering them from scratch.
+- **Harness independence.** Use the same memory through Claude Code, OpenCode,
+  Codex CLI, Kimi Code, Qwen Code, Pi, or another MCP client.
+- **Local by default.** The default stdio server stores data on your computer;
+  remote access, embeddings, capture, and external context are explicit
+  opt-ins.
+- **Bounded agent guidance.** Managed `AGENTS.md` instructions and project
+  playbooks tell compatible agents when to retrieve context and which checks
+  apply, but never execute work or grant approval.
+- **Least authority.** Complete MCP annotations, read-only/custom tool profiles,
+  capability gates, and immutable context packs keep observation separate from
+  action.
+
+## Quick start
+
+Cairnkeep requires Node.js 22 or newer. In an interactive terminal, guided
+setup presents selectable Git and memory choices plus checkboxes for every
+supported coding harness:
 
 ```bash
 npm install --global @cairnkeep/cli
-cairn setup /path/to/project --git init --harness codex --memory local --yes
+cairn setup /path/to/project
 cd /path/to/project
+cairn doctor
 ./.ai/start-codex.sh                 # Windows: .\.ai\start-codex.cmd
 ```
 
-Review `.codex/config.toml` and accept Codex's project-trust prompt on first
-use. No separate MCP registration or machine-level asset sync is needed. See
-the **[quickstart](docs/quickstart.md)** for existing repositories, Claude Code,
-verification, and the first remember/recall cycle.
-
-## Status
-
-Shipped: the memory server, the `cairn` CLI (`setup`, `bootstrap`, `memory-server`, `sync`, `sync-pi`, `sync-kimi`,
-`doctor`, `playbook`, `trajectory`, `artifact`, `evidence`, `mcp-tools`, `pack`, `notes`, `memory`, `eval`, `audit-timer`, `completion`, `uninstall`) installable via
-`npm i -g @cairnkeep/cli`, and the
-operating layer (commands,
-agents, hooks) installed on Claude Code and OpenCode, plus the native Pi
-trajectory extension and thin Pi/Kimi graph and playbook adapters. The generic launchers
-expose wrapper seams (`.ai/pre-launch.sh`/`.ai/pre-launch.ps1`,
-`CAIRN_EXTRA_SETTINGS`, `.ai/post-exit.sh`/`.ai/post-exit.ps1`) so an enterprise wrapper can add provider/credential setup
-without forking them. Also shipped: context exploration (`/context-explore`) and
-a thin routing seam (`route_check`), both of which delegate to
-[token-miser](https://github.com/cairnkeep/token-miser), a public
-cairnkeep-org sibling project.
-
-Version 2.12 adds a declarative harness registry, first-class Codex project
-setup, and a shorter path from installation to verified recall.
-Version 2.13 adds opt-in local Git-linked work evidence around generated harness
-launchers, including native Windows, without capturing prompts or replacing Git.
-Version 2.15 adds bounded project playbooks that help agents select existing
-recall, planning, verification, review, security, documentation, and learning
-steps without becoming an agent runtime or granting approval.
-Version 2.15.4 makes the generic durable-context retrieval the first tool or
-command for compatible agents, puts bounded playbook signal values inline,
-and supports command- and event-scoped playbook help. Agents still verify
-repository provenance, and instruction presence remains distinct from runtime
-evidence that a tool was called.
-
-## Compatibility
-
-Node.js 22, 24, and 26 are supported. Cairnkeep 2.x requires Node.js 22 or
-newer; Cairnkeep 1.x remains available for older runtimes, although Node.js 18
-and 20 are end-of-life upstream.
-
-| Client or platform | Support level |
-|---|---|
-| Claude Code on Linux/macOS | Memory server plus commands, agents, hooks, and launchers |
-| OpenCode on Linux/macOS | Memory server plus commands, plugins, hooks, and launchers |
-| Kimi Code on Linux/macOS | Memory MCP server, project launcher, and opt-in `/graphify` Skill |
-| Qwen Code on Linux/macOS | Memory MCP server plus project launcher; no Cairnkeep operating-layer assets yet |
-| Pi on Linux/macOS | Memory MCP through a maintained local stdio extension; native opt-in trajectory extension, launcher, and `/graphify` prompt; Pi 0.84.1 minimum for the bridge |
-| Codex CLI on Linux/macOS | Project-scoped memory MCP configuration and launcher; no Cairnkeep-specific commands or hooks |
-| Other MCP clients | Memory plus optional domain-knowledge and context-pack MCP tools |
-| Native Windows x64 | Node-native CLI, guided setup, memory server, bootstrap compatibility, PowerShell/Command Prompt launchers, sync, hooks, doctor, storage lifecycle, Task Scheduler, completion, and uninstall |
-| Windows ARM64 | Supported through Windows x64 emulation only; a native database binding is not currently shipped |
-| WSL | Uses the normal Linux workflow; distinct from native Windows and Git Bash |
-
-The `cairn graph` CLI is harness-independent and can be run from a project
-shell used by Kimi Code, Pi, Qwen Code, Codex, or another client. Claude Code,
-OpenCode, Pi, and Kimi can receive thin `/graphify` adapters; those adapters do
-not imply equivalent hooks, agents, or MCP support.
-
-Linux, macOS, Bash 3.2 portability, native PowerShell on Windows x64, global npm
-installation, and clean Node 22/24/26 runtime checks are exercised in CI. See
-[Native Windows operation](docs/native-windows.md) for platform-specific setup,
-ACL, scheduling, process-tree, and recovery details.
-
-See [Harness compatibility](docs/harness-compatibility.md) for exact support
-levels, trust boundaries, and candidates that are not yet runtime-tested.
-
-## Try with Podman
-
-The minimal OCI image runs the memory server as an unprivileged user and keeps
-all databases in a named volume:
-
-```bash
-podman run --rm -i \
-  --userns=keep-id:uid=10001,gid=10001 \
-  --read-only --cap-drop=all --security-opt=no-new-privileges \
-  --tmpfs=/tmp:rw,noexec,nosuid,size=64m,mode=1777 \
-  --volume cairnkeep-data:/data:Z,U \
-  ghcr.io/cairnkeep/cairnkeep:latest stdio
-```
-
-For persistent authenticated HTTP, rootless Quadlet, isolated workspace mode,
-storage paths, secrets, and private derived images, see
-**[Containers](docs/containers.md)**.
-
-## Components
-
-- **`mcp-memory-server/`** — an MCP server exposing durable, scoped memory
-  (`memory_write`, `memory_search`, …) backed by AgentFS, with optional
-  embedding-ranked search against any OpenAI-compatible endpoint.
-- **`bin/cairn`** — the CLI. `cairn setup [path]` guides or deterministically
-  reconciles selected project assets; `cairn bootstrap [path]` preserves the
-  established scripted scaffold contract; `cairn doctor` health-checks the configured pieces;
-  `cairn trajectory list|show|prune` manages opt-in local session trajectories;
-  `cairn artifact list|show|delete|prune` manages opt-in local artifacts;
-  `cairn mcp-tools list|status|set|reset` applies least-authority discovery
-  profiles; `cairn pack` validates, installs, pins, updates, and approves
-  immutable external context;
-  `cairn eval validate|run|ablate|report|prune|delete` coordinates explicit
-  local two-pass and one-capability-at-a-time measurements;
-  `cairn skill harvest|list|show|review|propose|evaluate|apply|rollback`
-  turns recurring hindsight evidence into reviewed, measured, reversible
-  skill-file improvements;
-  `cairn graph build|query|status|diff|explain|path` owns the local Graphify
-  workflow from any project shell without installing Graphify-owned harness
-  assets; Claude Code, OpenCode, Pi, and Kimi add thin `/graphify` wrappers;
-  `cairn notes distill|search-error|promote|doctor` compiles and searches
-  default-off local hindsight notes outside the online agent path;
-  `cairn memory export|import` relocates the durable store between machines
-  (`export` requires the optional `sqlite3` CLI);
-  `cairn audit-timer` installs the scheduled memory+wiki audit;
-  `cairn completion bash|zsh|fish` generates shell completion definitions; and
-  `cairn sync-pi` installs the native Pi memory and trajectory extensions plus graph prompt;
-  `cairn sync-kimi` installs the Kimi graph Skill;
-  `cairn uninstall` reverses the install (backup-first, revertible).
-- **`templates/`** — project scaffolding (generic launchers, env) plus the
-  derived-knowledge layer (wiki, alignment, graph, security, planning).
-- **`scripts/`** — asset-sync and maintenance utilities.
-
-## Related projects
-
-- **[token-miser](https://github.com/cairnkeep/token-miser)** — a public
-  cairnkeep-org sibling that owns context exploration and request routing;
-  cairnkeep's `context_explore` and `route_check` tools are thin delegates
-  to it.
-
-## Optional companion tools
-
-cairnkeep runs standalone — none of the tools below are required. Its memory
-server, `cairn bootstrap`, and derived-knowledge features work with none of
-them. These are the accelerators the author pairs cairnkeep with; each is opt-in.
+Select Codex CLI in the harness checklist for this route. Review
+`.codex/config.toml` and accept Codex's project-trust prompt on first use.
+Automation can supply every choice explicitly; the quickstart documents that
+deterministic form.
 
-| Tool | What it adds | How it plugs in |
-|------|--------------|-----------------|
-| [lean-ctx](https://github.com/yvgude/lean-ctx) | Compressed reads/searches/shell/dir-maps — large token savings on exploration | Register as an MCP server in your harness |
-| [token-miser](https://github.com/cairnkeep/token-miser) | Model routing (`route_check`) + codebase mapping (`context_explore`) | Already integrated, env-gated: `CAIRN_ROUTE_ENDPOINT` / `CAIRN_EXPLORE_BINARY` |
-| [rtk](https://github.com/rtk-ai/rtk) | "Rust Token Killer": token-reduced proxy for git/npm/cargo output | Shell-level, no wiring needed |
+See the [quickstart](docs/quickstart.md) for Claude Code, the first
+remember/recall cycle, recovery, and setup ownership. See
+[harness compatibility](docs/harness-compatibility.md) for the exact surface
+supported by each client.
 
-## Setup
-
-A working workflow needs three things: the memory server registered, the
-operating layer installed into your harness, and a configured project. `cairn
-setup` is the recommended guided entry point; `cairn bootstrap` remains the
-deterministic compatibility primitive for established scripts. Project setup
-reports but never performs machine-level sync. The full ordered walkthrough is
-in **[the quickstart](docs/quickstart.md)**; the complete operator reference is
-in **[docs/operating.md](docs/operating.md)**.
-
-This setup is local by default: the registered stdio server stores memory on
-the user's computer. Cairnkeep never discovers or selects a remote host.
-Remote HTTP storage requires an explicit server deployment and client URL; see
-**[Memory storage and deployment](docs/storage.md)** before enabling it.
-
-The short version for Claude Code:
-
-```bash
-# 1. Install cairnkeep and register the memory server (server name: cairn-memory)
-npm install -g @cairnkeep/cli
-claude mcp add cairn-memory -s user -- cairn memory-server
-
-# 2. Install the operating layer (commands, agents, hooks, scaffold templates)
-cairn sync --apply                       # add --live-root <proj>/.claude to scope it
-
-# 3. Configure a project deterministically
-cairn setup /path/to/project --git init --harness claude --memory local --yes
-cp /path/to/project/.ai/env.example /path/to/project/.ai/.env   # then edit
-
-# 4. Launch (and, optionally, check the wiring first)
-cd /path/to/project && cairn doctor
-./.ai/start-claude.sh
-```
-
-After setup, the basic workflow is intentionally small:
-
-```text
-> /remember Use transactional migrations for schema changes
-Stored as patterns/transactional-migrations.
-
-> /recall transactional migrations
-patterns/transactional-migrations: Use transactional migrations for schema changes
-```
-
-The exact command rendering depends on the client. Any MCP client can call
+The core loop is intentionally small: store a concise, verified project fact,
+close the session, and retrieve it when a later task needs it. Claude Code and
+OpenCode expose `/remember` and `/recall`; any compatible MCP client can use
 `memory_write` and `memory_search` directly.
 
-Setup also installs a balanced `.ai/playbooks.json` policy and an ownership-safe
-managed block in `AGENTS.md`. The block directs compatible agents to make one
-task-derived, project-scoped memory search for nontrivial work involving prior
-decisions, conventions, constraints, or failures. Results are locators, not
-authority; referenced repository sources must be verified, and memory is never
-promoted automatically. Agents can evaluate the playbook at task boundaries:
+## For coding agents
 
-```bash
-cairn playbook check start --complexity standard --familiarity mixed
-cairn playbook check finish --changed src/example.ts --completed verify.tests --enforce
-```
+Setup installs a managed project instruction block with a deliberately small
+protocol:
 
-The result selects only existing Cairnkeep actions. It never runs them, enables
-a disabled capability, grants approval, or promotes memory automatically. Use
-`cairn playbook status`, `set minimal|balanced|strict`, and `enable|disable` to
-inspect or customize the project policy.
+1. For a nontrivial task that may depend on prior project knowledge, make one
+   task-derived, project-scoped `memory_search` the first tool or command.
+2. Treat results as locators, not truth; verify the maintained repository
+   sources they reference.
+3. Continue with normal repository inspection if memory is unavailable or has
+   no relevant result.
+4. Never write, supersede, or approve durable memory unless the user or a
+   reviewed workflow explicitly requests it.
 
-For Codex CLI, `cairn setup --harness codex --memory local` writes the
-project-scoped `.codex/config.toml` entry and both POSIX and native Windows
-launchers. Review the configuration and trust the project before launching.
-Existing operator-owned `.codex/config.toml` files are never overwritten; a
-reported `skipped` file must be merged by the operator and checked with
-`cairn doctor`.
+Cairnkeep playbooks can recommend or require existing review, verification,
+security, documentation, and learning steps. They do not run those steps,
+activate skills, enable capabilities, or authorize destructive work.
 
-For Kimi Code, bootstrap supplies a launcher and Kimi reads the repository's
-MCP configuration. A local stdio entry uses `cairn memory-server`. Remote Kimi
-configuration requires a literal URL and supports a token reference through
-`bearerTokenEnvVar`; it does not expand `${VAR}` in the URL. See
-[Harness compatibility](docs/harness-compatibility.md#kimi-code).
+Read [Cairnkeep for coding agents](docs/agents.md) for the full contract,
+authority model, harness behavior, and graceful fallback.
 
-Install Kimi's thin graph Skill separately with `cairn sync-kimi --apply`.
-It registers `/graphify` (also `/skill:graphify`) and delegates every supported
-operation exclusively to `cairn graph`.
+## Trust boundary
 
-For Qwen Code, use project `.qwen/settings.json`: local stdio launches
-`cairn memory-server`, while remote HTTP uses `httpUrl` and environment-expanded
-headers. Review and approve project MCP configuration with
-`qwen mcp approve cairn-memory`, then launch with `./.ai/start-qwen.sh`. See
-[Harness compatibility](docs/harness-compatibility.md#qwen-code).
+Cairnkeep is not a hosted agent, telemetry service, or automatic remote
+knowledge collector. Memory is durable context, not source-of-truth
+documentation. Configured Claude Code and OpenCode hooks can derive local
+memory candidates; durable promotion and every networked or sensitive capture
+path remain separately controlled. Ordinary uninstall retains durable data
+unless an explicit purge is requested.
 
-For Pi, select Pi during project setup, explicitly install/check its machine
-assets, run doctor, and use the generated launcher:
+Start with [Privacy and data flow](docs/privacy-and-data-flow.md) and
+[Memory storage and deployment](docs/storage.md) before enabling remote HTTP,
+embeddings, trajectories, artifacts, work evidence, or context packs.
 
-```bash
-cairn sync-pi --apply
-cairn sync-pi --check
-cairn setup /path/to/project --git init --harness pi --memory local --yes
-cd /path/to/project && cairn doctor && ./.ai/start-pi.sh
-```
-
-This installs the maintained local stdio memory extension, trajectory capture,
-and the thin `/graphify` prompt. The memory extension discovers the effective
-server tool catalog and preserves annotations in trusted result details; Pi's
-public API has no native annotations field. It adds tools only—no prompt runs,
-skill activation, autonomous loop, or remote access. Pi 0.84.1 is the minimum
-validated version; v2.11 also passed the registry-current Pi release and the
-documented Node, Bash, and native Windows matrix.
-
-Preview removal before confirming it. Uninstall backs up every managed file it
-will change and prints the generated revert command; durable memory and context
-packs remain unless their explicit purge flags are supplied:
-
-```bash
-cairn uninstall --dry-run /path/to/project
-cairn uninstall --yes /path/to/project
-```
+## Documentation
 
-If setup-owned project assets drift, rerun the exact `cairn setup ... --yes`
-recovery command reported by `cairn doctor`. For Pi machine-asset drift, run
-`cairn sync-pi --apply`, then `cairn sync-pi --check` and `cairn doctor`.
+The [documentation hub](docs/README.md) is the index for setup, agents,
+operations, optional features, deployment, learning paths, and contributor
+guides. In particular:
 
-Closed trajectories can be compiled into local hindsight notes without a model
-or embedding service. Capture and distillation are separate opt-ins:
-
-```bash
-export CAIRN_TRAJECTORY_CAPTURE=1     # affects future closed sessions
-export CAIRN_NOTE_DISTILLATION=1
-cairn notes distill --project /path/to/project --json
-printf '%s\n' 'TypeError: example' | cairn notes search-error --project /path/to/project --json
-```
-
-Notes keep deterministic failure, resolution, abandonment, and recurrence
-history under `~/.cairnkeep/notes/`. Shared promotion is never automatic: it
-requires compatible evidence from two distinct projects and an explicit
-`cairn notes promote NOTE-ID --with NOTE-ID --confirm`. See the
-[operating guide](docs/operating.md#hindsight-notes-opt-in) before enabling
-optional model enrichment.
-
-Prefer working from a clone? Build the server with `cd mcp-memory-server && npm
-install && npm run build`, then use `scripts/sync-claude-assets.sh` and
-`bin/cairn` in place of the installed `cairn`.
-
-Step 2 is easy to miss and load-bearing: without it the memory server is
-registered but none of the `/remember`, `/recall`, `/wiki-*`, `/security-audit`,
-or `/repo-review` commands (and no memory hooks) exist. OpenCode uses the
-`sync-opencode-*.sh` scripts instead — see the operating guide.
-
-The launchers load `.ai/.env` and start the harness in the repo root. They stay
-deliberately minimal — provider/profile specifics belong in your own wrapper,
-which plugs in through the launcher seams below.
-
-**Wrapper seams.** The generic launchers are no-ops beyond loading `.ai/.env`
-unless a wrapper opts in:
-
-- **`.ai/pre-launch.sh`** — sourced after `.env`, before the harness starts. May
-  export env (e.g. a provider base URL) or abort the launch by returning
-  non-zero. This is where credential refresh / connectivity setup lives.
-- **`CAIRN_EXTRA_SETTINGS`** — path to a settings file layered onto the harness
-  (`--settings` for Claude Code, `OPENCODE_CONFIG` for OpenCode). Kimi, Qwen,
-  and Pi do not interpret this variable in their generic launchers.
-  Process env still wins, so an inline value beats the profile.
-- **`.ai/post-exit.sh`** — sourced after the harness exits, with
-  `CAIRN_EXIT_STATUS` set to its exit code.
-
-**Contributor mode.** Working on a repo you don't own? `cairn bootstrap
---untracked /path/to/project` additionally writes the scaffolded paths
-(`.ai/`, `.planning/`, `.agentfs/`) into the repo's `.git/info/exclude`, so the workflow
-files stay purely local: nothing to commit or push, invisible to every other
-contributor, and no edit to the shared `.gitignore`. The trade-off is that
-untracked planning state lives only on that clone — deleting the clone
-deletes it. To move the durable memory itself between machines, use
-`cairn memory export` / `cairn memory import`.
-
-## Configuration
-
-The memory server and collaboration commands are configured entirely through
-`.ai/.env` (any OpenAI-compatible API for extraction and embedding-ranked
-search):
-
-| Variable | Purpose |
-|---|---|
-| `CAIRN_LLM_API_KEY` | API key for the extraction / embeddings endpoint |
-| `CAIRN_LLM_API_URL` | Base URL of the OpenAI-compatible endpoint |
-| `CAIRN_LLM_EXTRACTION_MODEL` | Chat model used for memory extraction |
-| `CAIRN_MEMORY_EMBEDDING_URL` | Embeddings endpoint (falls back to `CAIRN_LLM_API_URL`) |
-| `CAIRN_MEMORY_EMBEDDING_MODEL` | Embedding model name (required for semantic search) |
-| `CAIRN_MEMORY_EMBEDDING_TIMEOUT_MS` | Embedding request timeout before substring fallback (default `15000`) |
-| `CAIRN_AGENTFS_BASE_DIR` | Base dir for global memory scopes (default `~/.cairnkeep`) |
-| `CAIRN_MCP_TOOL_PROFILE` | Process override for MCP exposure: `full`, `read-only`, or `custom` |
-| `CAIRN_MCP_ALLOWED_TOOLS` | Comma-separated exact allowlist required by a custom process profile |
-| `CAIRN_CONTEXT_PACKS` | Opt in to local context-pack list/search/read/related tools (default off) |
-| `CAIRN_CONTEXT_PACK_HTTP` | Separately consent to context-pack tools over authenticated HTTP (default off) |
-| `CAIRN_PACK_BASE_DIR` | Immutable pack objects, source records, pointers, and retrieval cache (default `~/.cairnkeep/packs`) |
-| `CAIRN_PLAYBOOK_PROFILE` | Process-only playbook profile override: `minimal`, `balanced`, or `strict` (project default: `balanced`) |
-| `CAIRN_PLAYBOOK_ACTOR` | Optional local receipt label; caller-supplied and unauthenticated in v2.15 |
-| `CAIRN_PLAYBOOK_ACTOR_KIND` | Optional local actor kind: `user`, `agent`, or `service` |
-| `CAIRN_PLAYBOOK_SESSION` | Optional bounded session label used by playbook decisions and receipts |
-| `CAIRN_TRAJECTORY_CAPTURE` | Opt in to local structured session capture (`1`, `true`, `yes`, or `on`; default off) |
-| `CAIRN_TRAJECTORY_SESSION_MAX_BYTES` | Maximum serialized bytes per captured session (default `5242880`, 5 MiB) |
-| `CAIRN_TRAJECTORY_STORE_MAX_BYTES` | Maximum logical bytes across local trajectories (default `268435456`, 256 MiB) |
-| `CAIRN_TRAJECTORY_RETENTION_DAYS` | Retain captured sessions for this many days (default `30`) |
-| `CAIRN_TRAJECTORY_REDACTION_FILE` | Optional project-contained redaction config (default `.ai/trajectory-redaction.json` when present) |
-| `CAIRN_REDACTION_FILE` | Optional project-contained redaction config shared by trajectories and artifacts (falls back to `CAIRN_TRAJECTORY_REDACTION_FILE`) |
-| `CAIRN_WORK_EVIDENCE` | Capture bounded Git state around generated harness launches (off by default) |
-| `CAIRN_WORK_EVIDENCE_PATCH` | Request an optional redacted patch artifact (off by default; also requires `CAIRN_ARTIFACT_STORE`) |
-| `CAIRN_WORK_EVIDENCE_RETENTION_DAYS` | Work-evidence retention (default `30`; `0` disables age pruning) |
-| `CAIRN_WORK_EVIDENCE_STORE_MAX_BYTES` | Project-local work-evidence metadata budget (default `67108864`, 64 MiB) |
-| `CAIRN_WORK_EVIDENCE_MAX_TOUCHED_PATHS` | Maximum touched-path labels per record (default and hard maximum `4096`) |
-| `CAIRN_WORK_EVIDENCE_PATCH_MAX_BYTES` | Maximum optional patch bytes (default `1048576`, 1 MiB; the artifact cap can lower it) |
-| `CAIRN_COMPACTION_CAPTURE` | Opt in to local harness-produced compaction capture and fresh-session recovery (off by default) |
-| `CAIRN_ARTIFACT_STORE` | Expose four local stdio artifact tools (off by default; independent of compaction capture) |
-| `CAIRN_ARTIFACT_HTTP` | Separately consent to artifact tools over authenticated HTTP (off by default; also requires `CAIRN_ARTIFACT_STORE`) |
-| `CAIRN_ARTIFACT_MAX_BYTES` | Maximum stored bytes per artifact (default `1048576`, 1 MiB) |
-| `CAIRN_ARTIFACT_SESSION_MAX_BYTES` | Maximum logical bytes per artifact session (default `16777216`, 16 MiB) |
-| `CAIRN_ARTIFACT_STORE_MAX_BYTES` | Maximum logical bytes in one artifact store (default `268435456`, 256 MiB) |
-| `CAIRN_ARTIFACT_RETENTION_DAYS` | Artifact age retention (default `30`) |
-| `CAIRN_COMPACTION_MAX_REVISIONS` | Retained compaction revisions per session (default `8`) |
-| `CAIRN_ARTIFACT_GENERATED_FILE_SNAPSHOT_MAX_BYTES` | Generated-file inline snapshot cap (default `262144`, 256 KiB; lower if the artifact cap is lower) |
-| `CAIRN_NOTE_DISTILLATION` | Opt in to one-shot/scheduled local note distillation and lookup (default off) |
-| `CAIRN_NOTE_ENRICHMENT` | Separately opt in to remote/local prose enrichment; never implied by credentials (default off) |
-| `CAIRN_NOTE_ENRICHMENT_MODEL` | Explicit chat model for optional note enrichment (no default) |
-| `CAIRN_NOTE_ENRICHMENT_TIMEOUT_MS` | Optional enrichment timeout (default `15000`) |
-| `CAIRN_TYPED_MEMORY_NODES` | Opt in to typed metadata, filters, logical note address spaces, and `memory_import` (default off; restart the server after changing) |
-| `CAIRN_CAPABILITY_CONTRACT` | Opt in to the managed eight-capability contract (default off) |
-| `CAIRN_CAPABILITY_LOGGING` | Override payload-free local callback logging (`1`/`0`; default off) |
-| `CAIRN_CAPABILITY_MEMORY_WRITE` | Override `memory.write` for this process |
-| `CAIRN_CAPABILITY_MEMORY_SEARCH` | Override `memory.search` for this process |
-| `CAIRN_CAPABILITY_NOTES_DISTILL` | Override `notes.distill` for this process |
-| `CAIRN_CAPABILITY_WIKI` | Override `wiki` for this process |
-| `CAIRN_CAPABILITY_GRAPH` | Override `graph` for this process |
-| `CAIRN_CAPABILITY_SECURITY_AUDIT` | Override `security.audit` for this process |
-| `CAIRN_CAPABILITY_ROUTE_CHECK` | Override `route.check` for this process |
-| `CAIRN_CAPABILITY_CONTEXT_EXPLORE` | Override `context.explore` for this process |
-| `CAIRN_EVAL` | Opt in to the local evaluation coordinator (default off; does not select a harness, model, endpoint, credential, or network) |
-| `CAIRN_GIT_PROVIDER` | Git host for collaboration commands: `github`\|`gitlab`\|`codeberg`\|`forgejo`\|`none` ([docs/git-providers.md](docs/git-providers.md)) |
-| `CAIRN_ROUTE_ENDPOINT` | Base URL of an already-running token-miser routing/tiering proxy (unset → `route_check` is inert) |
-| `CAIRN_GRAPHIFY_BINARY` | Optional Graphify command/path override (default `graphify` from `PATH`; JavaScript helpers run through Node) |
-| `CAIRN_EXPLORE_BINARY` | Absolute path to the `token_miser` binary used by `context_explore` (unset → the tool throws) |
-| `CAIRN_EXPLORE_REPO_ROOT` | Default repo root for `context_explore` when no per-call `repo_root` is given |
-| `CAIRN_EXTRA_SETTINGS` | Optional settings/config file the launcher layers onto the harness (wrapper seam) |
-| `CAIRN_ANYTHINGLLM_SYNC_SCRIPT` | Override path to the domain-knowledge sync script (when the integration lives outside the repo) |
-| `CAIRN_ANYTHINGLLM_PROJECTS_FILE` | Override path to the bundled sync script's project configuration |
-| `CAIRN_ANYTHINGLLM_STATE_FILE` | Override path to the bundled sync script's incremental state |
-
-Without an API key, search degrades gracefully to substring matching.
-There is no Cairnkeep telemetry. Optional extraction, embeddings, document RAG,
-remote memory, and delegated exploration can send content to endpoints you
-configure. Review [Privacy and data flow](docs/privacy-and-data-flow.md) before
-enabling them.
-
-### MCP authority and context packs
-
-Every tool publishes a stable title and all four MCP annotation hints. Use
-`cairn mcp-tools set read-only` for observation-only clients, or an exact custom
-allowlist when a workflow needs fewer tools. Process settings override the
-strict project file; the default remains `full`. Profiles only remove tools and
-cannot bypass capability or feature gates. See
-[MCP tool profiles](docs/mcp-tool-profiles.md).
-
-Context packs are immutable, digest-addressed local document/skill bundles.
-They are installed and project-pinned manually; no background Git sync occurs.
-With `CAIRN_CONTEXT_PACKS=1`, enabled documents are searchable and their local
-links traversable through four read-only MCP tools. Skills remain invisible until their exact file digest is
-approved, and are never copied or executed. See
-[Immutable context packs](docs/context-packs.md). OKF 0.1/0.2 import and
-privacy-reviewed OKF 0.2 export are documented in
-[Open Knowledge Format exchange](docs/open-knowledge-format.md).
-
-### Managed capability contract (opt-in)
-
-`CAIRN_CAPABILITY_CONTRACT=1` enables one versioned, typed boundary around the
-existing capability owners. The master flag and callback logging are both off
-by default. With the master flag unset, MCP registration, installed
-Markdown/workflow bytes, commands, processes, configuration reads, logging,
-output, and performance remain on the legacy path.
-
-| Capability ID | Kind | Existing owner | Compatibility default | Process override |
-|---|---|---|---:|---|
-| `memory.write` | MCP tool | `memory_write` | on | `CAIRN_CAPABILITY_MEMORY_WRITE` |
-| `memory.search` | MCP tool | `memory_search` | on | `CAIRN_CAPABILITY_MEMORY_SEARCH` |
-| `notes.distill` | offline job | note distillation CLI/timer | off | `CAIRN_CAPABILITY_NOTES_DISTILL` |
-| `wiki` | operating workflow | installed wiki commands/workflows | on | `CAIRN_CAPABILITY_WIKI` |
-| `graph` | operating workflow | installed graph commands | inherited from `graphify.enabled`, otherwise off | `CAIRN_CAPABILITY_GRAPH` |
-| `security.audit` | operating workflow | installed security commands/workflows | on | `CAIRN_CAPABILITY_SECURITY_AUDIT` |
-| `route.check` | MCP tool | existing token-miser routing delegate | on | `CAIRN_CAPABILITY_ROUTE_CHECK` |
-| `context.explore` | MCP tool | existing token-miser exploration delegate | on | `CAIRN_CAPABILITY_CONTEXT_EXPLORE` |
-
-Manage project overrides in `.ai/capabilities.json` through the CLI rather than
-editing JSON:
-
-```bash
-CAIRN_CAPABILITY_CONTRACT=1 cairn capabilities list
-CAIRN_CAPABILITY_CONTRACT=1 cairn capabilities status --json
-CAIRN_CAPABILITY_CONTRACT=1 cairn capabilities disable context.explore
-CAIRN_CAPABILITY_CONTRACT=1 cairn capabilities reset context.explore
-CAIRN_CAPABILITY_CONTRACT=1 cairn capabilities logging enable
-```
-
-Process overrides take precedence over project values, which take precedence
-over compatibility defaults. `reset` removes an explicit override and restores
-the inherited state; it does not mean enabled. Changes to the four MCP
-capabilities (`memory.write`, `memory.search`, `route.check`, and
-`context.explore`) require a fresh memory-server start and disabled tools are
-omitted from `tools/list`. Offline and operating workflows resolve state at
-each invocation. Enabling the master does not enable `notes.distill` or graph
-when their compatibility inputs remain off.
-
-Callback records are local, payload-free operating evidence, not evaluation
-results or telemetry. They require the contract, callback logging, and local
-trajectory capture to be enabled together. Cairnkeep makes no capability gain,
-memory-quality, or efficiency claim from this instrumentation; Phase 19 must
-first create an explicit all-enabled baseline and measure one-disabled states.
-See the [operating guide](docs/operating.md#managed-capability-contract-opt-in),
-[storage contract](docs/storage.md#capability-callback-storage), and
-[privacy flow](docs/privacy-and-data-flow.md#capability-callback-flow).
-
-### Evaluation harness (opt-in, measurement only)
-
-`CAIRN_EVAL=1` enables `cairn eval` for a committed schema-v1 task set and an
-explicit operator-owned adapter program. `validate` resolves immutable inputs,
-limits, commands, digests, output containment, and a deterministic serial
-schedule without invoking the adapter. `run` measures from-scratch Run 1 versus
-a fresh Run 2 that can see only its own task's immutable note snapshot.
-`ablate` measures an explicit all-eight-capabilities-on baseline against one
-exactly-one-disabled treatment, with both passes in both arms. Execution prints
-the invocation estimate and requires `--yes`; there is no retry, inference,
-provider, endpoint, credential, model, or network default.
-
-The canonical local JSON report records optional reported turns/tokens/cost,
-independently verified pass state, full and note-eligible populations,
-missingness, paired deltas, capability/notes/revision digests, and seeded
-bootstrap uncertainty. Turns compare only under exact matching turn-semantics
-compatibility IDs; token totals are never inferred and unknown verifier results
-are never counted as pass or fail. Reports describe estimates and
-inconclusive/small-sample conditions; they do not claim causality,
-significance, quality change, or efficiency change.
-
-The bundled fake task set and adapter are deterministic, offline framework
-fixtures. They cannot support a Cairnkeep performance statement. Any future
-efficiency statement requires a separate committed `live-evaluation` artifact
-whose source, task-set, report, schema, note-snapshot, missingness, runtime, and
-claim anchors all pass `scripts/verify-phase19-runtime-evidence.mjs`. No such
-live claim or evidence artifact is shipped here, and external paper calibration
-is neither a Cairnkeep result nor an acceptance target.
-
-Reports and note snapshots stay under
-`.agentfs/eval/experiments/<experiment-id>/`; default uninstall retains them,
-while explicit purge is backup-first and revertible. Cancellation retains an
-inspectable partial report. POSIX process-group cleanup and Windows descendant-
-tree cleanup through `taskkill.exe /T` are tested by their platform contracts. See the
-[operating guide](docs/operating.md#evaluation-harness-opt-in),
-[storage contract](docs/storage.md#evaluation-report-and-note-snapshot-storage),
-and [privacy flow](docs/privacy-and-data-flow.md#evaluation-adapter-and-report-flow).
-
-### Validated skill improvement (opt-in)
-
-`cairn skill` promotes repeated, resolved hindsight evidence through a guarded
-lifecycle: local harvest, explicit evidence review, bounded proposal generation,
-separate exploration and confirmation evaluations, exact-digest application,
-and backup-first rollback. Cairnkeep never rewrites a live skill during proposal
-or evaluation, never sends evidence to the proposal adapter before approval,
-and never applies a candidate automatically.
-
-Proposal generation uses an explicit strict adapter configuration with an
-environment allowlist. Evaluation remains disabled unless `CAIRN_EVAL=1`, uses
-the existing isolated worktree runner and independent verifier, and requires
-disjoint committed task sets bound to one immutable source revision. A
-candidate is eligible only when both stages meet the configured improvement
-floor with no regression or unknown pair. See the
-[validated skill guide](docs/skill-improvement.md),
-[storage contract](docs/storage.md#validated-skill-storage), and
-[privacy flow](docs/privacy-and-data-flow.md#validated-skill-improvement-flow).
-
-### Typed memory nodes and structured import (opt-in)
-
-`CAIRN_TYPED_MEMORY_NODES=1` adds schema-v1 `node_type`, canonical `tags`,
-`address_space`, hard list/search filters (`node_types`, `tags_all`,
-`tags_any`), and exactly one new MCP tool: `memory_import`. The flag is read
-when each server/session is created, so restart after changing it. Unset keeps
-the existing 14 tools, schemas, response roots, raw values, files, processes,
-network behavior, and output unchanged. It adds no read/edit/update/delete
-aliases; `memory_supersede` remains the sole edit operation.
-
-Core types are `memory`, `knowledge`, `hindsight`, `shared`, and `provenance`;
-extensions use a namespaced form such as `team:runbook`. Tags are ASCII
-lowercase, with whitespace and underscores normalized to hyphens, deduplicated,
-and sorted. Filters are applied before ranking. Exact key/tag/type hits precede
-semantic results; without a working configured embedding endpoint, search uses
-stable local substring matching.
-
-`memory_import` accepts one inline schema-v1 batch for one concrete scope and
-one `memory`, `project-notes`, or `shared-notes` address. It supports 1–256
-unique relative keys, values up to 256 KiB each and 5 MiB total, optional
-`import_id`, `dry_run`, and `conflict_policy: reject|supersede`. Results contain
-only digests, counts, keys, and actions—never supplied values. The default
-reject policy cannot overwrite; explicit supersede preserves typed history.
-Note addresses require `scope: project` and logical keys, never filesystem
-paths. See the [operating guide](docs/operating.md#typed-memory-nodes-and-note-address-spaces-opt-in).
-
-### Git-linked work evidence (opt-in)
-
-`CAIRN_WORK_EVIDENCE=1` makes generated Claude Code, OpenCode, Pi, Kimi, Qwen
-and Codex launchers record bounded start/end Git state and links to exact local
-trajectories, artifacts and reviewed-memory writes. It records no prompts,
-keystrokes or reasoning, and harness launch remains fail-open when Git or
-capture is unavailable. Inspect it with `cairn evidence list|show|delete|prune|doctor`.
-Optional patch capture requires both `CAIRN_WORK_EVIDENCE_PATCH=1` and
-`CAIRN_ARTIFACT_STORE=1`; Cairnkeep never applies or restores a patch. See the
-[work-evidence guide](docs/work-evidence.md).
-
-### Compaction continuity and artifacts (opt-in)
-
-`CAIRN_COMPACTION_CAPTURE=1` captures only harness-produced compaction summaries
-from the pinned Claude Code `PostCompact` 2.1.219 and 2.1.220 payloads and
-OpenCode `session.compacted` 1.17.20 seam. It stores redacted immutable revisions locally and injects the latest
-valid structured goals, decisions, TODOs, and critical errors when a session
-starts. A resumed session is preferred; a fresh session falls back to the
-newest valid project summary and marks stale context for validation. The raw
-redacted summary is available only through an explicit read. Cairnkeep never
-generates or triggers compaction.
-
-`CAIRN_ARTIFACT_STORE=1` independently exposes exactly four stdio MCP tools:
-`artifact_write`, `artifact_read`, `artifact_list`, and `artifact_delete`.
-The initial kinds are exactly `compaction_summary`, `diff`, `test_output`, and
-`generated_file`. Generated-file paths are labels only; the server never reads
-them. Operators can inspect retained local data whether or not MCP writes are
-currently enabled:
-
-```bash
-cairn artifact list --kind compaction_summary --json
-cairn artifact show ARTIFACT-ID --json
-cairn artifact delete ARTIFACT-ID --dry-run --json
-cairn artifact prune --dry-run --include-protected --json
-```
+- [Quickstart](docs/quickstart.md)
+- [For coding agents](docs/agents.md)
+- [Context intelligence](docs/context-intelligence.md)
+- [Operating guide](docs/operating.md)
+- [Harness compatibility](docs/harness-compatibility.md)
+- [Privacy and data flow](docs/privacy-and-data-flow.md)
+- [Guided learning paths and video scripts](docs/learning/README.md)
 
-Both capabilities are default-off, local, and require no key, model, endpoint,
-telemetry, or network. Remote tools require double consent:
-`CAIRN_ARTIFACT_STORE=1` plus `CAIRN_ARTIFACT_HTTP=1`, as well as the existing
-bearer, `Host`, and validated `X-Cairn-Project` controls. Artifact HTTP never
-exposes trajectory data. See the [operating guide](docs/operating.md#compaction-continuity-and-artifacts-opt-in),
-[storage contract](docs/storage.md#artifact-storage), and
-[privacy flows](docs/privacy-and-data-flow.md#compaction-and-artifact-flows).
+The repository supports Linux, macOS, native Windows x64, WSL, Node.js 22/24/26,
+and real Bash 3.2 within the boundaries documented in the compatibility guides.
 
-## More
+## Contributing and support
 
-- **Guided learning paths and video scripts** — [docs/learning/README.md](docs/learning/README.md)
-- **Optional document RAG** (`domain_knowledge_*` via AnythingLLM) — [docs/domain-knowledge.md](docs/domain-knowledge.md)
-- **Building a private overlay** (wrap cairnkeep for your org/provider) — [docs/building-an-overlay.md](docs/building-an-overlay.md)
-- **Managed overlay distributions** (wrapper CLI, policy lock, private registry, rollback) — [docs/overlay-distributions.md](docs/overlay-distributions.md)
-- **Full operating guide** — [docs/operating.md](docs/operating.md)
-- **Memory storage and deployment** — [docs/storage.md](docs/storage.md)
-- **Podman and OCI containers** — [docs/containers.md](docs/containers.md)
-- **Privacy and data flow** — [docs/privacy-and-data-flow.md](docs/privacy-and-data-flow.md)
-- **MCP tool profiles** — [docs/mcp-tool-profiles.md](docs/mcp-tool-profiles.md)
-- **Immutable context packs** — [docs/context-packs.md](docs/context-packs.md)
-- **Open Knowledge Format exchange** — [docs/open-knowledge-format.md](docs/open-knowledge-format.md)
-- **Validated skill improvement** — [docs/skill-improvement.md](docs/skill-improvement.md)
-- **Git providers** — [docs/git-providers.md](docs/git-providers.md)
-- **Support** — [SUPPORT.md](SUPPORT.md)
-- **Contributing** — [CONTRIBUTING.md](CONTRIBUTING.md)
-- **Security policy** — [SECURITY.md](SECURITY.md)
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development and pull-request
+guidelines, [SUPPORT.md](SUPPORT.md) for help, and [SECURITY.md](SECURITY.md) for
+private vulnerability reporting.
 
 ## License