Finish item 463 in the plan

This commit is contained in:
Lilleman
2026-11-20 01:51:10 +01:00
parent dbe275e59f
commit 1774bb4274
2 changed files with 1 additions and 15 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- `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.
- Under `merge = "human"`, `loop-claude` and `chunk-preflight` pass over an item whose ready pull request awaits a person's merge, and `loop-claude` stops, naming those pull requests, once every item left awaits one.
- do-epic reads two new settings from a project's config: `jira-unblocking-statuses` names the statuses at which an issue unblocks the issues it blocks, and `jira-automation-moves-issues` leaves the move out of "In Progress" to the team's own automation.
- The prose standard asks that a sentence about several named things holds for each of them.
-15
View File
@@ -12,7 +12,6 @@
| 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 |
@@ -78,20 +77,6 @@
## Details
### 463. Show the judge the transcript's tail whatever the size of the records.
`judge_prompt` in `bin/agent_cycle/judge.py` gives the transcript only what `JUDGE_PROMPT_CHARS = 400000` leaves after the premises, the records and the rules. In claude-config those now take about 519,000 to 523,000 characters, so `room` clamps to 0 and the judge reads the task above an empty transcript. Every judge prompt archived for claude-config since at least 2026-11-19 17:16 shows none:
- The 0.13.0 chunks of items 448, 455 and 451 each stopped after the judge failed three times.
- The chunk of items 458 and 459 drew four `unfinished` verdicts after it had merged, each quoting only the task.
The judge sees neither a merge nor a worker's question, so every chunk here loops until a human ends it. Item 460's fix, letting the judge quote the task, treated a symptom of this.
Keep the transcript's tail a floor of the budget. Where the head leaves less, cut the records or stop with a message that names their size, rather than send a blind prompt. The constant's comment sizes the budget for a 200,000-token context, so raise it only where the judge's model has room. Item 298 cuts the records for cost; this item only guarantees the transcript room. Write first the test that fails today: a brief whose records exceed the budget still shows the transcript's last message.
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.