Finish item 469 in the plan
CI / tests (pull_request) Successful in 4m54s

This commit was merged in pull request #680.
This commit is contained in:
2026-11-21 00:49:13 +01:00
parent cd45ced8b2
commit 0874b67b02
2 changed files with 1 additions and 32 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- `do-epic` moves a parent issue whose sub-tasks a person filed: to done by `jira-finish-transition` once every sub-task is done, and before that by the transition the new setting `jira-sub-tasks-landed-transition` names, once each sub-task is done or in one of `jira-unblocking-statuses`. The transition must lead to one of those statuses. `--dry-run` prints each such move.
- mutate-changes now mutates the Go lines a branch changes with Gremlins, as it does Python, Rust, TypeScript and PHP, and prints each mutant the tests do not kill.
- A project's config may set `epic-branch`, such as `epic-branch = "{epic}"`: do-epic then keeps one working branch per epic, level with the default branch by merge commits, and each chunk branches off it and merges into it without waiting for a person, even under `merge = "human"`. `chunk-pr open-epic` opens the finished epic's pull request into the default branch for a person to merge. `review-request-comment` names a comment `chunk-pr` posts after each push to ask a forge's reviewer for a review, and `jira-pull-request-open-status` and `jira-pull-request-merged-status` name the statuses do-epic moves an issue to as its pull request opens and merges.
- `mutate-changes` mutates a Python script from its own folder where a test beside it imports it by its file name, as in `import run_harness`, so mutmut finds the tests' calls to it. A crash inside mutmut now becomes one report line that names mutmut's error, not a traceback, and the other folders still report.
-32
View File
@@ -14,7 +14,6 @@
|---|---|---|---|---|---|---|---|---|---|---|---|
| 501 | 0.15.0 | | owner | **Ship `task-bench`, which plants a bug the tests catch at the places the comprehension seats found hardest, has Haiku fix it in a vanilla Claude Code at a base and a head, and prints for each side how often the fix passes, with its median tokens, turns, wall time and reads before it opens a file the bug is in.** | 4 | 2 | 1 | 5 | 9 | 1.1 by 5, code health by 4 | 0.6 |
| 502 | 0.15.0 | 501 | owner | **Distil each `task-bench` run into a digest of short traces and decoys, the files most failing runs read but no fix touches, and have a stronger model turn it into plan items before the transcripts are deleted.** | 3 | 2 | 1 | 4 | 5 | 1.1 by 4, code health by 4 | 4.8 |
| 469 | 0.15.0 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
| 503 | 0.15.0 | 502 | owner | **Calibrate `task-bench` on fejkdata: bench a head against itself for the noise floor, then one finished chunk at its base and head, and record in a decision how many tasks and runs the bench needs.** | 1 | 2 | 1 | 2 | 2 | 1.1 by 3 | 1.2 |
| 511 | 0.15.0 | | | **Hand the product-owner and prose reviewers the real output of each command a changed doc line says prints something, so a claim about output is checked by running it, not by reading code.** | 2 | 2 | 3 | 5 | 3 | 1.1 by 3 | 1.1 |
| 509 | 0.16.0 | 503 | owner | **Run `task-bench` beside the scoring run in larv-review comprehension check, and record its figures in the comprehension history beside the panel scores.** | 3 | 2 | 3 | 6 | 5 | code health by 5, 1.1 by 3 | 5.6 |
@@ -148,37 +147,6 @@ Touches:
- `bin/task_bench/main.py`: `main` (small)
- `bin/task_bench/test_task_bench.py`
### 469. Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.
do-epic moves to done only a parent it split itself (`split_items_closed`). A parent whose sub-tasks a person filed stays as Jira holds it, and `--status` says "its sub-tasks are done; close it in Jira". Until someone moves it, the parent blocks every issue it blocks, and through it their sub-tasks. On TW-13503, TW-13505 blocks most of the critical path this way, and TW-13547's sub-tasks are all Release Ready while the parent stays In Progress. The human asked, on 2026-11-20, for deterministic code to move these parents, not a worker or a person.
- A parent whose sub-tasks have all landed, each in one of `jira-unblocking-statuses` or done, with at least one not yet done, moves by a transition the config names, such as `jira-landed-transition = "Release Ready"`.
- A parent whose sub-tasks are all done moves by `jira-finish-transition`, as a split item does today.
- do-epic moves such parents as each run plans, and after each chunk finishes, where it now closes split items. A parent already at or past the target status stays: one in a done status never moves back.
- A parent with no sub-tasks, or with one sub-task still open, is left alone.
- Without `jira-landed-transition`, only the move to Done happens, and only where `jira-finish-transition` is set, as today.
- `--dry-run` prints each parent move it would make.
Choice, made 2026-11-20: a sub-task in any of `jira-unblocking-statuses` counts as landed, so TW's "Teach & Learn" counts as "Release Ready" does. The human named Release Ready and Done; Teach & Learn also means the work merged.
Release: lilleman moved it back into 0.15.0 on 2026-11-20, after dropping the plan to cut 0.15.0 early. A chunk had started it in 0.15.0 and was stopped before it committed; its naming panel picked `jira-sub-tasks-landed-transition` for the setting, 2 to 1.
Touches:
- `bin/do_epic/main.py`: `split_items_closed`, `planned_and_started` (small)
- `bin/do_epic/planning.py`: `planned` (small)
- `bin/do_epic/scheduler.py`: `chunks` (small)
- `bin/do_epic/split.py`: `finished` (small)
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
- `bin/do_epic/backend/protocol.py`: `EpicStore`
- `bin/do_epic/backend/jira.py`: `JiraEpic`
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
- `bin/do_epic/backend/contract.py`
- `bin/do_epic/dry_run.py`
- `bin/do_epic/test_do_epic.py`
- `bin/do_epic/backend/test_jira.py`
- `README.md`: `### Set up a project` (small)
### 503. Calibrate `task-bench` on fejkdata: bench a head against itself for the noise floor, then one finished chunk at its base and head, and record in a decision how many tasks and runs the bench needs.
The decision records the spread of the pass rate and of the median tokens when both sides are the same commit, the task and run counts at which a chunk's change rises above that spread, and what one bench costs in tokens and hours. Where no affordable count rises above the noise, it says so, and files what to try instead. The bench's defaults take the counts it picks.