fix(desktop): stop duplicating active-gateway bots in the multi-source roster

[29206394]

What does this PR do?

Fixes the Desktop BOTS pane listing every bot twice (and more on each refetch) when the desktop's only backend is a remote gateway (#88344).

Root cause

useRoster() merges two sources of truth:

• local = the active gateway's profiles.list (rich rows: ui_meta, last_session)
• union = host.agents() → buildAgentRoster(), which enumerates every registered connection, including the active gateway itself

mergeMultiSourceRoster() matched "rows that belong to the active gateway" with agent.connectionKind === 'local'. On a remote-primary desktop the active gateway reports connectionKind: 'remote', so its own agents fell into the "other source" branch and were appended as phantom duplicates — every bot ×2 at baseline, and the roster kept accumulating copies across refetch/repaint cycles.

Fix

• hermes:agents:roster now returns primaryConnectionId (the registry's primary, i.e. the connection that owns the active gateway).
• mergeMultiSourceRoster() matches union agents to the active gateway by connectionId === primaryConnectionId and annotates the local rows in place instead of appending duplicates.
• Same-named profiles on genuinely separate sources (This device, other remotes) still get their own tagged rows — the @name-device disambiguation rule is preserved.
• When primaryConnectionId is absent (older Electron builds), it falls back to the legacy connectionKind === 'local' rule, so single-source behavior stays byte-identical.

Related Issue

Fixes #88344

Complementary to #88341 (dedupes within the union and reuses canonical chats; this PR dedupes the active gateway across the local/union boundary).

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Tests
• Refactoring only

How to Test

1. node --test src/plugins/hermes-bots/tests/multi-source-roster.test.mjs — 7 passed
2. npm run check:test:plugins — 151 passed
3. npx vitest run electron/connection-registry.test.ts — 43 passed

Manual scenario: remote-only desktop (e.g. connect Desktop to a headless gateway, no local profiles). Open BOTS → every bot appears once; interacting with the app no longer multiplies rows. A local source with the same profile name still shows as a separate @name-device row.

Checklist

• My code follows the project's style guidelines.
• I have performed a self-review of my code.
• I have added tests that prove the regression and expected behavior.
• Type checking passes (project-wide typecheck not run; change is additive and type-local — registry.primary already exists on the registry type).
• I searched existing GitHub issues before opening the focused issue above.
• I kept the change scoped to the BOTS roster merge boundary.
• I manually exercised the packaged Desktop UI (automated coverage only).

[teknium1]

Merged via #88523 — your commit was cherry-picked with authorship preserved (1852092 on main). Your root-cause analysis was exactly right: connectionKind === 'local' misclassified the active remote gateway's own agents, and your primaryConnectionId matching is the shipped base of the fix. #88523 layered a live host.activeConnectionId() override on top (covers the activated-non-primary-source state) plus source-qualified React row keys, and wove in #88341's identity dedup. Thanks for the fast, well-tested fix — first submitter of the root cause.