hive-agent: self-announce boot instead of host-side kick_agent

docs/turn-loop/claude-invocation.md

@@ -222,11 +222,19 @@ to ack), plus an inline `({unread} more pending — drain via …)` hint
 when `unread > 0`. Claude drives any further `recv`/`send` itself via
 the embedded MCP server.
 
-Whenever hive-c0re starts / restarts / rebuilds a container, it
-also drops a `system` message into the agent's inbox via
-`Coordinator::kick_agent` — a one-line "you were just (re)started,
-check /state/ for your notes, your session is intact." The
-next turn picks it up like any other inbox message.
+`hive-agent` self-announces once on every boot:
+`boot_announce::announce` pushes a one-line "you were just
+(re)started, check /state/ for your notes, your session is intact"
+todo the moment the in-agent todo store opens, before the serve loop
+starts. This replaced `hive-c0re`'s old `Coordinator::kick_agent`
+calls at the tail of the rebuild and start DAG nodes — those fired a
+broker message per DAG node, so one rebuild (always a real
+`StopForUpdate` → `Swap` → `RebuildBookkeeping` → `Reconcile` →
+`Start` cycle) queued two separate restart messages for a single
+actual boot. The harness itself is the one side that knows for
+certain whether a boot happened, so it dedups for free: exactly one
+todo per real process start, surfaced the normal todo-wake way
+rather than as an inbox message.
 
 ## On-boot files