Not retrying sync even when network is online again (rtc-state: close)

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I suspended the computer and resumed today. I left Logseq running.

I found the network recognized to be "online", but sync seem to be stopped completely. There is not even a sync status indicator (green or orange dot).

### Reproduce the Bug

0. Have Logseq running
1. Suspend Computer
2. Resume Computer
3. Check Sync status

### Expected Behavior

Sync should be regularly retried when network is online. No manual intervention should be needed when sync can work technically.

### Screenshots

It synced again after clicking "Start Sync":

### Files

I have sent db-worker-node logs by e-mail.

Issue state:

```
{:pending-local-ops 1,
:local-tx 1244,
:remote-tx 1244,
:rtc-state :close}
```

At the same time on android with working sync:

```
{:pending-local-ops 0,
:local-tx 1500,
:remote-tx 1500,
:rtc-state :open}
```

The issue state seem to be displayed by `:rtc-state :close`.

### Browser, Desktop or Mobile Platform Information

NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260623

### Additional Context

Similar behavior to https://github.com/logseq/db-test/issues/780, but there the sync status is shown.

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

No source files, tests, or entry points are named. First reproduce the suspend-and-resume sequence on the reported NixOS desktop, then inspect the sync status around the reported `:rtc-state :close` value and compare it with the working Android state. Done means sync retries automatically after the network is online and the status indicator returns without clicking “Start Sync”.

Written by the indexing model from the issue text.