[Testing] useGamificationStore XP/level-up logic has zero unit tests despite stores.test.ts covering every other store

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

stores.test.ts explicitly tests useUserStore/useWalletStore/useUIStore/useThemeStore but never imports useGamificationStore, leaving its real logic untested: addXP -> checkLevelUp transitions (useGamificationStore.ts:210-254), calculateLevel threshold boundaries (125-132), getNextLevelInfo math (346-376), and unlockAchievement/updateAchievementProgress clamping (264-298).

Acceptance criteria

• Test addXP crossing each LEVEL_THRESHOLDS boundary sets level, kingdomTitle, showLevelUpModal, pendingLevelUp
• Test calculateLevel/getNextLevelInfo at exact and below-threshold XP values, and progress clamping to [0,100]
• Test updateAchievementProgress sets unlockedAt exactly once when progress reaches maxProgress

Files to touch

• frontend/src/app/stores/useGamificationStore.ts
• frontend/src/app/stores/stores.test.ts

Out of scope

• Gamification persisting transient state (already filed)

[Abioladory123]

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

Interested in taking this on. I’ve worked across smart contracts, APIs, and frontend integrations, and I can start immediately.

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

[TheShnider]

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

Hi. I have reviewed this issue and would like to work on it.

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

[Glam26]

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

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

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

[kingbitnation]

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

Hi! I'd like to work on this issue.

After reviewing the requirements, I believe it's a good match for my experience. I'll implement the requested functionality while following the project's existing architecture, coding conventions, and contribution guidelines. I'll ensure the solution is clean, well-tested, and covers all of the stated acceptance criteria, updating or adding tests where appropriate and documenting any relevant changes.

If I encounter any implementation details that need clarification, I'll communicate them early to avoid unnecessary rework.

Could this issue be assigned to me?

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

[drips-wave]

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

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