Seed: finished ranges marked done; relay XOVER timeout 10 minutes

- A range reported to its end but not finished (its node went away at
  the very end) was leased again with start past end; nodes asked for
  "from 49208000000 to 49207999999", got 400, and the range failed after
  five leases. The orchestrator now marks such ranges done before
  leasing, and runRange reports them done without fetching.
- Some old ranges come so slowly that one XOVER of 20k headers takes over
  two minutes: five ranges failed on "NNTP reply timed out". The relay
  pool's timeout is SEED_NNTP_TIMEOUT_MS (default 10 minutes, the node's
  HTTP timeout).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

app/services/SeedFetchPool.ts

@@ -61,7 +61,7 @@ class SeedFetchPool {
             servername: nntpConfig.tlsServername,
             user: nntpConfig.user,
             password: nntpConfig.password?.release(),
-            timeoutMs: nntpConfig.commandTimeoutMs,
+            timeoutMs: indexerConfig.seed.nntpTimeoutMs,
             compress: true,
           })
           return { client, usedAt: Date.now() }

app/services/SeedOrchestrator.ts

@@ -60,6 +60,12 @@ class SeedOrchestrator {
    */
   async lease(nodeId: number): Promise<SeedLease | null> {
     if ((await BackfillService.room()) !== true) return null
+    // Fully reported but never finished (the node went away at the very end): nothing left to fetch.
+    await db.rawQuery(
+      `UPDATE seed_ranges SET status = 'done', done_at = now(), node_id = NULL
+       WHERE next_id > end_id AND (status = 'queued' OR (status = 'leased' AND heartbeat_at < now() - make_interval(secs => ?)))`,
+      [LEASE_TTL_SECONDS]
+    )
     // Ranges that broke node after node stop being handed out.
     await db.rawQuery(
       `UPDATE seed_ranges SET status = 'failed', error = coalesce(error, 'lease expired too often')