8.12 - Docs attribute three boot guards to the wrong file

[determined-001]

Complexity: Trivial - 100 Points · type:docs

Milestone: M6 - Ops & rigor

Band lever: none

Context
docs/MAINNET.md:11 and docs/RUNBOOK.md:52 describe the boot-time guards that
refuse to start with a missing or unsafe DEFAULT_SELLER_WALLET,
SERVER_SIGNING_SECRET or JWT_SECRET, and cite apps/api/src/env.ts.

Problem
All three guards live in apps/api/src/services/container.ts (around :385,
:488 and :511), not in env.ts. The guards fire correctly, so this is an
accuracy problem rather than a functional one — but it sends whoever is
verifying or changing a safety check to a file that does not contain it, which
is exactly the wrong outcome for a document read under pressure.

What needs to be done

1. Correct the citations in both documents to container.ts, with line hints.
2. While there, verify the rest of the file:line references in both documents
   still resolve, and fix any that have drifted.

Key files

• docs/MAINNET.md:11
• docs/RUNBOOK.md:52
• apps/api/src/services/container.ts:385, :488, :511 — where the guards are

Done when

• Both documents cite the file that actually holds each guard.
• Every file:line reference in both documents resolves to what it claims.

---

Tracked in ISSUES.md — issue 8.12.

[soladayo21963-coder]

@soladayo21963-coder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign this to me maintainer

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

[acejayl]

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

I'll fix the file attribution in docs/MAINNET.md (line 11) and docs/RUNBOOK.md (line 52) so the three boot-time guards for DEFAULT_SELLER_WALLET, SERVER_SIGNING_SECRET, and JWT_SECRET point at their real location, apps/api/src/services/container.ts (around lines 385, 488, and 511), instead of apps/api/src/env.ts. It's purely a documentation-accuracy fix since the guards already fire correctly, so I'll only touch the references and any surrounding wording that points to env.ts. I'll render-check the Markdown before opening the PR. Happy to take it on.

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

[rahimatonize]

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

Hi, could you please assign me to this issue

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

[drips-wave]

Congratulations, @soladayo21963-coder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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