Summary��emit a client error to Sentry with a scoped tag.��## 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��- Structured logs only (key=value or JSON) — no
ree-
orm strings.�- Never log secrets, tokens, or
ull request bodies.�- Emit at INFO
or li
ecycle events, WARN
or recoverable, ERROR only when the caller cannot proceed.��## 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: logging · Campaign: GrantFo
OSS · O
icial Campaign | FWC26 · Maybe Rewarded
Summary��emit a client error to Sentry with a scoped tag.��## 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��- Structured logs only (key=value or JSON) — noree-
orm strings.�- Never log secrets, tokens, or
ull request bodies.�- Emit at INFO
or li
ecycle events, WARN
or recoverable, ERROR only when the caller cannot proceed.��## 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 testbeore pushing.�- Money amounts must
low as integer minor units through the UI — never as
loats. Invoice totals are
i 28on-chain; the client should model them asbigintandormat at the edge.�- Wallet integration goes through
@stellar/ reighter-api; do not readrom
window. reighterdirectly.�- The@/lib/qlclient wraps every on-chain read; do not callsoroban-sdkrom 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 reviewrom a
CODEOWNERSmaintainer.�4. PRs that close this issue and pass review may qualiy
or a reward — see the
MAYBE REWARDEDlabel and the FWC26 campaign page.��---��Category:logging· Campaign: GrantFoOSS · O
icial Campaign | FWC26 · Maybe Rewarded