Rename blueprints to Collections and add Operations tab

Fixes #46

docs/deployment-blueprints.md

@@ -1,14 +1,14 @@
-# Deployment blueprints
+# Deployment collections
 
-The Provisioning page is the starting point for reusable server collections. A
-blueprint describes a whole lineup: for example, two Kino lobbies, one Moon lobby,
+Open **Operations → Collections** to manage reusable server lineups. A
+collection describes a whole lineup: for example, two Kino lobbies, one Moon lobby,
 and two Town lobbies. Counts are desired fleet totals: existing and queued
 servers count toward each target, and only missing servers are created.
-Blueprints save game/map selections and lobby counts. Every new server uses the
+Collections save game/map selections and lobby counts. Every new server uses the
 latest promoted scripts, plugins, baseline, and matching configuration overlays
 when provisioning begins.
 
-For example, a blueprint targeting four Kino and two Der Riese lobbies, with
+For example, a collection targeting four Kino and two Der Riese lobbies, with
 two Kino already registered, creates two Kino and two Der Riese lobbies.
 The preview shows **Target / Existing or queued / To create** for each map.
 Matching is by game and exact map variant; T6 Town and Farm are distinct even
@@ -18,15 +18,15 @@ they appear in both the server registry and active creation queue.
 Registered servers count even if stopped or unhealthy; conforming does not
 restart or reconfigure them. Failed creation jobs without a registered server,
 destroyed records, and servers awaiting removal do not count. The default
-**Fill missing servers** mode keeps excess servers and maps outside the blueprint.
+**Fill missing servers** mode keeps excess servers and maps outside the collection.
 It fills deficits without changing existing servers' files.
 
 ## Build and launch a collection
 
-1. Choose **Create blueprint** on Provisioning and name the lineup.
+1. Choose **Create collection** on **Operations → Collections** and name the lineup.
 2. Add maps from Black Ops I or II and set the desired total lobbies for each.
-3. Choose **Save & preview** (or **Preview fleet changes** on a saved blueprint).
-   Choose **Fill missing servers** or **Match blueprint exactly**, then review
+3. Choose **Save & preview** (or **Preview fleet changes** on a saved collection).
+   Choose **Fill missing servers** or **Match collection exactly**, then review
    the server IDs and game ports.
 4. Lobbies with a saved key show **Saved key ready** and reuse it automatically.
    Enter a Plutonium key only for lobbies missing one. Update saved keys in **Keys**.
@@ -34,12 +34,12 @@ It fills deficits without changing existing servers' files.
    mode) and follow the collection progress page.
    If every target is already met, choose **Done**; no operation is created.
 
-### Match blueprint exactly
+### Match collection exactly
 
 Exact mode applies to the entire registered and queued fleet across both games.
 The preview lists servers to keep, create, and remove. It keeps deployed lobbies
 before unstarted creations, then the lowest lobby numbers within each game/map
-variant. It removes excess lobbies and maps outside the blueprint. Retained
+variant. It removes excess lobbies and maps outside the collection. Retained
 servers keep their containers, files, ports, and configuration without a restart.
 The option is chosen per launch; opening another preview defaults to fill mode.
 
@@ -64,17 +64,17 @@ tracks creations and removals, including removal-only plans, and lists the serve
 that were retained. The existing operation detail page offers removal cancellation
 and cleanup recovery where applicable.
 
-Blueprints support up to 40 distinct game/map selections, 1–20 lobbies per map,
+Collections support up to 40 distinct game/map selections, 1–20 lobbies per map,
 and 100 servers total. The host's configured port range and existing fleet may
-allow fewer. A blueprint can be saved even when there is insufficient capacity
-to launch it. Saving a blueprint does not capture or pin managed file versions.
+allow fewer. A collection can be saved even when there is insufficient capacity
+to launch it. Saving a collection does not capture or pin managed file versions.
 
-Use **Edit** on a blueprint card to change its name, description, maps, or lobby
+Use **Edit** on a collection card to change its name, description, maps, or lobby
 counts. Already reviewed launches keep their original lineup, including after
-blueprint edits or removal; their managed files still follow the latest promotions.
-Previously saved blueprints automatically use this policy without being resaved.
-Blueprints saved by the earlier single-server release load as one-server lineups
-and can be expanded directly. Any file snapshots in older blueprints are ignored
+collection edits or removal; their managed files still follow the latest promotions.
+Previously saved collections automatically use this policy without being resaved.
+Collections saved by the earlier single-server release load as one-server lineups
+and can be expanded directly. Any file snapshots in older collections are ignored
 when preparing new launches.
 
 A collection preview does not reserve capacity. At submission, all lobby IDs,
@@ -85,7 +85,7 @@ the preview retains typed keys only for unchanged server IDs still missing a sav
 key, and resets removal confirmation.
 
 Submitting the same preview again returns the same collection, including after
-a lost response or an application restart. Reusing the blueprint with a new
+a lost response or an application restart. Reusing the collection with a new
 preview recomputes the shortfall, including servers queued by earlier launches.
 It does not add another full copy of the lineup. If the shortfall or assigned
 capacity changes before submission, the request is rejected without changes and
@@ -114,7 +114,7 @@ operation links back to its collection.
 ## Create and review a launch
 
 1. Choose **Single server** on Provisioning (or the deploy action on the fleet).
-2. Choose the current promoted setup and select a game/map, or select a blueprint.
+2. Choose the current promoted setup and select a game/map, or select a collection.
 3. Choose **Preview launch**. Review the image reference, configuration sources,
    managed files and versions, selected map, lobby, port, and prerequisite checks.
 4. Enter the Plutonium key for the displayed server ID, or reuse its saved key.
@@ -132,24 +132,24 @@ rules, or credentials. Container and RCON verification happen after provisioning
 T6 variants retain their exact catalog slug and launch ruleset; RCON health checks
 verify the engine map, not the variant's start location.
 
-## Save and reuse a blueprint
+## Save and reuse a collection
 
-Expand **Make this a reusable blueprint** in a launch preview and give it a name
+Expand **Make this a reusable collection** in a launch preview and give it a name
 and optional description. You can save the map even when host configuration or
 available capacity blocks launching. Names are unique without regard to case.
 
-Each map in a blueprint retains the game, exact map variant, and desired lobby
+Each map in a collection retains the game, exact map variant, and desired lobby
 count. Image references, managed files, and composed configuration are resolved
 from the current setup for each new launch. Credentials, lobby IDs, and ports are
 not copied from the source server.
 
-Use **Conform fleet** on a blueprint card to review missing servers. Remove a
-blueprint from the library when it is no longer needed; its existing servers,
+Use **Conform fleet** on a collection card to review missing servers. Remove a
+collection from the library when it is no longer needed; its existing servers,
 reviewed previews, and deployment history remain intact.
 
 On a creation detail page, **Launch again** selects the original game and map
 with the next available lobby and port, using the latest promoted setup. The
-preview also lets you save that map as a blueprint with a target of one lobby.
+preview also lets you save that map as a collection with a target of one lobby.
 The recorded files remain visible as deployment history. Older deployments
 without a recorded recipe retain their history but cannot offer this action.
 
@@ -159,7 +159,7 @@ A preview shows the currently promoted managed files, configuration, and image
 reference for the selected map. It does not pin those versions. New launches
 resolve the promoted setup again when submitted and when provisioning begins, so
 promotions made after a preview or while a job is queued apply to that server.
-This applies to blueprint collections, single-server launches, and **Launch again**.
+This applies to collection collections, single-server launches, and **Launch again**.
 
 The files selected at provisioning, their hashes and version metadata, composed
 configuration, selected map, and image reference are recorded in SQLite for
@@ -201,6 +201,10 @@ repeats container creation or deployment as part of this recovery.
 
 ## API
 
+Collections retain the existing `/api/blueprints` endpoints and `blueprintId` /
+`blueprintName` fields for compatibility. Saved data needs no migration. Old
+`/provisioning?view=blueprints` links redirect to `/collections`.
+
 - `GET /api/blueprints`: list lineup summaries with game/map selections and counts.
 - `POST /api/blueprints`: save `{ name, description?, previewId }` or
   `{ name, description?, deploymentId }` for a single-map target of one lobby, or
@@ -222,7 +226,7 @@ repeats container creation or deployment as part of this recovery.
   each waiting server's global `queuePosition`, and the shared queue's concurrency,
   active startups, and queued count.
 - `POST /api/deployments/preview`: preview `{ game, mapSlug }` or `{ deploymentId }`
-  for a new single server using the latest promoted setup. All blueprints, including one-server
+  for a new single server using the latest promoted setup. All collections, including one-server
   targets, must use the collection endpoint so existing servers count correctly.
   Returns an ID, expiry, recipe summary, capacity, key
   availability (never its value), and prerequisite checks.