Correct TODO.md milestone state and record seventeen landed units #192

Merged
clawbot merged 1 commits from todo-md-milestone-state into next 2026-08-18 04:07:40 +02:00
Collaborator

Docs-only: TODO.md and nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy. Manager-maintained on next under the provisional ruling in #112.

Why now rather than at milestone close

The Status section asserted that next holds the completed 1.0.0 milestone: every issue in it is closed. Four are open — #176, #178, #186 and #187. next is required to be mergeable to main without notice, so that sentence was one unannounced merge away from shipping to main as a false statement about the release.

Changes

  • Status — names the four remaining issues instead of claiming none remain. The cache-defeated verification claim and the CI caveat about skipped superseded runs are unchanged and still true.
  • Next Step — was "merge the milestone PR to main and tag 1.0.0 from it", which skipped the four. Now states the remaining work and the merge order, which is forced by a real conflict on README.md and internal/middleware/middleware.go.
  • Next Step, owner decisions — named #115 and #125 as open. Both landed (9ae1915, c3b6623). Replaced with the two that are genuinely open: #150, decided by the manager and flagged for reversal, and #112.
  • Completed Steps — was seventeen units behind, back to 2026-08-12. Each new entry states the defect, matching the existing style.

Gate

make bootstrap then make fmt (no reflow beyond the edit) then make checkexit 0, lint in Docker 0 issues. in 47.1s. No containers left running, no image tagged, no prune of any kind.

Docs-only: `TODO.md` and nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy. Manager-maintained on `next` under the provisional ruling in https://git.eeqj.de/sneak/webhooker/issues/112. ## Why now rather than at milestone close The Status section asserted that **`next` holds the completed 1.0.0 milestone: every issue in it is closed**. Four are open — https://git.eeqj.de/sneak/webhooker/issues/176, https://git.eeqj.de/sneak/webhooker/issues/178, https://git.eeqj.de/sneak/webhooker/issues/186 and https://git.eeqj.de/sneak/webhooker/issues/187. `next` is required to be mergeable to `main` without notice, so that sentence was one unannounced merge away from shipping to `main` as a false statement about the release. ## Changes - **Status** — names the four remaining issues instead of claiming none remain. The cache-defeated verification claim and the CI caveat about `skipped` superseded runs are unchanged and still true. - **Next Step** — was "merge the milestone PR to `main` and tag 1.0.0 from it", which skipped the four. Now states the remaining work and the merge order, which is forced by a real conflict on `README.md` and `internal/middleware/middleware.go`. - **Next Step, owner decisions** — named https://git.eeqj.de/sneak/webhooker/issues/115 and https://git.eeqj.de/sneak/webhooker/issues/125 as open. Both landed (`9ae1915`, `c3b6623`). Replaced with the two that are genuinely open: https://git.eeqj.de/sneak/webhooker/issues/150, decided by the manager and flagged for reversal, and https://git.eeqj.de/sneak/webhooker/issues/112. - **Completed Steps** — was seventeen units behind, back to 2026-08-12. Each new entry states the defect, matching the existing style. ## Gate `make bootstrap` then `make fmt` (no reflow beyond the edit) then `make check` — **exit 0**, lint in Docker `0 issues.` in 47.1s. No containers left running, no image tagged, no prune of any kind.
clawbot added 1 commit 2026-08-18 04:07:20 +02:00
Correct TODO.md milestone state and record seventeen landed units
All checks were successful
check / check (push) Successful in 6s
d2cebb5783
The Status section claimed next held the completed 1.0.0 milestone with
every issue closed. Four are open (#176, #178, #186, #187), so a merge
of next to main would have shipped that claim to main.

Next Step still named #115 and #125 as open owner decisions; both
landed. It now names the real open items, #150 and #112, and the forced
merge order for the remaining four.

Completed Steps was seventeen units behind, back to 2026-08-12.
clawbot merged commit 9313b0fb41 into next 2026-08-18 04:07:40 +02:00
Author
Collaborator

Disclosure: this landed as a merge commit (9313b0f) rather than a squash, unlike every other unit on next. My mistake — I passed the merge style under the wrong parameter name, it was silently ignored, and the API default (merge) applied. next therefore carries 9313b0f plus d2cebb5 instead of one squashed commit.

Not rewritten. Force-pushing a shared integration branch to correct the shape of a docs-only commit is worse than the untidiness, especially with two reviews in flight against this base and next required to stay mergeable without notice. b573959 is still an ancestor, so nothing downstream is invalidated.

Corrected for the four remaining merges in this milestone, which are the ones where one-commit-per-issue actually matters.

Disclosure: this landed as a **merge commit** (`9313b0f`) rather than a squash, unlike every other unit on `next`. My mistake — I passed the merge style under the wrong parameter name, it was silently ignored, and the API default (`merge`) applied. `next` therefore carries `9313b0f` plus `d2cebb5` instead of one squashed commit. Not rewritten. Force-pushing a shared integration branch to correct the shape of a docs-only commit is worse than the untidiness, especially with two reviews in flight against this base and `next` required to stay mergeable without notice. `b573959` is still an ancestor, so nothing downstream is invalidated. Corrected for the four remaining merges in this milestone, which are the ones where one-commit-per-issue actually matters.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/webhooker#192