Add per-supplier daily booking cap enforced at booking-intent create

[thlpkee20-wq]

Description

Enforce a per-supplier daily-cap on booking-intent creation (default 500/day) with a 429 response and X-DailyCap-Reset header, plus an admin override on the supplier profile.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: src/routes/bookingIntents.ts, src/services/supplierCap.ts

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/supplier-daily-cap
• Implement changes
  • Track counter in Redis keyed by supplier:{id}:booking:{yyyy-mm-dd} with TTL 26h
  • Return 429 with reset header when cap exceeded
  • Add admin override CRUD on PUT /admin/suppliers/:id/booking-cap
• Validate security and correctness assumptions

Test and commit

• Run tests
  • npm test
• Cover edge cases
  • cap boundary (exactly at cap), midnight rollover, admin override to 0 (soft block), Redis miss
• Include test output and notes

Example commit message

feat: per-supplier daily booking cap

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[Sensei-Victor]

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

This is my dominant field

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

[Jagadeeshftw]

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

Hi, I’d love to take on this issue! With my expertise in Rust, Stellar, and smart contract development, I can implement a clean and efficient solution.

🚀 Why Me?

• Proven Blockchain Experience – Hands-on work with Stellar, Solidity, and Rust, building secure and optimized smart contracts.
• Open Source Contributor – Actively contributed to 50+ open-source projects, showcasing adaptability and collaboration.
• Efficient & Reliable – I deliver high-quality, production-ready solutions quickly, ensuring security and scalability.

⏱ Timeline

I estimate completing this within 24 hours. Let me know if I can proceed!

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

[Imole203]

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

I will love to work on this issue,pls 🙏 assign this to me

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

[mubby4]

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

Hello, this issue fits well with my background and I'm confident I can resolve it properly — could you assign it to me?

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

[drips-wave]

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

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