Merge remote-tracking branch 'origin/main' into item-472
CI / tests (pull_request) Failing after 3m37s

# Conflicts:
#	docs/reading-cost.md
This commit is contained in:
2026-11-20 23:35:16 +01:00
10 changed files with 459 additions and 103 deletions
+7 -1
View File
@@ -297,6 +297,12 @@ Only the stability pass was replayed, since the archive's long Bash results are
Valid while Claude Code saves a Bash result over the ceiling to a file and hands the model its path.
## loop: a step whose result a program can check, or whose trigger is a condition, moves from prose into `do-release`'s code, and the model keeps each step that needs the meaning of what it reads, returning output that code checks
2026-11-20, lilleman, in the session that planned the standalone install. Serves goals 1.1 and 1.4, and applies project principle 4 to the flow of a chunk. Prose that tells an agent to run a step leaves the agent to remember it, in order, every time, and rule-hook then guards a flow nobody owns. `todo.md` items 487 and 498 move larv-review's passes and the chunk's lifecycle into `do-release`, and item 488 cuts the prose they replace. A model step stays coarse, such as implementing an item, since many small calls each reread the context and raise reading cost.
Valid while tokens, 🔴 and 🟡 findings and interrupts per chunk don't rise against the chunks before the change; `todo.md` item 497 measures it.
## machine load: a heavy command waits for one of the machine's heavy slots, one for every 4 CPUs, which every session shares, and loop-claude starts a worker only while at least a quarter of the machine's memory is available
2026-10-23, lilleman. Serves goal 1.5. On 2026-10-22 ai-sandbox, with 8 CPUs and 16 GiB, thrashed for hours: four to six loops ran mutation tests, full gates, `docker build`s and QEMU-booting e2e tests at once, and nothing told one loop how busy the machine was. lilleman chose both limits; no standard sets either, and GNU parallel's `--memfree`, which does the memory wait's job, has no default. A slot is a file lock, so a session that dies frees its slot. The memory wait reads `/proc/meminfo` only, and off Linux a worker starts at once. `bin/machine_load/` holds the slots and the memory share, `bin/run-heavy` takes a slot, `CLAUDE.md` → "Working with the codebase" has every session use it, and loop-claude's worker waits for the share. rule-hook's rule `run-heavy` blocks a `docker build`, and a run of a mutation tool stability-reviewer names, outside run-heavy, in the forms its `checked` text in `bin/rule_hook/rules.py` lists. 2026-11-16, lilleman: rule-hook checks a run through `uv run`, `poetry run`, `sudo` and `doas` too, such as `uv run mutmut run` and `sudo docker build`, since project principle 4 has a program enforce a rule it can check. The 2026-11-04 note had let such forms pass until one became a problem. No program can tell a gate script from a light one, so only `CLAUDE.md` asks a session to run a gate under run-heavy. Valid while one machine runs several loops at once.
@@ -401,7 +407,7 @@ Valid while the later fixes per finished chunk, which `score-outcomes` and the r
- A file outside the checkout is read as it stands, never as the default branch held it: release standing, chunk-preflight and loop-claude's routing read such a plan or changelog from disk.
- chunk-preflight and loop-claude's routing learn that a release's items are all done from the plan's commits. A plan outside the checkout no longer names such a release, so the release after it reads as next, and only the last release of all gets a release review called due and is called ready to cut. Both tools say so on every run, and that the release reviews and the cuts are the human's to call (`bin/release_plan/release_standing.py`, `UNSEEN_RELEASES`).
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.16.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.23.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
## project config: `language` names the prose's language by its English name, and `commit-title`, `pull-request-title` and `branch` are brace templates over `{id}` and `{summary}`
+17
View File
@@ -3268,6 +3268,23 @@ Read most (opens and searches):
- `bin/atlassian/jira.py` 2
- `bin/do_epic/backend/fake.py` 2
## Reading cost, chunk f8d0ce3a214b, finished 2026-11-20T20:32:59Z
86081 new input tokens before the first commit.
Read most (opens and searches):
- `bin/mutate_changes/test_mutate_changes_runs.py` 7
- `bin/mutate_changes/mutmut_tool.py` 5
- `README.md` 3
- `bin/mutate_changes/main.py` 3
- `bin/mutate_changes/test_mutate_changes.py` 3
- `CHANGELOG.md` 2
- `bin/mutate_changes/changed_lines.py` 2
- `bin/mutate_changes/mutmut_mutants.py` 2
- `bin/mutate_changes/mutmut_setup.py` 2
- `skills/larv-review/SKILL.md` 2
## Reading cost, chunk fbec3b9bb507, finished 2026-11-19T13:23:00Z
37393 new input tokens before the first commit.