@tencent-rtc/mcp 1.6.4 → 1.6.5

package/resource/knowledge/push/integration/uni-app.md

@@ -29,7 +29,7 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 3. Huawei, HONOR, vivo, FCM.
 
 【FCM】
-1. Configure `com.google.gms.google-services` to `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `project.plugins`, as shown below:
+1. Configure `com.google.gms.google-services` to `uni_modules/TencentCloud-Push/utssdk/app-android/config.json`  in `project.plugins`, as shown below:
 
 ``` json
 "project": {
@@ -45,12 +45,12 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 }
 ```
 
-2. Configure the `google-services.json` file to the `nativeResources/android/` directory (Note! Do not configure it to the `nativeResources/android/assets` directory). As shown in the figure:
+2. Configure the `google-services.json` file to the `nativeResources/android/` directory (Note! Do not configure it to the `nativeResources/android/assets`  directory). As shown in the figure:
 
 【Huawei】
 
 【HONOR】
-3. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:honor:8.3.6498"`.
+1. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:honor:8.3.6498"`.
 
 ``` bash
 {
@@ -61,9 +61,9 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
      ]
 }
 ```
-4. Configure the `mcs-services.json` file to the `nativeResources/android` directory (for details on obtaining this file, see Vendor Configuration > uniapp > Honor > Step 3.2: Enter Application Details, Bind Application Package Name, Download mcs-services.json File).
+2. Configure the `mcs-services.json` file to the `nativeResources/android` directory (for details on obtaining this file, see Vendor Configuration > uniapp > Honor > Step 3.2: Enter Application Details, Bind Application Package Name, Download mcs-services.json File).
 
-5. Configure `appID` to `nativeResources/android/manifestPlaceholders.json` in `"HONOR_APPID"`.
+3. Configure `appID` to `nativeResources/android/manifestPlaceholders.json` in `"HONOR_APPID"`.
 
 ``` bash
 {
@@ -72,7 +72,7 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 ```
 
 【vivo】
-6. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:vivo:8.3.6498"`.
+1. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:vivo:8.3.6498"`.
 
 ``` bash
 {
@@ -83,7 +83,7 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
      ]
 }
 ```
-7. Configure `appID` and `appKey` to `nativeResources/android/manifestPlaceholders.json` in `VIVO_APPKEY` and `VIVO_APPID`.
+2. Configure `appID` and `appKey` to `nativeResources/android/manifestPlaceholders.json` in `VIVO_APPKEY` and `VIVO_APPID`.
 
 ``` bash
 {

package/resource/knowledge/push/integration/unity.md

@@ -109,11 +109,10 @@ android {
 
 Integrate the plugin and json configuration file by vendor method.
 
-> **Note:**
->
-
-> The following Honor adaptation requires configuration for version 7.7.5283 and above.
->
+   > **Note:**
+   >
+   > The following Honor adaptation requires configuration for version 7.7.5283 and above.
+   >
 
   1. Download the configuration file and add it to the project root directory `Assets/Plugins/Android/JsonConfigs`. `Create the directory manually if it does not exist`.
 
@@ -248,6 +247,7 @@ If you need to customize the parsing of received remote push, you can implement
 >
 > 1. Register the callback timing in the program entry function.
 > 2. Configure the console to click subsequent actions with the following configuration, select **open specified in-app page,** do not modify and use default values.
+>
 
 ``` csharp
 PushListener listener = new PushListener(onRecvPushMessage: (message) => {
@@ -267,7 +267,6 @@ Upon success of calling the `PushManager.RegisterPush` method, you can receive o
 
 > **Note:**
 >
-
 > Note: If you have already integrated the Chat product and call this API after successful log-in, set the appKey parameter to null. Otherwise, the Chat account will be taken offline.
 >
 
@@ -301,7 +300,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
 >
-
 > Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 version interface with no support for reachability and Receipt Click. Please regenerate the certificate ID.
 >
 
@@ -347,7 +345,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
 >
-
 > Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
 >
 
@@ -378,11 +375,11 @@ iOS Push Notification Reach Statistics Configuration, see:
 @end
 ```
 
-> **Note:**
->
-> 1. Report push reach data. The mutable-content switch requires enabling to support the iOS 10 Extension function.
-
-> 2. Data details can be viewed on the push data page. The push data page is only available after [purchasing the push plugin](https://console.cloud.tencent.com/im/plugin/TIMPush).
+      > **Note:**
+      >
+      > 1. Report push reach data. The mutable-content switch requires enabling to support the iOS 10 Extension function.
+      >
+      > 2. Data details can be viewed on the push data page. The push data page is only available after [purchasing the push plugin](https://console.cloud.tencent.com/im/plugin/TIMPush).
 
 The rest support manufacturers with no need to configure. FCM does not currently support the push notification statistics feature.
 

package/resource/knowledge/push/integration/unreal-engine.md

@@ -100,7 +100,6 @@ Integrate the corresponding plugin and json configuration file using the vendor
 
 > **Note:**
 >
-
 > Note: The following Honor adaptation requires configuration for version 7.7.5283 and above.
 >
 
@@ -167,7 +166,7 @@ If you need custom parsing for received remote push, you can implement it by the
 >
 > 1. Register callback timing is recommended to be placed in the program entry function.
 > 2. Configure the console and click subsequent actions with the following configuration. Select **open specified in-app page**. Do not modify and use default values.
-
+>
 >
 >
 
@@ -292,7 +291,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
 >
-
 > Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 API. Reach and Receipt Click are unsupported. Please regenerate and update the certificate ID.
 >
 
@@ -338,7 +336,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
 >
-
 > Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
 >
 
@@ -371,11 +368,11 @@ China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 @end
 ```
 
-> **Note:**
->
-> 5. Report push reach data. The mutable-content switch needs to be enabled to support the Extension function for iOS 10.
-
-> 6. Data details can be viewed on the push data page. The push data page is only available after [purchasing the push plugin](https://console.cloud.tencent.com/im/plugin/TIMPush).
+      > **Note:**
+      >
+      > 1. Report push reach data. The mutable-content switch needs to be enabled to support the Extension function for iOS 10.
+      >
+      > 2. Data details can be viewed on the push data page. The push data page is only available after [purchasing the push plugin](https://console.cloud.tencent.com/im/plugin/TIMPush).
 
 Other manufacturers support it with no need to configure. FCM does not currently support the push notification statistics feature.
 

package/resource/knowledge/push/overview/prepare.md

@@ -22,11 +22,11 @@ Send real-time messages to all users or targeted segments. Push delivers message
 
 ##### Chat Message Push
 
-Chat messages are delivered to users' devices as notification bar alerts. Tapping the notification takes users directly to the relevant conversation, automatically updating conversations, messages, and unread counts. Messages are received in real time while online, and offline users will receive push notifications upon their next login, ensuring no chat message is missed. **(Requires integration with the **[**Chat SDK**](https://trtc.io/sdkDownload)**)**
+Chat messages are delivered to users' devices as notification bar alerts. Tapping the notification takes users directly to the relevant conversation, automatically updating conversations, messages, and unread counts. Messages are received in real time while online, and offline users will receive push notifications upon their next login, ensuring no chat message is missed. **(Requires integration with the** [**Chat SDK**](https://trtc.io/sdkDownload)**)**
 
 ##### Audio and Video Call Invitations
 
-Push supports both notification bar and VoIP push for audio and video call invitations between users. Regardless of whether the app is running in the background, closed, or killed, call invitations are delivered instantly via the offline push channel, ensuring calls are never missed or interrupted. **(Requires integration with the **[**Audio/Video Call SDK**](https://trtc.io/sdkDownload)**)**
+Push supports both notification bar and VoIP push for audio and video call invitations between users. Regardless of whether the app is running in the background, closed, or killed, call invitations are delivered instantly via the offline push channel, ensuring calls are never missed or interrupted. **(Requires integration with the** [**Audio/Video Call SDK**](https://trtc.io/sdkDownload)**)**
 
 ## Product Advantages
 

package/resource/knowledge/roomkit/core-sdk/android/call-user-to-room.md

@@ -10,9 +10,9 @@ RoomStore is the dedicated module for room management in AtomicXCore, offering s
 Core concepts in `RoomStore` are summarized in the table below:
 | Core Concept | Type | Core Responsibility & Description |
 | --- | --- | --- |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-call-status/index.html">RoomCallStatus</a> | <code>enum class</code> | Indicates the status of an in-meeting call:<br>- <code>NONE</code> (default)<br>- <code>CALLING</code> (call in progress)<br>- <code>TIMEOUT</code> (call timed out)<br>- <code>REJECTED</code> (call rejected) |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-call-result/index.html">RoomCallResult</a> | <code>enum class</code> | Represents the result of an in-meeting call:<br>- <code>SUCCESS</code> (call succeeded)<br>- <code>ALREADY_IN_CALLING</code> (already in a call)<br>- <code>ALREADY_IN_ROOM</code> (already in the room) |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-call-rejection-reason/index.html">CallRejectionReason</a> | <code>enum class</code> | Specifies the reason for call rejection:<br>- <code>REJECTED</code> (actively rejected when invited)<br>- <code>IN_OTHER_ROOM</code> (user is in another room) |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-call-status/index.html">RoomCallStatus</a> | <code>enum class</code> | Indicates the status of an in-meeting call:<br>-  <code>NONE</code> (default)<br>-  <code>CALLING</code> (call in progress)<br>-  <code>TIMEOUT</code> (call timed out)<br>-  <code>REJECTED</code> (call rejected) |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-call-result/index.html">RoomCallResult</a> | <code>enum class</code> | Represents the result of an in-meeting call:<br>-  <code>SUCCESS</code> (call succeeded)<br>-  <code>ALREADY_IN_CALLING</code> (already in a call)<br>-  <code>ALREADY_IN_ROOM</code> (already in the room) |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-call-rejection-reason/index.html">CallRejectionReason</a> | <code>enum class</code> | Specifies the reason for call rejection:<br>-  <code>REJECTED</code> (actively rejected when invited)<br>-  <code>IN_OTHER_ROOM</code> (user is in another room) |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-call/index.html">RoomCall</a> | <code>data class</code> | Core data structure for in-meeting call operations. Stores caller info, callee info, and current call status. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-listener/index.html">RoomListener</a> | <code>abstract class</code> | Handles real-time events for room activity, including in-meeting call events. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-store/index.html">RoomStore</a> | <code>abstract class</code> | Manages the complete room lifecycle. Provides APIs to initiate and respond to in-meeting calls, fetch call lists, and subscribe to RoomListener for real-time call events. |

package/resource/knowledge/roomkit/core-sdk/android/capability-matrix.md

@@ -0,0 +1,46 @@
+# AtomicX Core Android capability matrix
+
+This document defines the capability boundary for `knowledge/roomkit/core-sdk/android/` in the MCP knowledge base.
+
+**Decision rule**: if an Android core document exists in this directory, the capability is treated as **supported**; if the document does not exist, it is treated as **unsupported** for Android Core.
+
+## Current coverage
+
+Supported capability documents:
+- `room-state.md`
+- `room-participant-state.md`
+- `call-user-to-room.md`
+- `schedule-room.md`
+
+Currently missing capability documents:
+- `device-detection.md`
+- `device-state.md`
+- `free-beauty-panel.md`
+- `room-chat.md`
+- `room-view.md`
+- `screen-share.md`
+- `virtual-background.md`
+
+## Capability matrix
+
+| Capability | Vue Core | Android Core | Alternative path |
+| --- | --- | --- | --- |
+| Room state management `room-state` | ✅ | ✅ | Use `room-state.md` directly |
+| Participant state management `room-participant-state` | ✅ | ✅ | Use `room-participant-state.md` directly |
+| In-room calling `call-user-to-room` | ✅ | ✅ | Use `call-user-to-room.md` directly |
+| Scheduled meeting `schedule-room` | ✅ | ✅ | Use `schedule-room.md` directly |
+| In-room chat `room-chat` | ✅ | ❌ Unsupported | Build with Chat / Chat Android SDK |
+| Screen share `screen-share` | ✅ | ❌ Unsupported | Prefer Android preset UI path |
+| Virtual background `virtual-background` | ✅ | ❌ Unsupported | Prefer Android preset UI path |
+| Room main view `room-view` | ✅ | ❌ Unsupported | If you need full room page, use `RoomMainView` preset UI |
+| Device detection `device-detection` | ✅ | ❌ Unsupported | No official Android Core atomic path currently |
+| Device state management `device-state` | ✅ | ❌ Unsupported | No official Android Core atomic path currently |
+| Basic beauty panel `free-beauty-panel` | ✅ | ❌ Unsupported | No official Android Core atomic path currently |
+
+## Answering policy
+
+When users ask whether Android AtomicX Core supports one of the ❌ capabilities above:
+1. Answer **unsupported** first.
+2. Explain this is an explicit **Android Core capability boundary** in current docs, not “example not found”.
+3. Do not output fabricated Android Core API integration steps.
+4. Only provide alternatives that are currently documented on Android (for example `RoomMainView` preset UI). If no documented alternative exists, say so clearly.

package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md

@@ -19,7 +19,7 @@ The core concepts of `RoomParticipantStore` is summarized as follows:
 | Core Concept | Type | Core Responsibilities & Description |
 | --- | --- | --- |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant/index.html">RoomParticipant</a> | <code>data class</code> | Represents the participant data model, encapsulating participant information and state management.<br>Main functions include managing participant basic information (user ID, user name, user avatar, in-room role) and managing device status (microphone, camera, screen sharing, message status). |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-state/index.html">RoomParticipantState</a> | <code>data class</code> | Represents the participant state management structure, responsible for maintaining participant-related state information in the room. Main properties:<br>- <code>participantList</code>: collection of all participant information in the current room.<br>- <code>participantListCursor</code>: snapshot for paginated participant list.<br>- <code>localParticipant</code>: current user's participant information in the room. |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-state/index.html">RoomParticipantState</a> | <code>data class</code> | Represents the participant state management structure, responsible for maintaining participant-related state information in the room. Main properties:<br>-  <code>participantList</code>: collection of all participant information in the current room.<br>-  <code>participantListCursor</code>: snapshot for paginated participant list.<br>-  <code>localParticipant</code>: current user's participant information in the room. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-listener/index.html">RoomParticipantListener</a> | <code>abstract class</code> | Handles real-time participant events in the room, grouped as join/exit events, role change events, and device control events. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-store/index.html">RoomParticipantStore</a> | <code>abstract class</code> | Core class for participant control. Functions include managing participant audio/video status, participant management operations, and subscribing to<br><code>RoomParticipantListener</code> for real-time events. |
 

package/resource/knowledge/roomkit/core-sdk/android/room-state.md

@@ -355,9 +355,9 @@ private fun subscribeCurrentRoomState() {
 
   - **Important**: In high-traffic situations (like a "live comments storm"), if message rates exceed 40/sec, participant count change messages may be dropped to prioritize core messages (such as live comments).
 
-      **What does this mean for developers?**
+        **What does this mean for developers?**
 
-      `participantCount` is a highly accurate, near real-time estimate. In rare cases with extremely high concurrency, brief delays or data loss may occur. We recommend using it for UI display only—not for billing, statistics, or scenarios requiring absolute precision.
+        `participantCount` is a highly accurate, near real-time estimate. In rare cases with extremely high concurrency, brief delays or data loss may occur. We recommend using it for UI display only—not for billing, statistics, or scenarios requiring absolute precision.
 
 ## Contact Us
 

package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md

@@ -16,9 +16,9 @@
 Core concepts in `RoomStore` are summarized in the table below:
 | Core Concept | Type | Core Responsibilities & Description |
 | --- | --- | --- |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-state/index.html">RoomStatus</a> | <code>enum class</code> | Current status of the room:<br>- <code>SCHEDULED</code> (scheduled).<br>- <code>RUNNING</code> (in progress). |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-state/index.html">RoomStatus</a> | <code>enum class</code> | Current status of the room:<br>-  <code>SCHEDULED</code> (scheduled).<br>-  <code>RUNNING</code> (in progress). |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-schedule-room-options/index.html">ScheduleRoomOptions</a> | <code>data class</code> | The data structure for scheduled rooms, including start time, end time, participant list, and more. |
-| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-state/index.html">RoomState</a> | <code>data class</code> | Core data structure for room state management. Maintains user-related room state information.<br>Key properties:<br>- <code>scheduledRoomList</code>: List of all scheduled rooms under the current account.<br>- <code>scheduledRoomListCursor</code>: Pagination cursor for the scheduled room list. |
+| <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-state/index.html">RoomState</a> | <code>data class</code> | Core data structure for room state management. Maintains user-related room state information.<br>Key properties:<br>-  <code>scheduledRoomList</code>: List of all scheduled rooms under the current account.<br>-  <code>scheduledRoomListCursor</code>: Pagination cursor for the scheduled room list. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-listener/index.html">RoomListener</a> | <code>abstract class</code> | Handles real-time events related to room activity, including scheduled room events. |
 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-store/index.html">RoomStore</a> | <code>abstract class</code> | The class for managing the entire room lifecycle. Use it to schedule rooms, retrieve scheduled room lists, and subscribe to <code>RoomListener</code> for real-time scheduled room events. |
 
@@ -77,7 +77,7 @@ Follow the Integration Overview to integrate the AtomicXCore SDK. Make sure you
    }
    ```
 
-   `scheduleRoom`** Method Parameters**
+   `scheduleRoom` **Method Parameters**
 
 | Parameter | Type | Required | Description |
 | --- | --- | --- | --- |
@@ -85,7 +85,7 @@ Follow the Integration Overview to integrate the AtomicXCore SDK. Make sure you
 | <code>options</code> | <code>ScheduleRoomOptions</code> | Yes | Room configuration object. See ScheduleRoomOptions Struct Details. |
 | <code>completion</code> | <code>CompletionHandler</code> | No | Callback for operation completion. Returns result or error code/message if scheduling fails. |
 
-`ScheduleRoomOptions`** Struct Details**
+   `ScheduleRoomOptions` **Struct Details**
 
 | Parameter | Type | Required | Description |
 | --- | --- | --- | --- |
@@ -158,7 +158,7 @@ fun updateScheduledRoom() {
 }
 ```
 
-`updateScheduledRoom`** Parameters**
+`updateScheduledRoom` **Parameters**
 | Parameter | Type | Required | Description |
 | --- | --- | --- | --- |
 | <code>roomID</code> | <code>String</code> | Yes | - Unique string identifier for the room.<br>- Length: 0–48 bytes.<br>- Use only numbers, English letters (case sensitive), underscores (_), and hyphens (-). Avoid spaces and Chinese characters. |
@@ -166,7 +166,7 @@ fun updateScheduledRoom() {
 | <code>modifyFlagList</code> | <code>List<ScheduleRoomOptions.ModifyFlag></code> | Yes | Flags specifying which room properties to update. Can update room name, start time, and end time. See <code>ModifyFlag</code> documentation. |
 | <code>completion</code> | <code>CompletionHandler</code> | No | Callback for completion. Returns result or error code/message if update fails. |
 
-`ScheduleRoomOptions.ModifyFlag`** Details**
+`ScheduleRoomOptions.ModifyFlag` **Details**
 | Parameter | Type | Description |
 | --- | --- | --- |
 | <code>ROOM_NAME</code> | <code>enum</code> | - Use this flag when updating the scheduled room name.<br>- You must also set the <code>roomName</code> field in <code>ScheduleRoomOptions</code>. |

package/resource/knowledge/roomkit/core-sdk/android/unsupported-features.md

@@ -0,0 +1,79 @@
+# AtomicX Core Android unsupported features
+
+This document summarizes features currently **unsupported** in `knowledge/roomkit/core-sdk/android/`.
+
+## Usage policy
+
+- If this document is retrieved, the answer should focus on **capability boundary**, not implementation steps.
+- For alternatives, only reference capabilities that are already documented for Android.
+
+## In-room chat / Room Chat / In-room IM Chat
+
+**Unsupported.** Android Core currently has no `room-chat.md`.
+
+- Do not reuse `MessageList`, `MessageInput`, `MessageStore`, or conversation bootstrap flow from other platforms.
+- Do not treat preset `RoomMainView` capability as Android Core atomic capability.
+
+**Alternative path**:
+1. Build chat UI and message flow with Chat / IM Android SDK.
+2. See `knowledge/chat/urls/sdk/android.md` for Android message API entries.
+
+## Screen share / Screen Sharing
+
+**Unsupported.** Android Core currently has no `screen-share.md`.
+
+- Do not provide Android Core `startScreenShare`-style steps.
+- Do not reuse screen-share flow from other platforms.
+
+**Alternative path**:
+1. Prefer preset room main page solution.
+2. No documented Android Core atomic alternative currently.
+
+## Virtual background
+
+**Unsupported.** Android Core currently has no `virtual-background.md`.
+
+- Do not output Android Core virtual-background initialization / resource-path / state-management steps.
+- Do not reuse panel hooks from other platforms.
+
+**Alternative path**:
+1. Prefer preset UI path.
+2. No Android Core atomic integration path currently.
+
+## Room main view / video layout
+
+**Unsupported.** Android Core currently has no `room-view.md`.
+
+- Do not output Android Core `RoomView` component, layout template, or widget-slot steps.
+- Do not treat `RoomMainView` preset page as `RoomView` atomic capability.
+
+**Alternative path**:
+1. If the goal is a full meeting page, prefer `RoomMainView` preset UI.
+2. For atomic video-layout capability, no official Android Core doc currently.
+
+## Device detection
+
+**Unsupported.** Android Core currently has no `device-detection.md`.
+
+- Do not output Android Core pre-join camera/mic/speaker test steps.
+- Do not map test APIs from other platforms to Android Core.
+
+**Alternative path**: no documented Android Core solution currently.
+
+## Device state management
+
+**Unsupported.** Android Core currently has no `device-state.md`.
+
+- Do not output Android Core device-list switching, volume detection, mirror switching, or network panel steps.
+- Do not treat device-state logic from other platforms as Android Core capability.
+
+**Alternative path**: no documented Android Core solution currently.
+
+## Basic beauty panel
+
+**Unsupported.** Android Core currently has no `free-beauty-panel.md`.
+
+- Do not output Android Core beauty-panel UI / parameter steps.
+- Do not directly reuse beauty interaction from other platforms.
+
+**Alternative path**: no documented Android Core solution currently.

package/resource/knowledge/roomkit/core-sdk/flutter/capability-matrix.md

@@ -0,0 +1,46 @@
+# AtomicX Core Flutter capability matrix
+
+This document defines the capability boundary for `knowledge/roomkit/core-sdk/flutter/` in the MCP knowledge base.
+
+**Decision rule**: if a Flutter core document exists in this directory, the capability is treated as **supported**; if the document does not exist, it is treated as **unsupported** for Flutter Core.
+
+## Current coverage
+
+Supported capability documents:
+- `room-state.md`
+- `room-participant-state.md`
+- `call-user-to-room.md`
+- `schedule-room.md`
+
+Currently missing capability documents:
+- `device-detection.md`
+- `device-state.md`
+- `free-beauty-panel.md`
+- `room-chat.md`
+- `room-view.md`
+- `screen-share.md`
+- `virtual-background.md`
+
+## Capability matrix
+
+| Capability | Vue Core | Flutter Core | Alternative path |
+| --- | --- | --- | --- |
+| Room state management `room-state` | ✅ | ✅ | Use `room-state.md` directly |
+| Participant state management `room-participant-state` | ✅ | ✅ | Use `room-participant-state.md` directly |
+| In-room calling `call-user-to-room` | ✅ | ✅ | Use `call-user-to-room.md` directly |
+| Scheduled meeting `schedule-room` | ✅ | ✅ | Use `schedule-room.md` directly |
+| In-room chat `room-chat` | ✅ | ❌ Unsupported | Build with Chat / IM Flutter SDK |
+| Screen share `screen-share` | ✅ | ❌ Unsupported | Prefer Flutter preset UI path |
+| Virtual background `virtual-background` | ✅ | ❌ Unsupported | Prefer Flutter preset UI path |
+| Room main view `room-view` | ✅ | ❌ Unsupported | If you need full room page, use `RoomMainWidget` preset UI |
+| Device detection `device-detection` | ✅ | ❌ Unsupported | No official Flutter Core atomic path currently |
+| Device state management `device-state` | ✅ | ❌ Unsupported | No official Flutter Core atomic path currently |
+| Basic beauty panel `free-beauty-panel` | ✅ | ❌ Unsupported | No official Flutter Core atomic path currently |
+
+## Answering policy
+
+When users ask whether Flutter AtomicX Core supports one of the ❌ capabilities above:
+1. Answer **unsupported** first.
+2. Explain this is an explicit **Flutter Core capability boundary** in current docs, not “example not found”.
+3. Do not output fabricated Flutter Core API integration steps.
+4. Only provide alternatives that are currently documented on Flutter (for example `RoomMainWidget` preset UI). If no documented alternative exists, say so clearly.

package/resource/knowledge/roomkit/core-sdk/flutter/room-participant-state.md

@@ -22,7 +22,7 @@
 
 - **设置/撤销管理员**：房主可以设置参与者为管理员，同时也可撤销房间内的管理员。
 
-- **将参与者移****出****房间**：房主或者管理员可以将房间内任意一名参与者移出房间。
+- **将参与者移出房间**：房主或者管理员可以将房间内任意一名参与者移出房间。
 
 - **更新参与者信息**：房间内所有人都可以更新自己的参与者信息。
 

package/resource/knowledge/roomkit/core-sdk/flutter/unsupported-features.md

@@ -0,0 +1,79 @@
+# AtomicX Core Flutter unsupported features
+
+This document summarizes features currently **unsupported** in `knowledge/roomkit/core-sdk/flutter/`.
+
+## Usage policy
+
+- If this document is retrieved, the answer should focus on **capability boundary**, not implementation steps.
+- For alternatives, only reference capabilities that are already documented for Flutter.
+
+## In-room chat / Room Chat / In-room IM Chat
+
+**Unsupported.** Flutter Core currently has no `room-chat.md`.
+
+- Do not reuse `MessageList`, `MessageInput`, `MessageStore`, or conversation bootstrap flow from other platforms.
+- Do not treat preset `RoomMainWidget` capability as Flutter Core atomic capability.
+
+**Alternative path**:
+1. Build chat UI and message flow with Chat / IM Flutter SDK.
+2. See `knowledge/chat/urls/sdk/flutter.md` for Flutter message API entries.
+
+## Screen share / Screen Sharing
+
+**Unsupported.** Flutter Core currently has no `screen-share.md`.
+
+- Do not provide Flutter Core `startScreenShare`-style steps.
+- Do not reuse screen-share flow from other platforms.
+
+**Alternative path**:
+1. Prefer preset room main page solution.
+2. No documented Flutter Core atomic alternative currently.
+
+## Virtual background
+
+**Unsupported.** Flutter Core currently has no `virtual-background.md`.
+
+- Do not output Flutter Core virtual-background initialization / resource-path / state-management steps.
+- Do not reuse panel hooks from other platforms.
+
+**Alternative path**:
+1. Prefer preset UI path.
+2. No Flutter Core atomic integration path currently.
+
+## Room main view / video layout
+
+**Unsupported.** Flutter Core currently has no `room-view.md`.
+
+- Do not output Flutter Core `RoomView` component, layout template, or widget-slot steps.
+- Do not treat `RoomMainWidget` preset page as `RoomView` atomic capability.
+
+**Alternative path**:
+1. If the goal is a full meeting page, prefer `RoomMainWidget` preset UI.
+2. For atomic video-layout capability, no official Flutter Core doc currently.
+
+## Device detection
+
+**Unsupported.** Flutter Core currently has no `device-detection.md`.
+
+- Do not output Flutter Core pre-join camera/mic/speaker test steps.
+- Do not map test APIs from other platforms to Flutter Core.
+
+**Alternative path**: no documented Flutter Core solution currently.
+
+## Device state management
+
+**Unsupported.** Flutter Core currently has no `device-state.md`.
+
+- Do not output Flutter Core device-list switching, volume detection, mirror switching, or network panel steps.
+- Do not treat device-state logic from other platforms as Flutter Core capability.
+
+**Alternative path**: no documented Flutter Core solution currently.
+
+## Basic beauty panel
+
+**Unsupported.** Flutter Core currently has no `free-beauty-panel.md`.
+
+- Do not output Flutter Core beauty-panel UI / parameter steps.
+- Do not directly reuse beauty interaction from other platforms.
+
+**Alternative path**: no documented Flutter Core solution currently.

package/resource/knowledge/roomkit/core-sdk/ios/capability-matrix.md

@@ -0,0 +1,46 @@
+# AtomicX Core iOS capability matrix
+
+This document defines the capability boundary for `knowledge/roomkit/core-sdk/ios/` in the MCP knowledge base.
+
+**Decision rule**: if an iOS core document exists in this directory, the capability is treated as **supported**; if the document does not exist, it is treated as **unsupported** for iOS Core.
+
+## Current coverage
+
+Supported capability documents:
+- `room-state.md`
+- `room-participant-state.md`
+- `call-user-to-room.md`
+- `schedule-room.md`
+
+Currently missing capability documents:
+- `device-detection.md`
+- `device-state.md`
+- `free-beauty-panel.md`
+- `room-chat.md`
+- `room-view.md`
+- `screen-share.md`
+- `virtual-background.md`
+
+## Capability matrix
+
+| Capability | Vue Core | iOS Core | Alternative path |
+| --- | --- | --- | --- |
+| Room state management `room-state` | ✅ | ✅ | Use `room-state.md` directly |
+| Participant state management `room-participant-state` | ✅ | ✅ | Use `room-participant-state.md` directly |
+| In-room calling `call-user-to-room` | ✅ | ✅ | Use `call-user-to-room.md` directly |
+| Scheduled meeting `schedule-room` | ✅ | ✅ | Use `schedule-room.md` directly |
+| In-room chat `room-chat` | ✅ | ❌ Unsupported | Build with Chat / IM iOS SDK |
+| Screen share `screen-share` | ✅ | ❌ Unsupported | Prefer iOS preset UI path |
+| Virtual background `virtual-background` | ✅ | ❌ Unsupported | Prefer iOS preset UI path |
+| Room main view `room-view` | ✅ | ❌ Unsupported | If you need full room page, use `RoomMainView` preset UI |
+| Device detection `device-detection` | ✅ | ❌ Unsupported | No official iOS Core atomic path currently |
+| Device state management `device-state` | ✅ | ❌ Unsupported | No official iOS Core atomic path currently |
+| Basic beauty panel `free-beauty-panel` | ✅ | ❌ Unsupported | No official iOS Core atomic path currently |
+
+## Answering policy
+
+When users ask whether iOS AtomicX Core supports one of the ❌ capabilities above:
+1. Answer **unsupported** first.
+2. Explain this is an explicit **iOS Core capability boundary** in current docs, not “example not found”.
+3. Do not output fabricated iOS Core API integration steps.
+4. Only provide alternatives that are currently documented on iOS (for example `RoomMainView` preset UI). If no documented alternative exists, say so clearly.

package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md

@@ -19,7 +19,7 @@ The core concepts of `RoomParticipantStore` is summarized as follows:
 | Core Concept | Type | Core Responsibilities & Description |
 | --- | --- | --- |
 | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipant">RoomParticipant</a> | <code>struct</code> | Represents the participant data model, encapsulating participant information and state management.<br>Main functions include managing participant basic information (user ID, user name, user avatar, in-room role) and managing device status (microphone, camera, screen sharing, message status). |
-| <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstate">RoomParticipantState</a> | <code>struct</code> | Represents the participant state management structure, responsible for maintaining participant-related state information in the room. Main properties:<br>- <code>participantList</code>collection of all participant information in the current room.<br>- <code>participantListCursor</code>snapshot for paginated participant list.<br>- <code>localParticipant</code>current user's participant information in the room. |
+| <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstate">RoomParticipantState</a> | <code>struct</code> | Represents the participant state management structure, responsible for maintaining participant-related state information in the room. Main properties:<br>-  <code>participantList</code>collection of all participant information in the current room.<br>-  <code>participantListCursor</code>snapshot for paginated participant list.<br>-  <code>localParticipant</code>current user's participant information in the room. |
 | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantevent">RoomParticipantEvent</a> | <code>enum</code> | Represents real-time participant events in the room. Main categories: participant join/leave, role changes, device control events. |
 | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstore">RoomParticipantStore</a> | <code>class</code> | Core class for participant control. Features: manage participant audio/video status, perform participant operations, receive real-time events via <code>participantEventPublisher</code>. |