diff --git a/docs/servers.md b/docs/servers.md index ec18a737..7e52194b 100644 --- a/docs/servers.md +++ b/docs/servers.md @@ -30,6 +30,7 @@ Seven, all running. | `fofos` | 100.64.0.17 | `pastilhas` | `~/officerdev/platform` | `officer.fofosfluffybastards.com` | | `macbookpro` | 100.64.0.9 | `pastilhas` | `~/projects/officer-suite/platform` | `macbookpro.pastilhas.dev` | | `production-pertento-bridge` | 100.64.0.12 | `pastilhas` | `~/officerdev/platform` | `officer.pertento.ai` | +| `edge-pertento-bridge` | 100.64.0.15 | `pastilhas` | `~/officerdev/platform` | `edge.pertento.ai` | | `deadpool-rezio-bridge` | 100.64.0.21 | **`br`** | `/home/br/officerdev/platform` | `officer.rezio.dev` `[pending]` | Only `platform.officer.dev` is public (77.42.39.155). The rest resolve to tailnet addresses and are @@ -40,15 +41,12 @@ reachable from inside only. A host here is NOT a deploy target. A rollout names it as skipped and moves on — it is not a failure, and it must not be reported as one. -| Host | Since | Why | -| ---------------------- | ---------- | ---------------------------------------------------------------- | -| `edge-pertento-bridge` | 2026-08-23 | Down, and staying down for some days. Owner's call, not a fault. | +None today. `edge-pertento-bridge` was here from 2026-08-23 and came back up on 2026-08-24; it is a +deploy target again and its row is in the table above. -Its row, kept so restoring it is one move: - -``` -| `edge-pertento-bridge` | 100.64.0.15 | `pastilhas` | `~/officerdev/platform` | `edge.pertento.ai` | -``` +It was down long enough to matter, so expect it to be behind: when it returned it was 215 commits back at +`2026.08.22.02`, with no `roles` table and no commanders. A host coming off this list needs its schema +brought forward before it is treated as ordinary. On 2026-08-23 the deploy agent spent four attempts and up to 60s per try on this host before reporting it unreachable — TCP on 22 accepted, then no SSH banner. That work was correct and entirely wasted, which