Add structured log for each cache miss and cache hit on the creator profile query

[Chucks1093]

Summary

The creator profile query uses an in-memory cache to avoid repeated Horizon calls. There is currently no visibility into cache effectiveness. A debug-level log on each cache hit and miss would let the team measure the hit rate and tune the TTL.

Scope

• Emit a debug-level log on each cache hit with fields: creator_wallet, cache_key, hit: true, ttl_remaining_ms
• Emit a debug-level log on each cache miss with fields: creator_wallet, cache_key, hit: false
• Logs emitted before the cache lookup result is used
• Log level is debug — must not appear in production log output at the default log level

Acceptance Criteria

• Cache hit log emitted with all four fields
• Cache miss log emitted with all three fields
• Logs emitted before the result is used
• Log level is debug (suppressed at default info level in production)

ETA: 12 hours

---

Coordinate on Telegram

[Lspnjr1]

Hello maintainers,
I’m Lspnjr1
I would like to be assigned to this issue. After reviewing the requirements, I’m confident that I understand the scope of the task and the project’s contribution criteria. I believe I can deliver a clean, maintainable implementation that aligns with the project’s standards.