Config: expose the Sentry DSN as a runtime env

[Baskarayelu]

Summary��e

pose the Sentry DSN as a runtime env.��## Background��We want to keep the invoice-lending
rontend (dashboard
or suppliers / investors) auditable and sa
e to change. Landing this issue tightens one speci
ic corner and gives reviewers a clear di

to reason about rather than a general "cleanup" commit. It should be scoped small enough to close in a single PR.��## Acceptance criteria��- [ ] The change matches the summary above.�- [ ] Tests cover the new behavior (happy path + one e
plicit
ailure mode).�- [ ] Lint, type-check, and tests all pass locally.�- [ ] PR description re
erences this issue with Closes #<this-issue>.��## Implementation hints��- Sane de
ault
irst, environment override second.�- Any new env var must be documented in .env.e ample and any deploy README.�- Do not read env vars deep inside business logic — inject through a con
ig module.��## Repo-speci
ic notes��- Ne
t.js/TypeScript app. This repo is early-stage — i
the sca

old isn't in place yet, add it in a preparatory commit be
ore the
eature commit.�- Standard tooling: npm ci, npm run lint, npm run typecheck, npm test be
ore pushing.�- Money amounts must
low as integer minor units through the UI — never as
loats. Invoice totals are i 28 on-chain; the client should model them as bigint and
ormat at the edge.�- Wallet integration goes through @stellar/ reighter-api; do not read
rom window. reighter directly.�- The @/lib/ql client wraps every on-chain read; do not call soroban-sdk
rom component code.��## Out o
scope��- Unrelated re
actors in adjacent
iles.�- Stylistic-only changes (
ormatting, renaming) that are not required by the
i
.�- Anything beyond the acceptance criteria above; sur
ace
ollow-ups as separate issues.��## How to claim and submit��
. Comment on this issue saying you'd like to take it on; wait
or a maintainer to assign you (avoids duplicated e

ort).�2. Open a PR that re
erences this issue (Closes #<this-issue>).�3. Make sure CI is green and request review
rom a CODEOWNERS maintainer.�4. PRs that close this issue and pass review may quali
y
or a reward — see the MAYBE REWARDED label and the FWC26 campaign page.��---��Category: con ig  ·  Campaign: GrantFo
OSS · O

icial Campaign | FWC26 · Maybe Rewarded

[Jagadeeshftw]

Hi, I’d love to take on this issue! With my expertise in Rust, Stellar, and smart contract development, I can implement a clean and efficient solution.

🚀 Why Me?

• Proven Blockchain Experience – Hands-on work with Stellar, Solidity, and Rust, building secure and optimized smart contracts.
• Open Source Contributor – Actively contributed to 50+ open-source projects, showcasing adaptability and collaboration.
• Efficient & Reliable – I deliver high-quality, production-ready solutions quickly, ensuring security and scalability.

⏱ Timeline

I estimate completing this within 24 hours. Let me know if I can proceed!

[grantfox-oss]

🦊 GrantFox — @Jagadeeshftw has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[Baskarayelu]

You've got it, @Jagadeeshftw. Reminder: Closes #139 in the PR description. Real-time help lives at https://discord.gg/WC53JxDqx.

[Jagadeeshftw]

Already implemented and merged via #160 (feat: expose SENTRY_DSN as a runtime env var via lib/config) — lib/config.ts reads process.env.SENTRY_DSN, it's documented in .env.example, and lib/config.test.ts covers both the set and unset cases. Closing as a duplicate of already-completed work.