feat(memory): add project-scope CLAUDE.md; link.sh deploys CLAUDE.global.md

CLAUDE.md

@@ -0,0 +1,29 @@
+<!-- PROJECT SCOPE ONLY (claude-config repo). The user-scope GLOBAL memory is
+     ./CLAUDE.global.md, deployed as ~/.claude/CLAUDE.md by link.sh — edit
+     THAT file for cross-project doctrine. -->
+
+# claude-config — project instructions
+
+## Health Stack
+- shell: `shellcheck *.sh hooks/*.sh lib/*.sh`
+
+## rules/ maintenance
+
+Modular instruction files loaded by Claude Code alongside the global memory.
+`rules/` is symlinked to `~/.claude/rules` by `link.sh` (user scope, ALL
+projects). One rule = one file = one concern.
+
+A rule WITH `paths:` YAML frontmatter (glob list) loads lazily — only when
+Claude reads a file matching a glob; a rule WITHOUT it loads at session
+start, same cost as the global memory. Extract from CLAUDE.global.md only
+what can be path-scoped (the token win) or what is generated; always-on
+doctrine stays in CLAUDE.global.md. `paths:` globs match against the
+CURRENT project's tree — a broad glob (e.g. `rules/**`) can fire in foreign
+projects; keep rule bodies tiny.
+Docs: https://code.claude.com/docs/en/memory.md#path-specific-rules
+
+Machine-owned: `rules/context7.md` is DELETED BY DESIGN (BDR-053,
+2026-07-06) — `ctx7 setup --claude --cli` still writes it, but
+install-plugins.sh STEP ctx7 purges it right after; the find-docs skill is
+the single ctx7 surface. If it reappears (manual `ctx7 setup`), delete it
+or re-run `make plugin`.

link.sh

@@ -17,7 +17,7 @@ link_file() {
   CHANGED=$((CHANGED + 1))
 }
 
-link_file "$REPO/CLAUDE.md"     "$CLAUDE/CLAUDE.md"
+link_file "$REPO/CLAUDE.global.md" "$CLAUDE/CLAUDE.md"
 link_file "$REPO/settings.json" "$CLAUDE/settings.json"
 
 for item in hooks agents skills lib templates rules; do