Persist user preferences (theme, density, pageSize) under one typed store

[greatest0fallt1me]

Description

This is a UI/UX issue. Several UX choices (theme, list density, page size, sort) need persistence and currently sprawl into ad-hoc localStorage usage. Introduce a single typed userPrefs store with helpers (getPref, setPref) and migrate ThemeContext.tsx plus future density/page-size to it for consistent UX continuity.

Requirements and Context

• Reference: src/ThemeContext.tsx, src/ThemeToggle.tsx
• Single localStorage key callora.prefs holds a JSON map
• Helpers handle JSON parse failures and migrate from any legacy keys
• Default values exported as constants
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/user-prefs-store

2. Implement changes
   • src/utils/userPrefs.ts
   • Migrate ThemeContext.tsx to use it
   • Add format.test.ts-style unit tests for prefs
3. Test and commit
   • npm test for new tests
   • Verify legacy theme key still loads after migration

Example commit message

chore: introduce typed userPrefs store

Acceptance Criteria

• Single callora.prefs key holds all preferences
• Helpers cover get/set/remove with default fallbacks
• Theme migration from legacy keys works on first load
• Unit tests cover parse failures and migrations

Guidelines

• Strictly typed via TS generics
• No external state libraries
• Clear documentation and inline comments
• Timeframe: 96 hours

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[Ayomide-codex]

@Ayomide-codex has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign so I can work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ayomide-codex to this issue.

[drips-wave]

Congratulations, @Ayomide-codex! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Ayomide-codex: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊