TruncatedReply: a compressed reply the server cut at a ".\r\n" fails in 2 s; ranges:dates samples plain

Eweka stops a compressed XOVER reply at the first ".\r\n" in its own
output (78 01 2e 0d 0a and nothing more), which some small replies begin
with; the text path waited for more until the reply timeout. ranges:dates
uses plain connections of its own instead of the pool.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

REBUILD.md

@@ -247,7 +247,10 @@ corpus filtered this way no longer serves a sweep of those two rules.
 Windows by posting time (2026-10-25; voyager 3's test data, LOG.md (104)):
 `ranges:dates` samples when each active group's articles were posted (one
 XOVER of 32 articles every 500M articles of the group, 16 … 1000 samples,
-the median Date of each slice, kept monotone; `group_dates`) and estimates
+the median Date of each slice, kept monotone; `group_dates`; over plain
+connections: Eweka cuts a compressed reply at the first ".\r\n" in its
+output, which some small replies begin with, `TruncatedReply`, LOG.md
+2026-10-25 (105)) and estimates
 every range's posting date from the curve (`ranges.est_date`; the edges of
 a window are off by up to one sample interval, three weeks in boneless).
 `ranges:capture --from 2025-01-01 --to 2026-01-01` marks every active