Archive FuneralFinder V1/V2, set V3 as production (D032)

- V1 stories → Archive/FuneralFinder V1
- V2 stories → Archive/FuneralFinder V2
- V3 stories → Organisms/FuneralFinder (primary)
- Component registry updated (V3 = done, V1/V2 = archived)
- Retroactive review plan confirmed: P0/P1 only, interleaved (D033)
- CLAUDE.md: added proactive session startup review procedure
- Build skills updated with internal QA stages

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

CLAUDE.md

@@ -76,6 +76,14 @@ This project uses structured markdown files for cross-session memory.
 - `docs/memory/token-registry.md` — All tokens with their current values and usage notes
 - `docs/memory/session-log.md` — Recent sessions (last 2-3); older sessions in `docs/memory/archive/`
 
+**Session startup — proactive review pass (do this automatically):**
+Check `docs/reference/retroactive-review-plan.md` for the current review state. If
+there are tiers or components that haven't been reviewed yet, run the next review
+step (typically `/normalize {tier}` or `/audit {component}`) at the start of the
+session before the user's main request. Keep this to ~30-60 min, then report
+findings and shift to whatever the user wants to work on. This is "morning
+housekeeping" — the user has approved this and expects it to happen without asking.
+
 **After completing work, update:**
 - The relevant memory files with what changed
 - `docs/memory/session-log.md` with a summary of what was accomplished and next steps