CB-622 (unit C): rename bridge_* tools to fleet_* in scripts, e2e tests, config; mount name bridged -> fleetd #132

2026-08-22T21:49:49+02:00

agent commented

2026-08-22 21:49:49 +02:00

Ticket #126 (CB-622), epic #125 — unit C. Non-Java half of the tool rename.

Part 1 — eleven tool names bridge_ -> fleet_** in:

e2e/bridge_ask_test.py, e2e/conversation_test.py, e2e/conversation_sustained_test.py, e2e/issue_hunt_test.py
bridged/bridged.example.yaml (comments only)
scripts/redeploy-bridged.sh (echo text only)

The output-artifact filename e2e/bridge_ask_transcript.md and the script name bridge_ask_test.py were deliberately NOT renamed (out of scope: no file renames).

Part 2 — MCP mount name "bridged" -> "fleetd" in plugin/.mcp.json and .claude/skills/port-to-opencode/SKILL.md. In plugin/skills/setup/SKILL.md I renamed the mount key references and fully updated the mcp__bridged__bridge_* permission strings to mcp__fleetd__fleet_* plus adjacent tool-name prose, so that file is internally consistent; daemon-binary references to bridged were left alone. opencode.json contains no bridged mount entry (only a $schema key), so nothing changed there.

Not touched: root .mcp.json, .claude/settings.local.json, wiki/, BRIDGED_* env vars, any filename/directory, all .java and other .md files.

Checks run in the worktree: python3 -m json.tool plugin/.mcp.json (OK); python3 -m py_compile on all four e2e .py files (all OK); yaml.safe_load on bridged/bridged.example.yaml via a temp venv with pyyaml (OK — system python3 has no yaml module). The e2e tests themselves were NOT run: they need a live daemon rebuilt with the new names; that is the lead's step after the Java unit lands.

Ticket #126 (CB-622), epic #125 — unit C. Non-Java half of the tool rename. **Part 1 — eleven tool names bridge_* -> fleet_*** in: - e2e/bridge_ask_test.py, e2e/conversation_test.py, e2e/conversation_sustained_test.py, e2e/issue_hunt_test.py - bridged/bridged.example.yaml (comments only) - scripts/redeploy-bridged.sh (echo text only) The output-artifact filename e2e/bridge_ask_transcript.md and the script name bridge_ask_test.py were deliberately NOT renamed (out of scope: no file renames). **Part 2 — MCP mount name "bridged" -> "fleetd"** in plugin/.mcp.json and .claude/skills/port-to-opencode/SKILL.md. In plugin/skills/setup/SKILL.md I renamed the mount key references and fully updated the mcp__bridged__bridge_* permission strings to mcp__fleetd__fleet_* plus adjacent tool-name prose, so that file is internally consistent; daemon-binary references to `bridged` were left alone. opencode.json contains no `bridged` mount entry (only a $schema key), so nothing changed there. Not touched: root .mcp.json, .claude/settings.local.json, wiki/, BRIDGED_* env vars, any filename/directory, all .java and other .md files. Checks run in the worktree: python3 -m json.tool plugin/.mcp.json (OK); python3 -m py_compile on all four e2e .py files (all OK); yaml.safe_load on bridged/bridged.example.yaml via a temp venv with pyyaml (OK — system python3 has no yaml module). The e2e tests themselves were NOT run: they need a live daemon rebuilt with the new names; that is the lead's step after the Java unit lands.

agent added 1 commit 2026-08-22 21:49:50 +02:00

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

CI / build (pull_request) Successful in 58s

Details

CI / contract (pull_request) Successful in 1m9s

Details

03473a286b

ltms referenced this issue from a commit

2026-08-22 21:58:04 +02:00

Merge CB-622 Unit A: dual-register the MCP tools as fleet_* and bridge_*

ltms merged commit d82d0157cb into main

2026-08-22 21:58:10 +02:00