Renumber the two items filed here to 426 and 427, since main took 424 and 425
CI / tests (pull_request) Has been cancelled

This commit is contained in:
2026-11-18 17:05:16 +01:00
parent ba3f8a2b15
commit 251ca067d5
+8 -8
View File
@@ -6,17 +6,17 @@
`Bar = 0.1`
`Next ID = 426`
`Next ID = 428`
## Items
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 424 | 0.12.0 | | | **Read each epic issue's scores, its blockers and whether the loop filed it through `EpicStore`, from both backends.** | 2 | 2 | 2 | 4 | 3 | 1 by 5 | 1.9 |
| 426 | 0.12.0 | | | **Read each epic issue's scores, its blockers and whether the loop filed it through `EpicStore`, from both backends.** | 2 | 2 | 2 | 4 | 3 | 1 by 5 | 1.9 |
| 408 | 0.12.0 | | | **Score an epic's items by one weight chain, the epic's achieve goals, then code health, then the item's repo goals, and order them by score, then by Blocked by.** | 3 | 2 | 3 | 6 | 4 | 1 by 5 | 1.6 |
| 425 | 0.12.0 | 408, 424 | | **Re-rank Jira's backlog to match an epic's ranking, moving only the issues the loop filed, so people's issues keep their rank.** | 3 | 2 | 3 | 6 | 3 | 1 by 5 | 1.9 |
| 427 | 0.12.0 | 408, 426 | | **Re-rank Jira's backlog to match an epic's ranking, moving only the issues the loop filed, so people's issues keep their rank.** | 3 | 2 | 3 | 6 | 3 | 1 by 5 | 1.9 |
| 401 | 0.12.0 | | | **Move loop-claude's cycle, judge, interrupt, tmux and routing into a package a second entry point drives, with loop-claude's behaviour unchanged.** | 3 | 2 | 3 | 6 | 6 | 1 by 3, code health by 2 | 1.8 |
| 410 | 0.12.0 | 401, 408, 425 | | **Run `do-epic <EPIC-KEY>`: one tmux session per epic, a window per chunk, up to the epic's cap of running chunks and each repo's `parallel-chunks`, and never in a repo a loop-claude is running chunks in.** | 3 | 2 | 3 | 6 | 6 | 1 by 5 | 0.8 |
| 410 | 0.12.0 | 401, 408, 427 | | **Run `do-epic <EPIC-KEY>`: one tmux session per epic, a window per chunk, up to the epic's cap of running chunks and each repo's `parallel-chunks`, and never in a repo a loop-claude is running chunks in.** | 3 | 2 | 3 | 6 | 6 | 1 by 5 | 0.8 |
| 416 | 0.12.0 | 410 | | **Finish an epic's repo item with a bullet under its repo's `CHANGELOG.md` → `## Unreleased`, or with none where the repo's plan is in Jira.** | 1 | 1 | 1 | 1 | 2 | 1 by 5 | 2.1 |
| 413 | 0.12.0 | 410 | | **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.** | 3 | 2 | 3 | 6 | 4 | 1 by 5 | 1.6 |
| 415 | 0.12.0 | 410, 413 | | **Finish an epic: run release-review passes on each repo it changed, work what they file, have the human confirm each goal, post a summary comment, and close the epic in Jira last.** | 3 | 2 | 3 | 6 | 5 | 1 by 5 | 1.2 |
@@ -84,9 +84,9 @@
## Details
### 424. Read each epic issue's scores, its blockers and whether the loop filed it through `EpicStore`, from both backends.
### 426. Read each epic issue's scores, its blockers and whether the loop filed it through `EpicStore`, from both backends.
Today `EpicIssue` holds none of the three, so do-epic cannot score or order an epic's items (item 408) or tell a person's issue from its own (item 425). The Jira backend reads them as `plan_store/jira_epic.py` does: the `plan-item` issue property, its `Filed by` key, and the "is blocked by" links. The contract tests in `contract.py` cover both backends.
Today `EpicIssue` holds none of the three, so do-epic cannot score or order an epic's items (item 408) or tell a person's issue from its own (item 427). The Jira backend reads them as `plan_store/jira_epic.py` does: the `plan-item` issue property, its `Filed by` key, and the "is blocked by" links. The contract tests in `contract.py` cover both backends.
Touches:
@@ -100,14 +100,14 @@ Touches:
Where the epic and a repo disagree, the epic wins (`docs/decisions.md` → `do-epic: drives one Jira epic …`). An item without a repo weighs only the epic's goals. Build the chain as one list for `goal_weights`, score with `ranking.item_score` and order with `blockers_first`. `plan/ranking.py` `score` is a place the seats found hard, so the scorer must not add a branch to it.
The epic's and a repo's goal numbers collide, so a Moves cell needs a spelling for a repo's goal beside the epic's; a panel of readers picks it before it ships (`~/.claude/CLAUDE.md` → "Working loop"). The scorer takes the items and each repo's goals as values; item 424 reads them from the tracker, and item 425 re-ranks Jira by the order.
The epic's and a repo's goal numbers collide, so a Moves cell needs a spelling for a repo's goal beside the epic's; a panel of readers picks it before it ships (`~/.claude/CLAUDE.md` → "Working loop"). The scorer takes the items and each repo's goals as values; item 426 reads them from the tracker, and item 427 re-ranks Jira by the order.
Touches:
- `bin/plan/todo_table.py`: `parse_moves` (small)
- `bin/do_epic/ranking.py`
### 425. Re-rank Jira's backlog to match an epic's ranking, moving only the issues the loop filed, so people's issues keep their rank.
### 427. Re-rank Jira's backlog to match an epic's ranking, moving only the issues the loop filed, so people's issues keep their rank.
Split from item 408 (`docs/decisions.md` → `do-epic: drives one Jira epic …`). `EpicStore` gains a rank call, in both backends and the contract tests. Lift `JiraPlan.rank_refusal` to a module function both stores call. Walk the target order: where the issue at a position isn't the target's, rank the target's just before it; the slots people's issues hold stay theirs. A rank Jira refuses stops the walk and is reported, since a wrongly ranked team backlog takes hours to restore.