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>

docs/reference/retroactive-review-plan.md

@@ -126,12 +126,11 @@ improve the patterns used in new components.
 
 ---
 
-## Decision needed from user
+## Decisions (confirmed 2026-03-27)
 
-Before starting, confirm:
-1. **FuneralFinder version** — Which version (v1/v2/v3) should get the full
-   review? The others can be lightly maintained or archived.
-2. **Depth vs speed** — Do we fix all P2 issues too, or strictly P0/P1 only?
-   P0/P1 only is faster and doesn't risk changing things that already work.
-3. **Interleave with new work** — Review in dedicated sessions, or mix with
-   building remaining components (FormField, ArrangementForm, PricingTable)?
+1. **FuneralFinder version** — V3 is production. V1/V2 archived (viewable in
+   Storybook under Archive/). Only V3 gets the full review.
+2. **Depth** — P0/P1 only. Don't touch P2/P3 — not worth the risk on approved components.
+3. **Approach** — Interleaved. Start each session with a review pass (~30-60 min),
+   then shift to new component work. This is automated — the agent runs it
+   proactively at session start without being asked.