Footer no longer says IPv4 only (closes #111)

Nothing in the page limits a check to IPv4: each check is a fetch, and
the browser picks IPv4 or IPv6 for each target. The footer's first line
drops "IPv4 only" and its separator; the rest of the footer is
unchanged. TODO.md moves this to Completed Steps and the layout
decision from Future Steps into Next Step.

Model: opus-5-5

TODO.md

@@ -16,11 +16,16 @@ Docker image, and the Gitea workflow `.gitea/workflows/check.yml` runs
 
 # Next Step
 
-Take "IPv4 only" out of the page's footer, as nothing in the page limits a check
-to IPv4 ([#111](https://git.eeqj.de/sneak/netwatch/issues/111)).
+Decide whether the repo moves to the layout `REPO_POLICIES.md` gives, with
+`backend/` no longer repeating files from the root
+([#30](https://git.eeqj.de/sneak/netwatch/issues/30)).
 
 # Completed Steps
 
+- 2026-10-04: the page's footer no longer says "IPv4 only"
+  ([#111](https://git.eeqj.de/sneak/netwatch/issues/111)), as nothing in the
+  page limits a check to IPv4: each check is a `fetch`, and the browser picks
+  IPv4 or IPv6 for each target. The rest of the footer is unchanged
 - 2026-10-04: `README.md`, `TODO.md` and `test/viewport/README.md` say what the
   tree does (issue #24). The README's Getting Started leads with `make` targets;
   a new Backend section says what `netwatch-server` stores, its routes and how
@@ -384,9 +389,6 @@ to IPv4 ([#111](https://git.eeqj.de/sneak/netwatch/issues/111)).
 
 # Future Steps
 
-- Decide whether the repo moves to the layout `REPO_POLICIES.md` gives, with
-  `backend/` no longer repeating files from the root
-  ([#30](https://git.eeqj.de/sneak/netwatch/issues/30))
 - Run `make frontend-viewport-test` in CI as its own step; it is not part of
   `make check`, as it needs Docker and takes minutes
 - A backend test that posts a report to `POST /api/v1/reports` and checks the

src/main.js

@@ -857,7 +857,7 @@ function buildUI(state) {
       </div>
 
       <footer class="mt-8 text-center text-gray-600 text-xs">
-        <p>Latency measured via GET requests | IPv4 only | CORS restrictions may affect some measurements</p>
+        <p>Latency measured via GET requests | CORS restrictions may affect some measurements</p>
         <p class="mt-2">
           <span class="inline-block w-3 h-3 rounded-full bg-green-500 mr-1 align-middle"></span>&lt;50ms
           <span class="inline-block w-3 h-3 rounded-full bg-lime-500 mr-1 ml-3 align-middle"></span>&lt;100ms