richie/Parsons
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update session log, mark D034 resolved, document roadmap

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Richie
2026-03-29 15:50:41 +11:00
parent 884e79c0d2
commit 595ca33779
2 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/memory/session-log.md
View File

@@ -41,17 +41,21 @@ Each entry follows this structure:
- **[P2] Empty state guidance:** Added actionable guidance text to empty states in ProvidersStep, PackagesStep, VenueStep, CoffinsStep ("Try adjusting..." copy).
- **Steps that passed with no issues:** PreviewStep (4), SummaryStep (13), ConfirmationStep (15) — all clean.
- **IntroStep critique score: 35/40 (Good)** — full heuristic scoring completed as reference.
- **D034 implemented:** Form error styling unified to copper end-to-end. MuiOutlinedInput error border/ring, MuiFormHelperText error text, MuiFormLabel error state (neutral per D024), ToggleButtonGroup error border — all now use copper (#B0610F). `palette.error.main` remains red for non-form uses.
- **Tagged `v0.1-wizard-groomed`** — safe rollback point before user review checkpoint.
- **Roadmap documented** in persistent memory (`project_roadmap.md`) with 9 phases, checkpoint gates, and guiding principles.
**Decisions made:**
- Error text colour standardised on `var(--fa-color-text-brand)` (copper) for all wizard step error messages — consistent with D024's principle of gentle error feedback. Atom-level error styling (ToggleButtonGroup, TextField) still uses MUI's error.main; that's an atom concern for a separate pass.
- D034: Form error styling uses copper across theme (MuiOutlinedInput, MuiFormHelperText, MuiFormLabel, ToggleButtonGroup). `palette.error.main` stays red for destructive buttons/system alerts.
- User review checkpoint required before integration — tagged `v0.1-wizard-groomed` as rollback point.
**Open questions:**
- ToggleButtonGroup and TextField atoms still use `error.main` (red) for their built-in error borders. Should these be changed to copper at the atom level? (Would affect all consumers, not just wizard steps.)
- None
**Next steps:**
- Retroactive review backlog: Phase 2.2 (molecule audits), Phase 3 (organisms), Phase 4 (cross-cutting)
- Integration: routing, state management, GraphQL queries
- Consider atom-level error colour update (ToggleButtonGroup, TextField)
- **Phase 4: User review checkpoint** — user reviews all 15 steps in Storybook, provides feedback, agent iterates
- Phase 5: Retroactive review backlog (can interleave with Phase 4)
- Phase 6: Integration planning (after checkpoint resolved)
---