docs: drop removal-history framing, document current state only
This commit is contained in:
parent
fffe0a2c29
commit
2ab3c92a11
2 changed files with 10 additions and 12 deletions
|
|
@ -143,10 +143,10 @@ After the outcome handler, the stats sink records a row. `handle_turn`
|
|||
reports the result to `serve_loop` via `TurnControl { auth_failed }` —
|
||||
on auth failure the loop parks in `wait_for_login`; otherwise it loops
|
||||
straight back to the idle wait (step 1). There is no same-turn
|
||||
self-continue tool (removed — see forge #2777): every multi-step
|
||||
continuation rides an external wake instead — a new inbox message, a
|
||||
`remind`, or an in-container todo wake (bash-task completion, forge
|
||||
notification, matrix activity). Ending the turn and letting one of
|
||||
self-continue mechanism: every multi-step continuation rides an
|
||||
external wake instead — a new inbox message, a `remind`, or an
|
||||
in-container todo wake (bash-task completion, forge notification,
|
||||
matrix activity). Ending the turn and letting one of
|
||||
those drive the next one is strictly better than parking in-process:
|
||||
it checkpoints the session and observes wakes that only reach the
|
||||
harness between turns.
|
||||
|
|
|
|||
Loading…
Reference in a new issue