A Steer ends the step it was meant to help #412
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 181's apply got a Steer, did it, wrote a report back and ended its turn with 14 tasks left; the attempt failed on
every taskafter 89 min and a fresh session re-read the project.Fix. Braid appends to a Steer "act on this, then carry on with your tasks; do not stop to report", and an apply attempt that ends with tasks left is sent on in the same session ("N tasks remain: continue") instead of a fresh one, as a spec-test retry already continues its session.
Done when. a sim with a steered apply finishes its tasks in one attempt and one session.
From run 181, the verifying run after #407; the log is
docs/design/measurements/work/run-180/findings.md.Shipped in PR #421 (
ff9381d8), changebriefs-after-run-181.openspec.applyopts in toretry_continues: an attempt whosetasks-completecheck fails with tasks unticked is tried again in a fork of its own session, told which tasks remain ("N tasks of the change remain (ids): continue them in this session"), under the existing room rule. An attempt stopped at its limit still starts fresh.steeroperator action;sim/apply-steered.yamlsteers a whole-change apply whose turn ends with two tasks left, and the run finishes in two attempts of one session.Evidence:
tests/engine/test_operator_messages.py,test_mediation.pyandtest_fork_room.py(failing before, passing after), the sim, and a green suite. The next Scratch run is the production check.