budgetTracker: Add onOverspend callback when spending exceeds budget ceiling

[Kingsman-99]

Description

budgetTracker tracks cumulative spending against a budget but silently exceeds limits. Contributors should add an onOverspend(overspentBy: number, budgetId: string) callback option that fires whenever a new payment pushes the total above the configured budget ceiling, so callers can trigger warnings or block further payments.

Acceptance Criteria

• An onOverspend callback option is accepted by the tracker's configuration
• The callback fires exactly once per payment that crosses the budget ceiling (not once per subsequent payment)
• overspentBy is the positive difference between the new total and the budget limit
• Existing tests continue to pass

Context

• Target file: src/lib/budgetTracker.ts

[guptakumarranjeet150]

Hello @maintainers,

I can tackle budgetTracker: Add onOverspend callback when spending exceeds budget ceiling. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Stellar-split/split-app
• Implementation: Deliver a clean, modular solution for budgetTracker: Add onOverspend callback when spending exceeds budget ceiling strictly following Stellar-split/split-app conventions.
• Testing: Cover changes with automated tests ensuring CI passes smoothly.
• PR: Atomic commit with clean git hygiene and passing CI

Looking forward to contributing—please feel free to assign!

[EmannuellaO]

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

I’m interested in taking on this issue. I’ve worked on similar tasks before and I’m available to start right away.

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

[Manager-dev1515]

@Manager-dev1515 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Please assign me, I can fix the issue

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

[Onomebello]

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

please assign me this issues

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

[drips-wave]

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

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

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