fix(desktop): mark truncated group-chat sync payloads

[686f6c61]

What does this PR do?

The Desktop group-chat ui_meta projection sliced each message at 1200 characters with no marker, so a receiving client/bot saw a mid-sentence cut and had no way to know the body continued.

Sync text that exceeds the budget now ends with … [truncated] (kept inside the same 1200-char cap) and sets truncated: true on the projected message. The 48KB envelope bound is unchanged.

This does not raise the per-message cap or switch to incremental full-text delivery — that would be a larger sync-protocol change. Receivers at least know the payload was cut.

Related Issue

Fixes #97373

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

• apps/desktop/src/plugins/hermes-bots/group-chat.ts: compactGroupChatSyncText + stamp truncated
• apps/desktop/src/plugins/hermes-bots/types.ts: optional truncated on GroupMessage
• apps/desktop/src/plugins/hermes-bots/group-chat.test.ts: marker + flag on oversized sync lines

How to Test

cd apps/desktop
npx vitest run src/plugins/hermes-bots/group-chat.test.ts
# 41 passed

Not runtime-tested in a live multi-bot room.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run the targeted vitest file above
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: Linux

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

N/A

[teknium1]

Thanks @686f6c61 — the work in this PR has landed on main via:

• fix(desktop): group chat members and the room mirror say how many earlier messages were omitted (#114341, salvage #114352, #97468) #114968 — fix(desktop): group chat members and the room mirror say how many earlier messages were omitted (Bot Mode group chat: a member's turn silently drops the oldest part of its delta (GROUP_CHAT_HISTORY_LIMIT slice) while the watermark advances past it #114341, salvage fix(desktop): mark the truncated head of a bot group-chat turn delta #114352, fix(desktop): mark truncated group-chat sync payloads #97468) (landed in d99226015dcc)

Your contribution is credited there (cherry-picked authorship / co-author trailer or credit in the PR body; see the linked PR for what was kept and what was trimmed). Closing this one as landed / superseded so the backlog reflects reality. If something in your original diff is still missing on current main, please comment and we'll reopen or follow up.