feat(capitalize): add CAPITALIZE step across completion skills

Registries only get filled if something actively writes to them.
Without integration, the 3-question ritual is aspirational text.
Adds a CAPITALIZE step at the end of every completion skill so work
milestones automatically propose BDR/LRN/BLK entries from context.

- ship-feature STEP 9 — decision/learning/blocker candidates per feature
- bugfix STEP 7 — always propose BLK with root cause; LRN if pattern reusable
- hotfix STEP 5 — default skip; only prompt when non-obvious lesson surfaces
- feat STEP 6 — propose BDR for design choice, LRN for pattern
- commit-change Phase 4 — analyze the commit batch, propose grouped entries

Every variant also appends a one-liner to .claude/memory/journal.md under
today's date heading.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

agents/hotfixer.md

@@ -74,6 +74,18 @@ Load `$HOME/.claude/agents/doc-syncer.md`.
 Execute in automatic mode:
 `auto-mode scope: <list of files modified during this session>`
 
+## STEP 5 — CAPITALIZE (memory registries, lightweight)
+
+Hotfixes are often trivial (typo, config, import) — skip by default. But if the fix revealed something non-obvious:
+
+- Wrong default that should never have been merged → propose `LRN-XXX` in `.claude/memory/learnings.md`.
+- Bug that cost real time to locate despite being "superficial" → propose `BLK-XXX` in `.claude/memory/blockers.md` (status: resolved).
+
+Default behaviour: `CAPITALIZE: hotfix trivial, skip` (no prompt, no output).
+Ask the user only when there is an actual candidate to propose.
+
+Always append a 1-line entry to today's heading in `.claude/memory/journal.md` (even trivial hotfix — journal is timeline, not signal).
+
 ---
 
 ## RULES