Update registry + session log — FuneralFinder v2 complete

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-03-26 17:28:14 +11:00
parent cc87827c39
commit ad1d755ef1
2 changed files with 38 additions and 0 deletions

View File

@@ -23,6 +23,43 @@ Each entry follows this structure:
## Sessions
### Session 2026-03-26d — FuneralFinder v2 build
**Agent(s):** Claude Opus 4.6 (1M context)
**Work completed:**
- Built FuneralFinderV2 from scratch — completely different approach from v1 (quick-form vs stepped wizard)
- 4-step vertical form with 48px numbered circles (brand-200 default → brand-500 completed) and 3px connector lines
- Steps: (1) Intent (3 options), (2) Planning for (conditional auto-set for arrange-now), (3) Funeral type (5 options), (4) Location
- Sequential unlock logic: each step enables only when the previous is filled
- Labels use brand-700 copper when active, text.disabled when locked
- Selects match Input medium height (48px) via py: 14px
- Display serif heading + body2 subheading with full-width divider
- Default contained CTA (copper), disabled until location has 3+ chars
- Trust signal "Free to use · No obligation" below CTA
- Focus rings suppressed (subtle brand-400 border only)
- Full accessibility: role="search", aria-required, aria-label on all fields
- Multiple iteration rounds incorporating user feedback on sizing, alignment, colours, spacing, and layout
- Ran /critique (33/40 Good) and /audit (18/20 Excellent) — fixed all P0/P1 issues
**Decisions made:**
- v2 keeps v1 alongside — both exported from index.ts for comparison
- Step circles use brand-200 warm fill (not neutral grey) for palette cohesion
- "Plan a funeral for someone expected to pass soon" softened to "Plan ahead for someone who is unwell"
- Connector lines use ::after on each StepCircle rather than container ::before (starts from circle bottom, not above)
- Location input uses no icon, matches select styling (py: 14px, fontSize: 0.875rem)
**Open questions:**
- Which version (v1 or v2) to proceed with for production? May keep both and A/B test
- Connector line height (60px) is a magic number — works for single-line labels but would need adjustment if labels wrap
**Next steps:**
- User to review in Storybook and decide on v1 vs v2 direction
- If v2 chosen: add location autocomplete, consider progress summary state
- Update docs/reference/ with v2 flow logic doc (similar to funeral-finder-logic.md for v1)
---
### Session 2026-03-26c — FuneralFinder v1 refinement and completion
**Agent(s):** Claude Opus 4.6 (1M context)