Add /admin/scheduler/pause endpoint to freeze new booking-intent creation during incidents

[thlpkee20-wq]

Description

Add an admin-only POST /admin/scheduler/pause and /resume pair, backed by a Redis flag, that freezes new booking-intent creation platform-wide during incidents while leaving read paths intact.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: src/routes/admin/scheduler.ts, src/middleware/schedulerGate.ts, src/redis.ts
• Emit scheduler_pause_total and scheduler_resume_total counters

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/scheduler-pause
• Implement changes
  • Store scheduler:paused=1 in Redis with a reason and initiated_by
  • Guard the booking-intent create route with a schedulerGate middleware
  • Broadcast paused status via the existing WebSocket bus
• Validate security and correctness assumptions

Test and commit

• Run tests
  • npm test
• Cover edge cases
  • Redis unavailable at guard time (fail-open with warning), pause then immediate resume, unauthorized caller
• Include test output and notes

Example commit message

feat: scheduler pause/resume with Redis flag

Guidelines

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

[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.

[mich-sys]

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

assign to me big chief

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

[abdulsamadr943-code]

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

i would love to work on this issue and summit a clean pr withing 1 days

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

[solidsole]

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

I'd like to claim this issue. I have reviewed the details and can begin working on a fix right away. Please assign it to me if it's still available. Thanks!

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

[drips-wave]

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

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