Finish items 12, 272 and 283
CI / tests (pull_request) Successful in 4m4s

This commit was merged in pull request #451.
This commit is contained in:
2026-11-09 03:13:31 +01:00
parent da4d376136
commit 4593c2969a
2 changed files with 3 additions and 17 deletions
+3
View File
@@ -2,6 +2,9 @@
## Unreleased
- `command-patterns [<version>]` prints a table of the shell command patterns a release's chunks ran.
- `deploy-release --cut` reports each step as it finishes, waits for the checks `main`'s protection requires and names them, deletes the merged release branch, and ends on one line saying the release is cut.
- CI runs the test suite on every pull request, and `main` merges nothing until it passes.
- `larv-review reviewer-header <pass> [--rerun]` writes the branch diff and the places into the chunk's review folder and prints the header of a reviewer's prompt: the pass, its next round, the PR, the worktree, the branch, the merge base of HEAD and the default branch, and the paths of the report, the diff and the places.
- `chunk-pr open|ready|merge` opens a chunk's pull request as a draft, marks it ready and merges it, with `gh` or `tea` as the remote needs. It merges only with `--gate-passed`, by the first merge method the repository allows. `larv-review` and `CLAUDE.md` now tell workers to use it.
- `score-outcomes` now gives, where most of the chunks it counts for L hold no 🔴, the share of chunks with a 🔴 at each L in place of L's rank correlation by 🔴 findings.
-17
View File
@@ -14,11 +14,8 @@
|---|---|---|---|---|---|---|---|---|---|---|---|
| 277 | 0.7.0 | | question | **Map the size of the code an item names onto S, on a scale the human picks, and have `score-outcomes` print that S for the item being scored and for each finished item it lists.** | 3 | 2 | 2 | 5 | 4 | 1.1 by 4, 1.4 by 3 | 2.4 |
| 1 | 0.7.0 | | question | **Say in README → Install how the transcript archive is backed up, once bender-infra backs up ai-sandbox's data volume.** | 1 | 2 | 1 | 2 | 1 | | 0.0 |
| 12 | 0.7.0 | | | **Run the test suite in CI on every PR, or record in `docs/decisions.md` why the local run is enough.** | 3 | 2 | 1 | 4 | 4 | 1.1 by 6 | 2.1 |
| 285 | 0.7.0 | | | **Cut a worker's opens and searches of `todo.md` from the median 7 per chunk to at most 3, by finding in the last five chunks' archived transcripts what each read was for and removing its cause.** | 2 | 2 | 3 | 5 | 3 | 1.4 by 4 | 1.6 |
| 281 | 0.7.0 | | | **Remove a merged chunk's worktree and branch and fast-forward the main checkout with one command.** | 3 | 2 | 3 | 6 | 3 | 1.4 by 2, 1.5 by 2 | 1.6 |
| 283 | 0.7.0 | | | **Print, for the archived chunks of a release, a table of its shell command patterns, such as `tea pr create`: the chunks that ran each, its calls, command tokens, result tokens and tool time, so an audit reads one table.** | 3 | 2 | 1 | 4 | 3 | 1.4 by 2, 1.5 by 2 | 1.6 |
| 272 | 0.7.0 | | owner | **Make `deploy-release --cut` say when each step finishes, end on one line saying the release is cut and `~/.claude` is on it, and delete the merged release branch.** | 1 | 1 | 1 | 1 | 2 | 1.5 by 3 | 1.3 |
| 274 | 0.7.0 | | | **Let an item name a maintain goal it raises confidence in, such as a test leg that guards it, and weigh that move against the achieve goals in `bin/release_plan/ranking.py`.** | 2 | 2 | 3 | 5 | 4 | 1 by 3 | 1.1 |
| 286 | 0.7.0 | | | **Lower the reading cost of the files a chunk reads most before its first commit.** | 3 | 2 | 2 | 5 | 5 | 1.4 by 4 | 1.0 |
| 284 | 0.8.0 | | owner | **Script each step that 0.7.0's chunks repeated by hand and a program can compute, filing one item per step, and file this audit again for the next release.** | 1 | 2 | 1 | 2 | 2 | 1.4 by 3, 1.5 by 3 | 2.6 |
@@ -74,12 +71,6 @@ It lives under `~/.claude`, which `.gitignore` keeps from the remote, so a lost
The README line covers the bench's transcripts in `workflow-bench/logs/` too (goal 3).
### 12. Run the test suite in CI on every PR, or record in `docs/decisions.md` why the local run is enough.
The repo has no CI, so larv-review's gate is the local run, and larv-review's Gate skips even that when the last stability round left the suite green: an unattended chunk can merge on the worker's own word.
When CI runs a rule check, such as one of `bin/rule-hook`'s, let `<!-- rule-override <rule>: <reason> -->` in the PR body override it.
### 285. Cut a worker's opens and searches of `todo.md` from the median 7 per chunk to at most 3, by finding in the last five chunks' archived transcripts what each read was for and removing its cause.
Item 105 compared the five chunks before and after the `worker:` decision, merged 2026-10-13 at 06:49Z in 21b060e, matching chunks to PRs by finish time. Reading cost, the new input tokens before the first commit, rose: median 56,802 before and 136,132 after. The ranges, 46k to 172k and 50k to 140k, overlap. Review rounds per pass did not rise: 2.26 before and 1.52 after, among the five multi-pass chunks on each side.
@@ -92,14 +83,6 @@ Some reads serve an edit, since Edit needs a Read first; items 278 and 279 remov
Audit of release 0.2.0's chunks (item 162): 31 chunks ran `git worktree remove`, `git branch -d` and `git pull --ff-only` by hand, 56 calls and about 5k command tokens. The program refuses a dirty main checkout, as `CLAUDE.md` → "Working with the codebase" says, and reports it.
### 283. Print, for the archived chunks of a release, a table of its shell command patterns, such as `tea pr create`: the chunks that ran each, its calls, command tokens, result tokens and tool time, so an audit reads one table.
Audit of release 0.2.0's chunks (item 162): the audit wrote a 40-line extraction script by hand to tally 12,000 tool calls in 42 chunks, then clustered the patterns by hand. Every later audit repeats that step; item 284 names this tool as the first thing to run. Leave judging which pattern is a scriptable step with the model.
### 272. Make `deploy-release --cut` say when each step finishes, end on one line saying the release is cut and `~/.claude` is on it, and delete the merged release branch.
Cutting 0.6.0 printed `waiting for the checks of pull request 418`, then `Cut v0.6.0.` and `Moved from v0.5.0 to v0.6.0.`, then the whole 0.6.0 changelog section. The two lines saying it worked scrolled off behind the changelog, and no line said the checks passed or the pull request merged. So the human couldn't tell whether the cut had finished or was still waiting. Print a line on stderr as each step finishes: branch pushed, pull request opened, checks passed, merged, tagged, tag pushed. End stdout with one line, after the changelog: `Done: v<version> is cut and pushed, and <checkout> is on it.` Once the tag is pushed, delete the remote branch `release-<version>`, which 0.6.0's cut left on origin. A failed delete only warns, since the release is cut by then. Update the tests in `bin/deploy_release/test_deploy_release.py` and `deploy-release --help`.
### 274. Let an item name a maintain goal it raises confidence in, such as a test leg that guards it, and weigh that move against the achieve goals in `bin/release_plan/ranking.py`.
Today only a `defect` item may name a maintain goal, and only to restore one the project breaks