fix: 1874 network connectivity UI

[dhru7777]

Summary

• Drive header green/grey dot from listSessions.status instead of stored networkId
• Drive Networks CONNECTED badge from session.status === 'connected'
• Fixes Indicate network connectivity in User UI #1874

Test plan

• Unit tests cover connected vs disconnected listSessions status
• LocalNet + healthy /v2/version → green dot + CONNECTED badge
• Ledger unreachable → grey / no CONNECTED

Screenshots

Ledger Health Check Status

Green Dot

Ledger Health Check Failed - Grey Dot

[mjuchli-da]

@dhru7777 thank you for the contribution. It looks good.
Do you mind rebasing (resolving the conflicts)? Also note that the e2e test failed. This is likely due to the dapps expecting a different (still wrong) network state.

[dhru7777]

Yes, I’ll get it done. Thankyou

…

On Wed, Aug 5, 2026 at 7:45 AM Marc Juchli ***@***.***> wrote: ***@***.**** commented on this pull request. @dhru7777 <https://github.com/dhru7777> thank you for the contribution. It looks good. Do you mind rebasing (resolving the conflicts)? Also note that the e2e test failed. This is likely due to the dapps expecting a different (still wrong) network state. — Reply to this email directly, view it on GitHub <#2211?email_source=notifications&email_token=BPUJQ6Q7725V7BIACWQLYGT5IMM6HA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOBWGM4TONBVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#pullrequestreview-4863974591>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPUJQ6SHQHNFKMSTTQGMT4T5IMM6HAVCNFSNUABFKJSXA33TNF2G64TZHM4TSMZTGM2DEMBSHNEXG43VMU5TKMBSGE3DSMZZGY32C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BPUJQ6RWLAN64CU3IE2OBXT5IMM6HA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOBWGM4TONBVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BPUJQ6WE4SXHWQC67GYA7KT5IMM6HA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOBWGM4TONBVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[dhru7777]

Thanks for the review

Rebase

Rebased onto latest main and resolved the conflict in wallet-gateway/remote/src/web/frontend/index.ts by keeping both:

• upstream multi-session support (currentOrigin / detectCurrentOrigin)
• this PR’s connectivity fix (networkConnected from listSessions → status === 'connected')

About the e2e failures

I investigated the earlier ping-e2e failures and also ran the suite locally.

Local run (Canton + gateway + mock OAuth + ping, with CI_SECRET_DEPENDENCY=false to mirror fork PR CI / skip external-signing specs):

• 16 passed, including the core flows most relevant to this change:
  • connection status handling edge cases (Chromium + Firefox)
  • reconnect / popup / wallet picker
  • most settings tests
• 2 failed, and they look flaky / unrelated to the connectivity UI change:
  1. multisession.spec.ts — failed only on Chromium (stuck on OAuth /callback, never reached /parties); passed on Firefox
  2. One Firefox settings IDP test — dApp stayed on Loading... after connect; same test passed on Chromium

Those failure modes are OAuth callback / connect-settle races, not assertions on the header/network “CONNECTED” badge. This PR only drives that badge from listSessions[].status (aligned with the Settings sessions UI) and does not gate login, callback navigation, or dApp connect.

Regarding your note that dapps may still expect the old (wrong) network state: the dApp’s isConnected is the RPC connect result, which is separate from the gateway ledger-connectivity badge. Locally, the connect/disconnect edge-case e2e passed on both browsers after this change.

Happy to dig further if CI still fails on the rebased commits, or if you’d prefer a follow-up for hardening the flaky multisession/settings paths.

---