Add integration test asserting webhook delivery at-least-once semantics with exponential backoff

[thlpkee20-wq]

Description

Cover webhook delivery: on 5xx from the receiver, retry with exponential backoff (up to 6 attempts), and mark as succeeded after any 2xx, asserting metrics reflect each attempt.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: src/workers/webhookRetry.ts, src/webhooks/dispatch.ts

Suggested execution

• Fork the repo and create a branch
• git checkout -b tests/webhook-at-least-once
• Implement changes
  • Mock receiver returning 500 twice then 200
  • Assert exactly 3 attempts with backoff timings
  • Assert webhook_deliver_attempts_total{result} counter increments per attempt
• Validate security and correctness assumptions

Test and commit

• Run tests
  • npm test
• Cover edge cases
  • receiver always 500 (max attempts exhausted, moved to DLQ), receiver 2xx on first try, 429 with Retry-After
• Include test output and notes

Example commit message

tests: webhook at-least-once + backoff

Guidelines

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

[Nwapu-TrustJah]

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

Good morning Maintainer ! I'd love to take on this issue and implement a clean shutdown lifecycle for the stdio transport.
Ensuring the server handles termination signals and EOF gracefully is crucial for preventing state corruption and guaranteeing in-flight writes flush cleanly before exit.
Here’s my plan for the implementation:
Signal & Transport Lifecycle Handlers:
Register signal listeners for SIGINT and SIGTERM as well as stdin EOF/end and transport error/close events.
Implement a centralized, idempotent shutdown() helper that prevents duplicate cleanup executions.
State Flushing & Clean Termination:
Ensure all in-flight state operations and pending writes are fully flushed/awaited before invoking server.close().
Ensure the process exits with deterministic status codes (e.g., 0 on graceful signal/EOF, 1 on unhandled transport errors).
Testing & Documentation:
Add unit tests asserting signal handler registration, state flushing on shutdown, and clean server termination without state leaks.
Update contributor/deployer documentation if lifecycle behavior or environment options are affected.
Assign this issue to me please

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

[Paranoa-dev]

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

i would love to work on this

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

[mikewheeleer]

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

I would like to work on this issue, and I have good knowledge of smart contacts and Sorabani Rust. Kindly assign it to me.

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

[drips-wave]

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

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

[thlpkee20-wq]

Assigned to @Nwapu-TrustJah based on their Drips Wave application. This assignment was checked against the limit of 4 active assigned issues without a linked PR across the Chronopay-Org organization. Please open a PR referencing this issue when ready.