remove hive and agent apis nothing calls: build-log routes, /api/compact, host.sock list, mcp.sock wake

docs/4-implementation/agent-state/persistence.md

@@ -152,13 +152,12 @@ Capturing the full stream (rather than a short tail buffer) matters
 because real eval errors routinely run long — "tried alternatives"
 blocks alone are often 30+ lines — so a truncated tail would cut off
 the actual failure and leave only the host journal holding the
-complete output. With this table the dashboard can surface the entire
-log.
+complete output. This table holds the entire log; no HTTP route serves
+it.
 
 Three indices:
 
-- `(agent, started_at)` — backs the per-agent latest-N lookup used
-  by the agent card chip.
+- `(agent, started_at)` — per-agent lookup by recency.
 - `(status, finished_at)` — backs the retention sweep that runs
   as part of the existing hourly vacuum.
 - `(node_id)` — added by a later migration so a build log row can be

docs/4-implementation/agent-state/roster.md

@@ -101,10 +101,8 @@ state dirs work as for every other agent.
 - **Wire-protocol** — `hive-core-agent-sock`'s unified `Request` enum
   is the same on both socket flavours. Container lifecycle
   ops (kill/start/restart/rebuild) go through the separate host-admin
-  socket `hivectl` speaks. `Wake` (inject a `from: <X>` message straight
-  into the caller's own inbox) is on this socket too, unprivileged on
-  both flavours; matrix, bash and forge don't call it — their
-  notifications push a todo on the harness's in-agent socket (see
+  socket `hivectl` speaks. Matrix, bash and forge wake the agent by pushing a todo on the
+  harness's in-agent socket (see
   [`docs/4-implementation/turn-loop/mcp.md`](../turn-loop/mcp.md#waking-the-agent-from-inside-the-container)).
 - **Storage/mounts** — the `manage_root_agent` permission, which the
   [`ruth` archetype](../../2-handbook/swarm/archetypes.md#the-built-in-archetypes) grants, gets a container