Add ProcessEnv type interface for environment variables

[AbelOsaretin]

What

Environment variables are accessed via process.env.VARIABLE with no type safety. Typos produce undefined silently.

Why

A typed interface prevents typos and documents which env vars are available.

Scope

• Create a ProcessEnv interface extending NodeJS.ProcessEnv
• Declare all expected env vars with types
• Use the interface throughout the codebase

Acceptance Criteria

• src/types/env.d.ts or similar with ProcessEnv interface
• All env vars typed (string, optional/required)
• No process.env.VARIABLE without type checking
• IDE autocomplete for env vars

Technical Context

• Env vars used: PORT, FRONTEND_URL, STELLAR_NETWORK, RPC_URL, ADMIN_SECRET_KEY, PROJECT_REGISTRY_CONTRACT_ID, ADMIN_API_KEY
• TypeScript declaration merging for NodeJS.ProcessEnv

[pimaster900]

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

I would sincerely love to work on this issue because I have strong experience in working and dealing with complex workflow logic.

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

[Chinonso-Peter]

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

Can i work on this

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

[Gbemi-programmer]

@Gbemi-programmer 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, I have read the requirements and can deliver a good Pr that satisfy this issue condition.

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

[chigozzdevv]

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

Hello, good day! I’d like to work on this issue.
I’ll add the NodeJS.ProcessEnv declaration with all required and optional variables, update environment access across the backend, and ensure TypeScript catches unknown or unsafe values.
I’d appreciate being assigned to the issue.

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

[drips-wave]

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

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

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