Add structured log for React Query cache hit on creator profile fetch with cache age

[Chucks1093]

Summary

When a creator profile is served from the React Query cache without a network request, there is no log recording the hit or how old the cached data is. A debug-level log on cache hit would help developers verify that caching is working as intended in production.

Scope

• Add a query observer on the creator profile query that fires when data is returned from cache (isFetching: false and isStale: false immediately on mount)
• Emit a debug-level log with fields: creator_id, cache_status: 'hit', data_age_ms (time since the query was last fetched)
• Log must not fire when the query performs a network fetch
• Log not emitted in the test environment

Acceptance Criteria

• Log emitted on cache hit with all three fields
• data_age_ms reflects time since last successful fetch
• Log not emitted when a network fetch occurs
• Log not emitted in test environment

ETA: 12 hours

---

Coordinate on Telegram

[Malcolm-Wander]

@Malcolm-Wander has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer,I’d love to work on this issue please,I promise to do a good and swift job..thank you very much

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

[mikevill20]

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

Hello maintainer, please assign this issue to me. Thanks

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

[Kvnghayjay]

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

Hi.... I’ve reviewed the expected behavior and I’m confident I can implement the necessary changes accurately and efficiently.

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

[k-deejah]

@k-deejah has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, I can work on this issue

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @k-deejah as part of the Stellar Wave Program's 7th Wave 🥳

😎 @k-deejah: You earned 200 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.