Add request body schema validation for POST /api/streams (rate, recipient, schedule)

[greatest0fallt1me]

Description

app/api/streams/route.ts and app/api/v2/streams/route.ts only check that recipient, rate, and schedule are present, then store them as raw strings — no Stellar address validation, no numeric/precision validation on rate, no allowed-values check on schedule. Add strict server-side schema validation so malformed streams cannot be created. This is a backend input-validation task.

Requirements and Context

• Validate recipient as a Stellar public key using isValidStellarPublicKey from app/lib/wallet-link.ts.
• Validate rate against the money/precision rules in app/lib/amount.ts (positive, bounded decimals).
• Validate schedule against the supported set in app/lib/schedules.ts.
• Return 422 VALIDATION_ERROR with per-field detail; share validation between v1 and v2 handlers.
• 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 task/streams-create-validation

2. Implement changes
   • app/api/streams/route.ts, app/api/v2/streams/route.ts
   • app/lib/stream-validation.ts (new) — shared validator using amount.ts, schedules.ts, wallet-link.ts
3. Test and commit
   • npm test -- app/api/streams
   • Cover edge cases: bad public key, negative/over-precision rate, unknown schedule
   • Include test output and notes in the PR

Example commit message

task: add strict schema validation to stream creation

Acceptance Criteria

• Invalid Stellar recipient rejected with 422
• Invalid rate precision/sign rejected with field detail
• Unknown schedule rejected
• Coverage ≥ 90% for the validator and both routes

Guidelines

• Minimum 90% test coverage including each invalid-field case
• Clear documentation and inline comments
• Timeframe: 96 hours

[DonaldXoftDev]

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

I would like to work on this,
I have experience in writing Restful Api's that follows the Open api specifications..

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

[drips-wave]

Congratulations, @DonaldXoftDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[DonaldXoftDev]

Thanks for assigning this! I've started digging into the codebase and will have a PR ready for review in due time...