TODO.md asks every change to add its entry at the top of Completed Steps in the same commit. With many fixes for the audit findings open at once, every PR adds a line at the same place, so each merge into next leaves every other open PR in conflict, and each needs a rebase and a fresh check before it can merge.
Decision: the open and future PRs for the audit findings do not touch TODO.md; a PR that already has an entry drops it on its next rebase. This issue logs them all together once the last of them has merged.
Definition of done
TODO.md's Completed Steps has one entry per audit fix merged into next since v1.0.0-rc2, newest first, in the style of the entries there, each linking its issue.
TODO.md's Status section no longer says there are no git tags.
Model: opus-5-5
`TODO.md` asks every change to add its entry at the top of Completed Steps in the same commit. With many fixes for the audit findings open at once, every PR adds a line at the same place, so each merge into `next` leaves every other open PR in conflict, and each needs a rebase and a fresh check before it can merge.
Decision: the open and future PRs for the audit findings do not touch `TODO.md`; a PR that already has an entry drops it on its next rebase. This issue logs them all together once the last of them has merged.
**Definition of done**
- `TODO.md`'s Completed Steps has one entry per audit fix merged into `next` since `v1.0.0-rc2`, newest first, in the style of the entries there, each linking its issue.
- `TODO.md`'s Status section no longer says there are no git tags.
Model: opus-5-5
clawbot
added this to the 1.0.0 milestone 2026-10-14 23:15:21 +02:00
clawbot
self-assigned this 2026-10-14 23:15:21 +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.
TODO.mdasks every change to add its entry at the top of Completed Steps in the same commit. With many fixes for the audit findings open at once, every PR adds a line at the same place, so each merge intonextleaves every other open PR in conflict, and each needs a rebase and a fresh check before it can merge.Decision: the open and future PRs for the audit findings do not touch
TODO.md; a PR that already has an entry drops it on its next rebase. This issue logs them all together once the last of them has merged.Definition of done
TODO.md's Completed Steps has one entry per audit fix merged intonextsincev1.0.0-rc2, newest first, in the style of the entries there, each linking its issue.TODO.md's Status section no longer says there are no git tags.Model: opus-5-5