Simplify single-server launch flow

docs/guides/provisioning.md

@@ -7,6 +7,13 @@ Provisioning owns the queues, safety checks, execution, and
 recovery for all six actions. Create a server using **Create server**. For an existing
 server, choose **Manage server** or open its **Server actions** menu.
 
+**Create server** opens one dialog with game and map choices followed by automatic
+readiness checks. Blockers explain what needs attention before launch. Runtime
+and network overrides are under **Advanced settings**; image, configuration,
+managed files, upload time, and internal server ID are under **Setup details**.
+The footer keeps **Cancel** and **Launch server** available while reviewing the
+setup. Create and launch reusable lineups separately in **Fleet → Collections**.
+
 | Action | Behavior |
 | --- | --- |
 | Create | Create a new instance using the latest promoted files and verify container health, game status, the selected map, and the Plutonium revision. |
@@ -164,8 +171,9 @@ Create and rebuild capture a setup when queued and select the latest promoted
 files again when creation begins. The page distinguishes **Setup captured when
 queued** from **Files selected for this attempt**. A queued capture does not pin
 versions; an attempted selection is not proof that every file was installed.
-**Launch another server** uses the latest promoted setup with a fresh identity and
-port, rather than repairing or replaying the recorded job.
+**Launch another server** opens the creation dialog with the recorded game and
+map as editable starting values. It checks the latest promoted setup and creates
+a separate server with a fresh identity and port.
 
 ### History and refresh behavior