Finish item 461 in the plan
CI / tests (pull_request) Successful in 3m47s

This commit was merged in pull request #646.
This commit is contained in:
Lilleman
2026-11-19 23:34:00 +01:00
parent 04852c3417
commit 2efe914521
2 changed files with 4 additions and 10 deletions
+4
View File
@@ -1,5 +1,9 @@
# Changelog
## Unreleased
- `larv-review prepare-scoring` takes the scoring run's project values from the checkout's `skills/comprehension-panel/seat-prompts.md` where the working-rules file holds no "Scoring run" section, not only where that file is missing.
## 0.13.0
- Fix loop-claude stopping after a finished chunk: its judge may now quote the worker's task as evidence, so the loop starts the next chunks instead of exiting.
-10
View File
@@ -13,7 +13,6 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 460 | 0.14.0 | | | **Review the judge's fix for quoting the worker's task as evidence with every larv-review pass it fires, and adjust it to their findings.** | 2 | 2 | 3 | 5 | 2 | code health by 3, 1.1 by 5 | 7.2 |
| 461 | 0.14.0 | | defect | **Take the scoring run's project values from `seat-prompts.md` where the working-rules file holds no "Scoring run" section, so `larv-review prepare-scoring` runs in claude-config again.** | 1 | 1 | 2 | 2 | 1 | code health by 3 | 5.5 |
| 452 | 0.14.0 | | | **Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.** | 3 | 2 | 2 | 5 | 5 | 1.6 by 7, 1.5 by 3 | 2.1 |
| 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 |
| 458 | 0.14.0 | | | **Resume a chunk whose pull request awaits a person's merge once it no longer merges cleanly into the default branch, so the worker brings it level again.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4, 1.5 by 3 | 1.9 |
@@ -92,15 +91,6 @@ Touches:
- `bin/agent_cycle/test_judge.py`
- `bin/judge_replay/test_judge_replay.py`
### 461. Take the scoring run's project values from `seat-prompts.md` where the working-rules file holds no "Scoring run" section, so `larv-review prepare-scoring` runs in claude-config again.
`prepare-scoring` falls back to `skills/comprehension-panel/seat-prompts.md` → "claude-config's values" only where the working-rules file is missing. Since claude-config's project config names `docs/decisions.md` as its working rules, that file exists, holds no "Scoring run" section, and `prepare-scoring` exits 1. No chunk can then record the scoring run its merge owes.
Touches:
- `bin/larv_review/scoring_setup.py`: `prepare_scoring` (small)
- `bin/larv_review/test_scoring_setup.py`
### 452. Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.
do-epic counts an issue as done only where Jira's status category is done, and moves a finished chunk's issue to done itself, by `jira-finish-transition`. On a team whose CI moves issues through the workflow, both are wrong. On TW, CI moves an issue to Code Review when its pull request opens, to Release Ready when it merges, and to Done when it is deployed. So do-epic would move an issue to Done before it is deployed, and would hold every blocked issue until the blocker is deployed, though the team wants blocked work to start once the blocker's pull request merges.