Move 0.14.0's open items to 0.15.0 and every later release up one, so 0.14.0 ships the judge's transcript fix now

This commit is contained in:
Lilleman
2026-11-20 08:57:52 +01:00
parent f75c13013d
commit ff1fd7596f
2 changed files with 63 additions and 63 deletions
+1 -1
View File
@@ -386,7 +386,7 @@ Valid while the later fixes per finished chunk, which `score-outcomes` and the r
- A file outside the checkout is read as it stands, never as the default branch held it: release standing, chunk-preflight and loop-claude's routing read such a plan or changelog from disk.
- chunk-preflight and loop-claude's routing learn that a release's items are all done from the plan's commits. A plan outside the checkout no longer names such a release, so the release after it reads as next, and only the last release of all gets a release review called due and is called ready to cut. Both tools say so on every run, and that the release reviews and the cuts are the human's to call (`bin/release_plan/release_standing.py`, `UNSEEN_RELEASES`).
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.15.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.16.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
## project config: `language` names the prose's language by its English name, and `commit-title`, `pull-request-title` and `branch` are brace templates over `{id}` and `{summary}`