Merge remote-tracking branch 'origin/main' into item-453
CI / tests (pull_request) Has been cancelled

This commit is contained in:
Lilleman
2026-11-20 13:57:44 +01:00
7 changed files with 118 additions and 28 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- do-epic names the team's own label for each repo, from the `[label-repos]` table, when it tells a chunk's worker how to file a finding or a release review, and keeps `repo:<name>` for a repo the table doesn't name.
- do-epic records a repo pick, and the summary of each sub-task it files, in the team's own spelling: a label from the `[label-repos]` table of its config, and a `sub-task-summary` template with `{label}` and `{Summary}`.
- Add `do-epic <EPIC-KEY> --dry-run`, which prints every Jira write planning would make and each chunk that would start, and makes none of them.
- The stability reviewer checks each parser that splits text on a separator or strips a suffix against a value that holds the separator, and reports a row the parse misplaces or drops.
+16 -8
View File
@@ -7,7 +7,7 @@ import fcntl
import pathlib
import typing
from do_epic.repo_pick import also, CLAUDE_LABEL, HUMAN_LABEL, LabelRepos, of_label, REPO_PREFIX, REVIEW_LABEL
from do_epic.repo_pick import CLAUDE_LABEL, HUMAN_LABEL, label_of, LabelRepos, of_label, REPO_PREFIX, REVIEW_LABEL, team_label
from do_epic.backend.protocol import EpicIssue, EpicStore
from do_epic.epic_record import EpicRecord
from failure import Failure
@@ -20,15 +20,22 @@ LABEL = "--label"
BLOCKED_BY = "--blocked-by"
PARENT = "--parent"
RECORD_DECISION = "--record-decision"
# The labels that say where an issue is worked, as do-epic's scheduler reads them.
LABELS = f"`{REPO_PREFIX}<name>` for the repo that works it, `{CLAUDE_LABEL}` for work of Claude's that changes no repo, or `{HUMAN_LABEL}` for a task of the human's"
def worked_by(team: LabelRepos) -> str:
"""The labels that say where an issue is worked, as do-epic's scheduler reads them: for each repo the team's table names, the label on its first line for that repo, and `repo:<name>` for any other repo."""
named = [f"`{label}` for the repo {name}" for name in sorted(set(team.values())) if (label := team_label(name, team))]
repos = ", ".join([*named, f"`{REPO_PREFIX}<name>` for {'any other repo' if named else 'the repo'} that works it"])
return f"{repos}, `{CLAUDE_LABEL}` for work of Claude's that changes no repo, or `{HUMAN_LABEL}` for a task of the human's"
# Under the epic's folder, the file a do-epic holds locked while it appends a decision.
DECISIONS_LOCK = "decisions.lock"
USAGE = f"""do-epic <EPIC-KEY> {FILE} <summary> [{LABEL} <label>]... [{BLOCKED_BY} <KEY>] [{PARENT} <KEY>] [<<'EOF' detail EOF]
do-epic <EPIC-KEY> {RECORD_DECISION} <title> <<'EOF' entry EOF"""
HELP = f"""{FILE} files a finding about one of the epic's goals as an open issue of the epic, with the markdown piped in as its description.
A finding about a repo's own goals goes into that repo's plan instead.
{LABEL} is {LABELS}; without one, the next `do-epic <EPIC-KEY>` you run picks where the issue is worked.
{LABEL} is {worked_by({})}; without one, the next `do-epic <EPIC-KEY>` you run picks where the issue is worked.
A second {LABEL}, `{REVIEW_LABEL}`, marks the issue as a repo's release review, which the epic's finishing files.
{BLOCKED_BY} <KEY> makes the new issue wait for the issue <KEY>, which is a child issue of the epic or a sub-task of one.
{PARENT} <KEY> files the new issue as a sub-task of the child issue <KEY>.
@@ -41,11 +48,12 @@ def instructions(epic: str, launcher: pathlib.Path, language: str, team: LabelRe
next_step = ""
if issue:
parent = f" {PARENT} {issue.parent}" if issue.parent != epic else ""
label = next((f" {LABEL} {each}" for each in issue.labels if of_label(each, team)), "")
pick = next((found for each in issue.labels if (found := of_label(each, team))), None)
label = f" {LABEL} {label_of(pick, team)}" if pick else ""
next_step = f"Where the repo's rules ask for a change to ship as more than one pull request, finish only this issue's pull request, and file only the next one as an issue that waits for it, with `{launcher} {epic} {FILE} \"<summary>\" {BLOCKED_BY} {issue.key}{parent}{label}` and its detail on stdin. "
return (
f"File a finding about one of the epic's goals in the epic, with `{launcher} {epic} {FILE} \"<summary>\" {LABEL} <label>` and its detail on stdin. "
f"The label is {LABELS}; leave it out where you cannot tell, and the next `do-epic` the human runs picks it. "
f"The label is {worked_by(team)}; leave it out where you cannot tell, and the next `do-epic` the human runs picks it. "
"Where filing fails and says the issue may exist, ask the human to look before you file it again. "
"File a finding about a repo's goals by that repo's rules. Where unsure which, ask the human. "
f"Record a decision that governs the epic, such as an answer the human typed, with `{launcher} {epic} {RECORD_DECISION} \"<title>\"` and its text on stdin. "
@@ -96,13 +104,13 @@ def written(epic: str, write: Write, store: EpicStore, team: LabelRepos, record:
flag, value, labels = write.flag, write.value, write.labels
if flag == FILE:
if unread := [label for label in labels if of_label(label, team) is None and label != REVIEW_LABEL]:
return Failure(f"cannot file the finding in the epic {epic}: do-epic doesn't read the label {unread[0]!r}; write {LABELS}{also(team)}")
return Failure(f"cannot file the finding in the epic {epic}: do-epic doesn't read the label {unread[0]!r}; write {worked_by(team)}")
if len(picks := [label for label in labels if of_label(label, team)]) > 1:
return Failure(f"cannot file the finding in the epic {epic}: {listed(picks, 'and')} each say who works it; write one of them")
key = store.file(write.parent or epic, value, text, labels, write.blocked_by)
if isinstance(key, Failure):
return Failure(f"cannot file the finding in the epic {epic}: {key.reason}")
return f"Filed {key} {f'under {write.parent} in ' if write.parent else 'in '}the epic {epic}." + (f" It is blocked by {write.blocked_by}." if write.blocked_by else "") + ("" if any(of_label(label, team) for label in labels) else f" It has no label that says where it is worked, so the next `do-epic {epic}` picks one: {LABELS}.")
return f"Filed {key} {f'under {write.parent} in ' if write.parent else 'in '}the epic {epic}." + (f" It is blocked by {write.blocked_by}." if write.blocked_by else "") + ("" if any(of_label(label, team) for label in labels) else f" It has no label that says where it is worked, so the next `do-epic {epic}` picks one: {worked_by(team)}.")
try:
with decisions_locked(folder):
added = record.append_decision(value, text)
+3 -2
View File
@@ -15,7 +15,7 @@ from do_epic.backend.protocol import EpicIssue, EpicStore
from failure import Failure
from do_epic import findings
from do_epic.split import finished
from do_epic.repo_pick import LabelRepos, recorded, Repo, REPO_PREFIX, REVIEW_LABEL
from do_epic.repo_pick import label_of, LabelRepos, recorded, Repo, REVIEW_LABEL
from text_files.markdown_text import listed
from text_files.piped_text import piped
@@ -57,7 +57,8 @@ def task(epic: str, issues: list[EpicIssue], team: LabelRepos, launcher: pathlib
if lacking := unreviewed(issues, team):
return (
f"{opening} Each repo the epic changed takes a release review first, and {listed(lacking, 'and')} {'has' if len(lacking) == 1 else 'have'} none. "
f"File one issue per such repo, with `{launcher} {epic} {findings.FILE} \"<summary>\" {findings.LABEL} {REPO_PREFIX}<name> {findings.LABEL} {REVIEW_LABEL}` and its detail on stdin, both in {language}, the epic's language. "
f"File one issue per such repo, with `{launcher} {epic} {findings.FILE} \"<summary>\" {findings.LABEL} <label> {findings.LABEL} {REVIEW_LABEL}` and its detail on stdin, both in {language}, the epic's language. "
f"The `<label>` is {listed([f'`{label_of(Repo(name), team)}` for {name}' for name in lacking], 'and')}. "
f"The detail asks for a release review of the whole repo, as the epic's issues left it: the one `~/.claude/skills/larv-review/SKILL.md` → \"Release review\" describes. The epic's key stands in place of the release there, so the review's branch opens with an empty commit titled `Release review of {epic}`. "
"Where filing fails and says the issue may exist, ask the human to look before you file it again. "
f"The chunk is finished once each issue is filed: {DRIVER} works them, and starts this chunk again once the epic holds no open issue."
+17 -1
View File
@@ -93,7 +93,9 @@ class FilingAFinding(FindingsTest):
code, _, err, _ = self.run_with(["ABC-12", "--file", "Retry", "--label", "twu-4", "--label", "repo:api"])
self.assertEqual((code, err), (1, "cannot file the finding in the epic ABC-12: twu-4 and repo:api each say who works it; write one of them\n"))
_, _, err, _ = self.run_with(["ABC-12", "--file", "Retry", "--label", "twu"])
self.assertTrue(err.endswith("or `do-epic-human` for a task of the human's (or the team's `twu-4`)\n"), err)
self.assertTrue(err.endswith(f"write {findings.worked_by({'twu-4': 'tenant-web-ui-4'})}\n"), err)
_, out, _, _ = self.run_with(["ABC-12", "--file", "Retry"])
self.assertTrue(out.endswith(f"picks one: {findings.worked_by({'twu-4': 'tenant-web-ui-4'})}.\n"), out)
def test_a_release_review_takes_its_label_beside_its_repo(self) -> None:
code, out, _, _ = self.run_with(["ABC-12", "--file", "Review api", "--label", "repo:api", "--label", "do-epic-release-review"])
@@ -155,6 +157,20 @@ class Instructions(unittest.TestCase):
self.assertTrue(told.endswith("its text on stdin. Write the issue and the decision in Swedish, the epic's language."), told)
self.assertNotIn("--blocked-by", told)
def test_name_the_labels_the_team_has_for_its_repos(self) -> None:
team = {"core": "core-4", "twu-4": "tenant-web-ui-4"}
self.assertIn(f"The label is {findings.worked_by(team)};", findings.instructions("ABC-12", pathlib.Path("/b/do-epic"), "Swedish", team))
class WorkedBy(unittest.TestCase):
def test_lists_repo_colon_name_alone_for_a_team_without_a_table(self) -> None:
self.assertEqual(findings.worked_by({}), "`repo:<name>` for the repo that works it, `do-epic-claude` for work of Claude's that changes no repo, or `do-epic-human` for a task of the human's")
def test_lists_each_repo_the_table_names_once_by_the_first_label_for_it_in_the_order_of_the_repos(self) -> None:
named = findings.worked_by({"twu-4": "tenant-web-ui-4", "core": "core-4", "c4": "core-4"})
self.assertTrue(named.startswith("`core` for the repo core-4, `twu-4` for the repo tenant-web-ui-4, `repo:<name>` for any other repo that works it, `do-epic-claude`"), named)
self.assertNotIn("`c4`", named)
class RecordingADecision(FindingsTest):
def test_appends_the_entry_to_the_descriptions_decisions(self) -> None:
+7 -1
View File
@@ -54,11 +54,17 @@ class TheFinishingChunksTask(DoEpicTest):
self.assertIn("Finish the epic ABC-12", task)
self.assertIn("first, and api and web have none. ", task)
self.assertIn("first, and api has none. ", finish.task("ABC-12", [issue("ABC-20", "repo:api", done=True)], {}, LAUNCHER, "Swedish"))
self.assertIn('`/b/do-epic ABC-12 --file "<summary>" --label repo:<name> --label do-epic-release-review`', task)
self.assertIn('`/b/do-epic ABC-12 --file "<summary>" --label <label> --label do-epic-release-review`', task)
self.assertIn("`Release review of ABC-12`", task)
self.assertIn("in Swedish", task)
self.assertNotIn("--close-epic", task)
def test_names_each_unreviewed_repos_label_from_the_teams_table_else_repo_colon_name(self) -> None:
done = [issue("ABC-20", "twu-4", done=True), issue("ABC-21", "repo:web", done=True)]
task = finish.task("ABC-12", done, {"twu-4": "tenant-web-ui-4"}, LAUNCHER, "Swedish")
self.assertIn("The `<label>` is `twu-4` for tenant-web-ui-4 and `repo:web` for web. ", task)
self.assertIn("The `<label>` is `twu-4` for tenant-web-ui-4. ", finish.task("ABC-12", done[:1], {"twu-4": "tenant-web-ui-4", "web": "tenant-web-ui-4"}, LAUNCHER, "Swedish"))
def test_then_has_the_human_confirm_each_goal_before_the_summary_and_the_closing(self) -> None:
task = finish.task("ABC-12", REVIEWED, {}, LAUNCHER, "Swedish")
self.assertIn("Finish the epic ABC-12", task)
+2
View File
@@ -426,6 +426,8 @@ class TheFirstPrompt(unittest.TestCase):
self.assertIn("--file \"<summary>\" --blocked-by ABC-23 --parent ABC-20 --label repo:api` and its detail on stdin.", task)
task = chunk_prompt.task(issue("ABC-20", "twu-4", "urgent"), "ABC-12", {"twu-4": "tenant-web-ui-4"}, "/code/api", pathlib.Path("/b/do-epic"), "Swedish", CONFIG)
self.assertIn("--file \"<summary>\" --blocked-by ABC-20 --label twu-4` and its detail on stdin.", task)
task = chunk_prompt.task(issue("ABC-20", "repo:tenant-web-ui-4"), "ABC-12", {"twu-4": "tenant-web-ui-4"}, "/code/api", pathlib.Path("/b/do-epic"), "Swedish", CONFIG)
self.assertIn("--file \"<summary>\" --blocked-by ABC-20 --label twu-4` and its detail on stdin.", task)
def test_a_chunk_without_a_repo_is_told_nothing_of_shipping(self) -> None:
task = chunk_prompt.task(issue("ABC-20"), "ABC-12", {}, None, pathlib.Path("/b/do-epic"), "Swedish", None)
+72 -16
View File
@@ -6,16 +6,17 @@
`Bar = 0.1`
`Next ID = 469`
`Next ID = 472`
## Items
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 469 | 0.15.0 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
| 453 | 0.15.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 |
| 470 | 0.15.0 | | | **Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.** | 3 | 2 | 2 | 5 | 5 | 1.2 by 4, 1.6 by 3 | 1.5 |
| 454 | 0.15.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
| 467 | 0.15.0 | 453, 454 | question | **Cut 0.15.0 as soon as items 449, 450, 453 and 454 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 468 | 0.15.0 | | | **Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4 | 1.4 |
| 467 | 0.15.0 | 453, 454, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 446 | 0.16.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
| 462 | 0.16.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
| 77 | 0.16.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 |
@@ -29,6 +30,7 @@
| 264 | 0.16.0 | | | **Report the comprehension seats and the escalated subagents as subagent types of their own in `routing-figures.md`, with their dollars.** | 2 | 2 | 1 | 3 | 3 | 1.4 by 5 | 1.7 |
| 323 | 0.16.0 | | | **Count a release review as landed once its pull request has merged, whatever its commits are titled.** | 3 | 2 | 3 | 6 | 3 | 1.4 by 3, 1.5 by 2 | 1.7 |
| 342 | 0.16.0 | | | **Research the tooling agents read, search and run commands with once more, and file an item for each tool that cuts tokens a replay shows keep quality.** | 1 | 2 | 1 | 2 | 3 | 1.4 by 3, 1.5 by 2 | 1.7 |
| 471 | 0.16.0 | | | **Ship `jira-rest METHOD PATH [BODY]`, which makes one Jira Cloud REST call with the credentials of the project's config, or do-epic's, reading the env file itself, so an agent calls Jira without naming a file rule-hook guards.** | 2 | 2 | 4 | 6 | 3 | 1.6 by 3, 1.4 by 2 | 1.7 |
| 149 | 0.16.0 | | decision | **Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release.** | 4 | 2 | 3 | 7 | 5 | 1.1 by 7 | 1.6 |
| 165 | 0.16.0 | | | **Make this repo's tests assert the facts a prompt or help text carries in place of its sentences, and drop the tests that scan source or assert a constant.** | 3 | 2 | 1 | 4 | 5 | 1.1 by 4, 1.4 by 3 | 1.6 |
| 392 | 0.16.0 | | owner | **Group bin/'s packages by concern into seven folders (plan, records, integrations, loop, review, forge and host), so a newcomer finds a tool's neighbours in one place.** | 3 | 1 | 3 | 5 | 7 | code health by 4 | 1.6 |
@@ -75,6 +77,35 @@
## Details
### 469. Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.
do-epic moves to done only a parent it split itself (`split_items_closed`). A parent whose sub-tasks a person filed stays as Jira holds it, and `--status` says "its sub-tasks are done; close it in Jira". Until someone moves it, the parent blocks every issue it blocks, and through it their sub-tasks. On TW-13503, TW-13505 blocks most of the critical path this way, and TW-13547's sub-tasks are all Release Ready while the parent stays In Progress. The human asked, on 2026-11-20, for deterministic code to move these parents, not a worker or a person.
- A parent whose sub-tasks have all landed, each in one of `jira-unblocking-statuses` or done, with at least one not yet done, moves by a transition the config names, such as `jira-landed-transition = "Release Ready"`.
- A parent whose sub-tasks are all done moves by `jira-finish-transition`, as a split item does today.
- do-epic moves such parents as each run plans, and after each chunk finishes, where it now closes split items. A parent already at or past the target status stays: one in a done status never moves back.
- A parent with no sub-tasks, or with one sub-task still open, is left alone.
- Without `jira-landed-transition`, only the move to Done happens, and only where `jira-finish-transition` is set, as today.
- `--dry-run` prints each parent move it would make.
Choice, made 2026-11-20: a sub-task in any of `jira-unblocking-statuses` counts as landed, so TW's "Teach & Learn" counts as "Release Ready" does. The human named Release Ready and Done; Teach & Learn also means the work merged.
Touches:
- `bin/do_epic/main.py`: `split_items_closed`, `planned_and_started` (small)
- `bin/do_epic/planning.py`: `planned` (small)
- `bin/do_epic/scheduler.py`: `chunks` (small)
- `bin/do_epic/split.py`: `finished` (small)
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
- `bin/do_epic/backend/protocol.py`: `EpicStore`
- `bin/do_epic/backend/jira.py`: `JiraEpic`
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
- `bin/do_epic/backend/contract.py`
- `bin/do_epic/dry_run.py`
- `bin/do_epic/test_do_epic.py`
- `bin/do_epic/backend/test_jira.py`
- `README.md`: `### Set up a project` (small)
### 453. 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.
do-epic and `todo-item add` file every new issue as a Task, the name `plan_store/jira_epic.py` sets as `ISSUE_TYPE`. A Jira project without a Task type, such as TW, whose types are Feature, Bug, Chore and Investigation, refuses each one. So `do-epic --file` fails there, and so does the epic's finishing, which files a release review for each repo.
@@ -93,6 +124,32 @@ Touches:
- `bin/do_epic/backend/test_jira.py`
- `README.md`: `### Set up a project` (small)
### 470. Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.
do-epic starts the issues it may run in Jira's backlog order (`scheduler.chunks`). It scores and ranks only the issues it filed itself (`planning.ranked_keys`); a person's issue holds no scores and keeps the rank the team gave it. The human asked, on 2026-11-20, that only the score decide priority on an epic such as TW-13503, where people filed every issue.
- As it plans, do-epic scores each open issue that may become a chunk and holds no scores: L, E, I, S and Moves against the chain of goals `ranking.py` uses (the epic's, then code health, then the repo's). It writes the scores to the issue's `plan-item` property, as `todo-item edit` does on a person's issue, with a comment, in the epic's language, telling the team the issue is scored and why.
- Scores a person wrote, or that an earlier run wrote, stay as they are.
- `scheduler.chunks` orders the runnable issues by score, highest first, with each blocker lifted above what it blocks, as `rank_todo.py` does. An issue that couldn't be scored comes last, in backlog order, and `--status` says why.
- A sub-task is scored on its own, against its own repo's goals.
- The board's rank of a person's issue stays as the team set it. Choice, made 2026-11-20: start order is do-epic's decision, the board order is the team's (goal 1.6). do-epic still re-ranks the issues it filed.
- `--dry-run` prints the scores it would write and the order it would start in.
Touches:
- `bin/do_epic/planning.py`: `planned`, `ranked_keys`, `item_of`
- `bin/do_epic/ranking.py`: `ranked` (small)
- `bin/do_epic/scheduler.py`: `chunks`, `start_chunks`
- `bin/do_epic/main.py`: `planned_and_started` (small), `status_printed` (small)
- `bin/do_epic/backend/protocol.py`: `EpicStore`
- `bin/do_epic/backend/jira.py`: `JiraEpic`
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
- `bin/do_epic/backend/contract.py`
- `bin/do_epic/dry_run.py`
- `bin/do_epic/test_planning.py`
- `bin/do_epic/test_do_epic.py`
- `README.md`: `### Set up a project` (small)
### 454. Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.
When a do-epic chunk starts, its issue stays as Jira holds it: unassigned, in New and outside the sprint. A team whose board shows who works on what, such as TW, where an issue being worked is assigned to the person, In Progress and in the active sprint, then sees nothing of the loop's work. Today each worker would have to do this by hand, from rules only some machines hold.
@@ -112,7 +169,7 @@ Touches:
- `bin/do_epic/backend/test_jira.py`
- `README.md`: `### Set up a project` (small)
### 467. Cut 0.15.0 as soon as items 449, 450, 453 and 454 have merged, before its release review, and run that review in 0.15.1.
### 467. Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.
lilleman's call on 2026-11-20: they need what 0.15.0 holds to work, so 0.15.0 is cut without a release review. This item holds the loop back from starting 0.15.0's release review once its last item merges: it waits as a question, so the human, or the session that cuts, drops it at the cut. At the cut, an item in 0.15.1 runs the release review, and the review's follow-ups land in 0.15.1.
@@ -120,18 +177,6 @@ Touches:
- `CHANGELOG.md`: `## Unreleased` (small)
### 468. Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.
Item 449 makes do-epic record a repo pick, and each sub-task it files, under the team's own label from the `[label-repos]` table (`repo_pick.label_of(pick, team)`). The instructions do-epic gives a chunk's worker still name only `repo:<name>`: `LABELS` in `bin/do_epic/findings.py` (used in `HELP` at findings.py:31, in `instructions` at :48, and in `written`'s refusal at :99 and its reply at :105) and the `--file ... --label repo:<name> --label do-epic-release-review` command in `finish.task` at `bin/do_epic/finish.py:60`. A team whose board uses its own labels therefore still gets a finding or a release review labelled `repo:core-4` where it expects `core-4`.
Give both prompts the team's label for each repo of the table where the table names it (`repo_pick.team_label`, `also`), and keep `repo:<name>` for a repo the table doesn't name. `finish.task` already knows each repo that lacks its review, so it can name each one's label outright, as `label_of(Repo(name), team)` gives it. The README states the pick's spelling (`repo-rule.md`'s bullet) but not the finding's, so it needs no change.
Touches:
- `bin/do_epic/findings.py`: `LABELS`, `instructions` (small), `written` (small)
- `bin/do_epic/finish.py`: `task` (small)
- `bin/do_epic/test_findings.py`: `Instructions`
- `bin/do_epic/test_finish.py`: `TheFinishingChunksTask`
### 446. Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.
Item 422 judges a worker that stalls before its result, but only reports: each verdict goes to the terminal and to `stuck-workers.md` in the project's transcript archive. Question for the human: after a few days of verdicts there, do they match what you would have done? Once you say yes, kill only the process a `stuck` verdict names, and only where the pid is below the worker's claude, never the worker or the loop, and record the call in a decision.
@@ -256,6 +301,17 @@ Dropped in 312's round, and why; look again only where the reason has changed:
- LSP, repo maps and outline scripts: item 231's trial lost findings and agents didn't call them; the only figures found since are a vendor's and a blog's.
- Compact test reporters and output filters such as rtk: this archive's test output is a few thousand tokens per release, and the filters' figures are their own; trimming read output is item 311's ceiling.
### 471. Ship `jira-rest METHOD PATH [BODY]`, which makes one Jira Cloud REST call with the credentials of the project's config, or do-epic's, reading the env file itself, so an agent calls Jira without naming a file rule-hook guards.
Once a Jira credentials file is a config's `env-file`, rule-hook's `env-file-read` refuses every Bash command that names it. A machine's own rules that tell agents to `source` it and `curl` Jira then stop working. On 2026-11-20 this happened on a machine whose rules call Jira that way, and a machine-only script, `~/.local/bin/jira-rest`, took their place. The human asked for it as a claude-config tool, so every machine has it.
- `jira-rest METHOD PATH [BODY.json | -]` sends one call to a path under `/rest/`, with the body from the file or stdin, and prints Jira's JSON answer, or `null` for an empty one. A refused call exits non-zero with the message `atlassian.client.jira_errors` gives. No output, error or log line holds a credential.
- The site and the env file come from the project's config where the checkout has one whose `plan` or `goals-and-audience` is a Jira epic: the epic's site and the config's `env-file`. Otherwise they come from do-epic's config: `jira-url` and `env-file`. Where neither holds them, it fails, naming both places.
- It sends through `atlassian.client`, as `plan_store` and `do_epic` do, so it gains their error messages and timeouts.
- `--help` states the contract, and README → `## Tools` lists the tool.
After it ships, the machine's `~/.local/bin/jira-rest` is removed, and its rules call the shipped tool.
### 149. Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release.
A release's capacity is a sum of its items' cost, as the formula counts it. Each project states its own; the human sets the first value per project. Nothing is deleted by score.