@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/chat/preset/react/features/conversation-list.md

@@ -4,10 +4,6 @@ The `ConversationList` component provides the main conversation list functionali
 
 This guide covers basic usage, component customization, flexible composition, and a complete list of component props.
 
-|**Conversation List**|**Conversation Actions**|**Conversation Search**|**Create Conversation**|
-|---------|---------|---------|---------|
-|||||
-
 ## Component Structure
 
 The `ConversationList` component includes the following:
@@ -46,17 +42,15 @@ Control the display of conversation search, conversation creation, and conversat
 ``` typescript
 <ConversationList enableSearch={false} />
 ```
+
 ``` typescript
 <ConversationList enableCreate={false} />
 ```
+
 ``` typescript
 <ConversationList enableActions={false} />
 ```
 
-|`enableSearch={false}`|`enableCreate={false}`|`enableActions={false}`|
-|---------|---------|---------|
-||||
-
 ### Data Filtering and Sorting
 
 The `ConversationList` component provides `filterConversation` and `sortConversation` properties to filter and sort conversation list data.
@@ -103,7 +97,7 @@ By using the `filter` and `sort` properties, you can efficiently filter and sort
 
 Use actionsConfig to control the basic functionality of `ConversationActions`.
 
-For additional customization, refer to the ConversationActions section.
+For additional customization.
 ``` typescript
 import { ConversationList } from '@tencentcloud/chat-uikit-react';
 import type { ConversationInfo } from '@tencentcloud/chat-uikit-react';
@@ -122,10 +116,6 @@ import type { ConversationInfo } from '@tencentcloud/chat-uikit-react';
 />
 ```
 
-|`enablePin: false`|`enableDelete: false`|`enableMute: false`|`customConversationActions`|
-|---------|---------|---------|---------|
-|||||
-
 ### Custom Placeholder
 
 Customize the list display for different states by passing `PlaceholderEmptyList`, `PlaceholderLoading`, and `PlaceholderLoadError`.
@@ -176,10 +166,6 @@ const CustomConversationListHeader = (props) => {
 
 The following example implements conversation grouping, categorizing by All, Unread, C2C, and Group. Clicking each group button applies a different filter.
 
-|**Before**|**After**|
-|---------|---------|
-|||
-
 ``` typescript
 import { useState } from 'react';
 import { ConversationList, UIKitProvider, ConversationInfo } from '@tencentcloud/chat-uikit-react';
@@ -216,6 +202,7 @@ const App = () => {
   );
 };
 ```
+
 ``` scss
 .conversation-group-wrapper {
   display: flex;
@@ -264,8 +251,6 @@ By default, it displays the current conversation list data (`filteredAndSortedCo
 
 #### Basic Customization
 
-The `List` component manages different UI states as shown below. State transitions are handled internally within `ConversationList`.
-
 You can also control the component state by passing custom `empty`, `loading`, or `error` props.
 ``` typescript
 import { ConversationList, ConversationListContent } from '@tencentcloud/chat-uikit-react';
@@ -277,27 +262,20 @@ const CustomConversationListContent = (props) => {
 <ConversationList  List={CustomConversationListContent} />
 ```
 
-|`default`|`empty={true}`|`loading={true}`|`error={true}`|
-|---------|---------|---------|---------|
-|||||
-
 ### Custom ConversationPreview
 
-For details, see the ConversationPreview section.
 ``` typescript
 <ConversationList ConversationPreview={CustomConversationPreview} />
 ```
 
 ### Custom ConversationActions
 
-For details, see the ConversationActions section.
 ``` typescript
   <ConversationList ConversationActions={CustomConversationActions} />
 ```
 
 ### Custom ConversationSearch
 
-For details, see the ConversationSearch section.
 ``` typescript
 <ConversationList ConversationSearch={CustomConversationSearch} />
 ```

package/resource/knowledge/chat/preset/react/features/conversation-preview.md

@@ -27,8 +27,6 @@ Meanwhile, you can also use the `onConversationSelect` function to define select
 
 ### Discord-Like Style
 
-Discord is a popular chat application, similar to Skype or Telegram. The message content in Discord is as shown below:
-
 By customizing the `ConversationPreview` layout, features, and style, we can quickly achieve a Discord-like effect.
 
 【React】
@@ -94,8 +92,4 @@ const App = () => {
 
 `ConversationListPreview` effect as follows after customization:
 
-|**Before Modification**|**Modified**|
-|---------|---------|
-|||
-
 ###

package/resource/knowledge/chat/preset/react/features/search.md

@@ -3,7 +3,6 @@
 Search is a complete search solution with a full set of components, including search bar, result display, advanced search, and other features. It is suitable for user, group, and message search in instant messaging, online meeting, and online education scenarios.
 
 > **Note:**
->
 > Note: This feature belongs to VAS. You need to purchase cloud search plugin. Please click [purchase](https://console.trtc.io/chat/plugin/TUICloudSearch).
 >
 

package/resource/knowledge/chat/preset/react/features/theme.md

@@ -44,7 +44,6 @@ export default App;
 Use the `useUIKit` Hook to access theme and language features.
 
 > **Note:**
->
 > Note: Since the theme feature is implemented using React Context, `useUIKit()` is unable to be called in the root component.
 >
 

package/resource/knowledge/chat/preset/vue/features/contact-list.md

@@ -167,6 +167,7 @@ const handleClick = () => {
 </style>
 
 ```
+
 ``` typescript
 <template>
   <ContactList :ContactItem="CustomContactItem" />
@@ -177,9 +178,6 @@ import { ContactList } from '@tencentcloud/chat-uikit-vue3';
 import CustomContactItem from './CustomContactItem.vue';
 </script>
 ```
-| Before | After |
-| --- | --- |
-|  |  |
 
 ### Custom Contact Detail Action Toggle
 
@@ -191,9 +189,6 @@ Use the `showActions` prop to control whether action buttons are shown on the co
   />
 </template>
 ```
-| Before | After |
-| --- | --- |
-|  |  |
 
 ### Custom Contact Detail Empty State
 
@@ -205,6 +200,7 @@ When no contact is selected, you can customize the empty state component.
   </div>
 </template>
 ```
+
 ``` typescript
 <template>
   <ContactInfo
@@ -259,6 +255,7 @@ defineProps<{
 </style>
 
 ```
+
 ``` typescript
 <template>
   <ContactInfo
@@ -272,6 +269,3 @@ import type { FriendInfoProps, GroupInfoProps } from '@tencentcloud/chat-uikit-v
 import CustomFriendInfo from './CustomFriendInfo.vue';
 </script>
 ```
-| Before | After |
-| --- | --- |
-|  |  |

package/resource/knowledge/chat/preset/vue/features/conversation-actions.md

@@ -131,9 +131,6 @@ Use `enablePin`, `enableDelete`, `enableMute`, and `enableMarkUnread` to control
   <ConversationActions :enableMarkUnread="false" :conversation="conversation" />
 </template>
 ```
-| <code>enablePin: false</code> | <code>enableDelete: false</code> | <code>enableMute: false</code> | enableMarkUnread="false" |
-| --- | --- | --- | --- |
-|  |  |  |  |
 
 ### Event handlers
 

package/resource/knowledge/chat/preset/vue/features/conversation-list.md

@@ -2,10 +2,6 @@
 
 The `ConversationList` component renders the conversation list and supports search, creation, pinning, deletion, and other conversation actions.
 
-|**Conversation List**|**Conversation Actions**|**Create Conversation**|
-|---------|---------|---------|
-||||
-
 ## Component Structure
 
 The `ConversationList` component includes the following:
@@ -43,15 +39,14 @@ Use `enableSearch`, `enableCreate`, and `enableActions` to control whether conve
 ``` typescript
 <ConversationList :enableSearch="false" />
 ```
+
 ``` typescript
 <ConversationList :enableCreate="false" />
 ```
+
 ``` typescript
 <ConversationList :enableActions="false" />
 ```
-| <code>enableSearch="false"</code> | <code>enableCreate="false"</code> | <code>enableActions="false"</code> |
-| --- | --- | --- |
-|  |  |  |
 
 ### Data Filtering and Sorting
 
@@ -126,9 +121,6 @@ import { UIKitProvider, ConversationList } from '@tencentcloud/chat-uikit-vue3';
 import type { ConversationInfo } from '@tencentcloud/chat-uikit-vue3';
 </script>
 ```
-| <code>enablePin: false</code> | <code>enableDelete: false</code> | <code>enableMute: false</code> | <code>customConversationActions</code> |
-| --- | --- | --- | --- |
-|  |  |  |  |
 
 ### Custom Placeholder
 
@@ -300,9 +292,6 @@ const handleFilterClick = (filterType: FilterType) => {
 </style>
 
 ```
-| **Before** | **After** |
-| --- | --- |
-|  |  |
 
 ## Props
 

package/resource/knowledge/chat/preset/vue/features/conversation-preview.md

@@ -27,6 +27,7 @@ interface Props {
 const props = withDefaults(defineProps<Props>(), {});
 </script>
 ```
+
 ``` typescript
 <template>
   <ConversationList :Preview="CustomConversationPreview" />
@@ -199,6 +200,7 @@ const handleSelectConversation = () => {
 </style>
 
 ```
+
 ``` typescript
 <template>
   <ConversationList :Preview="CustomConversationPreview" />
@@ -211,6 +213,3 @@ import CustomConversationPreview from './CustomConversationPreview.vue';
 ```
 
 After customizing `ConversationListPreview`, the result looks like this:
-| <strong>Before</strong> | <strong>After</strong> |
-| --- | --- |
-|  |  |

package/resource/knowledge/chat/preset/vue/features/conversation-search.md

@@ -15,6 +15,7 @@ const onSelectResult = (data: SearchResultItem, type: SearchType) => {
 };
 </script>
 ```
+
 ``` typescript
 <template>
   <UIKitProvider>

package/resource/knowledge/chat/preset/vue/features/search.md

@@ -2,9 +2,6 @@
 
 Search is a complete search solution with a full set of components, including search bar, result display, advanced search, and more. It is suitable for user, group, and message search in instant messaging, online meeting, and online education scenarios.
 
-> **Note:**
->
-
 > This feature is a value-added service. You need to purchase the cloud search plugin. Click [Purchase](https://cloud.tencent.com/document/product/269/120945).
 >
 
@@ -204,6 +201,7 @@ const handleClear = () => {
 </style>
 
 ```
+
 ``` typescript
 <template>
   <Search :SearchBar="CustomSearchBar" />
@@ -394,6 +392,7 @@ const handleResultClick = (item: SearchResultItemType) => {
 </style>
 
 ```
+
 ``` typescript
 <template>
   <Search :SearchResults="CustomSearchResults" />
@@ -548,6 +547,7 @@ const handleSearchTypeChange = (type: SearchType) => {
 </style>
 
 ```
+
 ``` typescript
 <template>
   <Search :SearchAdvanced="CustomSearchAdvanced" />
@@ -708,6 +708,7 @@ const formatTime = (timestamp: number) => {
 }
 </style>
 ```
+
 ``` typescript
 <template>
   <Search :SearchResultItem="CustomSearchItem" />

package/resource/knowledge/chat/urls/sdk/web.md

@@ -21,7 +21,7 @@
 | Text message (createTextMessage → sendMessage) | `https://trtc.io/document/47993` |
 | Group @ message (createTextAtMessage → sendMessage) | `https://trtc.io/document/47993` |
 | Image message (createImageMessage → sendMessage) | `https://trtc.io/document/47993` |
-| Voice message (createVoiceMessage → sendMessage) | `https://trtc.io/document/47993` |
+| Audio message (createAudioMessage → sendMessage) | `https://trtc.io/document/47993` |
 | Video message (createVideoMessage → sendMessage) | `https://trtc.io/document/47993` |
 | File message (createFileMessage → sendMessage) | `https://trtc.io/document/47993` |
 | Custom message (createCustomMessage → sendMessage) | `https://trtc.io/document/47993` |

package/resource/knowledge/livekit/best-practice/android/voice-room-anchor-start.md

@@ -0,0 +1,120 @@
+---
+title: "Voice Room Anchor Creates Room and Starts Streaming (Android)（语聊房 / 房主 / 开播 / createLive）"
+product: live
+frameworks: [android]
+scope: platform_specific
+tags: [voice room, anchor, start streaming, publish audio, createLive, openLocalMicrophone, muteMicrophone, unmuteMicrophone, LiveListStore, AudioSalon, keepOwnerOnSeat, seatMode, TakeSeatMode, Android]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Anchor Creates Room and Starts Streaming (Android)
+
+## 1. Key Takeaways
+
+- Voice room streaming flow: construct `LiveInfo` (with `liveID`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`), call `createLive` to create the room; on success, call `openLocalMicrophone` to capture and publish audio so other users in the room can hear the anchor.
+- `liveID` is required — it is the unique identifier of the live room.
+- Setting `keepOwnerOnSeat` to `true` makes the anchor automatically take a seat upon entering the room (taking a seat is a prerequisite for publishing audio — only seated users can publish audio streams in the room).
+- `seatTemplate` should be set to `SeatLayoutTemplate.AudioSalon(n)`, where n is the maximum seat count supported by the plan or a value less than it.
+- `seatMode` sets the seat-taking mode (e.g., `TakeSeatMode.APPLY` for apply-to-take-seat).
+- `muteMicrophone` pauses publishing local audio; `unmuteMicrophone` resumes publishing local audio.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `LiveInfo` | Room information | Contains `liveID`, `liveName`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`, etc. |
+| `liveID` | Room ID | Required parameter for `createLive` |
+| `liveName` | Room name | Display name of the room |
+| `seatTemplate` | Seat layout template | Use `SeatLayoutTemplate.AudioSalon(seatCount = n)` for voice rooms, where n ≤ max seats in plan |
+| `keepOwnerOnSeat` | Auto-seat the owner | Set to `true` so the anchor automatically takes a seat upon entering |
+| `seatMode` | Seat-taking mode | e.g., `TakeSeatMode.APPLY` for apply-to-take-seat |
+| `createLive(liveInfo, callback)` | Create room (start streaming) | Pass `LiveInfo` and `LiveInfoCompletionHandler` callback |
+| `openLocalMicrophone` | Capture and publish audio | Opens local microphone and publishes audio stream to the room |
+| `muteMicrophone` | Pause audio publishing | Pauses local audio stream while microphone remains open |
+| `unmuteMicrophone` | Resume audio publishing | Resumes local audio stream while microphone remains open |
+
+## 3. Mechanism & Sequence
+
+Construct `LiveInfo` (`liveID` required, `seatTemplate=AudioSalon(n)`, `keepOwnerOnSeat=true`, `seatMode` as needed) -> call `createLive` to create the room -> `onSuccess` callback fires, anchor is auto-seated -> call `openLocalMicrophone` to capture and publish audio -> other users in the room hear the anchor.
+
+Taking a seat is a prerequisite for streaming: `keepOwnerOnSeat=true` ensures the anchor takes a seat before publishing audio. `muteMicrophone` / `unmuteMicrophone` are used to pause/resume during streaming.
+
+## 4. Standard Usage
+
+1. Construct `LiveInfo`: set `liveID`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`.
+2. Implement `LiveInfoCompletionHandler` and call `createLive` to start streaming.
+3. In `onSuccess` callback, call `openLocalMicrophone` to capture and publish audio.
+4. Call `muteMicrophone` / `unmuteMicrophone` to pause/resume streaming as needed.
+
+```kotlin
+import android.util.Log
+import androidx.appcompat.app.AppCompatActivity
+import io.trtc.tuikit.atomicxcore.api.live.LiveInfo
+import io.trtc.tuikit.atomicxcore.api.live.LiveInfoCompletionHandler
+import io.trtc.tuikit.atomicxcore.api.live.TakeSeatMode
+
+class YourAnchorActivity : AppCompatActivity() {
+    // ... 其他代码 ...
+
+    private fun startLive() {
+        val liveInfo = LiveInfo().apply {
+            // 1. 设置房间基础信息
+            liveID = this@YourAnchorActivity.liveID
+            liveName = "test 语聊房"
+
+            // 2. 设置语聊房麦位模板，seatCount 传入所需麦位数（≤ 套餐最大麦位数）
+            seatTemplate = SeatLayoutTemplate.AudioSalon(seatCount = 9)
+
+            // 3. 主播开播后自动上麦（上麦后才能推音频流）
+            keepOwnerOnSeat = true
+
+            // 4. 设置上麦模式（例如申请上麦）
+            seatMode = TakeSeatMode.APPLY
+        }
+
+        // 5. 调用 createLive 创建房间（开播）
+        liveListStore.createLive(liveInfo, object : LiveInfoCompletionHandler {
+            override fun onFailure(code: Int, desc: String) {
+                Log.e("Live", "Response startLive onError: $desc")
+            }
+
+            override fun onSuccess(liveInfo: LiveInfo) {
+                Log.d("Live", "Response startLive onSuccess")
+                // 6. 房主创建成功后默认自动上麦，此时调用 openLocalMicrophone 采集并发布音频
+                liveSeatStore.openLocalMicrophone(null)
+            }
+        })
+    }
+}
+```
+
+## 5. Expected Results
+
+- `onSuccess` callback fires: room created successfully, anchor is auto-seated.
+- After `openLocalMicrophone`: other users in the room can hear the anchor.
+- After `muteMicrophone`: local audio publishing is paused; after `unmuteMicrophone`: publishing resumes.
+- If `keepOwnerOnSeat` is not set to `true`: the anchor is not auto-seated and cannot publish audio.
+- `onFailure(code, desc)` callback fires: streaming failed, `code` is the error code, `desc` is the error description.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Calling `openLocalMicrophone` without calling `createLive` first (cannot publish audio without creating a room).
+- Pitfall 2: Not setting `keepOwnerOnSeat` to `true`, so the anchor is not seated and audio publishing does not work.
+- Pitfall 3: Not setting `seatTemplate` or setting `seatCount` beyond the plan's maximum seat count.
+- Pitfall 4: Confusing `muteMicrophone` (pauses audio stream publishing) with closing the microphone (stops audio capture).
+- Pitfall 5: Reusing `liveID` (it must be globally unique; otherwise creation fails).
+- Pitfall 6: Confusing `onSuccess` and `onFailure` callbacks (both branches require defensive handling).
+
+## 7. Problem Definition (retrieval hint)
+
+An Android voice room anchor needs to create a room and start audio streaming in the correct order, understanding the call timing and parameter meanings of `createLive`, `openLocalMicrophone`, `muteMicrophone`, and `unmuteMicrophone`.
+
+## 8. Alternative Queries (retrieval recall)
+
+- How does an Android voice room anchor start streaming?
+- What is the call order of `createLive` and `openLocalMicrophone` on Android?
+- How does an Android anchor take a seat and publish audio?
+- What does the `keepOwnerOnSeat` parameter do?
+- How to set the `AudioSalon` template for `seatTemplate`?
+- What is the difference between `muteMicrophone` and `unmuteMicrophone` on Android?
+- How to publish audio after creating a voice room?

package/resource/knowledge/livekit/best-practice/common/admin-take-seat.md

@@ -0,0 +1,73 @@
+---
+title: "Voice Room Admin Seat-Taking and Seat Locking（语聊房 / 管理员 / 上麦 / takeSeat / lockSeat）"
+product: live
+frameworks: [android, ios, flutter]
+scope: platform_common
+tags: [voice room, admin, take seat, takeSeat, lockSeat, unlockSeat, seatMode, FREE, seat, host seat, owner approval, VoiceRoom]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Admin Seat-Taking and Seat Locking
+
+## 1. Key Takeaways
+
+- An admin takes a seat by calling `takeSeat` with the seat index. There is no need to call `applyForSeat` — admins are **not restricted by `seatMode=APPLY`** and do **not need** owner approval.
+- Admins are **not restricted by `lockSeat`** — they can directly `takeSeat` to any seat (including seat 0, the host seat).
+- Regular users can only call `takeSeat` when `seatMode` is `FREE`, and they **are restricted by `lockSeat`**.
+- The seat management API in `LiveSeatStore` is consistent across all three platforms (Android/iOS/Flutter).
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `takeSeat` | Take a seat | Pass the seat index; admins are not restricted by `seatMode`/`lockSeat`; regular users require `seatMode=FREE` and the seat must be unlocked |
+| `lockSeat` | Lock a seat | After locking, regular users cannot `takeSeat`; admins are unaffected |
+| `unlockSeat` | Unlock a seat | After unlocking, regular users can `takeSeat` again |
+| `seatMode` | Seat-taking mode | Regular users can only `takeSeat` in `FREE` mode |
+| `LiveSeatStore` | Seat management | Provides `takeSeat`/`leaveSeat`/`lockSeat`/`unlockSeat` operations |
+| Owner | Room owner | Can lock/unlock seats |
+
+## 3. Mechanism & Sequence
+
+### Admin Taking a Seat
+
+Admin calls `takeSeat(index)` to take a seat directly (passing the target seat index) -> not restricted by `seatMode` -> no owner approval needed -> not restricted by `lockSeat` -> seat taken successfully.
+
+## 4. Standard Usage
+
+1. **Admin takes a seat**: Call `takeSeat(index)` where `index` is the target seat number (e.g., seat 0 for the host seat). Not restricted by `seatMode`/`lockSeat`.
+2. **Regular user takes a seat**: Confirm `seatMode=FREE` and the target seat is unlocked, then call `takeSeat(index)`.
+3. **Lock a seat**: Admin/owner calls `lockSeat(index)`. After locking, regular users cannot `takeSeat`, but admins are unaffected.
+4. **Unlock then take seat**: First call `unlockSeat(index)` to unlock, then the regular user can `takeSeat(index)`.
+
+```javascript
+// API is consistent across all three platforms (Android Kotlin / iOS Swift / Flutter Dart)
+// 1. 管理员直接上麦（不受 seatMode / lockSeat 限制，无需房主同意）
+liveSeatStore.takeSeat(0);   // 上麦到 0 号主持麦位
+```
+
+## 5. Expected Results
+
+- Admin `takeSeat(index)` succeeds immediately, not restricted by `seatMode`, no owner approval needed.
+- After `lockSeat`, an admin can still `takeSeat` on the same seat (admins are not restricted by seat locking).
+- Regular users can only `takeSeat` successfully when `seatMode=FREE`; if the seat is locked, it fails — `unlockSeat` must be called first.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Admin calls `applyForSeat` to take a seat (admins should call `takeSeat` directly — no application needed).
+- Pitfall 2: Assuming admin `takeSeat` requires owner approval (admins are not subject to this restriction).
+- Pitfall 3: Assuming `lockSeat` prevents admins from calling `takeSeat` on the same seat (admins are not restricted by seat locking — only regular users are).
+
+## 7. Problem Definition (retrieval hint)
+
+How a voice room admin directly takes a specified seat (including seat 0, the host seat), whether admins are restricted by `seatMode`/`lockSeat`, and the `seatMode` and locking conditions for regular users to take a seat.
+
+## 8. Alternative Queries (retrieval recall)
+
+- How does a voice room admin take seat 0?
+- Does admin `takeSeat` require owner approval?
+- Is admin seat-taking restricted by `seatMode`?
+- Can an admin `takeSeat` after `lockSeat`?
+- When can a regular user `takeSeat`?
+- Can a regular user take a seat when `seatMode=FREE`?
+- How to unlock a locked seat and take it?

package/resource/knowledge/livekit/best-practice/common/audience-leave-live.md

@@ -0,0 +1,81 @@
+---
+title: "Voice Room Audience Leaving and Seat State（语聊房 / 观众 / 上麦 / 下麦 / leaveLive）"
+product: live
+frameworks: [android, ios, flutter]
+scope: platform_common
+tags: [voice room, audience, take seat, leave seat, leaveLive, leaveSeat, exit, seat, re-take seat, VoiceRoom]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Audience Leaving and Seat State
+
+## 1. Key Takeaways
+
+- When a seated audience member calls `leaveLive` to exit the voice room, they are automatically removed from the seat.
+- After exiting and re-entering the room, the user is **not seated** and must take a seat again.
+- The method for taking a seat depends on `seatMode`:
+  - `seatMode = FREE`: Call `takeSeat` directly.
+  - `seatMode = APPLY`: Call `applyForSeat` to submit a seat request; the owner/admin must approve before the user is seated.
+- `leaveLive` does **not require** calling `leaveSeat` first — exiting automatically removes the user from the seat.
+- Behavior is consistent across all three platforms (Android/iOS/Flutter).
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `leaveLive` | Exit the voice room | Exits the room and automatically leaves the seat |
+| `leaveSeat` | Manually leave a seat | Used for explicit seat departure; not required before `leaveLive` since exiting auto-leaves the seat |
+| `takeSeat` | Take a seat freely (`seatMode = FREE`) | Call directly after re-entering the room in free mode |
+| `applyForSeat` | Apply to take a seat (`seatMode = APPLY`) | Submit a request; owner/admin approval is required |
+| `seatMode` | Seat mode | `FREE`: free seat-taking; `APPLY`: requires approval |
+| Seat state | Whether the user is seated | Cleared after `leaveLive`; user must re-take a seat after re-entering |
+
+## 3. Mechanism & Sequence
+
+Seated audience calls `leaveLive` -> automatically leaves seat (no need to call `leaveSeat` first) -> exits room -> re-enters room -> seat state is empty, user is not seated -> choose seat-taking method based on `seatMode`:
+
+- `seatMode = FREE`: Call `takeSeat(seatIndex)` to take a seat directly.
+- `seatMode = APPLY`: Call `applyForSeat(seatIndex)` to submit a request and wait for owner/admin approval.
+
+## 4. Standard Usage
+
+```javascript
+// API is consistent across all three platforms (Android Kotlin / iOS Swift / Flutter Dart)
+// 1. 直接退出语聊房（会自动下麦，无需先 leaveSeat）
+liveListStore.leaveLive();
+
+// 2. 重新进房后，根据 seatMode 选择上麦方式
+// seatMode = FREE 时：直接上麦
+liveSeatStore.takeSeat(seatIndex);
+
+// seatMode = APPLY 时：申请上麦（需房主/管理员同意）
+liveSeatStore.applyForSeat(seatIndex);
+```
+
+## 5. Expected Results
+
+- After `leaveLive`, the user is automatically removed from the seat.
+- After re-entering the room, `LiveSeatStore.seatList` does not contain the user.
+- `seatMode = FREE`: Calling `takeSeat` succeeds and the user is seated again.
+- `seatMode = APPLY`: After calling `applyForSeat`, the user waits for approval; once approved, the user is seated again.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Calling `leaveSeat` before exiting (not necessary — `leaveLive` automatically leaves the seat).
+- Pitfall 2: Assuming the user is still seated after re-entering the room (they must take a seat again).
+- Pitfall 3: Worrying that `leaveLive` does not leave the seat, causing a stale seat entry (it auto-leaves — no stale entries).
+- Pitfall 4: Calling `takeSeat` directly when `seatMode = APPLY` (use `applyForSeat` instead — otherwise it will fail or have no effect).
+
+## 7. Problem Definition (retrieval hint)
+
+Whether a seated audience member is automatically removed from the seat after calling `leaveLive`, whether the user is still seated after re-entering, whether `leaveLive` requires calling `leaveSeat` first, and how to re-take a seat under different `seatMode` values (FREE/APPLY) using `takeSeat` vs `applyForSeat`.
+
+## 8. Alternative Queries (retrieval recall)
+
+- Does a voice room audience member leave the seat after exiting?
+- Do I need to take a seat again after re-entering?
+- Do I need to call `leaveSeat` before `leaveLive`?
+- Is the seat cleared when a voice room audience member exits?
+- How to re-take a seat after entering the room?
+- How to take a seat when `seatMode = APPLY`?
+- When to use `takeSeat` vs `applyForSeat`?