Add creator route cache header constants

[Chucks1093]

Summary

Add shared cache header constants for creator-facing public routes.

Acceptance Criteria

• cache header values live in a shared constants location
• public route handlers can import the constants directly
• naming is clear and scoped to creator routes

Contributor coordination: https://t.me/accesslayerorg

[michaelvic123]

@michaelvic123 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Please assign this to issue to me

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

[Jayrodri088]

@Jayrodri088 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'll extract creator-facing public route cache headers into a shared constants file so they're consistent, reusable, and easy to tune globally. I'll create backend/src/constants/cache-headers.ts exporting named values like CREATOR_PUBLIC_CACHE = 'public, max-age=300, s-maxage=1800' for short‑lived lists/leaderboards, CREATOR_STATIC_CACHE = 'public, max-age=3600, immutable' for unchanging metadata, and CREATOR_PRIVATE_CACHE = 'private, max-age=60, must-revalidate' for user‑specific creator views.
​

Route handlers will import and apply them directly (res.set('Cache-Control', CACHE_HEADERS.CREATOR_PUBLIC_CACHE)), with a simple helper setCreatorCache(res, type) for convenience, and I'll document usage in README.md#cache-headers. This eliminates magic strings and ensures CDN/browser caching works optimally for public creator routes. ETA: 1–2 hours for constants file, handler updates, and docs.

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

[drips-wave]

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

🧑‍💻 @Jayrodri088: 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 @Jayrodri088 as part of the Stellar Wave Program's 3rd Wave 🥳

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