Move item 474 to 0.15.0 so mutation tests run in docs-and-tools before TW-13503 #672

Merged
lilleman merged 1 commits from move-474 into main 2026-11-20 18:56:32 +01:00
+23 -14
View File
@@ -12,9 +12,10 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 474 | 0.15.0 | | | **Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.** | 2 | 2 | 3 | 5 | 3 | 1.1 by 4 | 1.5 |
| 454 | 0.15.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 |
| 472 | 0.15.0 | 454 | owner | **Let a project's config name a working branch per epic, such as `TW-12345`, that chunks branch off, merge into and keep level with `main`, so a person merges the finished epic into `main` in one pull request.** | 4 | 2 | 3 | 7 | 7 | 1.5 by 6, 1.6 by 7 | 1.1 |
| 467 | 0.15.0 | 454, 472 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 470 and 472 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 467 | 0.15.0 | 454, 472, 474 | question | **Cut 0.15.0 as soon as every other item in it has merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 469 | 0.15.1 | | | **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 |
| 446 | 0.16.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.16.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 |
@@ -38,7 +39,6 @@
| 68 | 0.16.0 | | principle | **Test `workflow-bench/compare.py`'s blinding and `bench.py`'s run plan.** | 2 | 1 | 1 | 2 | 4 | 1.1 by 5 | 1.5 |
| 102 | 0.16.0 | | | **Give loop-claude's retry delay, and the file it reads the machine's memory from, environment overrides, so the black-box test stops replacing `time.sleep` and `machine_load.memory.MEMINFO` through `sitecustomize`.** | 1 | 1 | 2 | 2 | 3 | 1.1 by 4 | 1.5 |
| 135 | 0.16.0 | | | **Fingerprint only the modules loop-claude imports, so editing another tool's code no longer reloads a running loop.** | 2 | 2 | 3 | 5 | 3 | 1.1 by 4 | 1.5 |
| 474 | 0.16.0 | | | **Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.** | 2 | 2 | 3 | 5 | 3 | 1.1 by 4 | 1.5 |
| 443 | 0.16.0 | | | **Measure whether compacting a waiting worker's session cut the cost of 20 chunks with an interrupt, with quality holding.** | 2 | 2 | 1 | 3 | 3 | 1.4 by 4 | 1.4 |
| 5 | 0.16.0 | | decision | **Key a project on its checkout's full path, and refuse to start while another session uses that key.** | 4 | 2 | 3 | 7 | 5 | 1.1 by 6 | 1.4 |
| 291 | 0.16.0 | | owner | **Let `principles/technical-principles.md` → "Sane defaults" allow a library whose README goals ask that it work with no config to default the clock and randomness in its public constructor, where a documented option overrides each.** | 1 | 2 | 3 | 4 | 1 | 1.2 by 3 | 1.3 |
@@ -78,6 +78,26 @@
## Details
### 474. Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.
Found on 2026-11-20 while shipping TW-13648 in Timewave's `docs-and-tools`: `mutate-changes` failed twice there, so its worker mutated 18 changed lines by hand instead. The first run failed on a module path: the tests in `docker/scripts/` import the script under test as a top-level module (`import run_harness`), which mutmut's copy of the tree doesn't resolve as the tests expect. The second run crashed inside mutmut, with a `KeyError` in its worker pool.
- Find why each run failed, from a run against `docs-and-tools` at the commit TW-13648 merged.
- Where the module path is the cause, make `mutate-changes` run tests that import a script by its file name, as `docs-and-tools` does, the way they run outside mutmut.
- Where mutmut itself crashes, catch that crash and say so in one line naming mutmut and the error, so the worker knows to mutate by hand, instead of a traceback.
- Item 462 covers tests that fail in mutmut's copy of claude-config itself; check whether one fix serves both.
Release: lilleman moved it to 0.15.0 on 2026-11-20, ahead of epic TW-13503, which changes `docs-and-tools` in six sub-tasks. mutmut costs no tokens and tries every mutation it knows on each changed line; a worker that mutates by hand pays tokens for each edit, test run and revert, and tried only 18 mutants on TW-13648.
Touches:
- `bin/mutate_changes/mutmut_tool.py`: `mutate_folder`, `read_folder`, `project_setup`, `copy_files`, `mutate_copy`, `configured_run`
- `bin/mutate_changes/mutmut_setup.py`: `mutmut_config`
- `bin/mutate_changes/mutmut_mutants.py`: `module`, `mutant_globs` (small)
- `bin/mutate_changes/tool_process.py`: `failed` (small)
- `bin/mutate_changes/test_mutate_changes.py`
- `bin/mutate_changes/test_mutate_changes_runs.py`
### 454. 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.
When a do-epic chunk starts, its issue stays as Jira holds it: unassigned, in New and outside the sprint. A team whose board shows who works on what, such as TW, where an issue being worked is assigned to the person, In Progress and in the active sprint, then sees nothing of the loop's work. Today each worker would have to do this by hand, from rules only some machines hold.
@@ -127,7 +147,7 @@ Touches:
- `docs/decisions.md`
- `README.md`: `### Set up a project` (small)
### 467. Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 470 and 472 have merged, before its release review, and run that review in 0.15.1.
### 467. Cut 0.15.0 as soon as every other item in it has merged, before its release review, and run that review in 0.15.1.
lilleman's call on 2026-11-20: they need what 0.15.0 holds to work, so 0.15.0 is cut without a release review. This item holds the loop back from starting 0.15.0's release review once its last item merges: it waits as a question, so the human, or the session that cuts, drops it at the cut. Item 469 moved to 0.15.1 by lilleman's call the same day, so 0.15.0 ships sooner. After the cut, 0.15.1's release review, which runs once 469 has merged, covers what 0.15.0 shipped too, and its follow-ups land in 0.15.1.
@@ -356,17 +376,6 @@ Found by the principles audit of PR #242. The `SITECUSTOMIZE` block in `bin/loop
The maintainability senior and the inherited architect of PR #257's scoring run named `fingerprint` and `exec_if_edited` in `bin/loop_claude/loop/reload.py`: the fingerprint covers every `bin/**/*.py`, so editing `statusline.py` or `rank_todo.py` re-execs a running loop. Make `fingerprint` easier to read.
### 474. Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.
Found on 2026-11-20 while shipping TW-13648 in Timewave's `docs-and-tools`: `mutate-changes` failed twice there, so its worker mutated 18 changed lines by hand instead. The first run failed on a module path: the tests in `docker/scripts/` import the script under test as a top-level module (`import run_harness`), which mutmut's copy of the tree doesn't resolve as the tests expect. The second run crashed inside mutmut, with a `KeyError` in its worker pool.
- Find why each run failed, from a run against `docs-and-tools` at the commit TW-13648 merged.
- Where the module path is the cause, make `mutate-changes` run tests that import a script by its file name, as `docs-and-tools` does, the way they run outside mutmut.
- Where mutmut itself crashes, catch that crash and say so in one line naming mutmut and the error, so the worker knows to mutate by hand, instead of a traceback.
- Item 462 covers tests that fail in mutmut's copy of claude-config itself; check whether one fix serves both.
Not needed to start epic TW-13503: a worker can mutate the changed lines by hand, as TW-13648's did, so it lands in 0.16.0.
### 443. Measure whether compacting a waiting worker's session cut the cost of 20 chunks with an interrupt, with quality holding.
The check lilleman set for item 310 on 2026-11-11, which project principle 1 asks for before a cost cut stands: compare the cost entries of 20 archived chunks with an interrupt from before the compaction shipped against 20 from after it. Measure the tokens written to the cache by each resume after an interrupt, and the tokens per finished chunk, and check that review rounds and unfinished verdicts per chunk hold. Where the saving doesn't show, or quality drops, file an item to remove the compaction or retune `COMPACT_FLOOR` and `CACHE_MARGIN` in `bin/agent_cycle/interrupt.py`. Record the outcome as a decision. Start it once 20 chunks with an interrupt have run on 0.12.0 or later.