@tencent-rtc/mcp 1.4.6 → 1.6.0-beta.1

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-audience-list.md

@@ -12,12 +12,13 @@
 - **Room Management**: The host or administrator can remove (kick out) any regular viewer from the live room.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibilities & Description** |
-| --- | --- | --- |
-| `LiveUserInfo` | data class | Represents the basic information model of an audience member (user). It contains the user's unique identifier (`userID`), nickname (`userName`), and avatar URL (`avatarURL`). |
-| `LiveAudienceState` | data class | Represents the current state of the audience module. Its core property `audienceList` is a StateFlow that stores the real-time state of the audience list; `audienceCount` represents the real-time state of the current total number of viewers. |
-| `LiveAudienceListener` | abstract class | Represents real-time audience activity events. It includes `onAudienceJoined` (audience joins) and `onAudienceLeft` (audience leaves), used for incremental updates to the audience list. |
-| `LiveAudienceStore` | abstract class | This is the core management class for interacting with audience list functionality. Through it, you can obtain audience list snapshots, perform management operations, and subscribe to its `LiveAudienceListener` for real-time updates. |
+
+|**Core Concept**|**Type**|**Core Responsibilities & Description**|
+|---------|---------|---------|
+|`LiveUserInfo`|data class|Represents the basic information model of an audience member (user). It contains the user's unique identifier (`userID`), nickname (`userName`), and avatar URL (`avatarURL`).|
+|`LiveAudienceState`|data class|Represents the current state of the audience module. Its core property `audienceList` is a StateFlow that stores the real-time state of the audience list; `audienceCount` represents the real-time state of the current total number of viewers.|
+|`LiveAudienceListener`|abstract class|Represents real-time audience activity events. It includes `onAudienceJoined` (audience joins) and `onAudienceLeft` (audience leaves), used for incremental updates to the audience list.|
+|`LiveAudienceStore`|abstract class|This is the core management class for interacting with audience list functionality. Through it, you can obtain audience list snapshots, perform management operations, and subscribe to its `LiveAudienceListener` for real-time updates.|
 
 ## Implementation Guide
 
@@ -99,27 +100,29 @@ class AudienceManager {
         }
     }
 
-    /// Subscribe to events to handle real-time audience join/leave
-    private fun subscribeToAudienceEvents() {
-        audienceStore.addLiveAudienceListener(object : LiveAudienceListener() {
-            override fun onAudienceJoined(newAudience: LiveUserInfo) {
-                println("Audience ${newAudience.userName} joined the live room")
-                // Incremental update: add the new audience member to the end of the current list
-                val currentList = _audienceList.value.toMutableList()
-                if (!currentList.any { it.userID == newAudience.userID }) {
-                    currentList.add(newAudience)
-                    _audienceList.value = currentList
-                }
-            }
-
-            override fun onAudienceLeft(departedAudience: LiveUserInfo) {
-                println("Audience ${departedAudience.userName} left the live room")
-                // Incremental update: remove the departed audience member from the current list
-                val currentList = _audienceList.value.toMutableList()
-                currentList.removeAll { it.userID == departedAudience.userID }
+    private val liveAudienceListener = object : LiveAudienceListener() {
+        override fun onAudienceJoined(newAudience: LiveUserInfo) {
+            println("Audience ${newAudience.userName} joined the live room")
+            // Incremental update: add the new audience member to the end of the current list
+            val currentList = _audienceList.value.toMutableList()
+            if (!currentList.any { it.userID == newAudience.userID }) {
+                currentList.add(newAudience)
                 _audienceList.value = currentList
             }
-        })
+        }
+
+        override fun onAudienceLeft(departedAudience: LiveUserInfo) {
+            println("Audience ${departedAudience.userName} left the live room")
+            // Incremental update: remove the departed audience member from the current list
+            val currentList = _audienceList.value.toMutableList()
+            currentList.removeAll { it.userID == departedAudience.userID }
+            _audienceList.value = currentList
+        }
+    }
+
+    /// Subscribe to events to handle real-time audience join/leave
+    private fun subscribeToAudienceEvents() {
+        audienceStore.addLiveAudienceListener(liveAudienceListener)
     }
 }
 ```
@@ -207,27 +210,29 @@ class LiveRoomManager(
         setupWelcomeMessageFlow()
     }
 
+    private val liveAudienceListener = object : LiveAudienceListener() {
+        override fun onAudienceJoined(audience: LiveUserInfo) {
+            // 3. Create a local tip message
+            val welcomeTip = Barrage().apply {
+                liveID = liveId
+                messageType = BarrageType.TEXT
+                textContent = "Welcome ${audience.userName} to the live room."
+            }
+
+            // 4. Get an instance of BarrageStore (this will be the same instance due to internal mechanisms)
+            val barrageStore = BarrageStore.create(liveId)
+
+            // 5. Use BarrageStore's method to insert it into the barrage list
+            barrageStore.appendLocalTip(welcomeTip)
+        }
+    }
+
     private fun setupWelcomeMessageFlow() {
         // 1. Get an instance of LiveAudienceStore
         val audienceStore = LiveAudienceStore.create(liveId)
 
-        // 2. Get an instance of BarrageStore (this will be the same instance due to internal mechanisms)
-        val barrageStore = BarrageStore.create(liveId)
-
-        // 3. Subscribe to audience events
-        audienceStore.addLiveAudienceListener(object : LiveAudienceListener() {
-            override fun onAudienceJoined(audience: LiveUserInfo) {
-                // 4. Create a local tip message
-                val welcomeTip = Barrage().apply {
-                    liveID = liveId
-                    messageType = BarrageType.TEXT
-                    textContent = "Welcome ${audience.userName} to the live room!"
-                }
-
-                // 5. Use BarrageStore's method to insert it into the barrage list
-                barrageStore.appendLocalTip(welcomeTip)
-            }
-        })
+        // 2. Subscribe to audience events
+        audienceStore.addLiveAudienceListener(liveAudienceListener)
     }
 }
 ```
@@ -235,11 +240,12 @@ class LiveRoomManager(
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-audience-store/index.html) and its related classes, refer to the official API documentation included with the [AtomicX Core](https://tencent-rtc.github.io/TUIKit_Android/index.html) framework. The relevant Stores used in this document are as follows:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| LiveCoreView | Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
-| LiveAudienceStore | Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
-| BarrageStore | Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|LiveCoreView|Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)|
+|LiveAudienceStore|Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)|
+|BarrageStore|Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-audio-effect.md

@@ -12,14 +12,15 @@ By combining `AudioEffectStore` and DeviceStore, you can implement the following
 - **Reverb Effects**: Simulate different acoustic environments, such as KTV, metallic, deep, bright, and others.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibility & Description** |
-| --- | --- | --- |
-| `AudioChangerType` | `enum` | Enumerates available voice effects, such as "child", "man", etc. |
-| `AudioReverbType` | `enum` | Enumerates available reverb effects, such as "ktv", "hall", etc. |
-| `AudioEffectState` | `data` | Represents the current state of the audio effect module, typically used for UI rendering. Includes voice effect state, reverb state, ear monitoring enabled state, and ear monitor volume. |
-| `AudioEffectStore` | `abstract` | Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
-| `DeviceState` | `data` | Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status. |
-| `DeviceStore` | `abstract` | Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
+
+|**Core Concept**|**Type**|**Core Responsibility & Description**|
+|---------|---------|---------|
+|`AudioChangerType`|`enum`|Enumerates available voice effects, such as "child", "man", etc.|
+|`AudioReverbType`|`enum`|Enumerates available reverb effects, such as "ktv", "hall", etc.|
+|`AudioEffectState`|`data`|Represents the current state of the audio effect module, typically used for UI rendering. Includes voice effect state, reverb state, ear monitoring enabled state, and ear monitor volume.|
+|`AudioEffectStore`|`abstract`|Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.|
+|`DeviceState`|`data`|Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status.|
+|`DeviceStore`|`abstract`|Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.|
 
 ## Implementation
 
@@ -79,14 +80,14 @@ CoroutineScope(Dispatchers.Main).launch {
 ```
 
 #### setVoiceEarMonitorEnable Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `enable` | `Boolean` | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
+| <code>enable</code> | <code>Boolean</code> | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
 
 #### setVoiceEarMonitorVolume Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `Int` | Ear monitor volume.<br>- Range: [0, 150]<br>- Default: 100 |
+| <code>volume</code> | <code>Int</code> | Ear monitor volume.<br>- Range: [0, 150]<br>- Default: 100 |
 
 ### Step 4: Implement Microphone Volume Adjustment
 
@@ -117,9 +118,9 @@ CoroutineScope(Dispatchers.Main).launch {
 ```
 
 #### setCaptureVolume Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `Int` | Microphone (capture) volume.<br>- Range: [0, 150]<br>- Default: 100 |
+| <code>volume</code> | <code>Int</code> | Microphone (capture) volume.<br>- Range: [0, 150]<br>- Default: 100 |
 
 ### Step 5: Implement Voice Effects
 
@@ -138,9 +139,10 @@ audioEffectStore.setAudioChangerType(AudioChangerType.NONE)
 ```
 
 #### setAudioChangerType Parameters
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | `AudioChangerType` | Voice effect enum value. |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|`AudioChangerType`|Voice effect enum value.|
 
 ### Step 6: Implement Reverb Effects
 
@@ -157,9 +159,10 @@ audioEffectStore.setAudioReverbType(AudioReverbType.NONE)
 ```
 
 #### setAudioReverbType Parameters
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | `AudioReverbType` | Reverb effect enum value. |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|`AudioReverbType`|Reverb effect enum value.|
 
 ### Step 7: Reset Audio Effect Settings
 
@@ -186,10 +189,11 @@ Reset audio effect settings in the following scenarios:
 ## API Documentation
 
 For detailed information on all public interfaces and properties of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html), [DeviceStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html), and their related classes, refer to the official API documentation for the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework.
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| AudioEffectStore | Manage audio effects: configure and retrieve real-time audio effect status. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html) |
-| DeviceStore | Manage devices: control camera and microphone, and retrieve real-time device status. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|AudioEffectStore|Manage audio effects: configure and retrieve real-time audio effect status.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html)|
+|DeviceStore|Manage devices: control camera and microphone, and retrieve real-time device status.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-barrage.md

@@ -12,11 +12,12 @@ This document provides a comprehensive guide for iOS developers to quickly integ
 - Inserting system tips into the local message list (for example, "Welcome XX to the live room").
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibility & Description** |
-| --- | --- | --- |
-| [Barrage](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage/index.html) | data class | Represents a single barrage message. Contains sender info (sender), message content (textContent or data), and message type (messageType). |
-| [BarrageState](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-state/index.html) | data class | Represents the current state of the barrage module. The main property, messageList, is a StateFlow containing all barrage messages for the current live room, ordered chronologically. This serves as the UI data source. |
-| [BarrageStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html) | abstract class | The main manager for barrage features. Use it to send messages (sendTextMessage, sendCustomMessage) and subscribe to barrage message updates via its state property. |
+
+|**Core Concept**|**Type**|**Core Responsibility & Description**|
+|---------|---------|---------|
+|[Barrage](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage/index.html)|data class|Represents a single barrage message. Contains sender info (sender), message content (textContent or data), and message type (messageType).|
+|[BarrageState](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-state/index.html)|data class|Represents the current state of the barrage module. The main property, messageList, is a StateFlow containing all barrage messages for the current live room, ordered chronologically. This serves as the UI data source.|
+|[BarrageStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html)|abstract class|The main manager for barrage features. Use it to send messages (sendTextMessage, sendCustomMessage) and subscribe to barrage message updates via its state property.|
 
 ## Implementation
 
@@ -102,11 +103,12 @@ class BarrageManager(
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `text` | `String?` | The text content to send. |
-| `extensionInfo` | `Map<String, String>?` | Additional data for business customization. |
-| `completion` | `CompletionHandler?` | Callback invoked after sending, indicating success or failure. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`text`|`String?`|The text content to send.|
+|`extensionInfo`|`Map<String, String>?`|Additional data for business customization.|
+|`completion`|`CompletionHandler?`|Callback invoked after sending, indicating success or failure.|
 
 ### Step 4: Send Custom Barrage
 
@@ -153,11 +155,12 @@ class BarrageManager(
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| businessId | String | Unique business identifier (e.g., "live_gift"). Used by receivers to distinguish custom messages. |
-| data | String | Business data, typically a JSON string. |
-| completion | CompletionHandler? | Callback after sending. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|businessId|String|Unique business identifier (e.g., "live_gift"). Used by receivers to distinguish custom messages.|
+|data|String|Business data, typically a JSON string.|
+|completion|CompletionHandler?|Callback after sending.|
 
 ### Step 5: Insert Local Tip Messages
 
@@ -183,9 +186,10 @@ class BarrageManager(
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| message | Barrage | The message object to insert locally. The SDK appends this to messageList in BarrageState. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|message|Barrage|The message object to insert locally. The SDK appends this to messageList in BarrageState.|
 
 ### Step 6: Manage User Speaking Permissions (Mute and Unmute)
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-base-beauty.md

@@ -12,10 +12,10 @@
 - **State Monitoring:** Access real-time values of the currently applied beautification parameters.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibilities and Description** |
+| <strong>Core Concept</strong> | <strong>Type</strong> | <strong>Core Responsibilities and Description</strong> |
 | --- | --- | --- |
-| `BaseBeautyState` | `data` | - Represents the current state of the basic beautification module.<br>- Contains the currently applied intensity values for smoothing (smoothLevel), whitening (whitenessLevel), and rosy (ruddyLevel). |
-| `BaseBeautyStore` | `abstract` | - The core management class for interacting with basic beautification features.<br>-  Implemented as a global singleton (shared), responsible for setting, resetting, and synchronizing all basic beautification parameters. |
+| <code>BaseBeautyState</code> | <code>data</code> | - Represents the current state of the basic beautification module.<br>- Contains the currently applied intensity values for smoothing (smoothLevel), whitening (whitenessLevel), and rosy (ruddyLevel). |
+| <code>BaseBeautyStore</code> | <code>abstract</code> | - The core management class for interacting with basic beautification features.<br>-  Implemented as a global singleton (shared), responsible for setting, resetting, and synchronizing all basic beautification parameters. |
 
 ## Implementation
 
@@ -151,25 +151,27 @@ class BeautyManager() {
 ### Comparison: Basic vs. Advanced Beautification
 
 AtomicXCore also provides advanced beautification features for more demanding scenarios:
-| **Comparison Item** | **Basic Beautification (BaseBeautyStore)** | **Advanced Beautification (TEBeautyKit, requires additional integration)** |
-| --- | --- | --- |
-| Core Features | Smoothing, Whitening, Rosy | Includes all basic features, plus V-shape face, eye distance adjustment, nose slimming, 3D stickers, filters, makeup, and more |
-| Pricing | Free (included with AtomicXCore license) | Paid (requires separate Tencent Effects SDK license) |
-| Integration Method | Built-in by default; use BaseBeautyStore.shared() directly | Requires additional integration of the TEBeautyKit component and authentication |
-| Recommended Scenarios | Scenarios with basic beautification needs and rapid implementation requirements | Scenarios requiring advanced beautification, shaping, stickers, filters, and other premium features |
+
+|**Comparison Item**|**Basic Beautification (BaseBeautyStore)**|**Advanced Beautification (TEBeautyKit, requires additional integration)**|
+|---------|---------|---------|
+|Core Features|Smoothing, Whitening, Rosy|Includes all basic features, plus V-shape face, eye distance adjustment, nose slimming, 3D stickers, filters, makeup, and more|
+|Pricing|Free (included with AtomicXCore license)|Paid (requires separate Tencent Effects SDK license)|
+|Integration Method|Built-in by default; use BaseBeautyStore.shared() directly|Requires additional integration of the TEBeautyKit component and authentication|
+|Recommended Scenarios|Scenarios with basic beautification needs and rapid implementation requirements|Scenarios requiring advanced beautification, shaping, stickers, filters, and other premium features|
 
 ### Integrating Advanced Beautification
 
-To use advanced beautification features, refer to the [Advanced Beauty](https://trtc.io/document/60196?product=beautyar&menulabel=core%20sdk&platform=android) documentation. After integrating and authenticating TEBeautyKit, use its APIs to control all beautification effects.
+To use advanced beautification features, refer to the [Advanced Beauty](https://trtc.io/document/60196) documentation. After integrating and authenticating TEBeautyKit, use its APIs to control all beautification effects.
 
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [BaseBeautyStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-base-beauty-store/index.html) and related classes, see the official API documentation for the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Android/index.html) framework. The relevant stores referenced in this guide are:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| `LiveCoreView` | Core view component for displaying and interacting with live video streams. Handles video rendering and view widgets, supports host streaming, audience co-hosting, host connections, and more. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
-| `BaseBeautyStore` | Basic beautification: adjust smoothing, whitening, and rosy (levels 0–9), reset status, synchronize effect parameters. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-base-beauty-store/index.html) |
-| `DeviceStore` | Audio and video device control: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, real-time device status monitoring. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|`LiveCoreView`|Core view component for displaying and interacting with live video streams. Handles video rendering and view widgets, supports host streaming, audience co-hosting, host connections, and more.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)|
+|`BaseBeautyStore`|Basic beautification: adjust smoothing, whitening, and rosy (levels 0–9), reset status, synchronize effect parameters.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-base-beauty-store/index.html)|
+|`DeviceStore`|Audio and video device control: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, real-time device status monitoring.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-co-guest-interaction.md

@@ -8,11 +8,11 @@
 - **Host Invites to Join**: The host can invite any audience member in the live room to co-host.
 
 ## Core Concepts
-| **Core Concept** | **Core Responsibilities** | **Key APIs / Properties** |
+| <strong>Core Concept</strong> | <strong>Core Responsibilities</strong> | <strong>Key APIs / Properties</strong> |
 | --- | --- | --- |
-| `CoGuestStore` | Manages the entire signaling workflow for viewer-host interaction (Apply, Invite, Accept, Reject, Disconnect) and maintains real-time state of related user lists. | - `coGuestState`: A read-only StateFlowcontaining `connected` (current co-guests), `applicants` (pending applications), and `invitees` (pending invitations).<br>- `applyForSeat()`: Viewer applies to become a co-guest.<br>- `inviteToSeat()`: Host invites a viewer to take a seat.<br>- `acceptApplication()`: Host accepts a link mic application.<br>- `disconnect():` Terminates the connection. |
-| `HostListener` | Used by the UI layer to respond to events such as "Received viewer application" or "Viewer accepted invitation". | - `onGuestApplicationReceived()`: Triggered when a viewer applies for a seat.<br>- `onHostInvitationResponded()`: Triggered when a viewer responds to an invitation. |
-| `GuestListener` | Used by the UI layer to respond to events such as "Received host invitation", "Application approved", or "Kicked off seat". | - `onHostInvitationReceived()`: Triggered when the host sends an invitation.<br>- `onGuestApplicationResponded()`: Triggered when the host processes an application (Accept/Reject).<br>- `onKickedOffSeat()`: Triggered when kicked off the seat by the host. |
+| <code>CoGuestStore</code> | Manages the entire signaling workflow for viewer-host interaction (Apply, Invite, Accept, Reject, Disconnect) and maintains real-time state of related user lists. | - <code>coGuestState</code>: A read-only StateFlow containing <code>connected</code> (current co-guests), <code>applicants</code> (pending applications), and <code>invitees</code> (pending invitations).<br>- <code>applyForSeat()</code>: Viewer applies to become a co-guest.<br>- <code>inviteToSeat()</code>: Host invites a viewer to take a seat.<br>- <code>acceptApplication()</code>: Host accepts a link mic application.<br>- <code>disconnect():</code> Terminates the connection. |
+| <code>HostListener</code> | Used by the UI layer to respond to events such as "Received viewer application" or "Viewer accepted invitation". | - <code>onGuestApplicationReceived()</code>: Triggered when a viewer applies for a seat.<br>- <code>onHostInvitationResponded()</code>: Triggered when a viewer responds to an invitation. |
+| <code>GuestListener</code> | Used by the UI layer to respond to events such as "Received host invitation", "Application approved", or "Kicked off seat". | - <code>onHostInvitationReceived()</code>: Triggered when the host sends an invitation.<br>- <code>onGuestApplicationResponded()</code>: Triggered when the host processes an application (Accept/Reject).<br>- <code>onKickedOffSeat()</code>: Triggered when kicked off the seat by the host. |
 
 ## Implementation
 
@@ -335,7 +335,7 @@ Use the "slot" feature provided by the `VideoViewAdapter` interface to add custo
 > **Note：**
 >
 
-> You can also refer to the [widgets](https://github.com/Tencent-RTC/TUIKit_Android/tree/main/live/tuilivekit/src/main/java/com/trtc/uikit/livekit/features/anchorboardcast/view/coguest/widgets) directory in the open-source TUILiveKit project for a complete implementation.
+> You can also refer to the [widgets](https://github.com/Tencent-RTC/TUIKit_Android/tree/main/live/tuilivekit/src/main/java/com/trtc/uikit/livekit/features/audienceview/view/coguest/widgets) directory in the open-source TUILiveKit project for a complete implementation.
 >
 
 - **Step 1**: Create the foreground view `CustomSeatView` to display user info above the video stream.
@@ -455,24 +455,25 @@ Use the "slot" feature provided by the `VideoViewAdapter` interface to add custo
    ```
 
 #### Parameter Description:
-| **Parameter** | **Type** | **Description** |
+| <strong>Parameter</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `seatInfo` | `SeatFullInfo?` | Seat information object, containing detailed information about the user on the seat |
-| `seatInfo.userId` | `String` | ID of the user on the seat |
-| `seatInfo.userName` | `String` | Nickname of the user on the seat |
-| `seatInfo.userAvatar` | `String` | Avatar URL of the user on the seat |
-| `seatInfo.userMicrophoneStatus` | `DeviceStatus` | Microphone status of the user on the seat |
-| `seatInfo.userCameraStatus` | `DeviceStatus` | Camera status of the user on the seat |
-| `viewLayer` | `ViewLayer` | View layer enum:<br>- `FOREGROUND`: Foreground widget view, always displayed on top of the video<br>- `BACKGROUND`: Background widget view, displayed below the foreground view, only shown when the user has no video stream (e.g., camera is off); typically used for the user's avatar or a placeholder image |
+| <code>seatInfo</code> | <code>SeatFullInfo?</code> | Seat information object, containing detailed information about the user on the seat |
+| <code>seatInfo.userId</code> | <code>String</code> | ID of the user on the seat |
+| <code>seatInfo.userName</code> | <code>String</code> | Nickname of the user on the seat |
+| <code>seatInfo.userAvatar</code> | <code>String</code> | Avatar URL of the user on the seat |
+| <code>seatInfo.userMicrophoneStatus</code> | <code>DeviceStatus</code> | Microphone status of the user on the seat |
+| <code>seatInfo.userCameraStatus</code> | <code>DeviceStatus</code> | Camera status of the user on the seat |
+| <code>viewLayer</code> | <code>ViewLayer</code> | View layer enum:<br>- <code>FOREGROUND</code>: Foreground widget view, always displayed on top of the video<br>- <code>BACKGROUND</code>: Background widget view, displayed below the foreground view, only shown when the user has no video stream (e.g., camera is off); typically used for the user's avatar or a placeholder image |
 
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-guest-store/index.html) and related classes, refer to the official API documentation included with the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Android/index.html) framework. The relevant stores used in this guide include:
-| **Store/Component** | **Function Description** | **API Documentation** |
-| --- | --- | --- |
-| LiveCoreView | Core view component for live video stream display and interaction. Handles video rendering and widget management, supporting host streaming, audience co-hosting, host connections, and more. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
-| DeviceStore | Audio and video device control: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, real-time device status monitoring. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html) |
-| CoGuestStore | Audience co-hosting management: request/invite/accept/reject co-hosting, permission control (microphone/camera), state synchronization. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-guest-store/index.html) |
+
+|**Store/Component**|**Function Description**|**API Documentation**|
+|---------|---------|---------|
+|LiveCoreView|Core view component for live video stream display and interaction. Handles video rendering and widget management, supporting host streaming, audience co-hosting, host connections, and more.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)|
+|DeviceStore|Audio and video device control: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, real-time device status monitoring.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html)|
+|CoGuestStore|Audience co-hosting management: request/invite/accept/reject co-hosting, permission control (microphone/camera), state synchronization.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-guest-store/index.html)|
 
 ## FAQs