[Docs] INDEXER_HEALTH_LAG_LIMIT and PORT are read by the backend but documented nowhere

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

INDEXER_HEALTH_LAG_LIMIT is consumed in backend/src/app.ts:204-205 and PORT in backend/src/index.ts:36, but neither appears in backend/.env.example nor in docs/ENVIRONMENT.md. check-env-docs.mjs only compares .env.example keys to the doc, so code-only env vars are never flagged.

Acceptance criteria

• Add INDEXER_HEALTH_LAG_LIMIT (default 100) and PORT (default 3001) to docs/ENVIRONMENT.md
• Add both to backend/.env.example with their defaults and a comment

Files to touch

• docs/ENVIRONMENT.md
• backend/.env.example
• backend/src/app.ts
• backend/src/index.ts

Out of scope

• Build-time GIT_SHA/BUILD_TIME (already documented in code comments)

[mordabdul1]

Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.

[mordabdul1]

Hello, this issue aligns well with my skill set and I’m confident I can resolve it properly. Please assign it to me.

[dhareymu]

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

Maintainer, abeg gimme this project 🙏🙏😭😭

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

[Georgechisom]

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

Hi, I have reviewed this issue and am familiar and skilled to solve this issue, kindly assign it to me

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

[itzabdoull]

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

Hi maintainer! Can I work on this issues?

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @Georgechisom has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1212)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Georgechisom's PR #1266 was approved and merged by @ogazboiz.

🏆 @Georgechisom: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (471 total points). Track your full progress on GrantFox.

👏 Great work, @Georgechisom! Keep contributing to LabsCrypt.