Validate required env vars against a schema and redact secrets in src/config.ts

[Jagadeeshftw]

📌 Description

src/config.ts (already improved to fail fast on missing vars) should go further and validate each var's shape (URL format, numeric ranges, allowed enum values) using a schema library, and ensure any error output never echoes secret values verbatim.

🧩 Requirements and context

• Add schema validation (e.g. zod) covering type/format/range for each config value, not just presence.
• On validation failure, list which fields failed and why, without printing secret values (DB URL credentials, API keys) into the error message.
• Add a redactedConfig() helper safe to log for debugging.

🛠️ Suggested execution

1. Introduce a schema in src/config.ts and validate the parsed env against it at startup.
2. Add a redaction helper that masks known-sensitive fields.
3. Add tests for a malformed value (wrong type/format) producing a redacted, actionable error.

✅ Acceptance criteria

• Malformed (not just missing) env vars fail startup with a clear, field-specific error.
• No secret value ever appears verbatim in a thrown error or log line.
• redactedConfig() output is safe to log.

🔒 Security notes

This directly prevents secret leakage via error messages/logs during misconfiguration, a common accidental-disclosure vector.

📋 Guidelines

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

[Opulencechuks]

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

I am confident that I can implement this issue having worked on similar issues in the past

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

[drips-wave]

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

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

[Jagadeeshftw]

Thanks for applying here. Please also join our Telegram group here: https://t.me/+vTbe0hOUKrFhNTJl. It helps us keep communication clear while we review contributions.

[drips-wave]

This issue has been completed by @Opulencechuks as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Opulencechuks: You earned 100 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.