docs: move the agent tool docs to 4-implementation/agent-tools

hive-subagent-mcp/src/role.rs

@@ -9,7 +9,7 @@
 //! agent ships roles yet, so "named but missing" is the ordinary first-run
 //! state, and quietly spawning without the file would hand a subagent a
 //! prompt missing every clause the role was there to carry. See
-//! `docs/2-handbook/tools/subagent.md`.
+//! `docs/4-implementation/agent-tools/subagent.md`.
 
 use std::path::{Path, PathBuf};
 

hive-subagent-mcp/src/session.rs

@@ -27,7 +27,7 @@
 //! (`resume_target`), and waits for the driver's answer on the rest.** A
 //! turn that still misses is the call's own error, naming the directory
 //! searched (`classify_end`), within `RESUME_GRACE`. See
-//! `docs/2-handbook/tools/subagent.md`.
+//! `docs/4-implementation/agent-tools/subagent.md`.
 
 //! **One `start` can be more than one turn.** With a `goal` set, a turn that
 //! ends without a stop signal is followed by another re-prompting the
@@ -43,7 +43,7 @@
 //! exactly the incentive to claim it — the same failure class as a build
 //! report asserting "done, tests pass". Everything here treats it as a claim
 //! about the work, never as the work, and says so. See
-//! `docs/2-handbook/tools/subagent.md`.
+//! `docs/4-implementation/agent-tools/subagent.md`.
 
 //! **A subagent cannot say who it is.** Neither signal tool takes a session
 //! name. Each run is minted an unguessable token at spawn
@@ -61,7 +61,7 @@
 //! `State::finish_turn` remembers it against the name, which is what lets
 //! `status`, the end-of-turn todo and `continue`'s own reply all say the
 //! session was killed rather than let it read as finished. See
-//! `docs/2-handbook/tools/subagent.md`.
+//! `docs/4-implementation/agent-tools/subagent.md`.
 //!
 //! **No mid-turn compaction.** Building on `hive_claude::Claude::spawn` +
 //! `RunningClaude::wait` directly (not `InfiniteSession::run`) is what makes
@@ -1193,7 +1193,7 @@ fn subagent_otel_attrs(name: &str) -> String {
 /// ones, via [`hive_sh4re::permissions::subagent_builtin_tools_for`] over the
 /// agent's permissions ([`crate::swarm_models::permissions_now`]), which
 /// documents its one `Bash` exception. `--tools` does not filter `mcp__*`,
-/// so the signal tools are unnamed in it (`docs/2-handbook/tools/subagent.md`).
+/// so the signal tools are unnamed in it (`docs/4-implementation/agent-tools/subagent.md`).
 ///
 /// `signal_url` is what makes `goal_reached`/`need_help` callable at all: a
 /// subagent reaches them over the same streamable-http listener its parent
@@ -1273,7 +1273,7 @@ fn build_config(
 ///
 /// Unreadable task instructions, or (with a role) a harness dir that
 /// cannot be written. Both refuse the spawn rather than dropping either
-/// half — see `docs/2-handbook/tools/subagent.md`.
+/// half — see `docs/4-implementation/agent-tools/subagent.md`.
 fn system_prompt_and_trigger(
     name: &str,
     role: Option<&str>,
@@ -2339,7 +2339,7 @@ pub fn status(state: &State, name: &str, dir: Option<&str>) -> anyhow::Result<St
 /// Deliberately just the number now — the full "seconds means working,
 /// minutes means wedged, resets each turn" explanation used to repeat here
 /// on every single call. It already lives in the `status` tool description
-/// and in `docs/2-handbook/tools/subagent.md`'s "Telling working from wedged"
+/// and in `docs/4-implementation/agent-tools/subagent.md`'s "Telling working from wedged"
 /// section, so restating it in a line meant to be skimmed, possibly several
 /// times a minute, was pure repetition.
 ///