commitlore-setuplisted

# CommitLore setup **Shortcut for a repository that just needs wiring up, nothing broken to diagnose:** `commitlore init` runs steps 2-4 below (`hooks install`, `index --rebuild`, then `doctor --fix` as a final check) in one command, reports what it did and what it could not, and is safe to re-run. Use the four steps below one at a time when something specific looks broken and you want to isolate which piece. Four checks, in order. Each one is independent and re-runnable — running any of them twice on an already-configured repo is a no-op, not an error. ## 1. Diagnose ``` commitlore doctor ``` Reports `ok`, `warn`, or `skipped` for: whether the `origin` remote fetches `refs/notes/commitlore` (records that live only in the notes mirror never reach a teammate whose fetch config omits that ref), whether there is a local notes mirror to push, whether the commit-msg hook is installed, and whether the local `git` build parses trailers the way the spec expects. `warn` lines carry their own fix directly underneath — read that before doing anything else. Example, run against a repo that has a remote but nothing else set up: ``` warn notes fetch refspec — origin does not fetch refs/notes/commitlore, so records pushed by others stay invisible here fix: git config --add remote.origin.fetch '+refs/notes/commitlore:refs/notes/commitlore' ok notes push — no local mirror yet — nothing to push (git push origin refs/notes/commitlore, once there is) warn commit-msg hook