docs: Update CLI documentation

docs/reference/cli/changes-apply.md

@@ -7,6 +7,6 @@ Options:
   -i, --id              The ID of the change to apply.
   --snapshot            Create a snapshot before applying.
   --hash                The expected hash of all included changes (for verification).
-  -k, --keep-staged     Keep staged assets in memory after applying the change.
+  -k, --keep-staged     Keep proposed staged assets in memory after applying the change.
   -h, --help            Output usage information.
 ```

docs/reference/cli/changes-reject.md

@@ -6,6 +6,6 @@ Usage: juno changes reject [options]
 Options:
   -i, --id              The ID of the change to reject.
   --hash                The expected hash of all included changes (for verification).
-  -k, --keep-staged     Keep staged assets in memory after applying the change.
+  -k, --keep-staged     Keep proposed staged assets in memory after applying the change.
   -h, --help            Output usage information.
 ```

docs/reference/cli/functions-publish.md

@@ -5,7 +5,7 @@ Usage: juno functions publish [options]
 
 Options:
   --no-apply            Submit the release as a change but do not apply it yet.
-  -k, --keep-staged     Keep staged assets in memory after applying the change.
+  -k, --keep-staged     Keep proposed staged assets in memory after applying the change.
   -s, --src             A path to a specific local gzipped WASM file to publish.
   -m, --mode            Choose which environment to use (production, staging, development). Defaults to production if omitted.
   -p, --profile         Specify an optional profile to use (e.g. personal, team). Useful when managing multiple Mission Controls.

docs/reference/cli/hosting-deploy.md

@@ -8,8 +8,9 @@ Options:
   --clear               Clear existing app files before proceeding with deployment.
   --config              Apply configuration after deployment succeeds.
   --no-apply            Submit the deployment as a change but do not apply it yet.
-  -k, --keep-staged     Keep staged assets in memory after applying the change.
+  -k, --keep-staged     Keep proposed staged assets in memory after applying the change.
   -i, --immediate       Deploy files instantly (bypasses the change workflow).
+  --prune               Prune stale app files after successful deployment.
   -m, --mode            Choose which environment to use (production, staging, development). Defaults to production if omitted.
   -p, --profile         Specify an optional profile to use (e.g. personal, team). Useful when managing multiple Mission Controls.
   --container-url       Override a custom container URL. If not provided, defaults to production or the local container in development mode.

docs/reference/cli/hosting-prune.md

@@ -1,7 +1,14 @@
-TBD
+Remove stale frontend files from your satellite that are no longer in your build output.
 
 ```
 Usage: juno hosting prune [options]
 
-
+Options:
+  --batch               Number of files to prune in parallel per batch (default: 100).
+  --dry-run             List stale files that would be deleted without actually deleting them.
+  -m, --mode            Choose which environment to use (production, staging, development). Defaults to production if omitted.
+  -p, --profile         Specify an optional profile to use (e.g. personal, team). Useful when managing multiple Mission Controls.
+  --container-url       Override a custom container URL. If not provided, defaults to production or the local container in development mode.
+  --console-url         Specify a custom URL to access the developer Console.
+  -h, --help            Output usage information.
 ```

docs/reference/cli/hosting.md

@@ -6,4 +6,5 @@ Usage: juno hosting <subcommand> [options]
 Subcommands:
   clear               Remove frontend files (JS, HTML, CSS, etc.) from your satellite.
   deploy              Deploy your app to your satellite.
+  prune               Remove stale frontend files from your satellite that are no longer in your build output.
 ```