CB-622: rename bridge_* tools to fleet_* in scripts, e2e tests and config; mount name bridged -> fleetd

plugin/.mcp.json

@@ -1,6 +1,6 @@
 {
   "mcpServers": {
-    "bridged": {
+    "fleetd": {
       "type": "http",
       "url": "http://127.0.0.1:8765/mcp"
     }

plugin/skills/setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: setup
-description: Make the current project bridge-ready — check the prerequisites, mount the bridged MCP gateway into the project's .mcp.json, apply standard Claude Code settings, and verify this session resolves as the primary. Writes no credentials. Load this when asked to set up, install, configure, or onboard a project onto claude-bridge, or when bridge_* tools are expected but absent.
+description: Make the current project bridge-ready — check the prerequisites, mount the bridged MCP gateway into the project's .mcp.json, apply standard Claude Code settings, and verify this session resolves as the primary. Writes no credentials. Load this when asked to set up, install, configure, or onboard a project onto claude-bridge, or when fleet_* tools are expected but absent.
 ---
 
 # Bridge setup — make this project bridge-ready
@@ -70,7 +70,7 @@ The entry to add, exactly:
 ```json
 {
   "mcpServers": {
-    "bridged": {
+    "fleetd": {
       "type": "http",
       "url": "http://127.0.0.1:8765/mcp"
     }
@@ -78,12 +78,12 @@ The entry to add, exactly:
 }
 ```
 
-If `.mcp.json` already exists, add only the `bridged` key and leave every other server untouched.
-If a `bridged` entry is already there with a different URL, **ask** rather than assuming yours is
+If `.mcp.json` already exists, add only the `fleetd` key and leave every other server untouched.
+If a `fleetd` entry is already there with a different URL, **ask** rather than assuming yours is
 right — a non-default port usually means a deliberate second daemon.
 
 > **If this plugin is installed, you can skip this step entirely.** The plugin ships its own
-> `.mcp.json`, so `bridged` is already mounted for any session with the plugin enabled. Write the
+> `.mcp.json`, so `fleetd` is already mounted for any session with the plugin enabled. Write the
 > project-level file only when the user wants the mount to work *without* the plugin — for
 > teammates who have not installed it, or for CI.
 
@@ -111,18 +111,18 @@ project already set.
   "$schema": "https://json.schemastore.org/claude-code-settings.json",
   "permissions": {
     "allow": [
-      "mcp__bridged__bridge_whoami",
-      "mcp__bridged__bridge_list",
-      "mcp__bridged__bridge_status",
-      "mcp__bridged__bridge_profiles",
-      "mcp__bridged__bridge_poll"
+      "mcp__fleetd__fleet_whoami",
+      "mcp__fleetd__fleet_list",
+      "mcp__fleetd__fleet_status",
+      "mcp__fleetd__fleet_profiles",
+      "mcp__fleetd__fleet_poll"
     ]
   }
 }
 ```
 
-Only the **read-only** bridge verbs are pre-allowed. `bridge_spawn`, `bridge_send`, and
-`bridge_stop` start processes, deliver work, and tear down terminals — those stay behind a prompt
+Only the **read-only** bridge verbs are pre-allowed. `fleet_spawn`, `fleet_send`, and
+`fleet_stop` start processes, deliver work, and tear down terminals — those stay behind a prompt
 on purpose. Do not "helpfully" add them.
 
 Never write `settings.local.json` on the user's behalf; that file is personal and usually
@@ -157,7 +157,7 @@ Write none of these into any file. Show the user the `export` lines to run thems
 Reconnect MCP if needed (`/mcp`), then confirm the tools are live and this session is the primary:
 
 ```
-bridge_whoami
+fleet_whoami
 ```
 
 - `{"role":"primary"}` — correct, you are done with this step.
@@ -169,7 +169,7 @@ bridge_whoami
 
   ```yaml
   primary:
-    terminal: term_xxxxxxxxxxxx     # the terminalId bridge_whoami just reported
+    terminal: term_xxxxxxxxxxxx     # the terminalId fleet_whoami just reported
   ```
 
   The daemon reads this **at boot**, so it needs a restart. Re-pin whenever the primary moves
@@ -178,9 +178,9 @@ bridge_whoami
 Then prove the fleet actually works, with a real spawn:
 
 ```
-bridge_profiles                       → the configured backends
-bridge_spawn{profile: "<one of them>"} → must reach state "ready"
-bridge_stop{paneId: "<from spawn>"}
+fleet_profiles                       → the configured backends
+fleet_spawn{profile: "<one of them>"} → must reach state "ready"
+fleet_stop{paneId: "<from spawn>"}
 ```
 
 **`/healthz` reporting `ok` is not evidence that spawning works.** It reports that the daemon can
@@ -216,7 +216,7 @@ State plainly:
 ```
 prereqs:   herdr <version> · bridged <protocol> · ccs <version> · codex <version|absent>
 written:   <files created or merged, or "none">
-role:      <bridge_whoami result — and the pin, if one was needed>
+role:      <fleet_whoami result — and the pin, if one was needed>
 spawn:     <real spawn result: profile, state reached, torn down>
 env:       <variables the USER still needs to export — names only, never values>
 skipped:   <anything not done, and why>