[Ason-Lee]

What does this PR do?

Keeps ordinary Desktop session lists and the currently open persisted transcript synchronized across multiple Desktop clients connected to the same remote gateway.

The gateway does not currently broadcast another client's session-list or ordinary transcript writes into each renderer websocket. A visible remote Desktop now reconciles the backend-owned session list every two seconds, and also refreshes the selected ordinary Desktop transcript every two seconds when the receiving client is idle. New chats and completed cross-client turns therefore appear without a manual reload or navigating away and back.

The polling paths are scoped to remote connections, visible documents, and the active connection/profile. Session-list requests reject stale responses after connection changes. Open-transcript requests coalesce while in flight, skip local streaming/busy state, re-check session identity before publishing, and signature-gate unchanged transcripts.

Related Issue

No existing issue or PR found for this behavior.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• Add visible two-second session-list reconciliation for remote Desktop connections.
• Add visible two-second reconciliation for the open ordinary Desktop transcript on remote shared gateways.
• Reuse the existing persisted-transcript hydration path for local and messaging sessions while preserving local assistant errors.
• Skip active-transcript publication while the receiving client is busy, and reject responses after session/runtime switches.
• Coalesce slow transcript and session-list requests so timer ticks never overlap.
• Key session-list poll ownership by remote gateway URL and profile so remote-to-remote switches invalidate stale responses.
• Preserve the dedicated cron and messaging polling cadences.
• Add regression tests for remote polling, local exclusion, in-flight coalescing, gateway invalidation, stale-response rejection, and cron-side-effect suppression.

How to Test

1. Connect two Hermes Desktop clients to the same remote gateway and profile.
2. Create and send a new ordinary Desktop chat from client A.
3. Verify client B shows the new session in its sidebar within two seconds without a manual reload.
4. Open the same completed conversation on both clients.
5. Send a new turn from client A and leave client B on the open conversation.
6. Verify client B displays the persisted turn within two seconds without navigating away and back.
7. Verify a local-mode Desktop does not perform the two-second ordinary chat polls.
8. Switch client B to another session or remote connection while a refresh is pending and verify stale messages/rows are not applied.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs and issues to make sure this isn't a duplicate
• My PR contains only changes related to this fix
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes
• I've tested on macOS with two Desktop clients sharing a Tailscale-restricted remote gateway

Python tests could not start because the existing project venv does not include pytest. This change is limited to Desktop TypeScript. The relevant Desktop checks passed:

• npm run test:ui: 1,792 passed, 1 skipped
• active transcript and polling targeted regression tests: 20 passed
• npm run typecheck
• ESLint on the modified Desktop files
• npm run pack
• git diff --check
• static security scan
• real MacBook → iMac open-transcript reconciliation without navigation
• independent fail-closed review

Documentation & Housekeeping

• Documentation update: N/A
• cli-config.yaml.example: N/A
• CONTRIBUTING.md / AGENTS.md: N/A
• Cross-platform impact considered: renderer-only timers, fetch coordination, and nanostore state; no platform-specific APIs
• Tool descriptions/schemas: N/A

Screenshots / Logs

Not applicable. The regression is cross-client timing. Hook tests cover polling and overlap behavior, and the packaged app was verified with two live Desktop clients.

[teknium1]

Thanks for addressing cross-client Desktop consistency. The ordinary active-transcript gap is still present on current main: apps/desktop/src/app/contrib/hooks/use-background-sync.ts:358-375 only refreshes persisted transcripts for messaging sessions.

Problems

• The PR's two-second remote polls were written before current main's event-driven change watcher. tui_gateway/server.py:3060-3123 now broadcasts sessions.changed for shared state.db writes, and apps/desktop/src/app/contrib/hooks/use-background-sync.ts:299-338 already coalesces that signal into sidebar-list refreshes. Adding unconditional remote polls would duplicate that work on event-capable gateways.

Suggested changes

• Rework the active ordinary-transcript refresh to subscribe to $sessionsChangeTick, retaining the PR's idle/staleness guards.
• Keep a polling fallback only for gateways without change_events, mirroring the compatibility split used for messaging transcripts at apps/desktop/src/app/contrib/hooks/use-background-sync.ts:358-386.

This is an automated hermes-sweeper review.