Add integration test for React Query key constants used consistently across hooks

[Chucks1093]

Summary

The centralized query key constants module needs a test confirming that the keys exported from the module match what is actually used in each hook. A mismatch would silently prevent cache sharing between hooks that reference the same data.

Scope

• Import the query key constants and the hooks that use them
• For each hook, assert its query key matches the expected constant from the module
• Cover: creator list hook, creator detail hook, wallet holdings hook, wallet activity hook

Acceptance Criteria

• Each hook's query key matches the corresponding constant
• Test fails if a hook is updated to use a different key without updating the constant

ETA: 12 hours

---

Coordinate on Telegram

[wagmiiii]

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

I want this issue

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

[shogun444]

@shogun444 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.
I've contributed to Rust, TypeScript, backend, frontend, and smart contract projects, with a focus on delivering focused, well-tested changes. I'll keep the implementation within the requested scope, preserve existing behavior unless the issue requires otherwise, include the necessary tests and documentation, and submit a PR that's straightforward to review.
Portfolio: https://portfolio-amber-one-v8ggyhsjyr.vercel.app/ • ETA: ~2–4 hours.

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

[KingDavid9999]

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

I'd like to claim this issue. I'll add an integration test file that imports the query key constants and each of the four hooks, renders them inside a QueryClient wrapper via renderHook, and asserts that each hook's queryKey matches its corresponding constant. The tests will be wired so any future mismatch between a hook and its constant breaks the suite immediately. I can have a PR ready well within the 12-hour window.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@wagmiiii's PR #473 was approved and merged by @Chucks1093.

🏆 @wagmiiii: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (188 total points). Track your full progress on GrantFox.

👏 Great work, @wagmiiii! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @wagmiiii as part of the Stellar Wave Program's 6th Wave 🥳

😎 @wagmiiii: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.