docs: TODO.md describes the old branch-from-main workflow and its Status/Next Step are stale #191

New Issue

2026-08-10T16:16:38+02:00

clawbot commented

2026-08-10 16:16:38 +02:00

TODO.md opens with a Workflow section that says to branch from main and "merge to main if the branch is not protected". That is no longer how this repo works: next is the branch for the next milestone, every issue gets its own branch cut from next and its own PR based on next, and those are squash-merged into next by the manager on a passed review. main is only ever touched by the milestone PR from next.

The Status and Next Step blocks are also stale — they describe feat/issue-144-settings-about as in flight, which landed as 23aeae4.

Definition of done

The Workflow section describes the current model: branch from next, one branch and one PR per issue based on next, commit title ending (closes #N), squash-merged into next, main reached only via the milestone PR, next kept green and mergeable at all times.
Status reflects reality: pre-1.0, milestone 1.0.0 in flight on next, make check green on next.
Next Step names one real next item rather than a landed one.
Completed Steps is not rewritten — entries are appended or left alone, never deleted.
make check green, make fmt run and its result committed.

Documentation only: no change to code, config, scripts, CI or build files.

`TODO.md` opens with a Workflow section that says to branch from `main` and "merge to `main` if the branch is not protected". That is no longer how this repo works: `next` is the branch for the next milestone, every issue gets its own branch cut from `next` and its own PR based on `next`, and those are squash-merged into `next` by the manager on a passed review. `main` is only ever touched by the milestone PR from `next`. The Status and Next Step blocks are also stale — they describe `feat/issue-144-settings-about` as in flight, which landed as `23aeae4`. ## Definition of done - The Workflow section describes the current model: branch from `next`, one branch and one PR per issue based on `next`, commit title ending ` (closes #N)`, squash-merged into `next`, `main` reached only via the milestone PR, `next` kept green and mergeable at all times. - Status reflects reality: pre-1.0, milestone 1.0.0 in flight on `next`, `make check` green on `next`. - Next Step names one real next item rather than a landed one. - Completed Steps is not rewritten — entries are appended or left alone, never deleted. - `make check` green, `make fmt` run and its result committed. Documentation only: no change to code, config, scripts, CI or build files.

clawbot referenced this issue from a commit

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

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

clawbot referenced this issue

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

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

clawbot referenced this issue from a commit

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

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

clawbot referenced this issue

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

decision: RULES.md "Build & Workflow" still says merge to main, contradicting the branch-per-issue-onto-next model #193