Finish item 344
CI / tests (pull_request) Successful in 2m58s

This commit was merged in pull request #519.
This commit is contained in:
2026-11-13 01:50:52 +01:00
parent 7eb573cf17
commit 1272894aea
2 changed files with 4 additions and 10 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- Every tool, prompt, rule and skill reads and writes the plan, `AGENTS.md`, the records and the changelog at the paths the project's config names. A plan outside the checkout is read as it stands; the tools that need a file's commits say what they leave undone for it, and the loop goes on.
- loop-claude, `rank_todo.py`, `todo-item` and rule-hook's `todo.md` checks now fail in a checkout no config names: write a config for each project, with `goals-and-audience = "checkout:README.md"` where its goals stay in its README. They read the goals and audience from the file that setting names, in place of `README.md`. `larv-review reviewer-header` names it on a `Goals and audience:` line, and the reviewers read it from there. A client's project can keep the file, named `goals.md`, in its config's folder, and void code health there as a README can.
- Reviewers read the technical principles from the folder a project's config sets as `principles`, in place of `~/.claude/principles/`. `larv-review reviewer-header` names the folder on a `Technical principles:` line and fails where no config sets it, or the folder is missing or empty. Write a config for each project before its next review; a project that keeps today's principles sets `principles = "~/.claude/principles"`.
- A project can now have a config, `~/.claude-projects/<key>/config.toml`, that names its checkout and the path of every file the loop keeps for it. `project-config` prints those paths, and fails naming each setting a config leaves out. README → Install → "Set up a project" shows how to write one. Every project needs one, as the first bullet says.
+3 -10
View File
@@ -12,14 +12,13 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 344 | 0.10.0 | | | **Read and write the plan, `AGENTS.md`, the records and the changelog at the paths a project's config names, in every tool, prompt, rule and skill.** | 4 | 2 | 3 | 7 | 6 | 1.6 by 7 | 0.9 |
| 345 | 0.10.0 | 344 | | **Commit each change a chunk makes to a plan or record outside the checkout into the project's `~/.claude-projects/<key>/` repo, titled like the chunk's own commits.** | 3 | 2 | 3 | 6 | 4 | 1.6 by 4 | 1.1 |
| 345 | 0.10.0 | | | **Commit each change a chunk makes to a plan or record outside the checkout into the project's `~/.claude-projects/<key>/` repo, titled like the chunk's own commits.** | 3 | 2 | 3 | 6 | 4 | 1.6 by 4 | 1.1 |
| 348 | 0.11.0 | | | **Read each project's credentials from the env file its config names, fail naming each missing key, and keep every value out of prompts, transcripts, logs and the archive.** | 2 | 2 | 4 | 6 | 3 | 1.6 by 2, 4 by 5 | 6.9 |
| 354 | 0.11.0 | 344 | | **Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.** | 3 | 2 | 3 | 6 | 6 | 1.6 by 4, code health by 1 | 1.2 |
| 354 | 0.11.0 | | | **Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.** | 3 | 2 | 3 | 6 | 6 | 1.6 by 4, code health by 1 | 1.2 |
| 364 | 0.11.0 | 354 | | **Read a client repo's own `CLAUDE.md` and `AGENTS.md`, propose to its team each change that aligns them with this setup, and record each conflict left as a decision in the project's records.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4, 1.2 by 2 | 2.2 |
| 360 | 0.11.0 | | | **Make `chunk-pr merge` wait for the human approvals a project's config requires, as part of the gate, before it merges.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 5 | 1.6 |
| 357 | 0.11.0 | | | **Write prose in the language a project's config names, and title its commits, pull requests and branches by the templates it names.** | 3 | 2 | 3 | 6 | 4 | 1.6 by 5 | 1.4 |
| 350 | 0.11.0 | 344 | | **Route every read and write of the plan, by tools and by agents, through one plan-store interface and `todo-item`, with the markdown file as one backend.** | 4 | 2 | 3 | 7 | 7 | 1.6 by 4, code health by 2 | 1.1 |
| 350 | 0.11.0 | | | **Route every read and write of the plan, by tools and by agents, through one plan-store interface and `todo-item`, with the markdown file as one backend.** | 4 | 2 | 3 | 7 | 7 | 1.6 by 4, code health by 2 | 1.1 |
| 349 | 0.11.0 | | | **Convert markdown to ADF and back with `@larvit/adf-codec`'s portable calls, through a pinned Node shim run in a container with a memory limit.** | 2 | 1 | 2 | 3 | 2 | 1.6 by 3 | 1.1 |
| 351 | 0.11.0 | 348, 349, 350 | | **Read a project's plan from the child issues of a Jira Cloud epic its config names, ranked in Jira's backlog order.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
| 353 | 0.11.0 | 351 | | **Let a project's config take its goals and audience from a Jira epic's description, under the same two headings.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 4 | 1.3 |
@@ -89,12 +88,6 @@
## Details
### 344. Read and write the plan, `AGENTS.md`, the records and the changelog at the paths a project's config names, in every tool, prompt, rule and skill.
Today about 40 modules, and `CLAUDE.md`, `rules/` and the skills, name `todo.md`, `AGENTS.md`, `docs/decisions.md`, `docs/score-anchors.md`, `docs/comprehension-history.md`, `docs/reading-cost.md` and `CHANGELOG.md` as files at the checkout's root. Among them are `rank_todo.py`, `todo-item`, `chunk-preflight`, loop-claude's routing, chunk items, judge records and prompts, larv-review, loop-inbox, `release_plan`, `subagent-rung` and `reviewer_context.principles_line`. After this item each of them uses the configured path. Agents get the path in the prompts and in the output of `todo-item` and `chunk-preflight`. Keep each file's name, so `rules/todo-items.md` and `rules/decisions.md` still load by their `paths:` patterns wherever the file lives.
lilleman's call, 2026-11-12: `AGENTS.md`'s path is configurable too. The tooling treats `AGENTS.md` as ours, since it lists the project principles and the decision titles, and a client repo may hold its own `AGENTS.md`, which stays theirs. Where the plan sits outside the checkout, loop-claude reads the chunk's items from that file, not from `todo.md` on the default branch. Tools that read `todo.md`'s git history in the checkout, `score-outcomes` and the routing figures, say they don't support a plan outside the checkout, and the loop goes on, until 0.13.0. R is above 5, so this item ships alone.
### 345. Commit each change a chunk makes to a plan or record outside the checkout into the project's `~/.claude-projects/<key>/` repo, titled like the chunk's own commits.
lilleman's call, 2026-11-12: each `~/.claude-projects/<key>/` is a git repo of its own, so plan and record edits keep a history. Those edits don't ride the chunk's branch: one loop runs per project, and it commits to the project repo's only branch. rule-hook's rank check, and the `Drop item` title rule, apply to these commits as they do in the checkout. Whether these repos are pushed anywhere for backup is a call for later: client data stays on the client's VM (goal 4).