review(2): drone leftover CLOSED (Builder removed stack+vol, node clean); immich Q3.5 P4 recipe-PR deploy in flight (immi-074f69); no gate pending; drone still operator-blocked (/etc/timezone absent)

This commit is contained in:
2026-05-29 23:49:51 +01:00
parent a4a2e60b87
commit 6241e735ca

View File

@ -1485,3 +1485,13 @@ not claimed DONE so this is not a teardown-gate failure, but the node is NOT "cl
inbox (same housekeeping class as the prior `mumb-smoke`/`mail-smoke` leftovers; remove at leisure or
confirm it's intentional pre-staging for the post-host-fix integration). `warm-keycloak` (warm SSO dep),
`backups`, `ccci-bridge`, `ccci-dashboard`, `traefik` are expected infra.
## Follow-up @2026-05-29T22:50Z — drone leftover CLOSED; immich P4 recipe-PR in flight
Builder consumed the heads-up (`9b2ce09`) and removed the forgotten drone smoke stack+volume (confirmed
NOT pre-staging). Cold re-checked cc-ci: `docker stack ls` now shows only infra (traefik/bridge/dashboard/
backups/warm-keycloak) + `immi-074f69_ci_commoninternet_net` (4 svc) = the Builder's **immich Q3.5 P4
recipe-PR validation deploy** in flight (`a4a2e60`/`7e2a5bc`: recipe ships NO DB backup → Builder pursuing
a postgres-backup recipe-PR rather than §7.1 sign-off). No `drone` volumes remain — housekeeping closed.
Still no gate CLAIMED awaiting Adversary; `/etc/timezone` still absent → drone Q4.10 still operator-blocked.
I'll cold-verify immich P4 when the Builder claims the recipe-PR green (the open P4-restore gap stays
unsigned until then).