Add webhook retry policy override per subscription

[greatest0fallt1me]

Description

This is a backend issue for the GrantFox campaign. This is a backend issue for the GrantFox campaign. Per-subscription override of default retry policy.

Requirements and Context

• Implement per the description
• Add focused tests for the change
• Document any API/visible changes
• Adhere to repo's lint and code style
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/webhook-retry-override

2. Implement changes
   • src/routes/webhooks.ts
   • src/services/webhookRetry.ts
3. Test and commit
   • Run the repo's standard test suite and lint
   • Cover edge cases; include output in the PR

Example commit message

feat: per-subscription retry override

Acceptance Criteria

• Implementation matches the description
• Tests added and passing
• Code review approved
• Docs updated

Guidelines

• Minimum 90% test coverage on changed lines
• Input validation at the boundary; standardized error envelope
• Structured logging with correlation IDs
• Clear documentation and inline comments
• Timeframe: 96 hours

[yunus-dev-codecrafter]

Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!

[CleanDev-Fix]

Hi, I would like to work on this.

My planned approach:

1. Review the webhook registration, signed delivery, retry, and event-history paths against the existing repo patterns and acceptance criteria.
2. Implement the smallest focused change needed for TypeScript implementation without broad refactors.
3. Verify with the package test/build command documented by the repo and include the results in the PR.

One trade-off I will keep in mind: I will avoid changing unrelated auth, billing, or payout behavior unless the existing code path requires it.

Does this approach line up with what you want for this issue?

[ayomidearegbeshola29-dev]

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

I would like to work on this pls

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@ayomidearegbeshola29-dev's PR #584 was approved and merged by @greatest0fallt1me.

🏆 @ayomidearegbeshola29-dev: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (576 total points). Track your full progress on GrantFox.

👏 Great work, @ayomidearegbeshola29-dev! Keep contributing to CalloraOrg.