@cairnkeep/cli 1.0.2

package/AGENTS.md

@@ -0,0 +1,45 @@
+# Cairnkeep — agent guide
+
+Cairnkeep is a durable, harness-agnostic memory + context layer for coding
+agents. This file is the operating contract for agents working *in this repo*.
+
+## Layout
+- `mcp-memory-server/` — the memory MCP server (`cairn-memory`). TypeScript.
+- `bin/cairn` — the CLI (`cairn bootstrap [path]`).
+- `scripts/` — bootstrap and maintenance utilities.
+- `templates/` — project scaffolding (launchers, env) + the derived-knowledge
+  layer (wiki, alignment, graphs, security, planning).
+
+## Build & test
+```bash
+cd mcp-memory-server
+npm ci
+npm run build
+npm test        # offline smoke tests — no API key required
+```
+`npm test` must pass before committing changes to the memory server.
+
+## Memory model (what the server exposes)
+- Scoped, durable key/value memory over AgentFS: `memory_write`, `memory_read`,
+  `memory_search`, `memory_supersede`, `memory_history`, `memory_extract`.
+- Keys are short kebab-case with a prefix: `decisions/`, `pitfalls/`,
+  `patterns/`, `bugs/`, `constraints/`, `conventions/`.
+- Search uses embeddings when `CAIRN_LLM_API_KEY` and an endpoint URL are set;
+  otherwise it degrades to substring match.
+
+## Conventions
+- Keep the core provider-neutral: no vendor names, no hardcoded endpoints. All
+  LLM configuration comes from `CAIRN_LLM_*` / `CAIRN_MEMORY_*` environment
+  variables.
+- Keep the git-host layer configurable via `CAIRN_GIT_PROVIDER`
+  (see `docs/git-providers.md`); never hardcode a specific host.
+- Match the existing style; prefer the smallest change that solves the task.
+- Run the relevant checks before closing work.
+
+## Working rules (hard)
+- This repo never references a specific employer, vendor, internal host/IP, or
+  private repo name — in code, comments, commit messages, or docs.
+- No AI/assistant authorship references anywhere (commits, comments, docs).
+- Scan every commit — the diff **and** the message — for the above before
+  creating it.
+- Commit locally, review, then push.

package/CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing to Cairnkeep
+
+Contributions are welcome through GitHub issues and pull requests.
+
+## Before starting
+
+- Open or reference an issue for behavior changes that affect users, storage,
+  security boundaries, or public interfaces.
+- Keep the core provider-neutral. Do not add employer names, private repository
+  names, internal endpoints, credentials, or environment-specific defaults.
+- Do not include generated authorship or assistant attribution in commits,
+  source files, or documentation.
+- Report security vulnerabilities privately as described in
+  [SECURITY.md](SECURITY.md), not through a public issue.
+
+## Development setup
+
+The memory server requires Node.js 18 or newer. Node.js 20 is used in CI.
+
+```bash
+git clone https://github.com/cairnkeep/cairnkeep.git
+cd cairnkeep/mcp-memory-server
+npm ci
+npm test
+```
+
+The repository-level checks exercise the CLI, bootstrap scripts, documentation
+parity, and public-content guard:
+
+```bash
+cd ..
+npm run check:public
+```
+
+Some integration verifiers require optional sibling tools or configured API
+endpoints. They are not part of the default offline test suite.
+
+## Pull requests
+
+- Create a focused branch from `main`.
+- Keep commits coherent and use imperative commit subjects.
+- Add or update tests for behavioral changes.
+- Update user documentation when configuration or commands change.
+- Confirm `npm run check:public` and `npm --prefix mcp-memory-server test` pass.
+- Keep the working tree free of generated databases, logs, credentials, and
+  local planning artifacts not intended for publication.
+
+By contributing, you agree that your contribution is licensed under the
+Apache License 2.0 found in [LICENSE](LICENSE).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Stefano Tondo
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,149 @@
+# Cairnkeep
+
+> 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, OpenCode, …).
+
+## Status
+
+Shipped: the memory server, the `cairn` CLI (`bootstrap`, `memory-server`, `sync`,
+`doctor`, `memory`, `audit-timer`) installable via `npm i -g @cairnkeep/cli`, and the
+operating layer (commands,
+agents, hooks) installed on both Claude Code and OpenCode. The generic launchers
+expose wrapper seams (`.ai/pre-launch.sh`, `CAIRN_EXTRA_SETTINGS`,
+`.ai/post-exit.sh`) 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.
+
+## 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 bootstrap [path]` scaffolds a project's
+  `.ai/` launchers + env; `cairn doctor` health-checks the configured pieces;
+  `cairn memory export|import` relocates the durable store between machines;
+  `cairn audit-timer` installs the scheduled memory+wiki audit.
+- **`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.
+
+| 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 |
+
+## Setup
+
+A working workflow needs three things: the memory server registered, the
+operating layer (commands, agents, hooks) installed into your harness, and a
+bootstrapped project. `cairn bootstrap` does only the last of these — the full
+ordered walkthrough is in **[docs/operating.md](docs/operating.md)**.
+
+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. Scaffold a project and configure it
+cairn bootstrap /path/to/project
+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
+```
+
+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, `--config` for OpenCode). 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/`) 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_AGENTFS_BASE_DIR` | Base dir for global memory scopes (default `~/.cairnkeep`) |
+| `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_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) |
+
+Without an API key, search degrades gracefully to substring matching.
+
+## More
+
+- **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)
+- **Full operating guide** — [docs/operating.md](docs/operating.md)
+- **Git providers** — [docs/git-providers.md](docs/git-providers.md)
+- **Contributing** — [CONTRIBUTING.md](CONTRIBUTING.md)
+- **Security policy** — [SECURITY.md](SECURITY.md)
+
+## License
+
+Apache-2.0 © 2026 Stefano Tondo

package/SECURITY.md

@@ -0,0 +1,37 @@
+# Security Policy
+
+## Supported versions
+
+Security fixes are applied to the latest released version of
+`@cairnkeep/cli`. Users should upgrade to the newest npm release before
+reporting an issue that may already be resolved.
+
+## Reporting a vulnerability
+
+Do not open a public issue for a suspected vulnerability or include secrets,
+private endpoints, memory databases, or reproduction data in public logs.
+
+Use GitHub's private vulnerability reporting flow:
+
+https://github.com/cairnkeep/cairnkeep/security/advisories/new
+
+Include the affected version, impact, reproduction steps, and any suggested
+mitigation. Use synthetic data and redact credentials and private repository
+details.
+
+The project will acknowledge the report, validate the issue, and coordinate a
+fix and disclosure through the private advisory. No response-time guarantee is
+provided, but confirmed issues will be prioritized according to impact.
+
+## Scope
+
+Reports are especially useful for:
+
+- memory-scope isolation or path traversal;
+- unauthorized HTTP access to the MCP server;
+- credential, cookie, or stored-memory disclosure;
+- unsafe command or file execution;
+- package or bootstrap integrity problems.
+
+Configuration mistakes that deliberately disable documented safeguards are
+normally outside scope unless the safe default is ineffective.

package/bin/cairn

@@ -0,0 +1,73 @@
+#!/usr/bin/env bash
+# cairn — Cairnkeep CLI. Thin dispatcher over the core scripts.
+set -euo pipefail
+
+# Resolve through symlinks so this works when installed as an npm global bin
+# (which symlinks <prefix>/bin/cairn -> the packaged bin/cairn).
+SOURCE="${BASH_SOURCE[0]}"
+while [ -L "$SOURCE" ]; do
+  DIR=$(cd -P "$(dirname "$SOURCE")" && pwd)
+  SOURCE=$(readlink "$SOURCE")
+  [[ "$SOURCE" != /* ]] && SOURCE="$DIR/$SOURCE"
+done
+CAIRN_ROOT=$(cd -P "$(dirname "$SOURCE")/.." && pwd)
+
+cmd="${1:-help}"
+[[ $# -gt 0 ]] && shift
+
+case "$cmd" in
+  bootstrap)
+    exec "$CAIRN_ROOT/scripts/bootstrap.sh" "$@"
+    ;;
+  doctor)
+    exec "$CAIRN_ROOT/scripts/doctor.sh" "$@"
+    ;;
+  memory)
+    exec "$CAIRN_ROOT/scripts/memory-store.sh" "$@"
+    ;;
+  memory-server)
+    # Run the memory MCP server (stdio by default). Use with your harness, e.g.
+    #   claude mcp add cairn-memory -s user -- cairn memory-server
+    exec node "$CAIRN_ROOT/mcp-memory-server/dist/index.js" "$@"
+    ;;
+  sync)
+    exec "$CAIRN_ROOT/scripts/sync-claude-assets.sh" "$@"
+    ;;
+  audit-timer)
+    exec "$CAIRN_ROOT/scripts/install-audit-timer.sh" "$@"
+    ;;
+  version | --version | -v)
+    v=$(sed -n 's/.*"version"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p' "$CAIRN_ROOT/package.json" 2>/dev/null | head -1)
+    echo "cairnkeep ${v:-unknown}"
+    ;;
+  help | --help | -h | *)
+    cat <<'USAGE'
+cairn — Cairnkeep CLI
+
+Usage:
+  cairn bootstrap [--untracked] [path]
+                           Scaffold .ai/ launchers + env into a project (default: .).
+                           --untracked keeps the scaffold out of git via the repo's
+                           .git/info/exclude (contributor mode: nothing to commit,
+                           invisible to other contributors, local-only).
+  cairn memory-server      Run the memory MCP server (stdio). Register it with your
+                           harness, e.g. claude mcp add cairn-memory -s user -- cairn memory-server.
+  cairn sync [--apply] [--live-root DIR]
+                           Install/update the Claude Code operating layer (commands,
+                           agents, hooks) into ~/.claude, or into DIR for a single
+                           project (--live-root <project>/.claude).
+  cairn doctor             Health-check the configured pieces (memory server, LLM /
+                           embedding endpoints, git provider, store); skips what is
+                           unconfigured, fails only on a configured-but-unreachable dep.
+  cairn memory <path|export|import>
+                           Relocate the durable memory store. `path` prints its
+                           location; `export <file.tgz>` takes a WAL-safe snapshot;
+                           `import <file.tgz>` restores it on another machine.
+  cairn audit-timer [--on-calendar SPEC] [--para-root PATH] [--render-only DIR]
+                           Install (opt-in) a systemd user timer that runs the
+                           memory+wiki audit on a schedule; prints a cron alternative.
+  cairn version            Print version
+  cairn help               Show this help
+USAGE
+    ;;
+esac