Run 202's findings: the estimate after a revision, joined additions, one README, the watchdog's redo (#559) #560
Loading…
Reference in a new issue
No description provided.
Delete branch "claude/run202-batch"
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?
Fixes run 202's findings (braid#557), batched as braid#559 and decided with the owner on 2026-11-19. The change is
openspec/changes/run202-batch.What changes
.osf/budget.jsonagain before they commit. The apply fan-out and its dependency gate then read the plan as revised. In run 202 the revise moved group 4 behind group 1 and nothing saw it.OSF_SHELL_HARD_S, or the call's longer timeout) and a minute, not a fixed 20 minutes. The redo's reason names the call and how long it ran.redo_step(mode="keep")supersedes the attempt without a rollback, and the next attempt continues from Braid's note. In run 202 the rollback threw away 72 minutes of Pairs.Evidence
./tools/test.sh: green in 50 s (900 backend, 204 UI unit, 61 browser).sim/revision-moves-a-dependency: fails with the estimate taken out of the operator's revision commit (group 2 starts beside group 1, and its edit misses) and passes with it.sim/parallel-additions-joined: fails with the join disabled (a conflict, and group 3 never merges) and passes with it../tools/sim.sh --smoke, plusparallel-conflict,parallel-groupsandthorough-request-changes: all pass.parallel-conflictedits one line on both sides, so it is still a conflict.On purpose
🤖 Generated with Claude Code