chore: update runtime documentation

Author: lordrip

content/docs/designer/04-runtime-selector/_index.md

@@ -27,13 +27,13 @@ Kaoto provides a Camel catalog generator CLI to ease this process, it supports t
 yarn install
 ```
 
-1. Build the default catalogs
+4. Build the default catalogs
 
 ```bash
 yarn build
 ```
 
-1. This will generate a Catalog library containing:
+5. This will generate a Catalog library containing:
     * Camel Main versions
     * Camel extensions for Quarkus
     * Camel Spring boot
@@ -42,12 +42,12 @@ yarn build
 > To check what specific versions are included, please visit [the index file](https://github.com/KaotoIO/camel-catalog/blob/main/index.js)
 {.note}
 
-1. The resulting files will be in the `catalog` folder
+6. The resulting files will be in the `catalog` folder
 
 > The latest catalog is version is available in [the GitHub repository](https://github.com/KaotoIO/camel-catalog/tree/main/catalog)
 {.note}
 
-1. Providing that folder through a http server will make it available for using it in Kaoto
+7. Providing that folder through a http server will make it available for using it in Kaoto
 
 #### Creating a Catalog library with different runtimes
 
@@ -79,10 +79,12 @@ For a different Kamelets catalog version, the `--kamelets or -k` flag can be spe
 
 {{< image-sh src="vscode-kaoto-settings.png" text="VSCode Kaoto settings" >}}
 
-1. In the `TextField`, provide the URL of the `index.json` file that specifies the location of the subsequent catalogs, for instance, the public Kaoto catalog can be used:
+2. In the `TextField`, provide the URL of the `index.json` file that specifies the location of the subsequent catalogs, for instance, the public Kaoto catalog can be used:
 
 {{< image-sh src="setting-kaoto-catalog-url.png" text="Setting a Kaoto catalog URL" >}}
 
-1. Restart Kaoto for the changes to have effect
+3. Use the Kaoto editor status bar to select from a custom catalogs.
 
 {{< image-sh src="runtime-selector.png" text="Kaoto runtime selector" >}}
+
+4. Restart Kaoto for the changes to have effect

content/docs/designer/04-runtime-selector/runtime-selector.png

@@ -15,6 +15,17 @@ Before running integrations in Kaoto, ensure you have completed the installation
 
 ---
 
+## Selecting an executor
+
+Starting with Kaoto 2.11, there's a new setting to select the runtime executor, which can be either `jbang` (default) or `camel-launcher` (experimental). This setting can be found in the same settings page as the Catalog library URL.
+
+{{< image-sh src="setting-executor-selection.png" text="Setting the runtime executor" >}}
+
+> [!WARNING]
+> At the moment, the `camel-launcher` executor is experimental and may not work with all Apache Camel versions.
+
+---
+
 ## Understanding Execution Scopes
 
 Kaoto provides three execution scopes to match your workflow:
@@ -272,4 +283,4 @@ api.debug=true
 3. **Environment-specific settings**: Create separate property files for test/prod environments
 4. **Secure credentials**: Never hardcode sensitive data in integrations or commit secrets to version control
 5. **Document settings**: Add comments to property files explaining each configuration value
-6. **Version control**: Commit `application.properties` but consider excluding `application-dev.properties` if it contains sensitive local settings
+6. **Version control**: Commit `application.properties` but consider excluding `application-dev.properties` if it contains sensitive local settings