@lh8ppl/claude-memory-kit 0.1.0 → 0.1.1

package/template/.gitignore.fragment

@@ -1,12 +1,12 @@
-# claude-memory-kit — added by `cmk install`. Do not edit by hand;
-# `cmk install` refreshes these lines idempotently. Remove via
-# `cmk uninstall`.
-
-# Local-tier (per-machine, never committed)
-context.local/
-
-# SQLite + FTS5 read cache (regenerable from markdown)
-context/.index/
-
-# Run-time locks + transient state
-context/.locks/
+# claude-memory-kit — added by `cmk install`. Do not edit by hand;
+# `cmk install` refreshes these lines idempotently. Remove via
+# `cmk uninstall`.
+
+# Local-tier (per-machine, never committed)
+context.local/
+
+# SQLite + FTS5 read cache (regenerable from markdown)
+context/.index/
+
+# Run-time locks + transient state
+context/.locks/

package/template/CLAUDE.md.template

@@ -1,49 +1,49 @@
-## Memory System — claude-memory-kit
-
-This project uses **claude-memory-kit** for per-project, in-repo memory that survives session boundaries. Memory lives in `context/` (committed) and `context.local/` (gitignored). Cross-project memory lives at `~/.claude-memory-kit/` (or `$MEMORY_KIT_USER_DIR`).
-
-> v0.1.0 is under active development. This block is the runtime contract. Specific mechanisms (auto-extract, memory-write skill, MCP search) come online incrementally — `cmk doctor` will tell you which layers are active in the current install. Full architecture: <https://github.com/LH8PPL/claude-memory-kit/blob/main/docs/journey/v0.1.0-build-log.md>
-
-### Where memory lives
-
-| Tier | Path | Travels with `git clone`? |
-| --- | --- | --- |
-| **User** | `~/.claude-memory-kit/` | No — machine-local, cross-project |
-| **Project** | `<repo>/context/` | **Yes** — committed |
-| **Local** | `<repo>/context.local/` | No — gitignored, per-machine |
-
-Precedence at session start: local > project > user (most-specific wins, others are logged as shadowed).
-
-### How memory works
-
-- **Session start** — the kit injects a frozen snapshot (≤10 KB) from the three tiers into Claude's context. Loaded once, never mutated mid-session — preserves the prefix cache.
-- **During the session** — durable facts get captured automatically by the Stop hook + `memory-write` skill (once Layer 4 is live). The user can also explicitly say "remember this", "from now on", "we decided X".
-- **End of session** — the rolling-window pipeline compresses `sessions/now.md` into a daily summary. Cron jobs distill into `recent.md` and `archive.md` over time (Layer 6, optional).
-
-### Health checks (when `cmk doctor` is live)
-
-Health checks (HC-1..HC-8) verify each layer is wired correctly: install integrity, hook registration, transcript capture freshness, INDEX accuracy, cron registration, semantic search backend, native Auto Memory coexistence. See [`docs/adr/`](docs/adr/) and [`specs/v0.1.0/design.md`](specs/v0.1.0/design.md) for the full contract.
-
-### Memory write rules (for Claude)
-
-When you learn something durable about this project or the user:
-
-1. **Working state** (current threads, today's environment, open decisions) → write to `context/MEMORY.md` (≤2,500 chars). Consolidate at the cap.
-2. **Typed durable fact** (user role / project decision / feedback / external reference) → create `context/memory/<type>_<slug>.md` with full YAML frontmatter; add a one-line entry to `context/memory/INDEX.md`.
-3. **Cross-project lesson** → user-tier `~/.claude-memory-kit/LESSONS.md` (via `cmk lessons promote`).
-4. **Never duplicate** between scratchpad and granular archive. If a working-state item becomes durable, MOVE it.
-5. **Confirm silently.** Frozen-snapshot semantics mean the write takes effect next session.
-
-### Privacy
-
-Anything inside `<private>...</private>` tags in a user prompt is stripped before any disk write — never persisted in any form. Per-fact `private: true` frontmatter excludes a fact from the session-start digest.
-
-### Uninstall / remove this block
-
-This block is managed by `cmk install`. To remove it cleanly:
-
-```bash
-cmk uninstall
-```
-
-Everything outside the `claude-memory-kit:start` / `:end` markers is byte-preserved.
+## Memory System — claude-memory-kit
+
+This project uses **claude-memory-kit** for per-project, in-repo memory that survives session boundaries. Memory lives in `context/` (committed) and `context.local/` (gitignored). Cross-project memory lives at `~/.claude-memory-kit/` (or `$MEMORY_KIT_USER_DIR`).
+
+> v0.1.0 is under active development. This block is the runtime contract. Specific mechanisms (auto-extract, memory-write skill, MCP search) come online incrementally — `cmk doctor` will tell you which layers are active in the current install. Full architecture: <https://github.com/LH8PPL/claude-memory-kit/blob/main/docs/journey/v0.1.0-build-log.md>
+
+### Where memory lives
+
+| Tier | Path | Travels with `git clone`? |
+| --- | --- | --- |
+| **User** | `~/.claude-memory-kit/` | No — machine-local, cross-project |
+| **Project** | `<repo>/context/` | **Yes** — committed |
+| **Local** | `<repo>/context.local/` | No — gitignored, per-machine |
+
+Precedence at session start: local > project > user (most-specific wins, others are logged as shadowed).
+
+### How memory works
+
+- **Session start** — the kit injects a frozen snapshot (≤10 KB) from the three tiers into Claude's context. Loaded once, never mutated mid-session — preserves the prefix cache.
+- **During the session** — durable facts get captured automatically by the Stop hook + `memory-write` skill (once Layer 4 is live). The user can also explicitly say "remember this", "from now on", "we decided X".
+- **End of session** — the rolling-window pipeline compresses `sessions/now.md` into a daily summary. Cron jobs distill into `recent.md` and `archive.md` over time (Layer 6, optional).
+
+### Health checks (when `cmk doctor` is live)
+
+Health checks (HC-1..HC-8) verify each layer is wired correctly: install integrity, hook registration, transcript capture freshness, INDEX accuracy, cron registration, semantic search backend, native Auto Memory coexistence. See [`docs/adr/`](docs/adr/) and [`specs/v0.1.0/design.md`](specs/v0.1.0/design.md) for the full contract.
+
+### Memory write rules (for Claude)
+
+When you learn something durable about this project or the user:
+
+1. **Working state** (current threads, today's environment, open decisions) → write to `context/MEMORY.md` (≤2,500 chars). Consolidate at the cap.
+2. **Typed durable fact** (user role / project decision / feedback / external reference) → create `context/memory/<type>_<slug>.md` with full YAML frontmatter; add a one-line entry to `context/memory/INDEX.md`.
+3. **Cross-project lesson** → user-tier `~/.claude-memory-kit/LESSONS.md` (via `cmk lessons promote`).
+4. **Never duplicate** between scratchpad and granular archive. If a working-state item becomes durable, MOVE it.
+5. **Confirm silently.** Frozen-snapshot semantics mean the write takes effect next session.
+
+### Privacy
+
+Anything inside `<private>...</private>` tags in a user prompt is stripped before any disk write — never persisted in any form. Per-fact `private: true` frontmatter excludes a fact from the session-start digest.
+
+### Uninstall / remove this block
+
+This block is managed by `cmk install`. To remove it cleanly:
+
+```bash
+cmk uninstall
+```
+
+Everything outside the `claude-memory-kit:start` / `:end` markers is byte-preserved.