Answer product-owner round 1: 0 🔴, 1 🟡 (0 misread); say where (small) goes in the refusal, file item 425
This commit is contained in:
+2
-2
@@ -1,6 +1,6 @@
|
||||
"""An item's prediction of the files and parts it will touch, as its detail spells it, and where two predictions overlap.
|
||||
|
||||
It sits in plan, beside the items whose details it reads, so that plan_store's `rank_todo.py --check` and todo-item can refuse a list it cannot read: touch_predictions imports plan_store, so plan_store cannot import from touch_predictions.
|
||||
It sits in plan so that plan_store's `FilePlan.check` and todo-item can call `predicted`: touch_predictions imports plan_store, and importing touch_predictions from plan_store would make the two packages import each other.
|
||||
|
||||
The spelling, which the decision `todo.md: an item of the next release predicts the files and parts it will touch …` gives the reasons for:
|
||||
|
||||
@@ -48,7 +48,7 @@ def predicted(detail: str) -> Touches | None | Failure:
|
||||
break
|
||||
read = bullet(line)
|
||||
if read is None:
|
||||
return Failure(f"the bullet {line!r} under `{LABEL}` is not a path in backticks, then optionally a colon and its parts, each a name in backticks or `lines <first>-<last>`, and optionally `{SMALL}`")
|
||||
return Failure(f"the bullet {line!r} under `{LABEL}` is not a path in backticks, then optionally a colon and its parts, each a name in backticks or `lines <first>-<last>` that `{SMALL.strip()}` may follow; `{SMALL.strip()}` follows a part, never a bare path")
|
||||
if any(span and span[0] > span[1] for span in map(line_range, read[1])):
|
||||
return Failure(f"the bullet {line!r} under `{LABEL}` holds a line range whose first line comes after its last")
|
||||
touches = together([touches, {read[0]: read[1]}])
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
|
||||
`Bar = 0.1`
|
||||
|
||||
`Next ID = 425`
|
||||
`Next ID = 426`
|
||||
|
||||
## Items
|
||||
|
||||
@@ -27,7 +27,7 @@
|
||||
| 414 | 0.12.0 | 410 | | **DM the human through the notifier when a human-task issue blocks the epic's next item, and poll until it closes.** | 2 | 2 | 2 | 4 | 3 | 1 by 5 | 1.9 |
|
||||
| 417 | 0.12.0 | 410 | | **Run do-epic end to end against a sandbox epic on a real Jira site with a command of its own, outside `run-tests`.** | 2 | 1 | 1 | 2 | 3 | 1 by 5 | 1.9 |
|
||||
| 421 | 0.12.0 | | | **Refuse in rule-hook a Bash or Monitor wait that has no end: a loop without a time or count cap, and a `pgrep -f` or `pkill -f` whose pattern the same command line contains.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 4 | 1.3 |
|
||||
| 424 | 0.12.0 | | | **Refuse a Touches: list touch-predictions cannot read in todo-item add and edit, and in rank_todo.py --check.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 4 | 1.3 |
|
||||
| 424 | 0.12.0 | | | **Refuse a `Touches:` list touch-predictions cannot read in todo-item add and edit, and in rank_todo.py --check.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 4 | 1.3 |
|
||||
| 316 | 0.12.0 | | | **Launch comprehension seats as an agent type of their own under `agents/`, without `CLAUDE.md` and the skill and agent listings a general-purpose subagent carries.** | 2 | 2 | 2 | 4 | 3 | 1.4 by 3 | 1.0 |
|
||||
| 310 | 0.12.0 | | | **Compact a waiting worker's session shortly before its prompt cache expires, only when the human has not answered an interrupt by then.** | 3 | 2 | 3 | 6 | 4 | 1.4 by 3 | 0.9 |
|
||||
| 422 | 0.12.0 | 401, 420 | | **Check every 5 minutes whether a tmux window of the loop looks stuck by other signs than a lingering worker, investigate it with a headless claude, and kill only the process the investigation names.** | 3 | 2 | 3 | 6 | 5 | 1.5 by 4 | 0.8 |
|
||||
@@ -40,6 +40,7 @@
|
||||
| 341 | 0.13.0 | | | **Hand each worker's claude a lower Read limit through `CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS`, kept only where replays of the archived review rounds find what two unchanged replays find.** | 2 | 2 | 3 | 5 | 3 | 1.4 by 3 | 1.0 |
|
||||
| 298 | 0.13.0 | | | **Send the judge only the decision entries and the transcript tail a verdict needs, and keep the cut only where `judge-replay` changes no verdict kind.** | 3 | 3 | 3 | 7 | 4 | 1.4 by 2, 1.5 by 1 | 0.9 |
|
||||
| 395 | 0.13.0 | | decision | **Keep each block a save didn't change, with its localId, and the spacing paragraphs beside it as Jira or Confluence holds them.** | 3 | 2 | 2 | 5 | 5 | 1.6 by 4 | 0.8 |
|
||||
| 425 | 0.13.0 | | | **Show on loop-claude's terminal why it doesn't start a chunk beside the next item, as chunk-preflight prints it.** | 1 | 1 | 2 | 2 | 2 | 1.5 by 2 | 0.7 |
|
||||
| 367 | 0.13.0 | | | **Check that every write to a Jira plan leaves it ranked, as rule-hook's `todo-rank-check` checks `todo.md` today.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 2 | 0.7 |
|
||||
| 423 | 0.13.0 | | | **Skip the judge's model call on a worker's final message that the offline classifier decides is finished.** | 3 | 3 | 3 | 7 | 5 | 1.4 by 2 | 0.4 |
|
||||
| 77 | 0.14.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 |
|
||||
@@ -268,11 +269,11 @@ Touches:
|
||||
- `bin/rule_hook/test_rule_hook.py`: `CommandBreaches` (small)
|
||||
- `settings.json`
|
||||
|
||||
### 424. Refuse a Touches: list touch-predictions cannot read in todo-item add and edit, and in rank_todo.py --check.
|
||||
### 424. Refuse a `Touches:` list touch-predictions cannot read in todo-item add and edit, and in rank_todo.py --check.
|
||||
|
||||
On 2026-11-18 six items (400, 401, 416, 420, 421 and 422) held `Touches:` lists that touch-predictions cannot read, such as ``- `bin/judge_replay/main.py` (small)`` and ``- `README.md`: loop-claude's section (small)``. chunk-preflight reads the lists first, so loop-claude silently started nothing beside item 401, and slots sat idle for over an hour; the same mistake had been fixed by hand on 2026-11-16 (commit 4b508615). Nothing checked a list when it was written.
|
||||
On 2026-11-18 six items (400, 401, 416, 420, 421 and 422) held `Touches:` lists that touch-predictions cannot read, such as ``- `bin/judge_replay/main.py` (small)`` and ``- `README.md`: loop-claude's section (small)``. loop-claude reads the lists before it starts chunks beside the next item, so it didn't start any chunk beside item 401, and didn't say why; slots sat idle for over an hour. The same mistake had been fixed by hand on 2026-11-16 (commit 4b508615). Nothing checked a list when it was written.
|
||||
|
||||
Both checks call `predicted`, so they cannot drift from the reader; its spelling stays as it is. The reader moves from `bin/touch_predictions/prediction.py` to `bin/plan/touches.py`, since touch_predictions imports plan_store and plan_store's check needs the reader. `todo-item add` and `edit --detail` refuse such a detail, writing nothing, in main.py before the plan's backend gets it, so a plan in Jira is held to it too. `rank_todo.py --check` fails on any item in todo.md whose list it cannot read, naming the item and the reason. Moves 1.5 (delivery speed): idle chunk slots are what the mistake cost.
|
||||
Both checks call `predicted`, touch-predictions' parser, so they cannot drift from it, and the spelling it reads stays as it is. The parser moves from `bin/touch_predictions/prediction.py` to `bin/plan/touches.py`, with its tests, since touch_predictions imports plan_store and plan_store's check needs the parser. `todo-item add` and `edit --detail` refuse such a detail, writing nothing, in main.py before the plan's backend gets it, so a plan in Jira is held to it too. `rank_todo.py --check` fails on any item in todo.md whose list it cannot read, naming the item and the reason. Moves 1.5 (delivery speed): idle chunk slots are what the mistake cost.
|
||||
|
||||
Touches:
|
||||
|
||||
@@ -282,7 +283,9 @@ Touches:
|
||||
- `bin/test_rank_todo.py`
|
||||
- `bin/rank_todo.py`: `(module)` (small)
|
||||
- `bin/plan/touches.py`
|
||||
- `bin/plan/test_touches.py`
|
||||
- `bin/touch_predictions/prediction.py`
|
||||
- `bin/touch_predictions/test_touch_predictions.py`
|
||||
- `rules/todo-items.md`: `` # Todo items (`todo.md`) `` (small)
|
||||
|
||||
### 316. Launch comprehension seats as an agent type of their own under `agents/`, without `CLAUDE.md` and the skill and agent listings a general-purpose subagent carries.
|
||||
@@ -425,6 +428,10 @@ Touches:
|
||||
|
||||
Today a Jira detail edited in one line, or a Confluence record with one entry appended, is written back whole by adf-codec's portable pair, which drops each block's localId and the empty paragraphs Jira uses for spacing. A save whose text is the text a read showed already sends nothing (`docs/decisions.md` → `project config: the loop shows a Jira description and a Confluence page as adf-codec's portable markdown, …`). Match the saved markdown's top-level blocks against the held document's, each as the portable pair reads it, and send the held block where they match. The decision's limit on partial saves ends with this item.
|
||||
|
||||
### 425. Show on loop-claude's terminal why it doesn't start a chunk beside the next item, as chunk-preflight prints it.
|
||||
|
||||
`chunks_beside` names each item it refuses and why, such as an unreadable `Touches:` list, and chunk-preflight prints those lines, but loop-claude's `chunk_windows.may_start` keeps only `picked` and drops them, so idle slots show no reason. Found by item 424's product-owner review; a list a person edits in Jira's UI, or one filed before item 424, still reaches loop-claude unchecked.
|
||||
|
||||
### 367. Check that every write to a Jira plan leaves it ranked, as rule-hook's `todo-rank-check` checks `todo.md` today.
|
||||
|
||||
One of 0.13.0's history ports, per lilleman's call of 2026-11-12.
|
||||
|
||||
Reference in New Issue
Block a user