docs(#2627): crate READMEs for the harness column (hive-agent, hive-agent-mcp, hive-agent-wake, hive-bash-mcp)

hive-agent-wake/Cargo.toml

@@ -2,6 +2,7 @@
 name = "hive-agent-wake"
 version.workspace = true
 edition.workspace = true
+readme = "README.md"
 
 [[bin]]
 name = "hive-agent-wake"

hive-agent-wake/README.md

@@ -0,0 +1,25 @@
+# hive-agent-wake
+
+A tiny CLI that injects a wake-up event into an agent's own harness
+inbox, so the next turn fires with a given `--from`/`--body`. That's
+the whole crate.
+
+## When to use it
+
+Reach for this when you're wiring up an `extraMcpServers` daemon
+(scraper, webhook listener, custom integration) that needs to nudge
+claude on some external event — a new item arrived, a long job
+finished, whatever. The built-in daemons (matrix, bash) don't use
+this: they talk to the per-agent MCP socket directly instead. This CLI
+exists so a helper author only needs one small, dependency-light crate
+to get the same effect without linking `hive-agent-mcp` or the full
+`hive-agent` harness lib.
+
+## Shape
+
+One binary, `src/main.rs`: parses `--socket` (defaults to
+`/run/hive/mcp.sock`, the per-agent MCP socket bind-mounted from the
+host), `--from`, and `--body` (pass `-` to read the body from stdin),
+dials the socket with `hive-core-agent-sock`'s `Request`/`Response`
+wire types, sends a `Wake` request, and exits. It carries its own copy
+of the retrying request client rather than depending on `hive-agent-mcp`'s.