c0re: keep power intent in memory, drop agent_power/kv tables and the stop snapshot

docs/2-handbook/agent-lifecycle/persistence.md

@@ -42,29 +42,23 @@ schemas, file layouts, and internal migration mechanics.
 
 ### `/var/lib/hyperhive/db/broker.sqlite` (host)
 
-Three tables, all in one file — the message queue, a small key/value
-table, and the per-agent power-intent registry:
+One table, the message queue:
 
 - `messages` — every inter-agent / operator-authored message.
   `sender / recipient / body / sent_at / delivered_at / acked_at /
   in_reply_to / priority`. `in_reply_to` links a reply to its parent
   row id; the dashboard and per-agent inbox render these as threaded
   rows.
-- `kv` — small persistent key/value store (`key PK / value`) for
-  host-side bookkeeping that doesn't warrant its own table.
 
-  ⚠️ The `mcp__hyperhive__remind` queue lives in a harness-local,
-  per-agent store — see [`/harness/` contents
-  below](#state-dirs-per-agent) for where reminders (and todos)
-  live.
-- `agent_power` — one row per agent: `agent PK / wanted (up |
-  offline) / updated_at`, owned by `hive-c0re/src/stores/power.rs`.
-  This is the durable power *intent* the job queue reconciles the
-  observed container state against; intent survives hive-c0re
-  restarts even though in-flight queue work doesn't. See
-  [`docs/4-implementation/scheduler/coordinator.md`'s Desired-state
-  section](../../4-implementation/scheduler/coordinator.md#desired-state-spec-vs-status) for who
-  writes and reads it and how reconciliation works.
+⚠️ The `mcp__hyperhive__remind` queue lives in a harness-local,
+per-agent store — see [`/harness/` contents
+below](#state-dirs-per-agent) for where reminders (and todos)
+live.
+
+The swarm owns power intent, so hive-c0re keeps none on disk. An older build
+also kept a `kv` table (the agents running at the last `hivectl stop`) and an
+`agent_power` table (the durable `wanted` intent) here; opening the file drops
+both.
 
 On a host whose hive-c0re once kept scheduled prompts, the file also
 holds `scheduled_prompts` and `scheduled_prompt_targets`. Nothing opens
@@ -80,8 +74,6 @@ Retention:
   rows are always kept — the harness `ack_turn`s only after a
   successful turn, so `requeue_inflight` can still requeue
   an unacked row on a crash.
-- `agent_power` rows live until the operator destroys the agent (one row per
-  agent — nothing to vacuum).
 
 ### `/harness/hyperhive-events.sqlite` (per agent)
 

docs/2-handbook/tools/hivectl-cli.md

@@ -454,7 +454,7 @@ Bare `hivectl stop` stops every agent and the gateway; scope flags narrow it to
 
 Start containers hive-wide — the inverse of `hivectl stop`.
 
-Bare `hivectl start` restores the agents stopped by the last broad-scope `stop` (or starts everything if none); scope flags narrow it. The swarm's forge and matrix are never in scope.
+Bare `hivectl start` starts every agent; scope flags narrow it. The swarm's forge and matrix are never in scope.
 
 **Usage:** `hivectl start [OPTIONS]`