Record the 1.0.0 milestone as complete in TODO.md #199

2026-08-18T10:49:56+02:00

clawbot commented

2026-08-18 10:49:56 +02:00

Docs-only: TODO.md and nothing else, so no adversarial review per repo policy. Manager-maintained on next under the provisional ruling in #112.

The 1.0.0 milestone is empty — 39 closed, 0 open. Status and Next Step now say so, and the last six units are recorded in Completed Steps: #186, #176, #178, #187, #196 and #194.

One stale claim corrected

Status asserted, in the present tense, that "a superseded run is recorded as skipped and still rolls up green, so a commit status on next does not by itself evidence an executed check". That is the defect #152 fixed — superseded runs are now recorded as failure. The sentence described the world before its own fix landed.

The narrower caveat that genuinely survives is kept: a docs-only commit deliberately replays from the layer cache (#119), so a green check on such a commit evidences a replay rather than an executed run, while a code commit invalidates the COPY layer and really executes. Both historical hazards are now named as fixed rather than as current.

Next Step also records the three items that belong to the owner and block nothing: #150 (decided by the manager, flagged for reversal), #112, and #198.

Gate

make check — exit 0, lint in Docker 0 issues. in 46.99 s.

Note script/fmt and script/fmt-check are gofmt-only in this repo, so markdown is not machine-formatted here; the added prose is hand-wrapped to the file's existing 72-column width, verified as the maximum line length across the whole file.

Separately, next at 1326f82 — the tree this lands on — is verified green by a cache-defeated docker build --no-cache-filter=lint --no-cache-filter=builder: exit 0, lint 0 issues. in 49.62 s, make test 68.7 s across 16 packages with real durations and zero (cached) lines, make build 42.6 s. The only CACHED layers are the final runtime stage. internal/handlers measured 17.573 s against the new 90 s budget. Image removed, docker ps -a empty, no prune of any kind.

Docs-only: `TODO.md` and nothing else, so no adversarial review per repo policy. Manager-maintained on `next` under the provisional ruling in https://git.eeqj.de/sneak/webhooker/issues/112. The 1.0.0 milestone is empty — **39 closed, 0 open**. Status and Next Step now say so, and the last six units are recorded in Completed Steps: https://git.eeqj.de/sneak/webhooker/issues/186, https://git.eeqj.de/sneak/webhooker/issues/176, https://git.eeqj.de/sneak/webhooker/issues/178, https://git.eeqj.de/sneak/webhooker/issues/187, https://git.eeqj.de/sneak/webhooker/issues/196 and https://git.eeqj.de/sneak/webhooker/issues/194. ## One stale claim corrected Status asserted, in the present tense, that "a superseded run is recorded as `skipped` and still rolls up green, so a commit status on `next` does not by itself evidence an executed check". **That is the defect https://git.eeqj.de/sneak/webhooker/issues/152 fixed** — superseded runs are now recorded as `failure`. The sentence described the world before its own fix landed. The narrower caveat that genuinely survives is kept: a docs-only commit deliberately replays from the layer cache (https://git.eeqj.de/sneak/webhooker/issues/119), so a green check on such a commit evidences a replay rather than an executed run, while a code commit invalidates the `COPY` layer and really executes. Both historical hazards are now named as fixed rather than as current. Next Step also records the three items that belong to the owner and block nothing: https://git.eeqj.de/sneak/webhooker/issues/150 (decided by the manager, flagged for reversal), https://git.eeqj.de/sneak/webhooker/issues/112, and https://git.eeqj.de/sneak/webhooker/issues/198. ## Gate `make check` — **exit 0**, lint in Docker `0 issues.` in 46.99 s. Note `script/fmt` and `script/fmt-check` are **gofmt-only** in this repo, so markdown is not machine-formatted here; the added prose is hand-wrapped to the file's existing 72-column width, verified as the maximum line length across the whole file. Separately, `next` at `1326f82` — the tree this lands on — is verified green by a cache-defeated `docker build --no-cache-filter=lint --no-cache-filter=builder`: exit 0, lint `0 issues.` in 49.62 s, `make test` 68.7 s across **16 packages with real durations and zero `(cached)` lines**, `make build` 42.6 s. The only `CACHED` layers are the final runtime stage. `internal/handlers` measured 17.573 s against the new 90 s budget. Image removed, `docker ps -a` empty, no prune of any kind.

clawbot added 1 commit 2026-08-18 10:49:57 +02:00

Record the 1.0.0 milestone as complete in TODO.md

check / check (push) Successful in 7s

Details

ad5aac0eb1

The milestone is empty: 39 issues closed, 0 open. Status and Next Step
now say so, and the last six units are recorded.

Also corrects a stale caveat: Status claimed in the present tense that a
superseded CI run is recorded as skipped and rolls up green. That was
the defect #152 fixed. The narrower caveat that survives is that a
docs-only commit deliberately replays from cache (#119), so a green
check on one evidences a replay rather than an executed run.

clawbot merged commit aa463213f5 into next

2026-08-18 10:50:01 +02:00

clawbot deleted branch todo-final-1.0.0

2026-08-18 10:50:01 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/webhooker#199