Separate campaigns from server deployment lifecycle tracking

README.md

@@ -2,7 +2,7 @@
 
 Web app that manages a fleet of T5 Plutonium servers running under Komodo.
 Successor to `push_scripts.sh` — same job (push shared GSC scripts, run beta
-tests, restart empty servers, track deployments) with a live UI and real
+tests, restart empty servers, track campaigns) with a live UI and real
 audit diffs.
 
 ## Stack
@@ -23,7 +23,7 @@ audit diffs.
 - `src/lib/server/integrations/` — Komodo, RCON
 - `src/lib/server/pipeline/` — sweep loop, event bus, worker singleton
 - `src/routes/api/` — REST + SSE endpoints
-- `src/routes/` — UI pages (dashboard, deployments, betas, per-server)
+- `src/routes/` — UI pages (dashboard, campaigns, server deployments, betas, per-server)
 - `Dockerfile`, `docker-compose.yml`, `entrypoint.sh` — container build
 - `komodo/` — Komodo stack definition
 - `scripts/` — legacy JSON importer, fixture seeder
@@ -198,3 +198,9 @@ Every port carries a `// Ports push_scripts.sh:NN` comment pointing back to
 the original for the parts that had non-obvious behavior. Grep those if a
 behavior seems wrong — the shell script is the reference implementation
 until the parity check passes.
+
+## Campaigns and server deployments
+
+Campaigns (`/campaigns`) contains script/config rollouts, drift reconciliation, restart progress, file diffs, and rollbacks. Existing rollout records are preserved in the original database tables. The campaign API lives at `/api/campaigns`; legacy rollout detail API endpoints remain available for compatibility.
+
+Deployments (`/deployments`, `/api/deployments`) now tracks server creations and destructions with live stages and persistent history, including failures, warnings, and interrupted operations. History starts with operations performed after this update and survives server removal. Creation completion means the server was provisioned and Komodo accepted the container start request; runtime health remains on the Fleet page.