docs: rewrite TODO.md workflow for the branch-per-issue model on next #192

clawbot · 2026-08-11T14:14:24+02:00

clawbot commented

2026-08-11 14:14:24 +02:00

Closes #191. Documentation only — TODO.md is the sole changed file.

Workflow now describes what the repo actually does: pull next and cut one branch per issue from it, one commit whose title ends with (closes #N) carrying the TODO.md update, rebase onto current next before pushing, one PR per issue with base next, squash-merged into next on a passed independent review. main is reached only by the per-milestone PR from next, releases are tagged from main, next and main stay green while a feature branch may be red.

Status now names the 1.0.0 milestone in flight on next with its milestone PR #190, and points at the tracker as the authoritative backlog rather than duplicating it. Next Step names a real open item, #152.

Judgement calls:

Completed Steps was not rewritten. Two entries were appended: the build-time DEBUG flag (#149), which landed but had no entry, and this change. Existing entries keep their bare #N references untouched.
Future Steps was pruned to the three items that have no issue of their own (pre-1.0 security review, the docker-in-docker decision for make test-e2e in CI, cutting 1.0.0). Everything else there was already filed and is on the tracker.
RULES.md "Build & Workflow" still says "Feature branches for all changes, merge to main when done", which the new Workflow contradicts. RULES.md is owner-only and out of scope here; flagging it rather than editing it.

Verification: make fmt run, no change to TODO.md (already Prettier-clean). make check green on the rebased branch — 7 suites, 143 tests passed; prettier --check .: "All matched files use Prettier code style!" for both lint and fmt-check. Rebased onto origin/next at e9fa8be before pushing; no conflicts.

Closes https://git.eeqj.de/sneak/AutistMask/issues/191. Documentation only — `TODO.md` is the sole changed file. Workflow now describes what the repo actually does: pull `next` and cut one branch per issue from it, one commit whose title ends with ` (closes #N)` carrying the `TODO.md` update, rebase onto current `next` before pushing, one PR per issue with base `next`, squash-merged into `next` on a passed independent review. `main` is reached only by the per-milestone PR from `next`, releases are tagged from `main`, `next` and `main` stay green while a feature branch may be red. Status now names the 1.0.0 milestone in flight on `next` with its milestone PR https://git.eeqj.de/sneak/AutistMask/pulls/190, and points at the tracker as the authoritative backlog rather than duplicating it. Next Step names a real open item, https://git.eeqj.de/sneak/AutistMask/issues/152. Judgement calls: - Completed Steps was not rewritten. Two entries were appended: the build-time `DEBUG` flag (https://git.eeqj.de/sneak/AutistMask/issues/149), which landed but had no entry, and this change. Existing entries keep their bare `#N` references untouched. - Future Steps was pruned to the three items that have no issue of their own (pre-1.0 security review, the docker-in-docker decision for `make test-e2e` in CI, cutting 1.0.0). Everything else there was already filed and is on the tracker. - `RULES.md` "Build & Workflow" still says "Feature branches for all changes, merge to main when done", which the new Workflow contradicts. `RULES.md` is owner-only and out of scope here; flagging it rather than editing it. Verification: `make fmt` run, no change to `TODO.md` (already Prettier-clean). `make check` green on the rebased branch — 7 suites, 143 tests passed; `prettier --check .`: "All matched files use Prettier code style!" for both `lint` and `fmt-check`. Rebased onto `origin/next` at `e9fa8be` before pushing; no conflicts.

clawbot added 1 commit 2026-08-11 14:14:24 +02:00

docs: rewrite TODO.md workflow for the branch-per-issue model on next (closes #191 )

check / check (push) Successful in 20s

Details

085e3c1960

The Workflow section still described branching from `main` and merging
straight to it. It now describes what the repo actually does: one branch
and one PR per issue cut from and based on `next`, squash-merged into
`next` on a passed independent review, with `main` reached only by the
per-milestone PR from `next` and releases tagged from `main`.

Status and Next Step were stale (they named a branch that landed as
`23aeae4`). Status now points at the 1.0.0 milestone in flight and the
tracker as the authoritative backlog; Next Step names a real open item.
Future Steps keeps only work that has no issue of its own.

clawbot added the needs-review label 2026-08-11 14:14:29 +02:00

clawbot self-assigned this 2026-08-11 14:14:32 +02:00

clawbot merged commit d93eda31a0 into next

2026-08-11 14:15:06 +02:00

clawbot deleted branch docs/issue-191-todo-workflow

2026-08-11 14:15:06 +02:00

clawbot referenced this pull request

2026-08-11 14:16:11 +02:00

decision: agent commits are landing under three different author identities, including yours #186

Sign in to join this conversation.