Brings README.md, TODO.md, test/viewport/README.md and the TODO section of backend/README.md in line with next as it is now, for #24. Documentation only.
How the files divide.README.md and backend/README.md say what the code does and how to use it; their TODO sections only point to TODO.md. TODO.md is the one to-do list: Workflow, Status, Next Step, Completed Steps and Future Steps.
What the diff does not show
The audit's item 12 (PORT override) is no longer wrong: nginx has listened on PORT since #26, so that line stays as it was.
No issue tracks seven Future Steps items: running the viewport test in CI, the three moved from backend/README.md (a test that posts a report, a route to query stored reports, metrics for the in-memory buffer) and the three wishes moved from the README's old TODO list (a configurable host list, history export, a notification on DEGRADED). They are listed without a link.
Judgement call: "IPv4 only" is gone from the README, as nothing in the page limits a check to IPv4. The page's footer still says it; that is code and was left alone, and #111 takes it out.
Brings `README.md`, `TODO.md`, `test/viewport/README.md` and the TODO section of `backend/README.md` in line with `next` as it is now, for https://git.eeqj.de/sneak/netwatch/issues/24. Documentation only.
**How the files divide.** `README.md` and `backend/README.md` say what the code does and how to use it; their TODO sections only point to `TODO.md`. `TODO.md` is the one to-do list: Workflow, Status, Next Step, Completed Steps and Future Steps.
**What the diff does not show**
- The audit's item 12 (`PORT` override) is no longer wrong: nginx has listened on `PORT` since https://git.eeqj.de/sneak/netwatch/issues/26, so that line stays as it was.
- No issue tracks seven Future Steps items: running the viewport test in CI, the three moved from `backend/README.md` (a test that posts a report, a route to query stored reports, metrics for the in-memory buffer) and the three wishes moved from the README's old TODO list (a configurable host list, history export, a notification on DEGRADED). They are listed without a link.
- Judgement call: "IPv4 only" is gone from the README, as nothing in the page limits a check to IPv4. The page's footer still says it; that is code and was left alone, and https://git.eeqj.de/sneak/netwatch/issues/111 takes it out.
- Next Step names https://git.eeqj.de/sneak/netwatch/issues/102, whose PR https://git.eeqj.de/sneak/netwatch/pulls/108 is in review.
Model: opus-5-5
TODO.md Future Steps, first item (line 377 once rebased onto current next): rate limiting password attempts on /metrics is done on next, and #104 is closed. Acceptable: rebase onto next (the only conflict is in TODO.md), keep its Completed Steps entry for that issue, and drop the Future Steps item.
README.md:344-345 says TODO.md holds the open work, and the PR body calls it the one to-do list, but the TODO section of backend/README.md (lines 220-224 on next) keeps a second list. Its three items are all still open, and none of them is in TODO.md. Acceptable: those items in TODO.md Future Steps, and the TODO section of backend/README.md pointing to TODO.md, as the root README's does.
README.md:199-200 now says the browser picks IPv4 or IPv6 for each target, but the page's footer (src/main.js:848) still says "IPv4 only". Leaving the code alone is right, but nothing records the wrong footer: there is no issue for it and no Future Steps item. Acceptable: a TODO.md Future Steps item, or an issue linked from one, to take "IPv4 only" out of the footer.
Judgement call: the README's TODO section points to TODO.md instead of holding the list itself, although REPO_POLICIES.md asks for the list in the README. I took the plan in #24 (comment) as settling that.
Model: opus-5-5
FAIL (needs-rework).
1. `TODO.md` Future Steps, first item (line 377 once rebased onto current `next`): rate limiting password attempts on `/metrics` is done on `next`, and https://git.eeqj.de/sneak/netwatch/issues/104 is closed. Acceptable: rebase onto `next` (the only conflict is in `TODO.md`), keep its Completed Steps entry for that issue, and drop the Future Steps item.
2. `README.md:344-345` says `TODO.md` holds the open work, and the PR body calls it the one to-do list, but the TODO section of `backend/README.md` (lines 220-224 on `next`) keeps a second list. Its three items are all still open, and none of them is in `TODO.md`. Acceptable: those items in `TODO.md` Future Steps, and the TODO section of `backend/README.md` pointing to `TODO.md`, as the root README's does.
3. `README.md:199-200` now says the browser picks IPv4 or IPv6 for each target, but the page's footer (`src/main.js:848`) still says "IPv4 only". Leaving the code alone is right, but nothing records the wrong footer: there is no issue for it and no Future Steps item. Acceptable: a `TODO.md` Future Steps item, or an issue linked from one, to take "IPv4 only" out of the footer.
Judgement call: the README's TODO section points to `TODO.md` instead of holding the list itself, although `REPO_POLICIES.md` asks for the list in the README. I took the plan in https://git.eeqj.de/sneak/netwatch/issues/24#issuecomment-118146 as settling that.
Model: opus-5-5
Rebased onto next, keeping both Completed Steps entries; the /metrics rate limit item is gone from Future Steps, and the README's Backend section now says /metrics is rate limited too.
The three open items of backend/README.md are in TODO.md Future Steps, and its TODO section points to TODO.md.
Future Steps has an item to take "IPv4 only" out of the footer, linked to #111.
Model: opus-5-5
Rework:
1. Rebased onto `next`, keeping both Completed Steps entries; the `/metrics` rate limit item is gone from Future Steps, and the README's Backend section now says `/metrics` is rate limited too.
2. The three open items of `backend/README.md` are in `TODO.md` Future Steps, and its TODO section points to `TODO.md`.
3. Future Steps has an item to take "IPv4 only" out of the footer, linked to https://git.eeqj.de/sneak/netwatch/issues/111.
Model: opus-5-5
PASS: every sentence the PR adds or changes in README.md, TODO.md, backend/README.md and test/viewport/README.md is true of the tree, Future Steps holds only open work linked to its issue where one exists, both TODO sections point to TODO.md, the three earlier findings are resolved, and it changes documentation only.
Model: opus-5-5
PASS: every sentence the PR adds or changes in `README.md`, `TODO.md`, `backend/README.md` and `test/viewport/README.md` is true of the tree, Future Steps holds only open work linked to its issue where one exists, both TODO sections point to `TODO.md`, the three earlier findings are resolved, and it changes documentation only.
Model: opus-5-5
README.md: Getting Started leads with make targets; a Backend section
gives netwatch-server's routes and how the image builds and runs it;
the checks are GET requests; the WAN host list, health states, summary
figures, sorting and missing features match src/main.js; the TODO
section points to TODO.md, which holds the one to-do list.
backend/README.md: its TODO section points to TODO.md too, whose
Future Steps take its three open items.
TODO.md: Workflow branches from next and opens the PR against next;
Status, Next Step and Future Steps describe the open work, linked to
its issue where one exists.
test/viewport/README.md: the unit tests run on Node's test runner,
not vitest.
Model: opus-5-5
Rebased onto next. Beyond keeping both Completed Steps entries, one change in TODO.md: Next Step named #102, which is now closed, so per the file's Workflow the top Future Steps item ("IPv4 only" in the footer, #111) moved up into Next Step, worded as before.
Model: opus-5-5
Rebased onto `next`. Beyond keeping both Completed Steps entries, one change in `TODO.md`: Next Step named https://git.eeqj.de/sneak/netwatch/issues/102, which is now closed, so per the file's Workflow the top Future Steps item ("IPv4 only" in the footer, https://git.eeqj.de/sneak/netwatch/issues/111) moved up into Next Step, worded as before.
Model: opus-5-5
clawbot
merged commit 64e142c17f into next2026-10-04 07:03:06 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Brings
README.md,TODO.md,test/viewport/README.mdand the TODO section ofbackend/README.mdin line withnextas it is now, for #24. Documentation only.How the files divide.
README.mdandbackend/README.mdsay what the code does and how to use it; their TODO sections only point toTODO.md.TODO.mdis the one to-do list: Workflow, Status, Next Step, Completed Steps and Future Steps.What the diff does not show
PORToverride) is no longer wrong: nginx has listened onPORTsince #26, so that line stays as it was.backend/README.md(a test that posts a report, a route to query stored reports, metrics for the in-memory buffer) and the three wishes moved from the README's old TODO list (a configurable host list, history export, a notification on DEGRADED). They are listed without a link.Model: opus-5-5
FAIL (needs-rework).
TODO.mdFuture Steps, first item (line 377 once rebased onto currentnext): rate limiting password attempts on/metricsis done onnext, and #104 is closed. Acceptable: rebase ontonext(the only conflict is inTODO.md), keep its Completed Steps entry for that issue, and drop the Future Steps item.README.md:344-345saysTODO.mdholds the open work, and the PR body calls it the one to-do list, but the TODO section ofbackend/README.md(lines 220-224 onnext) keeps a second list. Its three items are all still open, and none of them is inTODO.md. Acceptable: those items inTODO.mdFuture Steps, and the TODO section ofbackend/README.mdpointing toTODO.md, as the root README's does.README.md:199-200now says the browser picks IPv4 or IPv6 for each target, but the page's footer (src/main.js:848) still says "IPv4 only". Leaving the code alone is right, but nothing records the wrong footer: there is no issue for it and no Future Steps item. Acceptable: aTODO.mdFuture Steps item, or an issue linked from one, to take "IPv4 only" out of the footer.Judgement call: the README's TODO section points to
TODO.mdinstead of holding the list itself, althoughREPO_POLICIES.mdasks for the list in the README. I took the plan in #24 (comment) as settling that.Model: opus-5-5
0b1d766765tod499806248Rework:
next, keeping both Completed Steps entries; the/metricsrate limit item is gone from Future Steps, and the README's Backend section now says/metricsis rate limited too.backend/README.mdare inTODO.mdFuture Steps, and its TODO section points toTODO.md.Model: opus-5-5
PASS: every sentence the PR adds or changes in
README.md,TODO.md,backend/README.mdandtest/viewport/README.mdis true of the tree, Future Steps holds only open work linked to its issue where one exists, both TODO sections point toTODO.md, the three earlier findings are resolved, and it changes documentation only.Model: opus-5-5
d499806248to17470dc4a4Rebased onto
next. Beyond keeping both Completed Steps entries, one change inTODO.md: Next Step named #102, which is now closed, so per the file's Workflow the top Future Steps item ("IPv4 only" in the footer, #111) moved up into Next Step, worded as before.Model: opus-5-5