chore(graphify): correct the recovery note, capitalize LRN-154

The previous note said a fresh clone gets the skill back from `make
plugin` without naming the command, and I picked the wrong one when the
files actually went missing. There are two, and only one restores the
skill:

  - `graphify install --platform claude` copies SKILL.md, references/
    and .graphify_version. Touches nothing else. This is the recovery
    command, verified: the skill came back at 0.9.61 and the four
    guarded configs were byte-identical afterwards.
  - `graphify claude install` writes the CLAUDE.md section and the
    .claude/settings.json PreToolUse hooks, rewrites both of those
    guarded configs (EVAL-020, reproduced today), and does NOT copy the
    skill.

LRN-154 records why the files vanished in the first place. `git rm
--cached` keeps the working file, but `gitflow finish` checks out the
target branch, where it is still tracked, so git restores it and the
merge then deletes it from disk. .gitignore does not protect it; it only
stops a re-add. The file survives the commit and dies at the merge, which
reads as unrelated.

CLAUDE.md

@@ -37,13 +37,27 @@ or re-run `make plugin`.
 (`install-plugins.sh` STEP graphify), which lands in the repo because
 `~/.claude/skills` is a symlink to `skills/`. They are gitignored: a
 `pipx upgrade graphifyy` used to dirty the tree and cost a
-`chore(graphify): sync vendored skill X -> Y` commit each time. A fresh
-clone gets them back from `make plugin`.
+`chore(graphify): sync vendored skill X -> Y` commit each time.
+
+Two graphify commands, easy to confuse, and only one restores the skill:
+- `graphify install --platform claude` copies SKILL.md + `references/` +
+  `.graphify_version` into `skills/graphify/`. Touches nothing else.
+  This is the recovery command.
+- `graphify claude install` writes the CLAUDE.md graphify section and the
+  `.claude/settings.json` PreToolUse hooks. It **rewrites both guarded
+  configs** (EVAL-020, verified again 2026-09-15), so revert them after. It does NOT copy
+  the skill.
+
+`make plugin` runs both (`install-plugins.sh` STEP graphify) behind the
+guarded-config EXIT trap, so a fresh clone is covered.
 
 Trade-off accepted: an upstream release can now change the skill's prompt
 with no diff to review. `skills/graphify/test-prompts.json` is hand-written
-for darwin and stays tracked. To inspect what upstream changed, read the
-files on disk or diff against a previous `pipx` version.
+for darwin and stays tracked.
+
+Gotcha, learned the hard way: `git rm --cached` keeps the working file,
+but if the branch you merge into still tracks it, the merge deletes it
+from disk. Untrack and merge, then restore with the command above.
 
 ## Transient planning artifacts