[Frontend] Borrower loans live under two disjoint query-key namespaces, so mutations/streams invalidate only one and leave the other stale

[grantfox-oss]

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

Why this matters

useBorrowerLoans uses queryKeys.borrowerLoans.byAddress -> [borrowerLoans, addr] (useApi.ts:1187) while useBorrowerLoansPage uses queryKeys.loans.borrowerPage -> [loans,borrower,addr,params] (useApi.ts:1221). These are disjoint prefixes. useCreateLoan invalidates only [loans] (useApi.ts:870) -> hits borrowerPage but misses byAddress; useRepayLoan (useApi.ts:1557) and useLoanStream (useLoanStream.ts:43) invalidate only byAddress -> miss the paginated borrowerPage list. Result: after creating/repaying, one of the two borrower lists shows stale data until staleTime expires.

Acceptance criteria

• Unify borrower-loan caching under a single key namespace, or have every borrower-loan mutation/stream invalidate both keys
• useCreateLoan should also invalidate queryKeys.borrowerLoans.byAddress for the borrower
• useRepayLoan/useLoanStream should also invalidate the borrowerPage key

Files to touch

• frontend/src/app/hooks/useApi.ts
• frontend/src/app/hooks/useLoanStream.ts

Out of scope

• Pagination cursor design

[Killerjunior]

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

I would love to work on this.

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

[wheval]

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

Hello i would love to work on this.

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

[Thoni76]

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

Please assign . you will get a pr today

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Thoni76 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.

[drips-wave]

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

🧑‍💻 @wheval: 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 — @wheval has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.