docs: Update CLI documentation (#489)

* docs: Update CLI documentation

* 📄 Update LLMs.txt snapshot for PR review

---------

Co-authored-by: juno-bot <juno-bot@users.noreply.github.com>
Co-authored-by: David Dal Busco <david.dalbusco@outlook.com>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: 3 people

.llms-snapshots/llms-full.txt

@@ -6,6 +6,7 @@ Usage: juno clear [options]
 Options:
   -f, --fullPath        Clear a particular file of your app.
   -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/clear.md

@@ -5,6 +5,7 @@ Usage: juno config [options]
 
 Options:
   -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/config.md

@@ -4,11 +4,13 @@ Deploy your app to your satellite.
 Usage: juno deploy [options]
 
 Options:
-  -c, --clear           Clear existing app files before proceeding with deployment.
+  --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.
   -i, --immediate       Deploy files instantly (bypasses the change workflow).
   -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/deploy.md

@@ -8,6 +8,7 @@ Options:
   -k, --keep-staged     Keep 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.
   --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/functions-publish.md

@@ -6,6 +6,7 @@ Usage: juno init [options]
 Options:
   --minimal         Skip few prompts and generate a config file with a placeholder satellite ID.
   -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/init.md

@@ -5,6 +5,8 @@ Usage: juno login [options]
 
 Options:
   -b, --browser         A particular browser to open. supported: chrome|firefox|edge.
+  -e, --emulator        Skips the Console UI and logs in your terminal with the emulator (⚠️  local development only).
   -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.
   -h, --help            Output usage information.
 ```

docs/reference/cli/login.md

@@ -7,6 +7,7 @@ Options:
   -b, --browser         A particular browser to open. supported: chrome|firefox|edge.
   -c, --console         Open satellite in the console.
   -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/open.md

@@ -11,6 +11,7 @@ Subcommands:
 Options:
   -t, --target          Which module type should be snapshotted? Valid targets are satellite, mission-control or orbiter.
   -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/snapshot.md

@@ -6,6 +6,7 @@ Usage: juno start [options]
 Options:
   -t, --target          Which module type should be started? Valid targets are satellite, mission-control or orbiter.
   -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.