A cap on the catalog's NVMe size: above it only the tail and the stored ranges

After reset 24 the catalog grew ~3.7 GB an hour (77 GB, root 31 GB free, 600k
history ranges to go). CATALOG_MAX_NVME_GB (as voyager 1's
BACKFILL_MAX_NVME_GB): once the default tablespace is over it, leases and the
prefetcher take priority < 0 only (the tail, the stored ranges); measured once
a minute. Off when unset; 90 on homelab.

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

config/coordinator.ts

@@ -77,6 +77,11 @@ export default {
     /** BODY commands in flight per connection (pipelined; XoverClient.bodies). */
     pipeline: env.get('PROBE_PIPELINE', 8),
   },
+  /**
+   * The catalog's tablespace may grow to this many GB (app/services/catalog_space.ts); above it only the tail and
+   * the stored ranges are leased and prefetched. 0: no cap.
+   */
+  catalogMaxNvmeGb: env.get('CATALOG_MAX_NVME_GB', 0),
   /**
    * Spotnet spots (app/services/spotter.ts, spot_inspector.ts): the group the spots are posted in, how many of
    * its last articles the spotter reads the first time (~215 spots a day: ~3 months), how often it looks again,