File items 464 and 465 from item 457's mutation run and paired ruling #650

Merged
lilleman merged 1 commits from plan-forge-timeout-test into main 2026-11-20 00:37:00 +01:00
+19 -1
View File
@@ -6,17 +6,19 @@
`Bar = 0.1`
`Next ID = 464`
`Next ID = 466`
## Items
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 463 | 0.14.0 | | defect | **Show the judge the transcript's tail whatever the size of the records.** | 2 | 2 | 3 | 5 | 3 | 1.2 by 6, 1.5 by 4, 1.4 by 2 | 4.2 |
| 465 | 0.14.0 | | | **Decide loop-claude's awaited-merges stop from the pull requests found, not from whether a sentence is empty.** | 1 | 1 | 2 | 2 | 2 | code health by 2 | 3.5 |
| 449 | 0.14.0 | | | **Record do-epic's repo picks and sub-task summaries in the team's own spelling, such as `core-4` and `core-4: Bygg …`, as its config sets them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 6 | 2.0 |
| 453 | 0.14.0 | | | **Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 5 | 1.8 |
| 450 | 0.14.0 | | | **Add `do-epic <EPIC-KEY> --dry-run`, which prints every Jira write planning would make and each chunk that would start, and makes none of them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 5 | 1.6 |
| 454 | 0.14.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
| 464 | 0.14.0 | | | **Fail a test where loop-claude's forge effect runs the forge's CLI without its timeout.** | 1 | 1 | 2 | 2 | 1 | 1.1 by 1 | 0.4 |
| 446 | 0.15.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
| 462 | 0.15.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
| 77 | 0.15.0 | | | **Teach `bin/metric-bench` Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel.** | 4 | 2 | 1 | 5 | 6 | 1.1 by 7, 1.4 by 7 | 2.1 |
@@ -90,6 +92,14 @@ Touches:
- `bin/agent_cycle/judge.py`: `JUDGE_PROMPT_CHARS` (small), `judge_prompt` (small)
- `bin/agent_cycle/test_judge.py`: `JudgePrompt`
### 465. Decide loop-claude's awaited-merges stop from the pull requests found, not from whether a sentence is empty.
Both seats of item 457's paired ruling voted Locality worse at this place. `planned` in `bin/release_plan/next_chunk.py` sets `NoItem.awaits_merge` to `bool(merges)`, where `merges` is the sentence `awaited_merges` wrote, so the loop's stop hangs on a string's truthiness, and `chunks_to_start` in `bin/loop_claude/loop/chunk_windows.py` reads it two packages away. Have `awaited_merges` return the pull requests it found, with the items each finishes, and build both the sentence and the flag from them, so a reader sees what stops the loop where it is decided.
Touches:
- `bin/release_plan/next_chunk.py`: `planned` (small), `awaited_merges`
- `bin/release_plan/test_release_standing.py`
### 449. Record do-epic's repo picks and sub-task summaries in the team's own spelling, such as `core-4` and `core-4: Bygg …`, as its config sets them.
do-epic writes its own spelling into a team's Jira: a pick as `repo:core-4` and a sub-task's summary as `[core-4] <the item's summary>`. A team with its own convention, such as TW's label `core-4` and summary `core-4: Bygg …` with a capital after the colon, then finds two labels on each issue and summaries in a shape its board doesn't use. Goal 1.6 asks the loop to fit the tracker's conventions, not change them.
@@ -163,6 +173,14 @@ Touches:
- `bin/do_epic/backend/test_jira.py`
- `README.md`: `### Set up a project` (small)
### 464. Fail a test where loop-claude's forge effect runs the forge's CLI without its timeout.
Today no test fails where `system_effects` builds `forge` as `runner(cwd)` instead of `runner(cwd, FORGE_TIMEOUT)`: a mutant of `bin/loop_effects/effects.py:128` that drops the timeout survived item 457's mutation run. A stalled `gh` or `tea` would then hold the loop again, which is what the timeout stops. Let `system_effects` take the timeout as a parameter that defaults to `FORGE_TIMEOUT`, as it takes `backends`, and test that a command outlasting a short one comes back as the `stopped after` Failure.
Touches:
- `bin/loop_effects/effects.py`: `system_effects` (small)
- `bin/loop_effects/test_effects.py`: `ForgeEffect` (small)
### 446. Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.
Item 422 judges a worker that stalls before its result, but only reports: each verdict goes to the terminal and to `stuck-workers.md` in the project's transcript archive. Question for the human: after a few days of verdicts there, do they match what you would have done? Once you say yes, kill only the process a `stuck` verdict names, and only where the pid is below the worker's claude, never the worker or the loop, and record the call in a decision.