Fix remaining OSINT signal text truncation

[schergr]

Summary

• Remove 120-char truncation in delta engine when building OSINT signals
• Remove 80-char truncation in memory snapshots for urgent Telegram posts
• Remove 120-char truncation in ideas/LLM context for OSINT posts
• Improve signal formatting in Telegram alerts (bulleted list instead of inline)

The prior fix (753c676) removed truncation at source ingestion and alert formatting, but signals were still arriving at the alerter pre-truncated from upstream. The sendMessage chunker already handles Telegram's 4096-char API limit.

Test plan

• Trigger a sweep with urgent OSINT posts and verify full text appears in Telegram alert
• Confirm alert messages are properly chunked if they exceed 4096 chars
• Verify delta engine correctly deduplicates signals with full-length text

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR removes remaining upstream truncation of urgent Telegram/OSINT signal text so full post content can flow through delta computation, memory snapshots, LLM context, and Telegram alert rendering (with improved “Signals” formatting).

Changes:

• Removed substring/slice truncation in Telegram source ingestion, delta engine signal construction, and memory snapshot compaction.
• Updated LLM “ideas” sweep compaction to include full urgent OSINT post text.
• Improved Telegram alert formatting for signals (more items + bulleted list output).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
lib/llm/ideas.mjs	Stops truncating urgent OSINT post text included in LLM ideas context.
lib/delta/memory.mjs	Stores full urgent post text in compacted memory snapshots.
lib/delta/engine.mjs	Emits full urgent post text in newly-detected OSINT signals.
lib/alerts/telegram.mjs	Expands/reshapes OSINT signal text shown in alerts and formats signals as bullets.
apis/sources/telegram.mjs	Stops truncating Telegram message text extracted via Bot API and web preview parsing.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[calesthio]

Thanks for opening this. The direction makes sense, but there are two issues I think should be fixed before this is merged:

1. Telegram alert formatting now sends full raw OSINT post text through parse_mode: Markdown without escaping. In the rule-based OSINT surge path, evaluation.signals can now contain full Telegram post bodies, and _formatTieredAlert() renders them as bullet lines. Real post text commonly contains _, brackets, parentheses, and similar Markdown-significant characters. That means alerts can render incorrectly or be rejected by the Bot API altogether. Please either escape Markdown-sensitive characters before formatting or send this section without Markdown parsing.

2. The ideas LLM context no longer has a length bound for urgent OSINT posts. Keeping full text in storage/delta/memory is reasonable, but compactSweepForLLM() is supposed to stay compact and now it can be dominated by a handful of long Telegram posts. That creates regression risk for latency, cost, and provider-side input-limit failures. Please keep full text upstream, but add an overall size/token cap when building the ideas prompt.

Once those two are addressed, this looks much closer to mergeable.

[schergr]

anything else you need?

[calesthio]

Added a follow-up commit on top of this branch to close the remaining review issues:

• switched broad OSINT dedup in lib/delta/engine.mjs to prefer stable post identity (postId, or channel/chat + date + text) instead of only the lossy semantic hash
• preserved channel/post identity in lib/delta/memory.mjs so cross-run dedup has enough information to suppress exact reposts without hiding genuinely new updates
• aligned signal escaping in lib/alerts/telegram.mjs with the bot's existing legacy Markdown parse mode instead of MarkdownV2-style escaping

Rechecked the branch after the patch: sweep still completes, dashboard inject still runs, the new-post dedup false negative is fixed, and this stays scoped to Telegram/delta/ideas paths without touching jarvis core UI code.

[calesthio]

Reviewed the updated branch including the follow-up fix commit. The truncation removal adds real value, and with the dedup identity + Markdown escaping fixes in place I don’t see a remaining blocker.

[schergr]

This PR is ready to merge — can you merge it when you get a chance? We're currently running the unpatched code on master.