cairn-ai 0.1.10 → 0.2.0

package/README.pt.md

@@ -33,8 +33,8 @@ O path escolhido e sua justificativa sao registrados em `docs/plan/<topic>.md` q
 `cairn toolcheck` inspeciona o repositorio atual para stacks JavaScript, TypeScript, Python, PHP, Java, Kotlin, Swift, Go e Rust, depois verifica os LSP e verification tools correspondentes.
 
 ```sh
-cairn toolcheck
-cairn toolcheck --install
+cairn toolcheck --root .
+cairn toolcheck --install --yes --root .
 ```
 
 - `toolcheck` informa detected stacks e missing tools.
@@ -57,7 +57,7 @@ Cairn aplica model-specific adjustment apenas a modelos Claude-family e Codex-fa
 - Claude-family: util para long context, policy interpretation e plan/evidence review.
 - Codex-family: util para small implementation tasks, explicit file edits, command-based verification e bounded `worker` tasks.
 
-A orientacao detalhada fica em `docs/model-guidance/README.md`, `docs/model-guidance/claude.md` e `docs/model-guidance/codex.md`.
+A orientação detalhada fica no plugin instalado em `cairn://docs/model-guidance/README.md`, `cairn://docs/model-guidance/claude.md` e `cairn://docs/model-guidance/codex.md`.
 
 ## Repository Artifacts
 
@@ -65,7 +65,7 @@ O harness cria e mantem estes arquivos na raiz do repositorio alvo.
 
 - `MEMORY.md`: indice curto de persistent domain knowledge.
 - `docs/memory/*.md`: conhecimento detalhado por dominio.
-- `docs/model-guidance/*.md`: Claude and Codex model adjustment guidance.
+- `.cairn/state.json`: estado git-ignored de goal, task e receipt para retomada e stop gates com escopo.
 - `PLAN.md`: indice curto de active and completed work topics.
 - `docs/plan/*.md`: detailed execution plans.
 
@@ -119,7 +119,7 @@ Codex-only hooks nao sao portados para Antigravity. Em vez disso, os mesmos proc
 
 ## Locale Policy
 
-As instrucoes reutilizaveis do Cairn sao escritas em English para global use. User-visible output deve seguir o OS locale configurado, a menos que o usuario peca explicitamente outro idioma. A CLI localiza mensagens comuns para `en`, `ko`, `ja`, `zh`, `es`, `fr`, `de` e `pt`, e volta para English em unsupported locales. O texto `statusMessage` dos Codex hooks permanece static English, enquanto hook command output e English ou Korean.
+As instrucoes reutilizaveis do Cairn sao escritas em English para global use. User-visible output e documentation, plans e memory artifacts gerados ou atualizados devem seguir o OS locale configurado, a menos que o usuario peca explicitamente outro idioma. Isso inclui conteudo em `MEMORY.md`, `PLAN.md`, `docs/memory` e `docs/plan`. A CLI localiza mensagens comuns para `en`, `ko`, `ja`, `zh`, `es`, `fr`, `de` e `pt`, e volta para English em unsupported locales. O texto `statusMessage` dos Codex hooks permanece static English, enquanto hook command output e English ou Korean.
 
 ## Delegation
 

package/README.zh.md

@@ -33,8 +33,8 @@ Cairn 在 execution policy 上刻意不同于 LazyCodex。它不采用 LazyCodex
 `cairn toolcheck` 会检查当前 repository 中的 JavaScript、TypeScript、Python、PHP、Java、Kotlin、Swift、Go 和 Rust stacks，然后检查匹配的 LSP 和 verification tools。
 
 ```sh
-cairn toolcheck
-cairn toolcheck --install
+cairn toolcheck --root .
+cairn toolcheck --install --yes --root .
 ```
 
 - `toolcheck` 报告 detected stacks 和 missing tools。
@@ -57,7 +57,7 @@ Cairn 只对 Claude-family 和 Codex-family models 应用 model-specific adjustm
 - Claude-family: 适合 long context、policy interpretation 和 plan/evidence review。
 - Codex-family: 适合 small implementation tasks、explicit file edits、command-based verification 和 bounded `worker` tasks。
 
-详细指南位于 `docs/model-guidance/README.md`、`docs/model-guidance/claude.md` 和 `docs/model-guidance/codex.md`。
+详细指南位于已安装插件的 `cairn://docs/model-guidance/README.md`、`cairn://docs/model-guidance/claude.md` 和 `cairn://docs/model-guidance/codex.md`。
 
 ## Repository Artifacts
 
@@ -65,7 +65,7 @@ harness 会在目标 repository root 创建并维护这些文件。
 
 - `MEMORY.md`: persistent domain knowledge 的短索引。
 - `docs/memory/*.md`: 按 domain 记录的详细 knowledge。
-- `docs/model-guidance/*.md`: Claude 和 Codex model adjustment guidance。
+- `.cairn/state.json`: 用于中断恢复和 scoped stop gate 的 git-ignored goal/task/receipt 状态。
 - `PLAN.md`: active 和 completed work topics 的短索引。
 - `docs/plan/*.md`: detailed execution plans。
 
@@ -119,7 +119,7 @@ Codex-only hooks 不会移植到 Antigravity。相同的 planning、memory、com
 
 ## Locale Policy
 
-Cairn 的 reusable instructions 为了 global use 使用英文编写。除非用户明确要求其他语言，user-visible output 应遵循 configured OS locale。CLI 会本地化 `en`、`ko`、`ja`、`zh`、`es`、`fr`、`de` 和 `pt` 的 common messages，不支持的 locales fallback 到 English。Codex hook `statusMessage` text 保持 static English，而 hook command output 为 English 或 Korean。
+Cairn 的 reusable instructions 为了 global use 使用英文编写。除非用户明确要求其他语言，user-visible output 以及生成或更新的 documentation、plans、memory artifacts 应遵循 configured OS locale。这包括 `MEMORY.md`、`PLAN.md`、`docs/memory` 和 `docs/plan` 内容。CLI 会本地化 `en`、`ko`、`ja`、`zh`、`es`、`fr`、`de` 和 `pt` 的 common messages，不支持的 locales fallback 到 English。Codex hook `statusMessage` text 保持 static English，而 hook command output 为 English 或 Korean。
 
 ## Delegation
 

package/commands/cairn-doctor.md

@@ -2,13 +2,7 @@
 
 Goal: diagnose Cairn installation status.
 
-Run:
-
-```sh
-node scripts/cairn.mjs doctor
-```
-
-With the published package:
+Run from the published or global package:
 
 ```sh
 bunx cairn-ai@latest doctor
@@ -26,3 +20,4 @@ Checks:
 - hook trust state.
 - Claude Code commands and agents mirror files.
 - Antigravity IDE/CLI skills and workflows mirror files.
+- Installed runtime locators and their referenced scripts, templates, and model guidance.

package/commands/cairn-install.md

@@ -2,18 +2,14 @@
 
 Goal: install Cairn into Codex, Claude Code, and Antigravity.
 
-Run:
-
-```sh
-node scripts/cairn.mjs install
-```
-
-With the published package:
+Run from the published or global package, not from the installed cache copy:
 
 ```sh
 bunx cairn-ai@latest install
 ```
 
+The current custom lifecycle remains in use. Do not invoke lifecycle install/upgrade from the cached plugin root because that copy is the replacement target.
+
 Actions:
 
 - Copy the Cairn installation into the Codex marketplace cache.
@@ -21,4 +17,5 @@ Actions:
 - Register marketplace, plugin, and hook trust state in `~/.codex/config.toml`.
 - Install `cairn-*` commands and agents mirror files for Claude Code.
 - Install `cairn-*` skills and workflows mirror files for Antigravity IDE/CLI.
+- Write runtime locators so all mirrors resolve scripts, templates, and model guidance from the installed plugin root.
 - Create `*.cairn-backup-*` backups before changing settings.

package/commands/cairn-memory.md

@@ -2,16 +2,16 @@
 
 Use the `cairn-memory` skill.
 
-Prerequisite: if `node scripts/cairn.mjs doctor` fails, restore installation with `node scripts/cairn.mjs install` or `node scripts/cairn.mjs upgrade`.
+Prerequisite: resolve the installed Cairn runtime from the plugin or skill locator. If `cairn doctor` fails, restore it with the published/global lifecycle command. Never look for Cairn scripts in the target repository.
 
 Goal: create or update repository memory without asking the user for discoverable facts.
 
 Procedure:
 
-1. Run the plugin state initialization script.
+1. Run the installed plugin state initialization script with an explicit target `--root`.
 2. Every agent must read the project-root `MEMORY.md` for domain knowledge and repository policy before assigned discovery or update work.
 3. Explore repository facts with focused tools.
 4. Use `explorer` for read-only domain discovery and contradiction checks when available; use `worker` for exact references, command checks, and bounded evidence capture. When subagent tools are available, each agent may recursively delegate bounded sub-tasks to subagents. Tell every delegated agent and child subagent to read the project-root `MEMORY.md` before work, keep scope, and preserve others' edits.
 5. Write details to `docs/memory/<domain>.md`.
 6. Keep `MEMORY.md` as a short index.
-7. Use the OS locale for user-visible output unless the user asks for another language.
+7. Use the OS locale for user-visible responses and generated or updated documentation, plans, and memory artifacts unless the user asks for another language.

package/commands/cairn-plan.md

@@ -2,7 +2,7 @@
 
 Use the `cairn-plan` skill.
 
-Prerequisite: if `node scripts/cairn.mjs doctor` fails, restore installation with `node scripts/cairn.mjs install` or `node scripts/cairn.mjs upgrade`.
+Prerequisite: resolve the installed Cairn runtime from the plugin or skill locator. If `cairn doctor` fails, restore it with the published/global lifecycle command. Never look for Cairn scripts, templates, or model guidance in the target repository.
 
 Goal: leave a decision-complete plan for the current task in files before non-trivial implementation.
 
@@ -10,9 +10,9 @@ Procedure:
 
 1. Every agent must read the project-root `MEMORY.md` for domain knowledge and repository policy before repository exploration, tool selection, work, or delegation.
 2. Read relevant `docs/memory/*.md`.
-3. If the active or assigned model is Claude-family, read `docs/model-guidance/claude.md`; if Codex-family, read `docs/model-guidance/codex.md`.
-4. Run `node scripts/cairn.mjs toolcheck` when available.
-5. If required LSP/check tools are missing, run `node scripts/cairn.mjs toolcheck --install` or a repository-native install command before accepting a fallback.
+3. If the active or assigned model is Claude-family, read `cairn://docs/model-guidance/claude.md`; if Codex-family, read `cairn://docs/model-guidance/codex.md`, resolving it through the installed runtime.
+4. Run the installed runtime's `toolcheck --root <repoRoot>`.
+5. If required LSP/check tools are missing, report the proposed install and obtain explicit user approval. Only then use `toolcheck --install --yes --root <repoRoot>` for pinned/supported installers or the approved repository-native command.
 6. Explore before asking the user.
 7. Understand the whole work and affected surfaces first, then classify it into small executable tasks. If a task is still too broad to verify cleanly, split it into sub-tasks.
 8. Run complexity triage before applying agent, plugin, or delegated workflow guidance, and record it before mutating files.
@@ -21,6 +21,7 @@ Procedure:
 11. Treat the user-called/main agent as the orchestrator: it plans, assigns, verifies, relays received subagent status events or observable lifecycle events to the user, and records evidence. Use `worker` for actual implementation edits with clear file ownership whenever subagent tools are available, on both Light Path and Heavy Path. When the subagent tool provides a progress-reporting channel, require subagents to report status when starting work, when deciding or confirming direction, during periodic progress, and when finishing; immediately relay received status events to the user. If no mid-run reporting channel exists, relay observable events such as assignment, waiting, and final completion. Require delegated subagents to provide a final report before leaving; after capturing the final report and evidence, close or release the completed subagent, then review the final report and evidence before marking the work complete. When subagent tools are available, each agent may recursively delegate bounded sub-tasks to subagents. Tell every delegated agent and child subagent to read the project-root `MEMORY.md` before work, keep scope, and preserve others' edits. If subagent tools are unavailable, the main agent takes over implementation directly and records that takeover in evidence.
 12. Write `docs/plan/<topic>.md`.
 13. Add the topic link and status to `PLAN.md`.
-14. Put the selected Light/Heavy Path, checked Heavy Path signals, tool readiness, module acceptance verification, and surface integration verification on every module task.
-15. For Heavy Path, include an explicit automated test command and `Tests:` evidence line; Heavy Path completion must not rely on generic verification wording alone.
-16. Use the OS locale for user-visible output unless the user asks for another language.
+14. Give the plan and every task stable IDs plus fail-closed task and goal evidence requirements. If implementation was requested, start or attach the Cairn goal after planning; do not activate a goal for plan-only requests.
+15. Put the selected Light/Heavy Path, checked Heavy Path signals, tool readiness, module acceptance verification, and surface integration verification on every module task.
+16. For Heavy Path, include an explicit automated test command and `Tests:` evidence line; Heavy Path completion must not rely on generic verification wording alone.
+17. Use the OS locale for user-visible responses and generated or updated documentation, plans, and memory artifacts unless the user asks for another language.

package/commands/cairn-review.md

@@ -2,7 +2,7 @@
 
 Use the `cairn-review` skill.
 
-Prerequisite: if `node scripts/cairn.mjs doctor` fails, restore installation with `node scripts/cairn.mjs install` or `node scripts/cairn.mjs upgrade`.
+Prerequisite: resolve Cairn from its installed runtime locator. If `cairn doctor` fails, restore it with the published/global lifecycle command. Never look for Cairn runtime files in the target repository.
 
 Goal: review completed work against plan, memory, policy, and evidence.
 
@@ -12,5 +12,5 @@ Procedure:
 2. Check changed files, tool readiness evidence, and verification evidence.
 3. Delegate independent read-only review to `explorer` when it materially improves speed or quality; use `worker` only for scoped verification reruns or QA artifacts. When subagent tools are available, each agent may recursively delegate bounded sub-tasks to subagents. Tell every delegated agent and child subagent to read the project-root `MEMORY.md` before work, keep scope, and preserve others' edits.
 4. Report findings first, ordered by severity, with file and line references. If no issues are found, say so clearly and mention remaining test gaps or residual risk.
-5. Record review evidence in `docs/plan/<topic>.md`.
-6. Use the OS locale for user-visible output unless the user asks for another language.
+5. Record review evidence in `docs/plan/<topic>.md` and as the goal-level final review receipt before completing the goal.
+6. Use the OS locale for user-visible responses and generated or updated documentation, plans, and memory artifacts unless the user asks for another language.

package/commands/cairn-toolcheck.md

@@ -5,15 +5,13 @@ Goal: detect repository stacks and check required LSP, typecheck, lint, dry-run,
 From a globally installed package:
 
 ```sh
-bunx cairn-ai@latest toolcheck
-bunx cairn-ai@latest toolcheck --install
+bunx cairn-ai@latest toolcheck --root /path/to/repository
 ```
 
-From this repository:
+From the installed plugin runtime (resolve `pluginRoot` from its locator, not the target repository):
 
 ```sh
-node scripts/cairn.mjs toolcheck
-node scripts/cairn.mjs toolcheck --install
+node "<pluginRoot>/scripts/cairn.mjs" toolcheck --root "/path/to/repository"
 ```
 
-Use `--install` when a required tool is missing. Record detected stacks, missing tools, install attempts, and blockers in the related `docs/plan/<topic>.md`.
+Default toolcheck is read-only. When a required tool is missing, report the proposed change and obtain explicit user approval. Only then use `--install --yes`; unpinned or unsupported installers remain unavailable. Record detected stacks, missing tools, approvals, install attempts, timeouts, and blockers in the related `docs/plan/<topic>.md`.

package/commands/cairn-uninstall.md

@@ -2,13 +2,7 @@
 
 Goal: remove the Codex, Claude Code, and Antigravity entries installed by Cairn.
 
-Run:
-
-```sh
-node scripts/cairn.mjs uninstall
-```
-
-With the published package:
+Run from the published or global package:
 
 ```sh
 bunx cairn-ai@latest uninstall

package/commands/cairn-upgrade.md

@@ -2,22 +2,19 @@
 
 Goal: update the Cairn installation from the current source.
 
-Run:
-
-```sh
-node scripts/cairn.mjs upgrade
-```
-
-With the published package:
+Run from the published or global package, not from the installed cache copy:
 
 ```sh
 bunx cairn-ai@latest upgrade
 ```
 
+The current custom lifecycle remains in use. The cached plugin root is a replacement target and must not upgrade itself.
+
 Actions:
 
 - Replace the Cairn installation in the Codex cache.
 - Recompute hook trust state and update settings.
 - Overwrite Claude Code mirror files with the latest content.
 - Overwrite Antigravity IDE/CLI skills and workflows mirror files with the latest content.
+- Refresh runtime locators for every installed surface.
 - Create `*.cairn-backup-*` backups before changing settings.

package/commands/cairn-work.md

@@ -2,17 +2,17 @@
 
 Use the `cairn-work` skill.
 
-Prerequisite: if `node scripts/cairn.mjs doctor` fails, restore installation with `node scripts/cairn.mjs install` or `node scripts/cairn.mjs upgrade`.
+Prerequisite: resolve the installed Cairn runtime from the plugin or skill locator. If `cairn doctor` fails, restore it with the published/global lifecycle command. Never look for Cairn scripts or model guidance in the target repository.
 
-Goal: execute the next incomplete module task in `PLAN.md` without bypassing the recorded complexity triage.
+Goal: execute the active goal's current task without bypassing complexity triage, then keep advancing tasks until goal-level final review completes or the goal is explicitly paused, blocked, or cancelled.
 
 Procedure:
 
 1. Every agent must read the project-root `MEMORY.md` for domain knowledge and repository policy before selecting or executing a task.
 2. Read `PLAN.md`, the detailed plan, and relevant memory notes.
-3. Read the Codex or Claude model guidance recorded in the plan.
-4. Select one small module task.
-5. Confirm required tool readiness. If a required LSP/check tool is missing, run `node scripts/cairn.mjs toolcheck --install` or a repository-native install command before accepting a fallback.
+3. Resolve and read the `cairn://` Codex or Claude model guidance recorded in the plan through the installed runtime.
+4. Read Cairn goal status and select only its current task. If implementation was requested but no goal exists, create it from the decision-complete plan.
+5. Confirm required tool readiness. If a required LSP/check tool is missing, report it and obtain explicit user approval before `toolcheck --install --yes` or a repository-native install command.
 6. Confirm the complexity triage and selected Light/Heavy Path recorded in the plan. If missing, update the plan before mutating files.
 7. For Light Path, keep the user-called/main agent in the orchestrator role and delegate implementation edits to one bounded `worker` whenever subagent tools are available, then run focused verification.
 8. For Heavy Path, follow the plan's staged implementation and review gates without role-mapping shortcuts.
@@ -20,6 +20,8 @@ Procedure:
 10. For Heavy Path, run the recorded automated test command and record explicit `Tests:` evidence before any completion claim.
 11. Re-run module acceptance verification.
 12. Re-run surface integration verification.
-13. Record tool readiness and verification evidence in `docs/plan/<topic>.md` and update `PLAN.md`.
-14. If the user asks a side question, status question, or narrow clarification while this task is still active, answer it briefly and then resume the previous active work unless the user explicitly asks to pause, stop, or switch tasks.
-15. Use the OS locale for user-visible output unless the user asks for another language.
+13. Record successful verification as structured receipts bound to the goal/task/plan. Missing, failed, skipped, or placeholder receipts never complete a task.
+14. Complete the current task, let Cairn advance to the next one, and continue until every task and goal-level final review receipt passes. Workers return only their assigned task handoff and never select the next task.
+15. Record tool readiness and verification evidence in `docs/plan/<topic>.md`, update goal state, and update `PLAN.md` only after evidence exists.
+16. If the user asks a side question, status question, or narrow clarification while this task is still active, answer it briefly and then resume the previous active work unless the user explicitly asks to pause, stop, or switch tasks.
+17. Use the OS locale for user-visible responses and generated or updated documentation, plans, and memory artifacts unless the user asks for another language.

package/docs/model-guidance/README.md

@@ -7,14 +7,15 @@ The goal is not to make prompts long by model. The goal is to stabilize the same
 ## Application Order
 
 1. Identify the active model name. If the model name is not directly exposed, infer it from the user's default model setting and agent role frontmatter.
-2. For Claude-family models, apply `docs/model-guidance/claude.md`.
-3. For Codex-family models, apply `docs/model-guidance/codex.md`.
-4. If the model is not clearly classified, apply only the common rules and skip model-specific adjustment.
+2. Resolve this installed guidance root from the active skill's `references/cairn-runtime.json` or the source skill's location. Never look for Cairn model guidance in the target repository.
+3. For Claude-family models, apply `cairn://docs/model-guidance/claude.md`.
+4. For Codex-family models, apply `cairn://docs/model-guidance/codex.md`.
+5. If the model is not clearly classified, apply only the common rules and skip model-specific adjustment.
 
 ## Common Rules
 
 - Keep root `MEMORY.md` and `PLAN.md` as indexes only.
-- Keep detailed judgment in `docs/memory/`, `docs/plan/`, and `docs/model-guidance/`.
+- Keep repository-specific judgment in `docs/memory/` and `docs/plan/`. Keep Cairn's model guidance in the installed plugin and reference it with `cairn://docs/model-guidance/...`.
 - Preserve proper nouns, file names, variable names, service names, alert names, MCP tool names, and agent names exactly as written.
 - Select Light Path or Heavy Path before implementation.
 - Treat the user-called/main agent as the orchestrator: it plans, assigns, verifies, and records evidence.
@@ -23,11 +24,13 @@ The goal is not to make prompts long by model. The goal is to stabilize the same
 - When a delegated subagent finishes, require a final report before it leaves; after capturing the final report and evidence, the orchestrator closes or releases the completed subagent, then reviews the final report and evidence before marking the work complete.
 - If subagent tools are unavailable, the main agent takes over implementation directly and records that takeover in evidence.
 - Detect required LSP, typecheck, lint, dry-run, and verification tools before implementation.
-- Missing required tools must trigger a project-local, repository-native, or ephemeral install attempt before they can be treated as unavailable.
+- Missing required tools must be reported with a proposed install. Installation requires explicit user approval and a pinned/supported installer.
+- Bind active work to a persisted Cairn goal and stable task IDs. Continue through tasks until goal-level final review completes, or record an explicit pause, blocker, or cancellation.
+- Treat missing, failed, skipped, stale, or placeholder evidence as failure. Task receipts must be bound to the current goal, task, and plan.
 - Every implementation task must pass module acceptance verification and surface integration verification.
 - Before mutating external state, run the closest available dry-run, check, plan, diff, validate, or equivalent command.
 - Limit each task to two verification passes by default. After two failed passes, record the blocker or split it into sub-tasks instead of continuing a repeated loop.
-- User-visible output must follow the OS locale unless the user asks for another language.
+- User-visible responses and generated or updated documentation, plans, and memory artifacts must follow the OS locale unless the user asks for another language.
 
 ## Delegation Defaults
 

package/docs/model-guidance/claude.md

@@ -20,7 +20,7 @@ Claude-family models are strong at long-context retention, policy interpretation
 - Do not allow open-ended verification loops. Require a blocker or sub-task split after two failed passes.
 - On Heavy Path, check plan gaps before implementation.
 - Before asking the user, use repository evidence and available `explorer`/`worker` delegation when it materially improves speed or quality.
-- Write user-visible output in the OS locale unless the user asks for another language.
+- Write user-visible responses and generated or updated documentation, plans, and memory artifacts in the OS locale unless the user asks for another language.
 
 ## Path Guidance
 

package/docs/model-guidance/codex.md

@@ -25,7 +25,7 @@ Codex-family models are strong at small implementation tasks, explicit tool use,
 - Do not trust success-looking output alone. Confirm real files, commands, and surface evidence.
 - Do not skip LSP, typecheck, lint, dry-run, or verification because a tool is missing. Try repository-local installation or record the failed install attempt as a blocker.
 - Do not continue an open-ended verification loop. Use at most two verification passes per task unless the plan records a risk-based exception.
-- Write user-visible output in the OS locale unless the user asks for another language.
+- Write user-visible responses and generated or updated documentation, plans, and memory artifacts in the OS locale unless the user asks for another language.
 
 ## Path Guidance
 

package/hooks/hooks.json

@@ -7,7 +7,7 @@
             "type": "command",
             "command": "node \"${PLUGIN_ROOT}/scripts/cairn-state.mjs\" session-start",
             "timeout": 10,
-            "statusMessage": "Cairn: preparing repository memory and plan indexes"
+            "statusMessage": "Cairn: loading read-only repository context"
           }
         ]
       }
@@ -19,7 +19,7 @@
             "type": "command",
             "command": "node \"${PLUGIN_ROOT}/scripts/cairn-state.mjs\" user-prompt-submit",
             "timeout": 10,
-            "statusMessage": "Cairn: loading compact work context"
+            "statusMessage": "Cairn: loading read-only work context"
           }
         ]
       }
@@ -32,7 +32,7 @@
             "type": "command",
             "command": "node \"${PLUGIN_ROOT}/scripts/cairn-state.mjs\" post-tool-use",
             "timeout": 10,
-            "statusMessage": "Cairn: checking memory and plan indexes"
+            "statusMessage": "Cairn: reminding current goal receipt requirements"
           }
         ]
       }
@@ -44,7 +44,7 @@
             "type": "command",
             "command": "node \"${PLUGIN_ROOT}/scripts/cairn-state.mjs\" stop",
             "timeout": 10,
-            "statusMessage": "Cairn: checking two-gate evidence requirements"
+            "statusMessage": "Cairn: checking the active goal task"
           }
         ]
       }
@@ -56,7 +56,7 @@
             "type": "command",
             "command": "node \"${PLUGIN_ROOT}/scripts/cairn-state.mjs\" subagent-stop",
             "timeout": 10,
-            "statusMessage": "Cairn: checking subagent handoff evidence"
+            "statusMessage": "Cairn: checking this subagent's assigned task"
           }
         ]
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cairn-ai",
-  "version": "0.1.10",
+  "version": "0.2.0",
   "description": "Token-efficient agent harness with tool readiness for Codex, Claude Code, and Antigravity",
   "license": "MIT",
   "author": {
@@ -39,7 +39,7 @@
     "README.*.md"
   ],
   "scripts": {
-    "check": "node --check scripts/cairn.mjs && node --check scripts/cairn-state.mjs && node --check scripts/cairn-lifecycle.mjs && node --check scripts/cairn-toolcheck.mjs && node -e \"JSON.parse(require('node:fs').readFileSync('package.json','utf8')); JSON.parse(require('node:fs').readFileSync('.codex-plugin/plugin.json','utf8')); JSON.parse(require('node:fs').readFileSync('hooks/hooks.json','utf8'))\" && npm test",
+    "check": "node --check scripts/cairn.mjs && node --check scripts/cairn-paths.mjs && node --check scripts/cairn-goal.mjs && node --check scripts/cairn-state.mjs && node --check scripts/cairn-lifecycle.mjs && node --check scripts/cairn-toolcheck.mjs && node -e \"JSON.parse(require('node:fs').readFileSync('package.json','utf8')); JSON.parse(require('node:fs').readFileSync('.codex-plugin/plugin.json','utf8')); JSON.parse(require('node:fs').readFileSync('hooks/hooks.json','utf8'))\" && npm test",
     "test": "node --test",
     "prepack": "npm run check"
   },