# 2026-06-10 — Bridge endpoint 404 fix

## Late night: PowerShell bridge command "hangs"

Larry tried:
```powershell
$env:SEE_OUTPUT = "1"
irm https://dashboard.aisetuppros.com/bridge/manual-start.ps1 | iex
```
…and it sat there for 6+ minutes before returning to the prompt with no output. He thought it was broken.

### Root cause
- `static-bridge/manual-start.ps1` was committed in c2457f7 (the "Patch installer.ps1" commit by Atlas, also added manual-start.ps1 as a fallback for users with a broken scheduled task).
- But `server.py` line 402 only allowlisted `installer.ps1` and `windows-bridge.py`. manual-start.ps1 404'd.
- PowerShell with `iex` silently swallowed the HTML 404 page (no `-ErrorAction`, no `Write-Error`), so the only symptom was "taking forever".

### Fix
- Edited `server.py` to add `/bridge/manual-start.ps1` to the static-file route, with a `return` so it doesn't fall through to the 404 fallback.
- Had to `chattr -i` first (server.py still immutable from the dashboard-clobber fix). Re-muted after edit.
- Killed pid 3529299, started fresh `nohup python3 server.py` in `/root/agent-dashboard/` (CWD matters — running from workspace/ silently 404s the file).
- All three bridge URLs now return 200: installer 12269B, manual-start 861B, win-bridge 7935B.
- Committed as 3995a43.

### Doc
- `/root/agent-dashboard/docs/hermes/2026-06-10_bridge-manual-start-fix.md`

### Lesson
- When adding a "fallback" file in `static-bridge/`, add the route in `server.py` in the same commit. The file existing ≠ the URL working.
- `iex` of a 404 HTML page in PowerShell is silent. If users are going to keep typing that command, the dashboard should at minimum return a plain-text 4xx with a real error body.