Finish item 466 in the plan
CI / tests (pull_request) Successful in 2m51s

This commit was merged in pull request #655.
This commit is contained in:
Lilleman
2026-11-20 09:12:35 +01:00
parent 0c44db8442
commit 798f08dc98
2 changed files with 4 additions and 8 deletions
+4
View File
@@ -1,5 +1,9 @@
# Changelog
## Unreleased
- The stability reviewer checks each parser that splits text on a separator or strips a suffix against a value that holds the separator, and reports a row the parse misplaces or drops.
## 0.14.0
- `loop-claude`'s judge stops, naming how much to cut the records by, rather than judge a prompt that leaves it less than the transcript's last 50,000 characters. A file the project's config names for two records is read once.
-8
View File
@@ -15,7 +15,6 @@
| 449 | 0.15.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.15.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.15.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 |
| 466 | 0.15.0 | | | **Have stability-reviewer check each parser that splits a field on a separator against a value that holds the separator.** | 1 | 2 | 2 | 3 | 2 | 1.1 by 3 | 1.2 |
| 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 |
| 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 |
@@ -130,13 +129,6 @@ Touches:
- `bin/do_epic/test_planning.py`
- `README.md`: `## Tools` (small)
### 466. Have stability-reviewer check each parser that splits a field on a separator against a value that holds the separator.
An outside reviewer found that an importer split a full address on its separator and took the last part as the leaf, though the leaf itself may hold the separator; the importer's own test fixture held such a value, and each such row was dropped with only a log line. Our stability pass read the function and its tests and didn't raise it, and no deterministic tool covers it: the mutation tool does not mutate that language, and a mutant would not show a wrong split. Add one line to the stability reviewer's checks: where the change splits text on a separator or strips a suffix, look in the fixtures and a sample of the source data for a field that holds the separator, and report a row the parse then misplaces or drops.
Touches:
- `agents/stability-reviewer.md`: `### 5. Edge Cases & Input Validation` (small)
### 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.