troubleshooting

Repairing the memory kit

Something in core-memory-kit is failing. Diagnose it, then repair what you are allowed to repair and PROPOSE the rest.

The one rule that outranks everything below

Never run a fix that touches the user's own state without asking first.

Each failure code below carries a fix class, and it is binding:

Fix class	What you may do
silent	Just run it. Kit-owned, idempotent, reversible — it rebuilds a derived view and destroys nothing. Say afterwards what you ran, in one line.
confirm	Prepare the exact command, show it, and wait for the user to approve before running it. Anything that rewrites memory content, settings, or install state is this class.
advise	Do not run it. Print the command and what it will do. This is for fixes that are expensive, or outside the kit's authority (installing someone's CLI, changing their PATH).

When you are unsure which class a failure belongs to, treat it as advise. An unknown failure never earns silent repair.

This is enforced, not just asked for: the only repair commands granted to this skill are cmk doctor, cmk reindex, and read-only lookups. cmk install and every form of cmk repair are deliberately ungranted — where a section below tells you to propose one, you propose it and the user runs it. If a command you need is not available to you, that is the boundary working, not a misconfiguration to route around.

The kit's memory tiers are only ever written through the kit's own commands. Never hand-edit a file under the memory directories to "fix" anything — that bypasses the safety screens and is itself a failure mode.

Step 1 — read the evidence before running anything

The whisper on the prompt already names the failure code. If you need more:

• cmk doctor — the full health audit. Every check reports PASS / WARN / FAIL / SKIP with a repair command. This is the diagnosis, not the fix; doctor repairs nothing by itself.
• context/.locks/health.log — the kit's own append-only failure log, one JSON object per line: {ts, class, outcome, detail}. Read the tail. A fail followed by a later ok for the same class means the problem already cleared.