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: at least 24 hours, then on until the feed stalls or
reconnects, up to 72 hours, 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.
The PTR entry defines TTL. An entry for this read is added.

Model: fable-5-1

README.md

@@ -197,8 +197,9 @@ also carries an `@meta` object:
 - `api_version`: `1`
 - `execution_time_ms`: the number of milliseconds the request took
 
-Every value with a unit is a number, and the unit ends the field name. Examples
-are `_ms`, `_seconds`, `_bytes`, `_per_sec` and `_per_min`.
+Every value with a unit is a number. The unit ends the field name, as in `_ms`,
+`_seconds`, `_bytes`, `_per_sec` and `_per_min`. `latitude` and `longitude` are
+in degrees, and their names do not say so.
 
 The paths:
 
@@ -705,8 +706,10 @@ What happens at each limit:
   allocating more.
 - The SQLite hard heap limit: a database statement fails with an out-of-memory
   error, which the handler logs. The prefix handler writes the routing table's
-  changes and its origin changes again in a later write. Everything else in the
-  failed write is dropped. The process keeps running.
+  changes and its origin changes again in a later write. Everything else in a
+  handler's failed write is dropped. The PTR cache and the geolocation part
+  write their answers to `cache.db` again in a later write. The process keeps
+  running.
 - The handler queues: the handlers are the four parts that take the feed's
   messages (see Design). The prefix handler's queue holds at most 100,000
   messages, about 100 MiB. Each of the other three holds at most 20,000. When a

TODO.md

@@ -30,7 +30,7 @@ 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`.
 
-A 24-hour run of `e58c663` on the live feed began at 09:19 UTC on 2026-11-10
+A run of `e58c663` on the live feed began at 09:19 UTC on 2026-11-10
 (https://git.eeqj.de/sneak/routewatch/issues/232). It is to confirm that fix.
 Next Step lists what its outcome reports. The seven IP lookup additions of
 https://git.eeqj.de/sneak/routewatch/issues/203 landed after it began, so it
@@ -41,7 +41,7 @@ https://git.eeqj.de/sneak/routewatch/issues/86.
 
 # Next Step
 
-Post the outcome of the 24-hour run of `e58c663` on
+Post the outcome of the run of `e58c663` on
 https://git.eeqj.de/sneak/routewatch/issues/232. The run lasts at least 24
 hours. If the feed has not stalled or reconnected by then, the run goes on until
 it does, up to 72 hours in all. The outcome says:
@@ -59,11 +59,10 @@ File an issue for each problem the run finds.
 
 - 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 except
-  measured figures is checked against the code on `next`. Six README sentences
-  are rewritten. Four failed the prose rules, on origin changes, PTR lookups and
-  geolocation. Two disagreed with the code, on a failed database write and
-  `script/test`. Status and Next Step describe the live-feed run in progress
-  (closes https://git.eeqj.de/sneak/routewatch/issues/251).
+  measured figures and what outside services do is checked against the code on
+  `next`. Four README sentences failed the prose rules. Five disagreed with the
+  code. Each is rewritten. Status and Next Step describe the live-feed run in
+  progress (closes https://git.eeqj.de/sneak/routewatch/issues/251).
 - 2026-11-10: the image creates the `routewatch` user as a regular user with UID
   1000, so the build no longer warns about the system UID range (closes
   https://git.eeqj.de/sneak/routewatch/issues/248).