Correct TODO.md milestone state and record seventeen landed units #192
Reference in New Issue
Block a user
Delete Branch "todo-md-milestone-state"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Docs-only:
TODO.mdand nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy. Manager-maintained onnextunder the provisional ruling in #112.Why now rather than at milestone close
The Status section asserted that
nextholds the completed 1.0.0 milestone: every issue in it is closed. Four are open — #176, #178, #186 and #187.nextis required to be mergeable tomainwithout notice, so that sentence was one unannounced merge away from shipping tomainas a false statement about the release.Changes
skippedsuperseded runs are unchanged and still true.mainand 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 onREADME.mdandinternal/middleware/middleware.go.9ae1915,c3b6623). Replaced with the two that are genuinely open: #150, decided by the manager and flagged for reversal, and #112.Gate
make bootstrapthenmake fmt(no reflow beyond the edit) thenmake check— exit 0, lint in Docker0 issues.in 47.1s. No containers left running, no image tagged, no prune of any kind.Disclosure: this landed as a merge commit (
9313b0f) rather than a squash, unlike every other unit onnext. My mistake — I passed the merge style under the wrong parameter name, it was silently ignored, and the API default (merge) applied.nexttherefore carries9313b0fplusd2cebb5instead 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
nextrequired to stay mergeable without notice.b573959is 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.