Claude Code Sync

Updates an existing setup without blowing away user customizations. Idempotent — safe to run weekly, monthly, or on a schedule.

What sync does

1. Re-fingerprint: scan the repo for stack changes since last setup. New framework? New DB? New CI/CD tool?
2. Delta propagation: push plugin rule updates (cc-always.md, cc-patterns.md) into the repo's .claude/rules/.
3. Section-merge CLAUDE.md: update the "Build & Test", "Tech Stack", "Key Paths" sections if stack changed; leave custom sections alone.
4. Fix drift (--fix-drift flag): find config that drifted from plugin defaults — missing hooks, missing MCP servers, outdated skill versions — and repair.
5. Propagate to sub-repos: for monorepos, walk workspace children and apply changes to their .claude/ dirs.
6. Scaffold docs/context/ (if absent): create the 22-template knowledge base that complements .claude/.
7. Auto-install LSPs: detect missing LSP servers from the stack and offer install commands.
8. Persist sync state: write .claude/sync-state.json with timestamp, plugin version, delta summary.

Section-merge protocol for CLAUDE.md

CLAUDE.md sections are identified by ## headings. Sync protocol: