[Senate] Finish bridge.py removal

← All Specs

[Senate] Finish bridge.py removal

Task

  • ID: 98c6ebf0-d363-4f71-a031-9610effff51b
  • Type: one_shot
  • Layer: Senate
Effort: quick

Goal

scidex-bridge.service was a remote file-management HTTP daemon (port
8899) that hadn't worked in years (3800+ failed restart cycles
logged on 2026-04-28; required SCIDEX_TOKEN env var that's not in .env). The Orchestra fleet drives every change through git
worktrees + PRs now; nothing internal calls the bridge.

The systemd unit was stopped + disabled + removed on 2026-04-28.
SciDEX PR #1014 was opened the same day to remove the source files
+ every code reference. PR #1014 was closed without merging.

This task delivers the file-deletion + reference-cleanup half of
#1014 as a fresh PR. The runtime systemd cleanup already happened.

What needs to be deleted

  • /home/ubuntu/scidex/bridge.py
  • /home/ubuntu/scidex/scripts/bridge.py

What needs to be cleaned up (still references the dead service)

  • cli.py:
- SERVICES dict entry "bridge": {...} (line ~50)
- BRIDGE_SERVICE = "scidex-bridge" constant (line ~56)
- Bundle-installer tar arg listing bridge.py (line ~870)
- sudo cp scidex-bridge.service in the bundle script (line ~857)
  • deploy/bootstrap/install.sh:
- scidex-bridge.service line in the services array (~line 139)
  • scidex/core/scidex_doctor.py:
- The check_bridge() probe (line ~316-331). Replace with a
"removed" comment, not a no-op probe.
  • AGENTS.md references (5 places):
- Restart-discipline mentions of bridge.py (line ~65)
- Ask-first list mentions (line ~94)
- Restart-sensitive paths checklist (line ~175)
- Architecture table row for "Bridge API" (line ~868)
- Restart-rules table row for bridge.py (line ~1056)

What NOT to do

  • Don't re-disable / re-stop the systemd unit. Already done
2026-04-28. The PR is purely repo cleanup.
  • Don't delete Orchestra/orchestra/agent.py heartbeat / lease
code that has # bridge comments — those are unrelated
(MessageBridge, event_bus, etc.).

Acceptance criteria

grep -rn "scidex-bridge\|bridge\.py" /home/ubuntu/scidex/cli.py
/home/ubuntu/scidex/AGENTS.md /home/ubuntu/scidex/scidex/core/scidex_doctor.py
/home/ubuntu/scidex/deploy/bootstrap/install.sh
returns zero
matches (or only matches inside <details>-tagged historical
context blocks).
ls /home/ubuntu/scidex/bridge.py /home/ubuntu/scidex/scripts/bridge.py
returns both as No such file.
scidex doctor (or scidex.core.scidex_doctor) runs without
the Bridge probe.
gh pr for this work merges cleanly to main; no follow-up
test failures.

Why priority 70

Cleanup hygiene. The runtime damage is already neutralized (unit
removed). The repo state is just embarrassing: future operators
reading AGENTS.md still see "bridge.py" listed as a restart-sensitive
service.

Lineage

  • Closed-unmerged PR: SciDEX #1014.
  • Originating session recap: docs/planning/2026-04-27-orchestra-session-summary.md.
  • Runtime removal already done 2026-04-28; documented in the
session recap.

File: 98c6ebf0-d363-4f71-a031-9610effff51b_bridge_removal_final_spec.md
Modified: 2026-05-20 18:03
Size: 3.2 KB