The durable field log's experiment 6 section stopped at 1.4 hours elapsed while the run is at 55, so it was missing everything learned since -- including its own closing advice going stale. "Judge health by sustained bandwidth, not repos/s" is right in the head of the distribution and WRONG past it. Once request-bound rather than bytes-bound, repos/s climbs while bytes/s falls, so a bandwidth projection reads backwards: it shows the run slowing while it is 13x faster than at hour 1 (3.43 -> 45.0 repos/s). Extended the throughput table to hour 55 and said where the rule expires. Records the rest of the run: - the denominator trap: sum(stream_backfill_repos_durable) is enumeration progress, +100,000 per batch, 132,000 -> 3,200,002 and never settling. Dividing by it produced a confident "92.7% done" at under half. The real denominator is ~5,716,765 from indigo's account_repo; hour 55 is 53.1%. The pending bucket is frozen at 103,077 and inert. - envelope 48h -> 72h -> 120h, extended in place by writing /etc/stream-watchdog/deadline rather than a Terraform replace, with the drift that leaves and why arm_watchdog.sh is not the tool. - 32 restarts, cause is the batch boundary not the firehose and not OOM (exactly one real oom-kill all run). Interval is batch size / crawl rate, which is why "every 3.5 h" became ~45 min. The restart is load-bearing: each fresh process admits the next 100,000. - resident blooms are 39.5 GiB of 41.3 GiB RSS (~96%), upstream fixed this at f02919c and states it is not a format change; plus the 4.5 min startup it causes every 45 min, ~10% of wall time. That revises the restart bug's cost from ~60 s to ~4.5 min per occurrence. - state at hour 55: still phase=1, so merge and cutover remain unexercised at full-network scale. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>