{"repo":"NousResearch/hermes-agent","public_id":"11466","display_label":"Unicode/UTF-16 surrogate pair splitting bugs and fixes","summary":"Bug reports and fixes across Telegram messaging and desktop cron labels where text truncation incorrectly splits UTF-16 surrogate pairs, causing delivery failures or display issues.","subsystem":"gateway","counts":{"members":4,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":2,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.3933333333333333},"fix_edges":[],"members":[{"kind":"issue","number":11466,"title":"Telegram message splitting can slice UTF-16 surrogate pairs, causing delivery failures","url":null,"state":"closed"},{"kind":"issue","number":11467,"title":"Telegram message splitting can slice UTF-16 surrogate pairs, causing delivery failures","url":null,"state":"closed"},{"kind":"pr","number":11522,"title":"fix(gateway): keep Telegram UTF-16 split points safe after natural break fallback","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#11649","number":11649},{"kind":"pr","value":"#11467","number":11467}],"category":"uncategorized","implication":"needs_llm"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true},{"kind":"pr","number":11649,"title":"fix(telegram): prevent surrogate pair splitting in truncate_message","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#11467","number":11467}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true}],"trust":{"default_tier":"verified","includes_suggested":false}}