Runs 194 and 195: the first batch of fixes #506
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Runs 194 and 195 (braid#501, braid#505) left findings the owner went through one by one on 2026-11-12. This is the first batch: the small fixes. Helpers that queue, keeping a waiting step warm, the agent documentation and the estimate are their own work.
Fix
groups/that is no group's worktree is not called another step's copy (194, 4).fuserandlsof(194, 7).Done when
./tools/test.shpasses and production runs it.Shipped: pull request 507 (main
7c2c565a, production7c2c565), archived in pull request 508 (merged with skip ci).Evidence, on the laptop
./tools/test.shpasses (39 s). The merge test fails without the rule: the run keptuv run pytest backend/tests -qalone; with it the result isuv run pytest backend/tests -q && (cd frontend && npm test).parallel-groupsandparallel-conflictamong them.sedandgrepover Braid's package refused, the lint's own command not;groups/screenshotsnot called another step's copy.On production:
osfd doctor0 failed, 0 warned;fuserandlsofin the image.Changed from the review: Braid cannot close the browser for an agent (its plugin does not see the browser tools), so that is a sentence in the brief.
Still to come, as their own work: helpers that queue and a step told its places (195, finding 5), keeping a waiting step warm (195, 2), the agent documentation and taking Braid's package out of the sandbox (194, 1 and 7), and the estimate against what filled the contexts (195, 6).