Make the Touches lists of items 400, 401, 416, 420, 421 and 422 readable
CI / tests (pull_request) Successful in 4m22s

This commit was merged in pull request #604.
This commit is contained in:
2026-11-18 14:52:51 +01:00
parent baee3252ca
commit bc65de4bf7
+12 -12
View File
@@ -103,11 +103,11 @@ Touches:
- `bin/loop_claude/cycle/prompts.py`: `QUOTE_SOURCES`, `ANSWER_DESTINATIONS`
- `bin/loop_claude/test_loop_claude.py`
- `bin/loop_claude/test_black_box.py`
- `bin/judge_replay/main.py` (small)
- `bin/judge_replay/replay.py` (small)
- `bin/judge_replay/archived_prompt.py` (small)
- `bin/rung_replay/command.py` (small)
- `bin/rung_replay/search.py` (small)
- `bin/judge_replay/main.py`
- `bin/judge_replay/replay.py`
- `bin/judge_replay/archived_prompt.py`
- `bin/rung_replay/command.py`
- `bin/rung_replay/search.py`
- `README.md`: `` ### Packages under `bin/` `` (small)
### 406. Pick each epic item's repo, or for an item without one whether it is Claude's work or a human task, by `repo-rule.md`, record the pick on the issue, and ask the human where the rule leaves it unclear.
@@ -148,7 +148,7 @@ An epic item has no release (`docs/decisions.md` → `do-epic: drives one Jira e
Touches:
- `bin/do_epic/main.py` (small)
- `bin/do_epic/main.py`
### 413. File a finding about an epic goal in the epic and one about a repo goal by that repo's rules, ask the human where unsure which, and give the judge the epic's records beside the repo's.
@@ -191,7 +191,7 @@ Source: a client project's pull request, where a fix hid a regression behind a c
Touches:
- `principles/technical-principles.md`: the tests bullet group, `A valuable test checks behaviour` (small)
- `principles/technical-principles.md`
- `agents/stability-reviewer.md`: `### 11. Tests` (small)
### 420. End a worker that printed its final result and lingers, by killing the background shells it left, after a few minutes, and print each kill with its evidence on loop-claude's terminal.
@@ -208,7 +208,7 @@ Touches:
- `bin/loop_claude/loop/main.py`: `run_loop` (small)
- `bin/loop_claude/loop/lingering_workers.py`
- `README.md`: loop-claude's section (small)
- `README.md`: `## Tools` (small)
### 409. Split an epic item that changes several repos into one Jira sub-task per repo, each labelled for its repo, with the parent tracking the whole change, when do-epic plans the item.
@@ -273,10 +273,10 @@ The test covers each kind refused, a bounded loop that passes, `wait-for` passin
Touches:
- `bin/rule_hook/rules.py`: the rule table (small)
- `bin/rule_hook/rules.py`: `RULES` (small)
- `bin/rule_hook/endless_wait.py`
- `bin/rule_hook/test_rule_hook.py`: the new rule's tests (small)
- `settings.json`: the PreToolUse matcher (small)
- `bin/rule_hook/test_rule_hook.py`: `CommandBreaches` (small)
- `settings.json`
### 311. Hand each worker's claude a Bash output ceiling that saves longer output to a file, and refuse a Read of a session transcript under `~/.claude/projects`.
@@ -338,7 +338,7 @@ Touches:
- `bin/loop_claude/loop/stuck_windows.py`
- `bin/loop_claude/tmux.py`: `Listed`, `listed`
- `README.md`: loop-claude's section (small)
- `README.md`: `## Tools` (small)
### 365. Have `score-outcomes` read the finished and dropped items of a plan outside the checkout, from the project repo's history or from Jira's issue changelogs.