feat(routes-f): channel theme override

[davedumto]

Summary

Per-channel accent color theme override.

Requirements

• GET ?creator_id returns { accent_color, secondary_color }
• PUT updates colors
• Validate hex format
• Bundle a default theme inside folder
• Tests cover update and default fallback

Scope Constraint - READ BEFORE STARTING

All files for this task must live inside app/api/routes-f/. This includes the route handler, helpers/utilities, types, and tests. Do NOT modify, import from, or add files to lib/, utils/, types/, components/, or anywhere else outside app/api/routes-f/. If you need shared logic, duplicate it inside your subfolder. Keeping everything scoped to this folder is intentional - it keeps these tasks independent and mergeable in any order.

Product Context

StreamFi is a blockchain-powered live streaming platform. Streamers broadcast via Mux, viewers tip in Stellar XLM/USDC, creators have stream privacy modes (public/unlisted/subscribers-only). Build these issues as practice implementations - use realistic data shapes that match the platform domain, but do not import from the real app code.

[omega58754]

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

Hi team, I’d like to be assigned to this issue. I can implement the per-channel accent color theme override under app/api/routes-f/theme/. I will build the GET query resolver with the default bundled fallback theme, a hex-validated PUT update handler, and the accompanying test files—keeping 100% of the types, helpers, and code strictly localized inside the routes-f directory per your architectural constraint.

ETA: 45–60 minutes

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

[devfoma]

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

Gm Chief, I would love to take on this issue. I'm a software engineer with over 4 years experience. and i'm confident I can resolve this issue

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

[drips-wave]

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

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

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