@cairnkeep/cli 2.5.0 → 2.7.0

package/docs/learning/video-scripts/L02-installation.md

@@ -1,97 +0,0 @@
-# L02 Video Script - Install the local workflow
-
-**Target duration:** 12 minutes
-**Companion lesson:** [L02](../lessons/L02-installation.md)
-
-## Recording setup
-
-- Use a clean user profile or disposable VM with Node.js 22 or newer.
-- Install Claude Code but remove any existing `cairn-memory` registration.
-- Ensure no private MCP servers, provider URLs, or environment variables appear.
-- Prepare a snapshot before installation for a repeatable retake.
-
-## 00:00 - Hook
-
-**Say:** “The most common incomplete installation has a running memory server
-but no Cairnkeep commands or hooks. We will install and verify all three parts
-of the local workflow.”
-
-**Show:** A three-part diagram: CLI, MCP registration, operating layer.
-
-## 00:40 - Outcome
-
-**Say:** “At the end, Claude Code can start the local `cairn-memory` server and
-the managed command assets pass a non-writing drift check.”
-
-## 01:10 - Runtime preflight
-
-**Do:** Run `node --version` and `npm --version`.
-
-**Say:** “Cairnkeep requires Node.js 22 or newer. I verify that before changing
-the machine.”
-
-## 02:00 - Install the CLI
-
-**Do:** Run the pinned npm install and `cairn --version` from L02.
-
-**Say:** “For a course recording I pin the version. Users can follow the current
-release instructions when the lesson is updated.”
-
-## 03:30 - Register MCP
-
-**Say:** “The stable server name is `cairn-memory`. This command tells Claude
-Code to launch a local stdio child process. It does not configure a remote URL.”
-
-**Do:** Run the `claude mcp add` command, followed by `claude mcp get cairn-memory`.
-
-**Point out:** The command is `cairn memory-server`.
-
-## 05:15 - Install the operating layer
-
-**Say:** “MCP tools alone do not install `/remember`, `/recall`, wiki commands,
-review workflows, agents, or hooks. That is the job of `cairn sync`.”
-
-**Do:** Run `cairn sync --apply`.
-
-**Pause:** Allow the learner to see the asset summary.
-
-## 07:00 - Verify without writing
-
-**Do:** Run `cairn sync --check`.
-
-**Say:** “This is the repeatable drift check. A healthy result means the
-operating layer matches the installed distribution. MCP registration plus this
-check distinguishes a complete setup from a partial one.”
-
-## 08:30 - Common failure demonstration
-
-**Say:** “If slash commands are missing, do not reinstall everything blindly.
-First check the MCP registration, then check operating-layer drift, and restart
-the harness after applying assets.”
-
-**Show:** The two verification commands together.
-
-## 09:30 - Optional shell completion
-
-**Do:** Run `source <(cairn completion bash)` and complete `cairn tra`.
-
-**Say:** “Completion is optional convenience. It does not start another server
-or enable any feature.”
-
-## 10:00 - Boundary
-
-**Say:** “This default server is local. We did not configure embeddings,
-document RAG, or remote HTTP memory. Those choices have separate lessons
-because they change data flow.”
-
-## 11:00 - Recap
-
-**Say:** “The machine setup has three pieces: CLI, MCP registration, and the
-operating layer. In L03 we add the fourth piece, a bootstrapped project, and
-prove memory survives a new session.”
-
-## Editing notes
-
-- Chapter markers: Preflight, CLI, MCP, Operating layer, Verify, Boundary.
-- Do not show the general MCP list if it contains unrelated server names.
-- Link L02, the operating guide, and L03.

package/docs/learning/video-scripts/L03-first-project.md

@@ -1,99 +0,0 @@
-# L03 Video Script - Bootstrap the first project
-
-**Target duration:** 13 minutes
-**Companion lesson:** [L03](../lessons/L03-first-project.md)
-
-## Recording setup
-
-- Start from the completed L02 VM snapshot.
-- Confirm `$HOME/cairnkeep-course/first-project` does not exist.
-- Use only the synthetic UTC convention from the lesson.
-- Prepare to stop and restart the harness during the recording.
-
-## 00:00 - Hook
-
-**Say:** “An installation is not proven by files on disk. The useful proof is a
-fact accepted in one session and recalled in a new session.”
-
-## 00:30 - Outcome
-
-**Say:** “We will bootstrap a disposable Git repository, run diagnostics, store
-one synthetic convention, restart Claude Code, and retrieve it again.”
-
-## 01:00 - Create the project
-
-**Do:** Run the directory, `git init`, and README commands from L03.
-
-**Say:** “I use a disposable repository so no course artifact can reach a real
-project.”
-
-## 02:00 - Bootstrap
-
-**Say:** “Bootstrap adds project launchers and derived-knowledge scaffolding. It
-does not reinstall the machine-level MCP server or operating assets.”
-
-**Do:** Run `cairn bootstrap "$PWD"` and copy `.ai/env.example` to `.ai/.env`.
-
-**Point out:** The generated next steps without reading every created filename.
-
-## 03:45 - Diagnose
-
-**Do:** Run `cairn doctor`.
-
-**Say:** “Optional unconfigured integrations may be skipped. A configured but
-unreachable dependency is a failure and should be fixed before relying on it.”
-
-**Point out:** Session capture, notes, compaction, artifacts, typed memory,
-capability governance, and evaluation remain off for the core-memory proof.
-
-## 05:00 - Launch and remember
-
-**Do:** Start `./.ai/start-claude.sh`.
-
-**Say:** “I launch through the project script so every session loads the same
-project environment.”
-
-**Do in Claude:** `/remember Course convention: examples use UTC timestamps.`
-
-**Point out:** The durable key returned by the workflow.
-
-## 07:00 - Recall
-
-**Do in Claude:** `/recall UTC timestamps`
-
-**Say:** “This confirms retrieval inside the first session, but not yet
-persistence across sessions.”
-
-## 08:00 - Persistence proof
-
-**Do:** Exit Claude Code, run the launcher again, and repeat `/recall UTC timestamps`.
-
-**Pause:** Keep the retrieved result visible.
-
-**Say:** “This is the important proof. The second harness process recovered the
-accepted fact from durable local storage.”
-
-## 10:00 - Locate storage
-
-**Do:** Exit the harness and run `cairn memory path`.
-
-**Say:** “The command reports the local store location. Nothing in bootstrap
-silently selected a remote server.”
-
-## 11:00 - Recovery and boundary
-
-**Say:** “If recall fails after restart, compare the launcher and environment,
-check the MCP registration, and verify the storage path. Do not solve routing
-problems by copying database files while the server is running.”
-
-## 12:00 - Recap
-
-**Say:** “We bootstrapped one project, used its launcher, and proved persistence
-across a new session. The quickstart is complete. L04 will teach how to choose
-keys, scopes, search, history, and the memory review gate.”
-
-## Editing notes
-
-- Do not cut away the harness exit/restart; it is the central proof.
-- Add captions for “first session” and “second session”.
-- Link L03 and L04 in the description.