Rename blueprints to Collections and add Operations tab

Fixes #46

README.md

@@ -131,13 +131,13 @@ RCON, and selected-map verification.
 No token, no session, no auth freeze. If Komodo or RCON aren't configured,
 the sweep marks pending rows `manual` so nothing hangs forever.
 
-## Provisioning blueprints and launch previews
+## Provisioning collections and launch previews
 
 Provisioning also offers **House Party Protocol**: review the entire fleet and queue
 destruction in one action. This includes queued creations and reuses pending
 destruction requests. Each server waits for a fresh zero-player reading; occupied
 or unreachable servers remain queued. Containers, server files, and registrations
-are removed, while saved keys and blueprints are retained. The preview must be
+are removed, while saved keys and collections are retained. The preview must be
 reviewed again if fleet membership changes before confirmation. Servers created
 after confirmation are not included. Progress appears in deployment history.
 
@@ -146,13 +146,13 @@ If deletion fails after Komodo removal, the operation detail page offers
 repeating Komodo deletion. Requesting destruction again also resumes that cleanup.
 Recovery is blocked if a newer operation exists for the same server name.
 
-Provisioning includes a blueprint builder for whole server collections: choose
+**Operations → Collections** includes a builder for whole server lineups: choose
 multiple T5/T6 maps and set the desired total lobbies for each. **Conform fleet**
 counts existing and queued servers and creates only the shortfall. The preview
 shows target/existing/missing counts and IDs, ports, and key requirements for new
 servers only. Already-satisfied targets create nothing; excess servers are kept.
-Choose **Match blueprint exactly** in the preview to also remove excess lobbies
-and maps outside the blueprint. Review the keep/create/remove lists and confirm
+Choose **Match collection exactly** in the preview to also remove excess lobbies
+and maps outside the collection. Review the keep/create/remove lists and confirm
 removals. Matching servers stay untouched; unstarted excess creations are cancelled,
 and running servers wait for a fresh zero-player check before removal. New lobbies
 can reserve ports from these removals and wait until they are released. The collection
@@ -167,16 +167,16 @@ shows the startup limit, and its progress page shows active startups and each
 server's place in the shared queue. Set `DEPLOYMENT_CREATE_CONCURRENCY` to a
 positive integer to increase the limit. Each worker pass starts at most the
 available number of slots; immediate failures do not drain the remaining queue.
-Existing single-server blueprints can be expanded with **Edit**. Single-server
+Existing single-server collections can be expanded with **Edit**. Single-server
 launches and launching again from recorded recipes remain available.
-Blueprints save maps and target lobby counts. Every new server uses the latest
+Collections save maps and target lobby counts. Every new server uses the latest
 promoted scripts, plugins, and configuration when provisioning begins, including
-promotions made after preview or while queued. Existing blueprints automatically
+promotions made after preview or while queued. Existing collections automatically
 follow this policy. Deployment history records the files selected for that launch;
 **Launch again** uses the current promoted setup for the same game and map.
 The progress page explains waiting conditions, shows elapsed time, and can resume
 health verification of an interrupted creation when its original server remains.
-See [Deployment blueprints](docs/deployment-blueprints.md) for the workflow,
+See [Deployment collections](docs/deployment-blueprints.md) for the workflow,
 promotion policy, and API details.
 
 ## Saved server keys