SettlementsPanel's available-liquidity data is fetched once on mount and never refreshed after settlement actions

[Jagadeeshftw]

📌 Description

SettlementsPanel (src/components/SettlementsPanel.tsx) fetches pools via a dedicated useEffect(() => { ... fetchPools(...) ... }, []) with an EMPTY dependency array, storing the result in pools state and deriving availableLiquidity from it via useMemo. This availableLiquidity is passed into SettlementForm to validate a proposed amount against real liquidity (SettlementForm's validate() rejects an amount exceeding availableLiquidity[asset]). However, opening, executing, or cancelling a settlement (open/runSettlementAction) never re-triggers this pools fetch — only the settlements list itself is reloaded/patched. After a settlement reserves or releases liquidity, pools/availableLiquidity keeps showing the figures from whenever the panel first mounted, so the client-side "Amount exceeds available liquidity" check can pass or fail based on stale numbers that no longer match the backend's actual liquidity state.

🧩 Requirements and context

• Re-fetch pools (or otherwise refresh availableLiquidity) whenever a settlement action that plausibly changes liquidity succeeds — at minimum after open() (which reserves liquidity) and after cancelSettlement (which releases it).
• The refresh should not block or visually disrupt the settlements list/table; it can run in the background the same way the initial pools fetch does.
• This is a client-side-only validation aid — the backend remains the source of truth and will still reject an over-limit amount regardless of this fix; the goal is keeping the friendlier client-side check reasonably fresh.

🛠️ Suggested execution

• Extract the pools-fetching logic in src/components/SettlementsPanel.tsx into a reusable function (or reuse useAsync's reload/refresh) that can be called both on mount and after a settlement action settles successfully.
• Call that refresh after open()'s run(...) succeeds and after a successful cancelSettlement via runSettlementAction.
• Extend src/components/SettlementsPanel.test.tsx with a test asserting fetchPools is called again after opening (or cancelling) a settlement, not just once on mount.

✅ Acceptance criteria

• availableLiquidity is refreshed after settlement actions that change liquidity, not only once on mount.
• The refresh happens silently, without disrupting the visible settlements table.
• Test coverage for the refresh being triggered by a settlement action.

🔒 Security notes

No new attack surface; the backend remains authoritative — this only keeps a client-side convenience check from going stale.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[github-actions]

Thanks for the interest, @martinshub-tech! You currently have 6 assigned issues in this repo with no PR up yet, which is the cap (6) for this project. Please open a PR for one of them (or release it) before taking on another — issues you've already submitted a PR for don't count against this.

[MerlinTheWhiz]

Hello, I'm MerlinThewhiz, a software engineer with a strong background in smart contract, and a couple years in my arsenal. Having read the task requirement, I'd love to work on this issue. Please assign.

[Jagadeeshftw]

Assigned @MerlinTheWhiz to this issue. Please open a PR referencing this issue (e.g. Closes #256) when you're ready. If you have questions along the way, feel free to join our contributor chat: https://t.me/+vTbe0hOUKrFhNTJl

[grantfox-oss]

🦊 GrantFox — @MerlinTheWhiz 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 #256)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.