feat: Update documentation for live updates channels and app setup

- Added descriptions and detailed instructions for managing live update channels in Japanese, Korean, and Chinese.
- Enhanced the explanation of device channel selection priority and the behavior of `setChannel()` for immediate channel switching.
- Included notes on installing the Capacitor updater plugin for different Capacitor versions in Korean and Chinese.
- Clarified the default channel behavior and best practices for channel configuration.

Author: riderx

src/content/docs/de/docs/getting-started/add-an-app.mdx

@@ -51,6 +51,23 @@ Falls der Init-Befehl für Sie nicht funktioniert, können Sie eine App manuell
 
 3. Installieren Sie das Plugin in Ihrer App: <Code code={`npm i @capgo/capacitor-updater`} lang="bash" />
 
+   <Aside type="note" title="Installation für ältere Capacitor-Versionen">
+   Der obige Befehl installiert die neueste Version (v8.x) für Capacitor 8. Für ältere Capacitor-Versionen verwenden Sie den entsprechenden npm-Tag:
+
+   ```bash
+   # Capacitor 7
+   npm i @capgo/capacitor-updater@lts-v7
+
+   # Capacitor 6
+   npm i @capgo/capacitor-updater@lts-v6
+
+   # Capacitor 5
+   npm i @capgo/capacitor-updater@lts-v5
+   ```
+
+   Jede Plugin-Hauptversion entspricht der Capacitor-Hauptversion (v8 → Capacitor 8, v7 → Capacitor 7, v6 → Capacitor 6, v5 → Capacitor 5). Minor-Versionen teilen denselben Funktionsumfang über alle Hauptversionen (z.B. 5.34.0, 6.34.0, 7.34.0 und 8.34.0 enthalten dieselben Funktionen).
+   </Aside>
+
 4. Konfigurieren Sie das Plugin in Ihrer `capacitor.config` <Code code={`{\n  "plugins": {\n    CapacitorUpdater: {\n      "appId": "Your appID",\n      "autoUpdate": true,\n      "version": "1.0.0"\n    }\n  }\n}`} lang="json" />
   [Siehe alle verfügbaren Optionen](/docs/plugin/settings/). Diese Informationen werden abgeleitet, wenn sie nicht bereitgestellt werden.
 

src/content/docs/de/docs/live-updates/channels.mdx

@@ -51,6 +51,23 @@ In case the init command doesn't work for you, you can manually add an app.
 
 3. Install the plugin in your app: <Code code={`npm i @capgo/capacitor-updater`} lang="bash" />
 
+   <Aside type="note" title="Installing for older Capacitor versions">
+   The command above installs the latest version (v8.x) for Capacitor 8. For older Capacitor versions, use the appropriate npm tag:
+
+   ```bash
+   # Capacitor 7
+   npm i @capgo/capacitor-updater@lts-v7
+
+   # Capacitor 6
+   npm i @capgo/capacitor-updater@lts-v6
+
+   # Capacitor 5
+   npm i @capgo/capacitor-updater@lts-v5
+   ```
+
+   Each plugin major version matches the Capacitor major version (v8 → Capacitor 8, v7 → Capacitor 7, v6 → Capacitor 6, v5 → Capacitor 5). Minor versions share the same feature set across all major versions (e.g., 5.34.0, 6.34.0, 7.34.0, and 8.34.0 all include the same features).
+   </Aside>
+
 4. Configure the plugin in your `capacitor.config` <Code code={`{\n  "plugins": {\n    CapacitorUpdater: {\n      "appId": "Your appID",\n      "autoUpdate": true,\n      "version": "1.0.0"\n    }\n  }\n}`} lang="json" />
   [See all option available](/docs/plugin/settings/). This information will be infer if not provided.
 

src/content/docs/docs/getting-started/add-an-app.mdx

@@ -14,7 +14,17 @@ A Live Update channel points to a specific JS bundle build of your app that will
 When a device checks for an update, Capgo decides which channel to use in this strict order (highest priority first):
 
 1. **Forced device mapping (Dashboard)** – Manually pin a specific device ID to a channel. Use for urgent debugging or controlled testing with a single real user. This always wins.
-2. **Cloud override (per‑device) via `setChannel()` or Dashboard** – Created when your app calls `setChannel()` (often exposed in a QA/debug menu) or you change the device's channel in the dashboard. Use for QA users switching between feature / PR channels or to reproduce a user issue. Reinstalling the binary does not clear it; deleting the device entry does.
+2. **Cloud override (per‑device) via Dashboard or API** – Created when you change the device's channel in the dashboard or via API. Use for QA users switching between feature / PR channels or to reproduce a user issue. Reinstalling the binary does not clear it; deleting the device entry does.
+
+<Aside type="tip" title="Instant Channel Switching with setChannel()">
+**Starting from plugin version 5.34.0, 6.34.0, 7.34.0, or 8.0.0** (depending on your major version), `setChannel()` works differently: it contacts the backend to **validate** that the channel is allowed (checking if self-assignment is enabled for that channel), then stores the channel **locally on the device** as `defaultChannel`. This means the new channel takes effect **instantly** for the next update check—no waiting for replication.
+
+Previously, `setChannel()` saved the channel override to the backend database (like Dashboard or API changes), and devices had to wait for data replication (up to 2 minutes) before the new channel was recognized. The new behavior only reads from the backend (for validation) and stores locally, making channel switches instant.
+
+**Note:** Even if a channel becomes disallowed after being set locally, the backend will still validate the channel during update checks, so security is maintained.
+
+**Important:** When channel changes are made via the Dashboard or API, there is still a replication lag of up to 2 minutes before all edge servers reflect the change. For instant channel switching, use `setChannel()` from your app code—it validates with the backend, then sets the channel locally for immediate effect.
+</Aside>
 3. **Capacitor config `defaultChannel` (test build default)** – If present in `capacitor.config.*` and no force/override exists, the app starts on this channel (e.g. `beta`, `qa`, `pr-123`). Intended for TestFlight / internal builds so testers land on a pre‑release channel automatically. Production builds typically leave this unset.
 4. **Cloud Default Channel (primary path ~99% of users)** – If you mark a default channel in the dashboard, all normal end‑users (no force, no override, no config defaultChannel) attach here. Change it to roll out or roll back instantly—no new binary. If you have platform-specific defaults (one iOS-only, one Android-only), each device lands on the default matching its platform. Leaving the cloud default unset is allowed; in that case the device must match on steps 1–3 to receive updates.
 
@@ -120,6 +130,51 @@ npx @capgo/cli@latest channel set production com.example.app \
 npx @capgo/cli@latest channel set beta com.example.app --self-assign
 ```
 
+### Using setChannel() from Your App
+
+The `setChannel()` method allows your app to programmatically switch channels at runtime. This is particularly useful for:
+
+- QA/debug menus where testers can switch between channels
+- Beta program opt-in flows
+- Feature flag implementations
+- A/B testing scenarios
+
+```typescript
+import { CapacitorUpdater } from '@capgo/capacitor-updater';
+
+// Switch to the beta channel
+await CapacitorUpdater.setChannel({ channel: 'beta' });
+
+// Optionally trigger an immediate update check after switching
+await CapacitorUpdater.setChannel({
+  channel: 'beta',
+  triggerAutoUpdate: true
+});
+```
+
+<Aside type="note" title="How setChannel() Works (v5.34.0+ / v6.34.0+ / v7.34.0+ / v8.0.0+)">
+When `setChannel()` is called:
+
+1. **Backend validation (read-only)**: A request is sent to the Capgo backend to validate the channel is allowed (checking self-assignment permissions)
+2. **Local storage update**: If validation passes, the channel is saved to the device's local storage as `defaultChannel`
+3. **Instant effect**: The next update check uses the new channel immediately (no waiting for replication)
+
+**Why this matters:** In older versions, `setChannel()` saved the channel override to the backend database (same as Dashboard or API changes). Devices had to wait for backend replication (up to 2 minutes) before the channel change took effect. Now, `setChannel()` only reads from the backend (for validation) and stores locally, making channel switches instant.
+
+**Security note:** Even if a channel's permissions change after being set locally (e.g., self-assignment is disabled), the backend will still validate the channel during update checks, ensuring security is maintained.
+
+**Comparison of channel change methods:**
+
+| Method | Effect Time | Persisted Where | Use Case |
+|--------|-------------|-----------------|----------|
+| `setChannel()` from plugin | **Instant** | Device only (local) | User-initiated channel switching in-app |
+| Dashboard device override | Up to 2 min | Backend database | Admin-initiated changes for specific devices |
+| API channel assignment | Up to 2 min | Backend database | Automated backend integrations |
+
+For the best user experience when building channel-switching UIs, always use the plugin's `setChannel()` method.
+
+Minimum versions for local-only channel switching: **5.34.0**, **6.34.0**, **7.34.0**, or **8.0.0** (depending on your major version). Each minor version number corresponds to the same feature set across all major versions (e.g., X.34.0 includes the same features whether X is 5, 6, 7, or 8). See [plugin installation](/docs/getting-started/add-an-app/) for version tags.
+</Aside>
 
 ## Assigning a Bundle to a Channel
 

src/content/docs/docs/live-updates/channels.mdx

@@ -52,6 +52,23 @@ En caso de que el comando init no funcione para ti, puedes añadir manualmente u
 
 3. Instala el Plugin en tu aplicación: <Code code={`npm i @capgo/capacitor-updater`} lang="bash" />
 
+   <Aside type="note" title="Instalación para versiones anteriores de Capacitor">
+   El comando anterior instala la última versión (v8.x) para Capacitor 8. Para versiones anteriores de Capacitor, usa la etiqueta npm apropiada:
+
+   ```bash
+   # Capacitor 7
+   npm i @capgo/capacitor-updater@lts-v7
+
+   # Capacitor 6
+   npm i @capgo/capacitor-updater@lts-v6
+
+   # Capacitor 5
+   npm i @capgo/capacitor-updater@lts-v5
+   ```
+
+   Cada versión mayor del plugin corresponde a la versión mayor de Capacitor (v8 → Capacitor 8, v7 → Capacitor 7, v6 → Capacitor 6, v5 → Capacitor 5). Las versiones menores comparten el mismo conjunto de características en todas las versiones mayores (ej., 5.34.0, 6.34.0, 7.34.0, y 8.34.0 incluyen las mismas características).
+   </Aside>
+
 4. Configura el Plugin en tu `capacitor.config` <Code code={`{\n  "plugins": {\n    CapacitorUpdater: {\n      "appId": "Your appID",\n      "autoUpdate": true,\n      "version": "1.0.0"\n    }\n  }\n}`} lang="JSON" />
   [Ver todas las opciones disponibles](/docs/plugin/settings/). Esta información se inferirá si no se proporciona.
 

src/content/docs/es/docs/getting-started/add-an-app.mdx

@@ -15,7 +15,17 @@ Un canal de Actualización en Vivo apunta a una compilación específica del Paq
 Cuando un dispositivo verifica una actualización, Capgo decide qué canal usar en este orden estricto (prioridad más alta primero):
 
 1. **Mapeo forzado de dispositivo (Panel)** – Ancla manualmente un ID de dispositivo específico a un canal. Úsalo para depuración urgente o pruebas controladas con un solo usuario real. Esto siempre gana.
-2. **Anulación en la nube (por dispositivo) vía `setChannel()` o Panel** – Creado cuando tu aplicación llama a `setChannel()` (a menudo expuesto en un menú QA/Depuración) o cambias el canal del dispositivo en el panel. Úsalo para usuarios de QA cambiando entre canales de características / PR o para reproducir un problema de usuario. Reinstalar el binario no lo borra; eliminar la entrada del dispositivo sí lo hace.
+2. **Anulación en la nube (por dispositivo) vía Panel o API** – Creado cuando cambias el canal del dispositivo en el panel o vía API. Úsalo para usuarios de QA cambiando entre canales de características / PR o para reproducir un problema de usuario. Reinstalar el binario no lo borra; eliminar la entrada del dispositivo sí lo hace.
+
+<Aside type="tip" title="Cambio Instantáneo de Canal con setChannel()">
+**A partir de la versión del plugin 5.34.0, 6.34.0, 7.34.0, o 8.0.0** (dependiendo de tu versión mayor), `setChannel()` funciona de manera diferente: contacta al backend para **validar** que el canal está permitido (verificando si la auto-asignación está habilitada para ese canal), luego almacena el canal **localmente en el dispositivo** como `defaultChannel`. Esto significa que el nuevo canal toma efecto **instantáneamente** para la próxima verificación de actualización—sin esperar replicación.
+
+Anteriormente, `setChannel()` guardaba la anulación del canal en la base de datos del backend (igual que los cambios del Panel o API). Los dispositivos tenían que esperar la replicación del backend (hasta 2 minutos) antes de que el nuevo canal fuera reconocido. El nuevo comportamiento solo lee del backend (para validación) y almacena localmente, haciendo los cambios de canal instantáneos.
+
+**Nota de seguridad:** Incluso si un canal se vuelve no permitido después de configurarse localmente, el backend aún validará el canal durante las verificaciones de actualización, asegurando que la seguridad se mantenga.
+
+**Importante:** Cuando los cambios de canal se realizan vía el Panel o API, todavía hay un retraso de replicación de hasta 2 minutos. Para cambio instantáneo de canal, usa `setChannel()` desde el código de tu aplicación—valida con el backend, luego establece el canal localmente para efecto inmediato.
+</Aside>
 3. **Config de Capacitor `defaultChannel` (predeterminado de compilación de prueba)** – Si está presente en `capacitor.config.*` y no existe forzado/anulación, la aplicación comienza en este canal (por ejemplo, `beta`, `qa`, `pr-123`). Destinado para TestFlight / compilaciones internas para que los evaluadores aterricen automáticamente en un canal de pre-lanzamiento. Las compilaciones de producción típicamente dejan esto sin configurar.
 4. **Canal Predeterminado en la Nube (ruta principal ~99% de usuarios)** – Si marcas un canal predeterminado en el panel, todos los usuarios finales normales (sin forzado, sin anulación, sin config defaultChannel) se conectan aquí. Cámbialo para desplegar o revertir al instante—sin nuevo binario. Si tienes predeterminados específicos de plataforma (uno solo para iOS, uno solo para Android), cada dispositivo aterriza en el predeterminado que coincida con su plataforma. Dejar el predeterminado en la nube sin configurar está permitido; en ese caso, el dispositivo debe coincidir en los pasos 1–3 para recibir actualizaciones.
 

src/content/docs/es/docs/live-updates/channels.mdx

@@ -52,6 +52,23 @@ In case the init Commande doesn't work for you, you can manually Ajouter an Appl
 
 3. Install the plugin in your app: <Code code={`npm i @capgo/capacitor-updater`} lang="bash" />
 
+   <Aside type="note" title="Installation pour les anciennes versions de Capacitor">
+   La commande ci-dessus installe la dernière version (v8.x) pour Capacitor 8. Pour les anciennes versions de Capacitor, utilisez le tag npm approprié :
+
+   ```bash
+   # Capacitor 7
+   npm i @capgo/capacitor-updater@lts-v7
+
+   # Capacitor 6
+   npm i @capgo/capacitor-updater@lts-v6
+
+   # Capacitor 5
+   npm i @capgo/capacitor-updater@lts-v5
+   ```
+
+   Chaque version majeure du plugin correspond à la version majeure de Capacitor (v8 → Capacitor 8, v7 → Capacitor 7, v6 → Capacitor 6, v5 → Capacitor 5). Les versions mineures partagent le même ensemble de fonctionnalités sur toutes les versions majeures (par ex., 5.34.0, 6.34.0, 7.34.0 et 8.34.0 incluent les mêmes fonctionnalités).
+   </Aside>
+
 4. Configure the plugin in your `capacitor.config` <Code code={`{\n  "plugins": {\n    CapacitorUpdater: {\n      "appId": "Your appID",\n      "autoUpdate": true,\n      "version": "1.0.0"\n    }\n  }\n}`} lang="json" />
   [See all Option Disponible](/docs/plugin/Paramètres/). This Information will be infer if not provided.
 

src/content/docs/fr/getting-started/add-an-app.mdx

@@ -15,7 +15,17 @@ A Live Mise à jour Canal points to a specific JS Bundle Construction of your Ap
 When a Appareil checks for an Mise à jour, Capgo decides which Canal to use in this strict order (highest priority first):
 
 1. **Forced Appareil mapping (Tableau de bord)** – Manually pin a specific Appareil ID to a Canal. Use for urgent Débogage or controlled Test with a single real Utilisateur. This always wins.
-2. **Cloud override (per‑device) via `setChannel()` or Dashboard** – Created when your app calls `setChannel()` (often exposed in a QA/debug menu) or you change the device's channel in the dashboard. Use for QA users switching between feature / PR channels or to reproduce a user issue. Reinstalling the binary does not clear it; deleting the device entry does.
+2. **Cloud override (per‑device) via Dashboard or API** – Created when you change the device's channel in the dashboard or via API. Use for QA users switching between feature / PR channels or to reproduce a user issue. Reinstalling the binary does not clear it; deleting the device entry does.
+
+<Aside type="tip" title="Changement Instantané de Canal avec setChannel()">
+**À partir de la version du plugin 5.34.0, 6.34.0, 7.34.0, ou 8.0.0** (selon votre version majeure), `setChannel()` fonctionne différemment : il contacte le backend pour **valider** que le canal est autorisé (en vérifiant si l'auto-attribution est activée pour ce canal), puis stocke le canal **localement sur l'appareil** comme `defaultChannel`. Cela signifie que le nouveau canal prend effet **instantanément** pour la prochaine vérification de mise à jour—pas d'attente pour la réplication.
+
+Auparavant, `setChannel()` sauvegardait le remplacement du canal dans la base de données backend (comme les changements du Tableau de bord ou API). Les appareils devaient attendre la réplication backend (jusqu'à 2 minutes) avant que le nouveau canal soit reconnu. Le nouveau comportement ne lit que depuis le backend (pour la validation) et stocke localement, rendant les changements de canal instantanés.
+
+**Note de sécurité :** Même si un canal devient non autorisé après avoir été défini localement, le backend validera toujours le canal lors des vérifications de mise à jour, assurant le maintien de la sécurité.
+
+**Important :** Lorsque les changements de canal sont effectués via le Tableau de bord ou l'API, il y a toujours un délai de réplication pouvant aller jusqu'à 2 minutes. Pour un changement de canal instantané, utilisez `setChannel()` depuis le code de votre application—il valide avec le backend, puis définit le canal localement pour un effet immédiat.
+</Aside>
 3. **Capacitor config `defaultChannel` (test build default)** – If present in `capacitor.config.*` and no force/override exists, the app starts on this channel (e.g. `beta`, `qa`, `pr-123`). Intended for TestFlight / internal builds so testers land on a pre‑release channel automatically. Production builds typically leave this unset.
 4. **Cloud Default Canal (primary path ~99% of Utilisateurs)** – If you mark a default Canal in the Tableau de bord, all normal end‑Utilisateurs (no force, no override, no config defaultChannel) attach here. Change it to roll out or roll Retour instantly—no Nouveau binary. If you have platform-specific defaults (one iOS-only, one Android-only), each Appareil lands on the default matching its platform. Leaving the cloud default unset is allowed; in that case the Appareil must match on steps 1–3 to receive Mises à jour.