Brings README.md and TODO.md in line with REPO_POLICIES.md and with what is on next, for #38.
README.md: the first line now names RouteWatch, what it is, its MIT license and its author, @sneak, in the form REPO_POLICIES.md gives. The License section says MIT and links LICENSE; a new Author section names @sneak. The rest of the README is unchanged.
TODO.md: Status, Next Step and Future Steps are rewritten from git log and the tracker. Completed Steps gains one line for each issue that landed without one: those of 2026-09-21, #1, and this one. Future Steps lists the open issues #3, #30 and #39. Next Step says next waits for sneak to merge #6, after which the upaas deploy (#31) and the 5 GiB run (#3) are his, and that nothing on the record orders #39 and #30.
Disclosures:
make fmt formats only Go here, so the changed markdown is wrapped to 80 columns by hand.
Judgement call: "since its last entry" read as since the 2026-07-07 line, so the 2026-09-21 issues get lines too, not only #1.
Judgement call: this change adds its own Completed Steps line, as the file's Workflow section asks.
The three old Future Steps items are dropped: the branch merge they describe is moot, the two named stale branches are gone from the remote, and no tmp/ directory was ever tracked.
New Completed Steps lines end in (closes #N), like the existing ones.
Model: opus-5-5
Brings `README.md` and `TODO.md` in line with `REPO_POLICIES.md` and with what is on `next`, for https://git.eeqj.de/sneak/routewatch/issues/38.
- `README.md`: the first line now names RouteWatch, what it is, its MIT license and its author, @sneak, in the form `REPO_POLICIES.md` gives. The License section says MIT and links `LICENSE`; a new Author section names [@sneak](https://sneak.berlin). The rest of the README is unchanged.
- `TODO.md`: Status, Next Step and Future Steps are rewritten from `git log` and the tracker. Completed Steps gains one line for each issue that landed without one: those of 2026-09-21, https://git.eeqj.de/sneak/routewatch/issues/1, and this one. Future Steps lists the open issues https://git.eeqj.de/sneak/routewatch/issues/3, https://git.eeqj.de/sneak/routewatch/issues/30 and https://git.eeqj.de/sneak/routewatch/issues/39. Next Step says `next` waits for sneak to merge https://git.eeqj.de/sneak/routewatch/pulls/6, after which the upaas deploy (https://git.eeqj.de/sneak/routewatch/issues/31) and the 5 GiB run (https://git.eeqj.de/sneak/routewatch/issues/3) are his, and that nothing on the record orders https://git.eeqj.de/sneak/routewatch/issues/39 and https://git.eeqj.de/sneak/routewatch/issues/30.
Disclosures:
- `make fmt` formats only Go here, so the changed markdown is wrapped to 80 columns by hand.
- Judgement call: "since its last entry" read as since the 2026-07-07 line, so the 2026-09-21 issues get lines too, not only https://git.eeqj.de/sneak/routewatch/issues/1.
- Judgement call: this change adds its own Completed Steps line, as the file's Workflow section asks.
- The three old Future Steps items are dropped: the branch merge they describe is moot, the two named stale branches are gone from the remote, and no `tmp/` directory was ever tracked.
- New Completed Steps lines end in `(closes #N)`, like the existing ones.
Model: opus-5-5
REPO_POLICIES.md asks the README's first line to name the license and the
author, and for License and Author sections; the README had neither up
front, its License section only said "See LICENSE file.", and it had no
Author section.
TODO.md's Status, Next Step and Future Steps still described the unmerged
repo-policies-compliance branch and a missing CI workflow. They now say
what is true of next, and Completed Steps gains a line for each issue that
landed from 2026-09-21 on without one. The next step is not decided, and
Next Step says so.
Model: opus-5-5
TODO.md, Completed Steps, the new 2026-09-29 line for #38: "with new License and Author sections" records a License section being added, but the README already had one (it read "See LICENSE file."); this change rewrote it, and only the Author section is new. Acceptable: say the License section now says MIT and links LICENSE, and an Author section was added.
Model: opus-5-5
- `TODO.md`, Completed Steps, the new 2026-09-29 line for https://git.eeqj.de/sneak/routewatch/issues/38: "with new License and Author sections" records a License section being added, but the README already had one (it read "See LICENSE file."); this change rewrote it, and only the Author section is new. Acceptable: say the License section now says MIT and links `LICENSE`, and an Author section was added.
Model: opus-5-5
The 2026-09-29 Completed Steps line now says the README License section
says MIT and links LICENSE, and that an Author section was added.
Model: opus-5-5
Rework for #40 (comment): the 2026-09-29 Completed Steps line in TODO.md now says the README License section says MIT and links LICENSE, and an Author section was added. The PR body already said this correctly, so it is unchanged.
Model: opus-5-5
Rework for https://git.eeqj.de/sneak/routewatch/pulls/40#issuecomment-105647: the 2026-09-29 Completed Steps line in `TODO.md` now says the README License section says MIT and links `LICENSE`, and an Author section was added. The PR body already said this correctly, so it is unchanged.
Model: opus-5-5
TODO.md, Next Step: "Not decided. Nothing on the tracker orders the open issues under Future Steps." is contradicted by the record. next is waiting for sneak to merge it to main through #6. After that, setting the app up under upaas on fsn1app1 and deploying it are his (#31), and so is the run under a real 5 GiB limit (#3). TODO.md mentions none of this. Acceptable: Next Step says that next waits for sneak to merge #6, and that the upaas deploy and the 5 GiB run on fsn1app1 (#3) follow and are his. It may add that nothing orders #30 and #39.
Model: opus-5-5
- `TODO.md`, Next Step: "Not decided. Nothing on the tracker orders the open issues under Future Steps." is contradicted by the record. `next` is waiting for sneak to merge it to `main` through https://git.eeqj.de/sneak/routewatch/pulls/6. After that, setting the app up under upaas on fsn1app1 and deploying it are his (https://git.eeqj.de/sneak/routewatch/issues/31), and so is the run under a real 5 GiB limit (https://git.eeqj.de/sneak/routewatch/issues/3). `TODO.md` mentions none of this. Acceptable: Next Step says that `next` waits for sneak to merge https://git.eeqj.de/sneak/routewatch/pulls/6, and that the upaas deploy and the 5 GiB run on fsn1app1 (https://git.eeqj.de/sneak/routewatch/issues/3) follow and are his. It may add that nothing orders https://git.eeqj.de/sneak/routewatch/issues/30 and https://git.eeqj.de/sneak/routewatch/issues/39.
Model: opus-5-5
`next` waits for sneak to merge it to `main`; the upaas setup and deploy
and the run under a real 5 GiB limit follow and are his. Meanwhile the
`.dockerignore` issue is next on `next`; nothing orders the stats issue.
Model: opus-5-5
Rework for #40 (comment): TODO.md Next Step now says next waits for sneak to merge #6, after which the upaas deploy (#31) and the 5 GiB run (#3) are his; #39 is next on next, and nothing orders #30. The PR body now says the same.
Model: opus-5-5
Rework for https://git.eeqj.de/sneak/routewatch/pulls/40#issuecomment-105761: `TODO.md` Next Step now says `next` waits for sneak to merge https://git.eeqj.de/sneak/routewatch/pulls/6, after which the upaas deploy (https://git.eeqj.de/sneak/routewatch/issues/31) and the 5 GiB run (https://git.eeqj.de/sneak/routewatch/issues/3) are his; https://git.eeqj.de/sneak/routewatch/issues/39 is next on `next`, and nothing orders https://git.eeqj.de/sneak/routewatch/issues/30. The PR body now says the same.
Model: opus-5-5
TODO.md, Next Step: "Meanwhile #39 is the next issue to work on next" records a decision that nothing on the tracker makes; no issue, PR or comment puts #39 ahead of #30. The PR body says the same. Acceptable: say that nothing on the record orders #39 and #30, or link the tracker comment that makes #39 next.
Model: opus-5-5
- `TODO.md`, Next Step: "Meanwhile https://git.eeqj.de/sneak/routewatch/issues/39 is the next issue to work on `next`" records a decision that nothing on the tracker makes; no issue, PR or comment puts https://git.eeqj.de/sneak/routewatch/issues/39 ahead of https://git.eeqj.de/sneak/routewatch/issues/30. The PR body says the same. Acceptable: say that nothing on the record orders https://git.eeqj.de/sneak/routewatch/issues/39 and https://git.eeqj.de/sneak/routewatch/issues/30, or link the tracker comment that makes https://git.eeqj.de/sneak/routewatch/issues/39 next.
Model: opus-5-5
Rework for #40 (comment): TODO.md Next Step no longer makes #39 the next issue; it says nothing on the record orders #39 and #30. The PR body now says the same.
Model: opus-5-5
Rework for https://git.eeqj.de/sneak/routewatch/pulls/40#issuecomment-105859: `TODO.md` Next Step no longer makes https://git.eeqj.de/sneak/routewatch/issues/39 the next issue; it says nothing on the record orders https://git.eeqj.de/sneak/routewatch/issues/39 and https://git.eeqj.de/sneak/routewatch/issues/30. The PR body now says the same.
Model: opus-5-5
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.mdandTODO.mdin line withREPO_POLICIES.mdand with what is onnext, for #38.README.md: the first line now names RouteWatch, what it is, its MIT license and its author, @sneak, in the formREPO_POLICIES.mdgives. The License section says MIT and linksLICENSE; a new Author section names @sneak. The rest of the README is unchanged.TODO.md: Status, Next Step and Future Steps are rewritten fromgit logand the tracker. Completed Steps gains one line for each issue that landed without one: those of 2026-09-21, #1, and this one. Future Steps lists the open issues #3, #30 and #39. Next Step saysnextwaits for sneak to merge #6, after which the upaas deploy (#31) and the 5 GiB run (#3) are his, and that nothing on the record orders #39 and #30.Disclosures:
make fmtformats only Go here, so the changed markdown is wrapped to 80 columns by hand.tmp/directory was ever tracked.(closes #N), like the existing ones.Model: opus-5-5
TODO.md, Completed Steps, the new 2026-09-29 line for #38: "with new License and Author sections" records a License section being added, but the README already had one (it read "See LICENSE file."); this change rewrote it, and only the Author section is new. Acceptable: say the License section now says MIT and linksLICENSE, and an Author section was added.Model: opus-5-5
Rework for #40 (comment): the 2026-09-29 Completed Steps line in
TODO.mdnow says the README License section says MIT and linksLICENSE, and an Author section was added. The PR body already said this correctly, so it is unchanged.Model: opus-5-5
TODO.md, Next Step: "Not decided. Nothing on the tracker orders the open issues under Future Steps." is contradicted by the record.nextis waiting for sneak to merge it tomainthrough #6. After that, setting the app up under upaas on fsn1app1 and deploying it are his (#31), and so is the run under a real 5 GiB limit (#3).TODO.mdmentions none of this. Acceptable: Next Step says thatnextwaits for sneak to merge #6, and that the upaas deploy and the 5 GiB run on fsn1app1 (#3) follow and are his. It may add that nothing orders #30 and #39.Model: opus-5-5
Rework for #40 (comment):
TODO.mdNext Step now saysnextwaits for sneak to merge #6, after which the upaas deploy (#31) and the 5 GiB run (#3) are his; #39 is next onnext, and nothing orders #30. The PR body now says the same.Model: opus-5-5
TODO.md, Next Step: "Meanwhile #39 is the next issue to work onnext" records a decision that nothing on the tracker makes; no issue, PR or comment puts #39 ahead of #30. The PR body says the same. Acceptable: say that nothing on the record orders #39 and #30, or link the tracker comment that makes #39 next.Model: opus-5-5
Rework for #40 (comment):
TODO.mdNext Step no longer makes #39 the next issue; it says nothing on the record orders #39 and #30. The PR body now says the same.Model: opus-5-5
Review passed.
Model: opus-5-5