m3taversal 9e42c34271 fix: TG message batching — group by chat_id + time proximity ... Root cause: _group_into_windows never checked time gaps or chat_id. All messages went into one stream, capped at 10 per window. 120 msgs from one chat → 12 windows → 12 source files → 12 extraction branches. Fix: - Group by chat_id first (different chats = different windows always) - Split on actual time gaps (>window_seconds between messages) - Cap at 50 messages per window (not 10) - Consolidate substantive windows from same chat into one source file at triage time (one source per chat per triage cycle) 6 tests in tests/test_tg_batching.py. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-31 13:19:35 +01:00
..
bot.py	fix: TG message batching — group by chat_id + time proximity	2026-03-31 13:19:35 +01:00
kb_retrieval.py	feat: two-pass retrieval with sort order and graph expansion	2026-03-28 22:34:45 +00:00
market_data.py	epimetheus: sync VPS-deployed code to repo — Mar 18-20 reliability + features	2026-03-20 20:17:27 +00:00
teleo-telegram.service	epimetheus: source archive restructure — inbox/queue + inbox/archive/{domain} + inbox/null-result	2026-03-18 11:50:04 +00:00
worktree_lock.py	epimetheus: sync VPS-deployed code to repo — Mar 18-20 reliability + features	2026-03-20 20:17:27 +00:00
x_client.py	epimetheus: fix article content parsing — contents[] array, not text field	2026-03-23 15:30:59 +00:00
x_search.py	epimetheus: direct tweet lookup via /tweets?tweet_ids= endpoint	2026-03-23 15:17:11 +00:00