fix(#1194): update Execution tool names + frontend + docs

docs/conventions.md

@@ -285,7 +285,7 @@ binary flavor.
 | `messaging` | `send`, `recv`, `ask`, `answer` |
 | `meta` | `set_status`, `get_agent_meta` |
 | `inbox` | `get_loose_ends`, `cancel_loose_end`, `remind`, `request_next_turn` |
-| `execution` | `bash_run`, `bash_status` |
+| `execution` | `run`, `status` (`mcp__bash__run`, `mcp__bash__status`) |
 | `lifecycle` | `kill`, `start`, `restart`, `update` *(privileged)* |
 | `approvals` | `request_init_config`, `request_apply_commit`, `request_update_meta_inputs` *(privileged)* |
 | `scheduling` | `request_schedule_prompt`, `fire_schedule_now`, `cancel_schedule`, `edit_schedule`, `list_schedules` *(privileged)* |

docs/gotchas.md

@@ -35,7 +35,7 @@ force-clear `HOST_ADDRESS` / `LOCAL_ADDRESS` / `HOST_ADDRESS6` /
 The hive-c0re service sets `path = [ pkgs.git "/run/current-system/sw" ]`.
 In-container harness services do the same so anything an agent adds
 to its own `agent.nix` (`environment.systemPackages`) is visible to
-the `bash_run` MCP tool (and any other in-container process) without
+the `mcp__bash__run` MCP tool (and any other in-container process) without
 editing the service definition.
 `environment.HYPERHIVE_GIT` bakes git's absolute path in (read by
 `lifecycle::git_command()`) for the host.

docs/persistence.md

@@ -177,7 +177,7 @@ Under `/var/lib/hyperhive/agents/<name>/`:
   agent consumption. Bind-mounted to `/agents/<name>/harness`
   inside the container (`$HYPERHIVE_HARNESS_DIR`). Contents:
   - `bash-tasks/` — task JSON + stdout/stderr files for
-    background `bash_run` jobs. JSON files are
+    background `mcp__bash__run` jobs. JSON files are
     `<id>.json` (status + tails), `<id>.out` / `<id>.err`
     (full captured output). Task files persist until container
     purge.

docs/turn-loop.md

@@ -373,20 +373,21 @@ it as a stdio child via `--mcp-config`. The hyperhive socket name is
   continue without waiting for an external message. The next turn starts
   with `from: "self"` and `body: "continue"`. No-op if new inbox
   messages arrive before this turn ends. No args.
-- `bash_run(cmd, timeout_secs?)` — submit a shell command for
+- `run(cmd, timeout_secs?)` — submit a shell command for
   background execution (`sh -c <cmd>`). Returns a task ID immediately;
   the command runs asynchronously in a harness-managed tokio task. Stdout
   and stderr stream to `harness/bash-tasks/<id>.{out,err}`. When the
   task completes (or times out, or the process errors), the harness wakes
   the agent with a summary body — handle on a future turn. Default
   timeout 180s; pass `timeout_secs` to override. Requires the
-  `execution` tool group.
-- `bash_status(id)` — poll the status of a task submitted with
-  `bash_run`. Returns status (`pending`/`running`/`done`/`timed_out`/
+  `execution` tool group. Exposed as `mcp__bash__run`.
+- `status(id)` — poll the status of a task submitted with
+  `run`. Returns status (`pending`/`running`/`done`/`timed_out`/
   `interrupted`), exit code, run duration, and the last 4 KiB of stdout
   and stderr (full output in the `.out`/`.err` files). Tasks marked
   `interrupted` had their process killed by a harness restart; a best-
   effort wake was still sent so the agent is not silently blocked.
+  Exposed as `mcp__bash__status`.
 
 ### Waking the agent from inside the container
 
@@ -581,9 +582,10 @@ status hint moved to the wake prompt + UI header.
 - Allowed MCP tools: as listed above per flavor.
 
 `Bash` is disallowed — shell execution goes through
-`mcp__hyperhive__bash_run` (background tasks with structured output +
-task-id tracking) instead of an interactive shell. The `bash_run` /
-`bash_status` MCP tools are always in the `--allowedTools` list.
+`mcp__bash__run` (background tasks with structured output +
+task-id tracking) instead of an interactive shell. The `run` /
+`status` MCP tools (`mcp__bash__run` / `mcp__bash__status`) are always
+in the `--allowedTools` list.
 
 `WebFetch` / `WebSearch` are off by default; enable the `web_tools`
 tool group in the P3RM1SS10NS tab and rebuild the agent to enable them.