Context
Storybook is configured (with a11y addon and vitest integration in vitest.config.ts), but stories exist for only ~16 components; critical UI (PropertyCard variants, FilterSidebar, WalletModal, NotificationCenter) lacks stories.
Problem
Design review, a11y addon checks, and visual regression have limited surface; component changes rely solely on app-level e2e.
Proposed approach
Add stories for the highest-traffic components with states (loading/error/empty, RTL), enable test-storybook in CI, and track coverage.
Acceptance criteria
- Stories added for priority components
npm run storybook displays them with a11y panel
- CI job builds/tests Storybook
Context
Storybook is configured (with a11y addon and vitest integration in
vitest.config.ts), but stories exist for only ~16 components; critical UI (PropertyCard variants, FilterSidebar, WalletModal, NotificationCenter) lacks stories.Problem
Design review, a11y addon checks, and visual regression have limited surface; component changes rely solely on app-level e2e.
Proposed approach
Add stories for the highest-traffic components with states (loading/error/empty, RTL), enable
test-storybookin CI, and track coverage.Acceptance criteria
npm run storybookdisplays them with a11y panel