Merge duplicate density preference modules

[greatest0fallt1me]

Summary

utils/density.ts (readDensityPreference/persistDensityPreference) and state/uiPrefs.ts (getDensityPreference/setDensityPreference) both read and write 'callora.density' with separate DensityPreference types.

Why this matters

Two sources of truth drift: one guards storage errors and one does not, and future changes must be made twice.

Scope

Keep a single module (state/uiPrefs.ts), re-export from the other temporarily, update MarketplacePage and tests, then delete the duplicate.

Relevant code in CalloraOrg/Callora-Frontend:

• src/utils/density.ts
• src/state/uiPrefs.ts
• src/pages/MarketplacePage.tsx

Priority

Low

Acceptance criteria

• Only one module owns the callora.density key
• MarketplacePage imports the canonical module
• Storage access is guarded
• density and uiPrefs tests are consolidated

Validation

npm test -- --run src/utils/density.test.ts src/state/uiPrefs.test.ts

Non-goals

• Typo-only, formatting-only, or cosmetic changes.
• Unrelated refactors, dependency upgrades, or broad rewrites.
• Removing safeguards or weakening validation to make tests pass.

Contributor application

Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.

PR requirements

Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.

Quality review

A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.

---

Generated by Claude Code

[shobhamerabacha-star]

Hi maintainers,

I can tackle Keep leaderboard rank pages deterministic. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in CalloraOrg/Callora-Frontend
• Core Implementation: Deliver Keep leaderboard rank pages deterministic with proper loading/error states and clean component architecture.
• Quality Assurance: Verify UI performance and zero console errors.

Happy to pick this up today—please assign to me!

[Praiz089017]

@Praiz089017 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I would love to resolve this issue

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

[drips-wave]

⚠️ @greatest0fallt1me: @shobhamerabacha-star has been assigned to this issue but hasn't applied to it via Drips Wave.

This issue is still part of the Stellar Wave Program, so Wave contributors can still apply and be assigned. If you'd rather hand it off outside of Wave, remove the Stellar Wave label to take this issue out of the Wave Program.

[drips-wave]

Congratulations, @Praiz089017! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @Praiz089017: 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 🌊