Add structured log for creator list query returning unexpected field types

[Chucks1093]

Summary
If a database migration changes a column type without updating the query mapping, the type mismatch is silently coerced or surfaces as a runtime error. A structured error-level log at the type mismatch detection point provides early warning before data corruption reaches clients.

Scope

• identify where creator list query results are mapped to response types
• add an error-level structured log when a field value does not match the expected type
• include the field name, expected type, and received type in the log fields

Acceptance Criteria

• a field type mismatch emits an error-level log with field name and type details
• the log does not fire for correctly typed fields
• the client response behavior for the mismatched field is unchanged

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[MerlinTheWhiz]

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

Hi, let me take this off your plate

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

[dhareymu]

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

Hi maintainer
Kindly assign this project to me. I would love to fix this issue

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

[sochima2]

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

can i work on this

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

[dubemoyibe-star]

@dubemoyibe-star has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hey can no work on this issue

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

[drips-wave]

Congratulations, @dubemoyibe-star! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @dubemoyibe-star: 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 @dubemoyibe-star as part of the Stellar Wave Program's 5th Wave 🥳

😎 @dubemoyibe-star: 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.