docs: drop removal-history framing, document current state only

This commit is contained in:
damocles 2026-07-27 22:14:04 +02:00 committed by mara
commit 2ab3c92a11
2 changed files with 10 additions and 12 deletions

View file

@ -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 }` reports the result to `serve_loop` via `TurnControl { auth_failed }`
on auth failure the loop parks in `wait_for_login`; otherwise it loops 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 straight back to the idle wait (step 1). There is no same-turn
self-continue tool (removed — see forge #2777): every multi-step self-continue mechanism: every multi-step continuation rides an
continuation rides an external wake instead — a new inbox message, a external wake instead — a new inbox message, a `remind`, or an
`remind`, or an in-container todo wake (bash-task completion, forge in-container todo wake (bash-task completion, forge notification,
notification, matrix activity). Ending the turn and letting one of matrix activity). Ending the turn and letting one of
those drive the next one is strictly better than parking in-process: those drive the next one is strictly better than parking in-process:
it checkpoints the session and observes wakes that only reach the it checkpoints the session and observes wakes that only reach the
harness between turns. harness between turns.

View file

@ -98,14 +98,12 @@ at_unix_timestamp?)`.
payloads spill to `/agents/<self>/state/reminders/`. Pending count payloads spill to `/agents/<self>/state/reminders/`. Pending count
capped at 50 per agent (`HIVE_REMIND_MAX_PENDING_PER_AGENT`). capped at 50 per agent (`HIVE_REMIND_MAX_PENDING_PER_AGENT`).
There is no same-turn self-continue tool (`request_next_turn` was There is no same-turn self-continue tool: ending the turn and letting
removed — unanimous consensus across every agent that used the harness an external wake drive the next one is always the right move — it
that ending the turn and letting an external wake drive the next one checkpoints the session and observes wakes that only reach the harness
is strictly better: it checkpoints the session and observes wakes that between turns. Multi-step work rides `remind` for a durable self-wake,
only reach the harness between turns, forge #2777). Multi-step work or an in-container todo wake (bash-task completion, forge notification,
rides `remind` for a durable self-wake, or an in-container todo wake matrix activity) for work already in flight.
(bash-task completion, forge notification, matrix activity) for
work already in flight.
**Meta** (`meta` group): `set_status(text)`, `get_agent_meta(name?)`. **Meta** (`meta` group): `set_status(text)`, `get_agent_meta(name?)`.