Trim provisioning job details (Refs #88)

docs/guides/provisioning.md

@@ -170,6 +170,13 @@ Related work links back to the requesting campaign, beta, maintenance item, or
 collection. A completed provisioning job does not imply that its requester has
 finished its own verification.
 
+Optional timestamps appear only when recorded. **Launch files** appears for Create
+and Rebuild, or when an older operation has a recorded recipe. Start, Restart,
+and Stop use the existing instance without selecting new launch files.
+
+While a job is active, **Controller activity** lists current work and elapsed
+time. Background scans run independently of provisioning.
+
 ### Verification evidence
 
 New operations record structured verification evidence alongside their activity:
@@ -201,6 +208,12 @@ the replacement in its reserved slot. Resuming the same operation preserves its
 earlier failure and resume events. Uncertain commands have no generic Retry action.
 
 Cancelling an operation does not stop a command already delivered to the host.
+The confirmation explains that remaining work and health checks stop, while
+changes already made remain. **Cancel creation and remove server** also deletes
+the launch's container and instance files, even if players have joined or their
+status is unknown. Shared game files are kept, and the key returns to its game
+pool after confirmed removal.
+
 A later rebuild waits for that command to settle. Its waiting message includes
 the host command's state and last reported error; **View cancelled operation**
 opens the original command details. If an interrupted rebuild removed its old