Run the standard test on the fixes of 2026-11-12, and settle what they left open #536
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
Run 195 (braid#505) is the last standard run, and it predates braid#506 and braid#509. No real run has exercised: the unit lane's command joined at a merge, the note for groups side by side, queued helpers, the guard's refusal of Braid's own code, or the several-people browser guidance.
Fix
Start the standard run (
./tools/standard-run.sh <server> 4) and measure against run 195 (4 h 49 min, 428 agent minutes):Smaller things to settle from the same runs:
writes-not-ignoredis on the apply steps only; a fix round or a quick fix can still write a code file git ignores.stoptakes a helper's name, not one helper.Done when
The run has ended, its record is beside run 195's, and each smaller item is fixed or dropped.
The smaller items of this issue are in pull request 550 (change
console-fixes-and-session-cap): the ignored-file check on fix rounds and quick fixes,stopby id, and the stall watchdog on vLLM.About the watchdog. A request waiting on vLLM already kept a silent step from being redone, so run 193's 531 s silence was a request the server was running, most likely a long prompt it was reading. Run 193 has been deleted from production, so its metric samples could not be read back to confirm it. The fix therefore uses vLLM's own behaviour: a silent step is spared while vLLM's prompt counter rises or its cache fills as it runs a request, with the same three-window bound braid#295 uses for llama.cpp.
The issue stays open for its standard run, which measures this change once it ships.
Run 202 (braid#557) was this issue's run. The owner stopped it at 4 h 15 min, during apply, after it turned up four findings, so it measured only part of what this issue asks:
(cd backend && uv run pytest) && (cd frontend && npm run test). No lane ran it before the stop.Still open here: the code review beside one helper, and a lane running both suites. Both need the next standard run, after braid#557's fixes.
Run 203 (braid#565) was this issue's run, after braid#559 fixed run 202's findings. It succeeded in 6 h 1 min on 421 agent minutes (run 195: 4 h 49 min on 428). Its record is on braid#565, beside run 195's.
(cd frontend && npx vitest run) && (cd backend && uv run python -m pytest), ran 41 front-end and 51 back-end tests in 11.6 s.The smaller items shipped in pull request 550. Every question here now has its measurement, so I am closing this. What the run found is on braid#565.