Bring TODO.md Status and Next Step to the run in progress (closes #251)

Status and Next Step described the 24-hour run of 9bd0e91, whose outcome
was posted on issue 226 on 3 November. They now describe the run of
e58c663 on issue 232 and what its outcome reports. Two Completed Steps
entries of 10 November are rewritten: the ProtonVPN entry ran past 30
words, and the busy-host test entry referred to waits it had not named.
An entry for this read is added.

Model: fable-5-1

TODO.md

@@ -22,37 +22,46 @@ formatting of the Go code and the markdown. Then it builds the image.
 The image sets memory ceilings for a 5 GiB container (README "Memory"). README
 "Running under upaas" says how to run it.
 
-A five-day run of `1c65656` on the live feed, from 2026-10-27 to 2026-11-01,
+Since 2026-10-27, `next` has run on the live feed five times, from three hours
-found three problems:
+to five days. The runs found the handlers dropping updates for five causes, and
+the WHOIS fetcher asking a registry that had refused it. Each is fixed on
+`next`, and its Completed Steps entry below names its issue. A 21-hour run of
+`742e759`, which has every fix but one, dropped no update except after the feed
+stalled. That cause, https://git.eeqj.de/sneak/routewatch/issues/229, is fixed
+on `next`.
 
-- The prefix handler dropped updates while a peer's session went down
+A 24-hour run of `e58c663` on the live feed began at 09:19 UTC on 2026-11-10
-  (https://git.eeqj.de/sneak/routewatch/issues/216).
+(https://git.eeqj.de/sneak/routewatch/issues/232). It reads whether any handler
-- The AS handler dropped updates when the feed burst
+drops an update, the size of the `origin_changes` table on disk, and the
-  (https://git.eeqj.de/sneak/routewatch/issues/217).
+process's peak memory against 5 GiB. The seven IP lookup additions of
-- The WHOIS fetcher kept asking a registry that had refused it
+https://git.eeqj.de/sneak/routewatch/issues/203 landed after it began, so it
-  (https://git.eeqj.de/sneak/routewatch/issues/218).
+does not exercise them.
-
-All three are fixed on `next`. So is
-https://git.eeqj.de/sneak/routewatch/issues/222, which the third fix brought up.
-A run of `26d939a` on the live feed showed the prefix handler still dropping
-updates while the home page's cards were worked out.
-https://git.eeqj.de/sneak/routewatch/issues/226 fixed that on `next`.
-https://git.eeqj.de/sneak/routewatch/issues/225, also on `next`, takes the peers
-whose sessions go down together out of the table in one walk. A 24-hour run of
-`9bd0e91` on the live feed is checking whether any handler still drops updates.
 
 The order of the project's remaining work is kept on
 https://git.eeqj.de/sneak/routewatch/issues/86.
 
 # Next Step
 
-Post the outcome of the 24-hour run of `9bd0e91` on
+Post the outcome of the 24-hour run of `e58c663` on
-https://git.eeqj.de/sneak/routewatch/issues/226: whether any handler still drops
+https://git.eeqj.de/sneak/routewatch/issues/232. The run lasts 24 hours, or
-updates, and the process's peak memory against 5 GiB. File an issue for each
+until the feed has stalled or reconnected once, up to 72 hours. The outcome
-problem the run finds.
+says:
+
+- whether any handler dropped an update, and the prefix queue's high-water mark
+- the held-back count
+- the size of the `origin_changes` table on disk
+- the process's peak memory against 5 GiB
+
+File an issue for each problem the run finds.
 
 # Completed Steps
 
+- 2026-11-10: `README.md` and this file are read whole against the rules of
+  https://git.eeqj.de/sneak/routewatch/issues/157, and every statement is
+  checked against the code on `next`. Four README sentences, on origin changes,
+  PTR lookups and geolocation, are rewritten. Status and Next Step describe the
+  live-feed run in progress (closes
+  https://git.eeqj.de/sneak/routewatch/issues/251).
 - 2026-11-10: each result of the IP lookup has `geo`, where the address is. It
   comes from geojs, with DB-IP's City Lite database as the fallback. The geojs
   answers stay in memory and in `cache.db` for 7 days (closes
@@ -60,16 +69,17 @@ problem the run finds.
 - 2026-11-10: the IP lookup checks the `icloud_private_relay` list of Apple's
   iCloud Private Relay networks, downloaded once a day. Each result has
   `flags.is_relay` (closes https://git.eeqj.de/sneak/routewatch/issues/237).
-- 2026-11-10: the IP lookup checks the `protonvpn` list of ProtonVPN's /24
+- 2026-11-10: the IP lookup checks two ProtonVPN lists from a public mirror of
-  networks and the `protonvpn_entry` list of its servers' IPv4 and IPv6
+  Proton's server list. `protonvpn` holds the /24 networks of ProtonVPN's
-  addresses, from a public mirror of Proton's server list (closes
+  servers, and `protonvpn_entry` holds the servers' IPv4 and IPv6 addresses
-  https://git.eeqj.de/sneak/routewatch/issues/236).
+  (closes https://git.eeqj.de/sneak/routewatch/issues/236).
 - 2026-11-10: the IP lookup finds PTR names over DNS-over-HTTPS and caches them
   for the record's TTL, in memory and in `cache.db` (closes
   https://git.eeqj.de/sneak/routewatch/issues/238).
 - 2026-11-10: the tests no longer fail when a busy host stalls for several
-  seconds. Most such waits are now 15 seconds. The test of the stream's idle
+  seconds. Most waits for something that should happen are now 15 seconds. Tests
-  timeout runs on a fake clock (closes #240)
+  that depend on a short idle timeout or a request limit run on a fake clock
+  (closes https://git.eeqj.de/sneak/routewatch/issues/240)
 - 2026-11-10: the IP lookup checks the public VPN server lists of Mullvad,
   NordVPN, Private Internet Access and IVPN, and X4BNet's community list. Each
   result has `flags.is_vpn` and `vpn_providers` (closes