@tencent-rtc/mcp 1.3.9 → 1.4.0

package/resource/doc/livekit/live/android/workflow.md

@@ -1,320 +0,0 @@
-# Native Live AtomicXCore Code Generation Workflow Instructions (Android)
-
-## 🚨 Core Principles (Highest Priority)
-
-**The Agent MUST ensure that the generated code compiles and runs successfully. Delivering uncompilable code to the user is strictly prohibited!**
-
-### ⚠️ Mandatory Compilation Verification
-**After every code generation or modification, a full Gradle compilation MUST be executed**:
-```bash
-./gradlew assembleDebug --stacktrace
-```
-
-**Prohibited Actions**:
-- ❌ DO NOT assume code is correct based only on `read_lints` checks.
-- ❌ DO NOT use `grep` to filter compilation output (this may miss critical error context).
-
-**Compilation Error Classification & Handling**:
-| Error Type | Example | Handling Strategy |
-|------------|---------|-------------------|
-| Dependency Resolution Failure | `Could not find xxx` | Check repository configurations (JitPack/Maven). |
-| Missing Dependency | `Unresolved reference` | Add missing dependency to `build.gradle`. |
-| Missing Import | `Unresolved reference: xxx` | Add the required `import` statement. |
-| Missing Resource | `cannot find symbol R.xxx` | Create the corresponding resource file. |
-| Missing Manifest Entry | `Activity not found` | Register the activity in `AndroidManifest.xml`. |
-
-**Validation Process**:
-1. Execute `./gradlew assembleDebug` (Full output, DO NOT filter).
-2. If it fails -> Analyze the full error -> **Auto-fix** -> Recompile.
-3. Repeat until `BUILD SUCCESSFUL`.
-
-**Key Point**: Emphasize that `read_lints != Full Compilation Verification`. Gradle dependency and configuration errors can only be detected through a full build.
-
-**Processing Flow**:
-1. **Compilation Successful (BUILD SUCCESSFUL)** -> Deliver code.
-2. **Compilation Failed** -> Analyze error -> **Auto-fix** -> Recompile.
-    * ✅ **Auto-fixable**: Missing dependencies, missing imports, missing AndroidManifest permissions/registrations.
-    * ❌ **Unfixable**: Internal SDK errors, network environment issues (inform the user).
-
----
-
-## 📋 Instruction Purpose & Architecture
-
-Provides the Agent with a **code generation blueprint** for implementing core features of Native (Android) Live AtomicXCore.
-
-**Core Architecture**:
-* **Container**: `LiveCoreView` (View layer)
-* **State**: `Store` (Data-driven)
-* **Events**: `Listener` (Callback handling)
-
-**Feature Dependency Logic (Important)**:
-1. **Base First**: Basic live streaming (Broadcasting/Viewing/List) must be completed first using the base tool (`get_native_live_uikit_integration`).
-2. **Interaction Overlay**: If requirements include "Co-guesting", "PK", or "Audience List", the interaction tool (`get_native_live_uikit_interaction`) must be called **after** basic features are completed.
-3. **Empty Project Handling**: If the user requests interaction features in an empty project, the Agent **MUST implement basic features first**, then add interaction capabilities.
-
----
-
-## ⚙️ Automated Workflow Steps
-
-### Step 0: Preparation (Automated)
-1. **Generate Credentials**: Call the `get_usersig` tool to generate test credentials.
-    * Host: `anchor001`, `anchor002`, `anchor003`
-    * Audience: `user001`, `user002`, `user003`
-2. **Environment Check**: Check `build.gradle` and add the following dependencies if missing:
-    ```gradle
-    api 'io.trtc.uikit:atomicx-core:latest.release'
-    api "io.trtc.uikit:rtc_room_engine:latest.release"
-    api "com.tencent.liteav:LiteAVSDK_Professional:latest.release"
-    api "com.tencent.imsdk:imsdk-plus:latest.release"
-    ```
-3. **Permission Injection**: Add Camera, Microphone, and Network permissions in `AndroidManifest.xml`.
-
-### Step 1: Retrieval & Generation
-**PRIORITIZE and EXCLUSIVELY** use the **real-time documentation content** returned by this tool for code generation.
-* **Host Only**: Generate `AnchorActivity`.
-* **Audience Only**: Generate `AudienceActivity`.
-* **Host + Audience**: Generate `MainActivity` (Entry selection) + `AnchorActivity` + `AudienceActivity`.
-
-### Step 2: Verification & Delivery
-Execute `./gradlew assembleDebug` and deliver once verified.
-
----
-
-## 🚫 Code Generation Constraints (Strictly Follow)
-
-### 1. General Code Constraints
-* **Strictly Prohibited to Modify Imports**: Import paths in the documentation are verified; DO NOT modify them.
-* **Strictly Prohibited to Fabricate APIs**: If an API is not in the documentation, DO NOT invent method or parameter names.
-* **MUST Consult API Docs**: For data model fields (e.g., `LiveInfo`), visit the documentation to confirm field names (e.g., confirm it's `liveOwner.userName` and not `name`).
-
-### 2. 🧩 Store & Listener Management Constraints (Lifecycle Safety)
-**Core Reason**: SDK `Store.create(liveId)` often returns a singleton or reusable instance. Using anonymous inner classes causes listener instances to be duplicated or overwritten, leading to bugs like "UI not updating on host side" or "only the first event being triggered."
-
-* **Member Variable Principle**: All Listeners (e.g., `GiftListener`, `CoGuestListener`, `BarrageListener`) **MUST be declared as member variables** of the Activity or Fragment.
-* **No Anonymous Inner Classes**: Prohibited to use anonymous objects directly inside `addXXXListener(object : ...)`.
-* **Pairing Principle**: If `addListener` is called in `onCreate/onStart`, `removeListener` **MUST** be called in `onDestroy/onStop` to prevent memory leaks and listener failure.
-
-### 3. ⏱️ Timeout Limits (Critical)
-**Strictly adhere to the following parameter limits, prioritizing values from documentation examples:**
-
-#### A. Co-guesting (`CoGuestStore`)
-* **Rules**:
-    * Optional parameter; if not filled, timeout is not checked.
-    * If filled, the range MUST be between **5 - 1800 seconds**.
-* **Correct Examples**:
-    ```kotlin
-    // ✅ Recommended: Follow doc examples (e.g., 30s)
-    applyForSeat(seatIndex = -1, timeout = 30, ...)
-    // ✅ Valid: No timeout check
-    applyForSeat(seatIndex = -1, timeout = 0, ...)
-    ```
-* **Incorrect Examples**: ❌ `timeout = 3` (too short), ❌ `timeout = 2000` (too long).
-
-#### B. Co-hosting/PK (`CoHostStore`)
-* **Rules**:
-    * **Maximum 30 seconds** (Hard limit).
-* **Correct Examples**:
-    ```kotlin
-    // ✅ Recommended: Use maximum value
-    requestHostConnection(..., timeout = 30, ...)
-    ```
-* **Incorrect Examples**: ❌ `timeout = 60` (will cause request failure).
-
-### 4. 🎨 Extra Feature Constraints (Beauty/Audio/UI)
-
-#### A. Audio Effects
-* **Voice Changer Enum (`AudioChangerType`)**:
-    * ✅ **Allowed**: `CHILD, LITTLE_GIRL, MAN, ETHEREAL`, etc.
-    * ❌ **Prohibited**: `UNCLE, LOLI, GIRL, BOY` (deprecated or incorrect).
-* **Reverb Enum (`AudioReverbType`)**:
-    * ✅ **Allowed**: `KTV, SMALL_ROOM, METALLIC`, etc.
-    * ❌ **Prohibited**: `ROOM, HALL, LOW`.
-
-#### B. Beauty
-* **Parameter Range**: **0.0 - 9.0** (Float).
-    * ❌ NOT 0-1 (Float), and NOT 0-100 (Int).
-* **UI Mapping Formula**: `progress / 100.0f * 9.0f`.
-
-#### C. Barrage, Gift & Layout (Barrage, Gift & UI)
-* **Layering Requirements**: Barrage list and full-screen gift animations MUST overlay **on top** of the video layer using `FrameLayout` or `RelativeLayout`.
-* **Split Screen Prohibited**: Strictly prohibited to split the screen (e.g., video on top, barrage at bottom); MUST use overlay mode.
-* **Keyboard Adaptation**: Must set `android:windowSoftInputMode="adjustNothing"` or `adjustPan` in the Manifest to **prevent video distortion or shifting when the keyboard appears**.
-
-##### Barrage Input
-* **Position**: Fixed at the bottom left of the screen, in the same row as function buttons (Gift, Co-guest, etc.).
-* **Style**: Semi-transparent rounded background + placeholder text "Say something...".
-* **Keyboard Adaptation**:
-    * When the keyboard is raised, the input box **must remain in its original position** and is prohibited from moving up with the keyboard.
-    * The `LiveCoreView` layout must be fixed to `match_parent`, prohibiting distortion or upward shifting.
-    * **MUST** set `android:windowSoftInputMode="adjustNothing"` in the Manifest.
-
-##### Barrage Display Flow
-```
-Sending Barrage:
-User input → Click Send/Enter → BarrageStore.sendTextMessage(text) → Insert into local barrage list immediately
-
-Receiving Barrage:
-Subscribe to BarrageStore.barrageState.barrageList → New message received → Insert into barrage list → Scroll to bottom
-```
-* **Data Source**: Subscribe to `BarrageStore.create(liveId).barrageState.barrageList`.
-* **Local Echo**: Insert into the local barrage list **immediately** after successful sending, without waiting for server callback.
-* **Scrolling Behavior**: Automatically scroll to the bottom when a new message arrives (`recyclerView.scrollToPosition(adapter.itemCount - 1)`).
-* **Message Format**: `[Nickname]: [Message Content]`, nickname uses theme color, content uses white.
-
-* **Gift Barrage**: **If the user needs gift barrage integration**, when `onReceiveGift` is triggered, a gift message MUST be inserted into the barrage list on **both host and audience sides**. DO NOT display only on the audience side.
-
-##### Full-screen Gift Animation
-**⚠️ MANDATORY**: Full-screen gift animation is a **mandatory requirement** when integrating gift features and cannot be omitted.
-
-* **Layering**: The full-screen gift animation view MUST overlay **on top** of the `LiveCoreView` using a separate `FrameLayout` container.
-* **Layout**: Constrained to `match_parent`, covering the entire screen.
-* **Dual-side Sync**: Upon receiving the `GiftStore.onReceiveGift` callback, the full-screen animation MUST be played on **both host and audience sides**. Playing only on the audience side is strictly prohibited.
-
-### 🎨 Default UI/UX Design & Interaction Specifications (Only applies if user doesn't specify)
-
-**⚠️ Note: The following specifications are only executed as default standards when the user does not provide specific UI design or requirements.**
-
-### 1. Global Aesthetics
-* **Immersive Dark**: The background of the live page must be `Color.BLACK`, and the video layer (`LiveCoreView`) must **fill the entire screen** (`match_parent`) and be at the bottom layer.
-* **Safe Area**: All floating UIs must consider status and navigation bars, and are strictly prohibited from being blocked by notches or bottom navigation bars.
-* **Text Readability**: White text above the video (e.g., barrage, ID) must have a **black shadow** (`setShadowLayer`).
-* **Error Prompts**: Use **Toast** uniformly; prohibit the use of modal AlertDialogs that interrupt the user.
-
-### 2. Component Standards
-* **Glass Capsule (Top)**:
-    * **Style**: **Semi-transparent black background** + **full rounded corners** (`cornerRadius = height / 2`).
-    * **Application**: Only used at the top left to display "Host Avatar + ID + Popularity".
-* **Flat Buttons**:
-    * **Style**: **"Text + Rounded Rectangle Background"**. Minimalist flat design, background color is semi-transparent black or theme color.
-    * **Close Button**: Special case, use a circular semi-transparent background icon.
-* **Floating Panels**:
-    * **Style**: Only top rounded corners (`topLeftRadius, topRightRadius`).
-    * **Taboo**: Solid color backgrounds at the bottom are prohibited; floating feeling must be maintained.
-
-### 3. Live Room Layout Blueprint
-**⚠️ Dynamic Layout Principle: Only render function buttons that the user has actually integrated. If a user did not request a feature (e.g., PK/Beauty), DO NOT add corresponding empty buttons.**
-
-#### A. Top Bar
-* **Left [Room Info]**: Wrapped in a **semi-transparent capsule** [Host Avatar | Host Nickname].
-* **Right [Control Area]**: Horizontally arranged [Online Audience Count] + [Close Icon (X)].
-
-#### B. Bottom Bar - Dynamically switches based on state
-* **Preview Mode**:
-    * Content **aligned to the right**: [Beauty] [Audio Effects] [Start Live (Main Button)].
-* **Anchor Live Mode**:
-    * **Left**: [Barrage List (Transparent Background)] + [Chat Input Box].
-    * **Right**: Function array [Beauty] [Audio Effects] [Co-hosting] [PK].
-* **Audience Live Mode**:
-    * **Left**: [Barrage List] + [Chat Input Box].
-    * **Right**: [Gift] [Apply for Co-guesting].
-
-### 4. Home Layout & Interaction
-
-#### A. Home Reference Layout
-```
-┌─────────────────────────────┐
-│       AtomicXCore Live       │
-│                             │
-│  Live Room ID                │
-│  ┌─────────────────────────┐│
-│  │ live_000001             ││  ← Input Box (with left padding, semi-transparent background)
-│  └─────────────────────────┘│
-│                             │
-│  Host Broadcasting           │
-│  (Click to login as anchor001)│
-│                             │
-│  Audience Viewing            │
-│  (Click to login as user001)  │
-│                             │
-│       [ 📋 Live List ]       │
-└─────────────────────────────┘
-```
-
-#### B. Implicit Login Flow
-**No separate login button is required on the home page**; login is automatically completed when a function button is clicked:
-* Click "Host Broadcasting" → Login using `anchor001` → Jump to host page.
-* Click "Audience Viewing" → Login using `user001` → Jump to audience page.
-* Click "Live List" → Login using `user001` → Jump to list page.
-
----
-
-## 🎯 Implementation Details
-
-### 1. Host Broadcasting (`host_streaming`)
-* **Core**: `LiveCoreView(viewType = PUSH_VIEW)`
-* **Flow**: `LiveListStore.createLive()`
-* **Cleanup**: `endLive()` MUST be called in `onDestroy`.
-
-### 2. Audience Viewing (`audience_streaming`)
-* **Core**: `LiveCoreView(viewType = PLAY_VIEW)`
-* **Flow**: `LiveListStore.joinLive()`
-* **Cleanup**: `leaveLive()` MUST be called in `onDestroy`.
-
-### 3. Live List (`live_list`)
-* **Core**: `LiveListStore.fetchLiveList()` + `RecyclerView`
-* **Data**: Subscribe to `liveState.liveList`.
-* **Navigation**: Clicking a list item navigates to the audience page, passing the `liveID`.
-
-### 4. Co-guest & Co-host Interaction Specifications (`co_guest` & `co_host`)
-
-#### A. Audience Co-guesting (Host passively receives)
-* **Host UI**: ❌ **Strictly prohibited** to display a "Co-guest Application" list button in the bottom toolbar or anywhere else.
-* **Interaction Logic**: Upon receiving a co-guest application callback, pop up a dialog (`AlertDialog`) directly in the center of the screen:
-    * **Title**: Co-guest Application
-    * **Content**: Received a co-guest application from audience [Nickname], accept?
-    * **Operations**: [Decline] [Accept]
-
-#### B. Host Co-hosting Panel (Pops up when clicking bottom [Co-host] button)
-* **Presentation**: Use a bottom floating panel (`BottomSheetDialog` or custom `View` animated up); prohibit `AlertDialog`.
-* **UI Layout (Strictly follow illustration)**:
-```
-┌─────────────────────────────────────┐
-│                                     │
-│  Initiate Connection   [🚪 End Co-host]  │  ← Red text
-│                                     │
-│  Connected (2 persons)               │
-│  ┌─────────────────────────────────┐│
-│  │ [👤] Li Ziming [💎20]      PK...   ││  ← Connected users
-│  │ [👤] Filinna  [💎32]      PK...   ││
-│  └─────────────────────────────────┘│
-├─────────────────────────────────────┤
-│  Other Live Users                   │
-│  ┌─────────────────────────────────┐│
-│  │ [👤] Li Ziming [💎20]  [Cancel Inv] ││  ← Gray-black background button
-│  │ [👤] Filinna  [💎32]  [Invite]      ││  ← Blue background button
-│  │ [👤] Tie Zhu   [💗99]  [Invite]      ││
-│  └─────────────────────────────────┘│
-└─────────────────────────────────────┘
-```
-
-#### C. PK Button Interaction Constraints
-* **Pre-check**: When clicking the bottom [PK] button, current connection status must be checked (`CoHostStore.connectedUsers.isEmpty()`).
-* **Status Handling**:
-    * **Not connected**: ❌ Prohibit jump, show Toast: `"Please initiate co-hosting first"`.
-    * **Connected**: ✅ Pop up PK invitation panel.
-
----
-
-## 📋 Agent Final Checklist
-
-- [ ] **Build Verification**: Full `./gradlew assembleDebug` executed and result is SUCCESS.
-- [ ] **API Accuracy**: Imports not modified, APIs not fabricated, `LiveInfo` field names verified.
-- [ ] **Timeout Compliance**: Co-guesting 5-1800s, Co-hosting ≤30s.
-- [ ] **Extra Feature Compliance**: Audio enums correct, beauty range 0-9, barrage layout overlays, and keyboard adaptation.
-- [ ] **Gift Compliance**: Full-screen gift animations implemented on both host and audience sides.
-- [ ] **Credential Injection**: Test UserSig automatically injected.
-- [ ] **Dependencies Complete**: `build.gradle` and permissions checked/fixed.
-
----
-
-## 🚨 Security Reminder (Code Comment Template)
-
-```kotlin
-/**
- * ⚠️ Test Credential Warning
- * - This UserSig is automatically generated by development tools and is valid for 7 days.
- * - ❌ PROHIBITED from generating UserSig on the client side in production.
- * - ✅ UserSig MUST be generated on a backend service before official launch.
- * - Reference: https://trtc.io/document/35166?product=live&menulabel=uikit&platform=android
- */
-```

package/resource/doc/livekit/live/flutter/workflow.md

@@ -1,353 +0,0 @@
-
-# Native Live AtomicXCore Code Generation Workflow Instructions (Flutter)
-
-## 🚨 Core Principles (Highest Priority)
-
-**Agent MUST ensure the generated code compiles and runs successfully. Delivering non-buildable code to users is STRICTLY PROHIBITED!**
-
-### ⚠️ Mandatory Build Verification
-
-**After every code generation/modification, a full build verification MUST be executed**:
-
-```bash
-flutter build apk --debug
-# Or on iOS environment
-flutter build ios --debug --no-codesign
-
-```
-
-**Prohibited Actions**:
-
-* ❌ Do NOT assume code is correct by only running `flutter analyze` (cannot detect native dependency issues)
-* ❌ Do NOT ignore `pubspec.yaml` version conflicts
-
-**Build Error Classification and Handling**:
-| Error Type | Example | Resolution |
-|---------|------|---------|
-| Dependency Resolution Failed | `Because xxx depends on yyy...` | Check `pubspec.yaml` version compatibility, run `flutter pub get` |
-| Missing Dependency | `Target of URI doesn't exist` | Add missing library to `dependencies` |
-| Missing Import | `Undefined class 'xxx'` | Add import statement |
-| Missing Asset | `Unable to load asset` | Register asset in `pubspec.yaml` under `assets` node |
-| Missing Permission | Crash on access Camera/Mic | Check `AndroidManifest.xml` and `Info.plist` |
-
-**Verification Flow**:
-
-1. Execute `flutter build apk --debug`.
-2. If failed → Analyze complete error stack → Fix → Rebuild.
-3. Loop until `BUILD SUCCESSFUL`.
-
-**Handling Flow**:
-
-1. **Build Successful** → Deliver code.
-2. **Build Failed** → Analyze error → **Auto-fix** → Rebuild.
-* ✅ **Auto-fixable**: Missing dependencies, Missing imports, Missing permission configurations.
-* ❌ **Not fixable**: SDK internal errors, Flutter environment configuration issues (notify user).
----
-
-## 📋 Instruction Purpose and Architecture
-
-Provides Agent with a **code generation blueprint** for implementing Native (Flutter) Live AtomicXCore core features.
-
-**Core Architecture**:
-
-* **Container**: `LiveCoreWidget` (View layer)
-* **State**: `Store` (Data-driven)
-* **Events**: `Listener` (Callback handling)
-
-**Feature Dependency Logic (Important)**:
-
-1. **Foundation First**: Must first use this tool (`get_flutter_live_uikit_integration`) to complete basic live streaming (host streaming/viewing/list).
-2. **Interaction Overlay**: If user requirements include "co-guest", "PK", "audience list", must call the interaction tool (`get_flutter_live_uikit_interaction`) **after basic features are completed**.
-3. **Empty Project Handling**: If user requests interaction features in an empty project, Agent **MUST implement basic features first**, then add interaction capabilities.
-
----
-
-## ⚙️ Automated Workflow Steps
-
-### Step 0: Prerequisites (Automated)
-
-1. **Generate Credentials**: Call `get_usersig` tool to generate test credentials.
-* Anchors: `anchor001`, `anchor002`, `anchor003`
-* Audience: `user001`, `user002`, `user003`
-
-2. **Environment Check**: Check `pubspec.yaml`, auto-add if missing the following dependencies:
-```yaml
-dependencies:
-  flutter:
-    sdk: flutter
-  atomic_x_core: ^3.6.0  # Core library
-  permission_handler: ^11.0.0 # Permission handling
-  svgaplayer_flutter: ^2.0.0 # Gift animation (if needed)
-
-```
-
-3. **Permission Injection**:
-* **Android**: Add Camera/Record Audio permissions in `android/app/src/main/AndroidManifest.xml`.
-* **iOS**: Add `NSCameraUsageDescription` and `NSMicrophoneUsageDescription` in `ios/Runner/Info.plist`.
-### Step 1: Fetch and Generate
-
-**MUST prioritize and exclusively** use the **real-time documentation content** returned by this tool to generate code.
-
-* **Anchor Only**: Generate `AnchorPage`
-* **Audience Only**: Generate `AudiencePage`
-* **Anchor + Audience**: Generate `MainPage` (entry selection) + `AnchorPage` + `AudiencePage`
-
-### Step 2: Verify and Deliver
-
-Execute `flutter build apk --debug`, deliver after ensuring no errors.
-
----
-
-## 🚫 Code Generation Constraints (Strictly Follow)
-
-### 1. General Code Constraints
-
-* **NEVER Modify Import**: Uniformly use `import 'package:atomic_x_core/atomicxcore.dart';`.
-* **NEVER Fabricate APIs**: Must strictly follow Store and Model definitions in the documentation.
-* **MUST Consult API Documentation**: When dealing with data model fields (e.g., `LiveInfo`), must check documentation to confirm field names (e.g., confirm it's `liveOwner.userName` not `name`).
-
-### 2. 🧩 Store and Listener Management Constraints (Lifecycle Safety)
-
-**Core Reason**: Dart's Stream and closure listeners, if not properly released, will cause severe memory leaks or null pointer exceptions.
-
-* **Unique Instance Principle**: All Listeners (e.g., `GiftListener`, `CoGuestListener`, `BarrageListener`) **MUST be declared as State member variables**.
-* **NO Anonymous Inner Classes**: Prohibit writing anonymous objects directly in `addListener(Listener(...))`, must instantiate first.
-* **Pairing Principle**: If `addListener` is called in `initState`, then `removeListener` **MUST** be called in `dispose` to prevent memory leaks and listener failures.
-
-### 3. ⏱️ Timeout Limits (Critical Technical Point)
-
-**MUST strictly follow these parameter limits, prioritize using values from documentation examples:**
-
-#### A. Co-Guest (`CoGuestStore`)
-
-* **Rules**:
-* Optional parameter, no timeout check if not provided.
-* If provided, range MUST be between **5 - 1800 seconds**.
-
-* **Correct Example**:
-```dart
-// ✅ Recommended: Follow documentation example (e.g., 30 seconds)
-guestStore.applyForSeat(seatIndex: -1, timeout: 30, extraInfo: null);
-
-```
-#### B. Co-Host/PK (`CoHostStore`)
-
-* **Rules**:
-* **Maximum 30 seconds** (backend hard limit).
-
-* **Correct Example**:
-```dart
-// ✅ Recommended: Use maximum value
-coHostStore.requestHostConnection(..., timeout: 30);
-
-```
-### 3. 🎨 Extended Feature Constraints (Beauty/Audio Effect/UI)
-
-#### A. Audio Effect
-
-* **Voice Changer Enum (`AudioChangerType`)**:
-* ✅ **Allowed**: `AudioChangerType.child`, `AudioChangerType.man` and other standard enums.
-* ❌ **Prohibited**: Using integer indices (e.g., `1`, `2`).
-#### B. Beauty
-
-* **Parameter Range**: **0.0 - 9.0** (Double).
-* **UI Mapping Formula**: `sliderValue * 9.0` (assuming Slider is 0.0-1.0).
-
-#### C. Barrage, Gift & Layout
-
-* **Layer Requirements**: Use `Stack` widget.
-* Bottom layer: `LiveCoreWidget` (full screen).
-* Top layer: Barrage, gift, function buttons (use `Positioned` for positioning).
-
-* **Keyboard Adaptation**:
-* `Scaffold` property `resizeToAvoidBottomInset: false`, prevent keyboard from pushing up video view.
-* Input box at top of `Stack`, use `MediaQuery` to monitor keyboard height or use `Positioned(bottom: 0)` with `SafeArea`.
-##### Barrage Input Box
-
-* **Position**: Fixed at bottom-left of screen, in the same row as function buttons (gift, co-guest, etc.).
-* **Style**: Semi-transparent rounded background + placeholder text "Say something...".
-* **Keyboard Adaptation**:
-* When keyboard pops up, input box **MUST stay in original position**, DO NOT move up with keyboard.
-* **MUST** set `resizeToAvoidBottomInset: false` on `Scaffold`.
-##### Barrage Display Flow
-
-* **Data Source**: Use `ValueListenableBuilder` to listen to `BarrageStore.create(liveId).barrageState.messageList`.
-* **Local Echo**: After successful send, **immediately** call `appendLocalTip` to insert into local barrage list, no need to wait for server callback.
-* **Scroll Behavior**: Auto-scroll to bottom when new message arrives.
-
-##### Full-screen Gift Animation
-
-**⚠️ MUST Implement**: When integrating gift feature, full-screen gift animation is **mandatory**, cannot be omitted.
-
-* **Dependency**: Must include `svgaplayer_flutter`.
-* **Layer**: Full-screen gift animation view must be placed **above** `LiveCoreWidget`.
-* **Dual-side Sync**: After receiving `GiftStore.onReceiveGift` callback, **both anchor and audience** must play the full-screen animation. Prohibit playing only on audience side.
-
-### 🎨 Default UI/UX Design and Interaction Standards (Only effective when user doesn't specify)
-
-**⚠️ Note: The following standards are only applied as defaults when user doesn't provide specific UI design mockups or requirements.**
-
-### 1. Global Visual Style (Global Aesthetics)
-
-* **Immersive Dark**: `Scaffold` background MUST be `Colors.black`, `LiveCoreWidget` MUST **fill the entire screen** (`Positioned.fill`) and be at the bottom layer.
-* **Safe Area**: All floating UI MUST be wrapped in `SafeArea`.
-* **Text Readability**: White text over video (e.g., barrage, ID) MUST have **black shadow** (`Shadow`).
-* **Error Prompts**: Uniformly use `SnackBar` or `FlutterToast`, DO NOT use modal Dialog to interrupt user.
-
-### 2. Common Component Standards
-
-* **Top Capsule (Glass Capsule)**:
-* **Style**: **Semi-transparent black background** + **Fully rounded corners**.
-* **Usage**: Only for top-left display of "anchor avatar + ID + popularity".
-
-* **Common Buttons (Flat Buttons)**:
-* **Style**: **"Text + Rounded rectangle background"**. Flat and minimalist visual style, background color is semi-transparent black or theme color.
-* **Close Button**: Exception, uses circular semi-transparent background icon.
-### 3. Live Room Layout Blueprint
-
-**⚠️ Dynamic Layout Principle: Only render function buttons that user actually integrates. If user didn't request a feature (e.g., PK/beauty), strictly prohibit adding corresponding empty buttons**
-
-#### A. Top Bar
-
-* **Left [Room Info]**: Use **semi-transparent capsule** to wrap [Anchor Avatar | Anchor Nickname].
-* **Right [Control Area]**: Horizontally arrange [Online Audience Count] + [Close Icon (X)].
-
-#### B. Bottom Bar - Dynamic switching based on state
-
-* **Preview Mode**:
-* Content **aligned to right**: [Beauty] [Audio Effect] [Start Live (Main Button)].
-
-* **Anchor Live Mode**:
-* **Left**: [Barrage List (transparent background)] + [Chat Input Box].
-* **Right**: Function array [Beauty] [Audio Effect] [Co-Host] [PK].
-
-* **Audience Mode**:
-* **Left**: [Barrage List] + [Chat Input Box].
-* **Right**: [Gift] [Apply Co-Guest].
-### 4. Home Page Layout and Interaction
-
-#### A. Home Page Reference Layout
-
-```
-┌─────────────────────────────┐
-│       AtomicXCore Live       │
-│                             │
-│  Live Room ID               │
-│  ┌─────────────────────────┐│
-│  │ live_000001             ││  ← Input box (with left Padding, semi-transparent background)
-│  └─────────────────────────┘│
-│                             │
-│  Start Live as Anchor        │
-│  (Click to login as anchor001)│
-│                             │
-│  Watch as Audience           │
-│  (Click to login as user001) │
-│                             │
-│       [ 📋 Live List ]       │
-└─────────────────────────────┘
-
-```
-
-#### B. Implicit Login Flow
-
-**Home page doesn't need a separate login button**, login is automatically completed when clicking function buttons:
-
-* Click "Start Live as Anchor" → Login as `anchor001` → Navigate to anchor page.
-* Click "Watch as Audience" → Login as `user001` → Navigate to audience page.
-* Click "Live List" → Login as `user001` → Navigate to list page.
-
----
-
-## 🎯 Feature Implementation Details
-
-### 1. Anchor Start Live (`AnchorPage`)
-
-* **Core**: `LiveCoreWidget` + `LiveCoreController`
-* **Flow**: `LiveListStore.createLive()`
-* **Destroy**: MUST call `endLive()` in `dispose`.
-
-### 2. Audience Watch (`AudiencePage`)
-
-* **Core**: `LiveCoreWidget` + `LiveCoreController`
-* **Flow**: `LiveListStore.joinLive()`
-* **Destroy**: MUST call `leaveLive()` in `dispose`.
-
-### 3. Live List (`LiveListPage`)
-
-* **Core**: `LiveListStore.fetchLiveList()` + `GridView`/`ListView`
-* **Data**: Subscribe to `liveState.liveList` (ValueListenable).
-* **Navigation**: Click list item to navigate to audience page, pass `liveID`.
-
-### 4. Co-Guest and Co-Host Interaction Standards (`co_guest` & `co_host`)
-
-#### A. Co-Guest (Anchor passively receives)
-
-* **Anchor UI**: ❌ **STRICTLY PROHIBIT** displaying "Co-Guest Request" list button in bottom toolbar or anywhere.
-* **Interaction Logic**: When receiving audience co-guest application callback (`onApplicationReceived`), directly pop up dialog at screen center (`showDialog`):
-* **Title**: Co-Guest Request
-* **Content**: Received co-guest request from audience [nickname], accept?
-* **Actions**: [Reject] [Accept]
-
-* **Custom View**: Flutter version MUST implement `LiveCoreWidget.videoWidgetBuilder`'s `coGuestWidgetBuilder`, return Foreground (nickname) or Background (avatar) based on `ViewLayer`.
-
-#### B. Co-Host Panel (Pops up when clicking bottom [Co-Host] button)
-
-* **Presentation**: Use bottom sheet panel (`showModalBottomSheet`), prohibit using Dialog.
-* **UI Layout (Strictly follow the diagram)**:
-
-```
-┌─────────────────────────────────────┐
-│                                     │
-│  Start Co-Host        [🚪 End Co-Host] │  ← Red text
-│                                     │
-│  Connected (2 people)               │
-│  ┌─────────────────────────────────┐│
-│  │ [👤] John [💎20]          In PK... ││  ← Connected users
-│  │ [👤] Alice [💎32]         In PK... ││
-│  └─────────────────────────────────┘│
-├─────────────────────────────────────┤
-│  Other Co-Host Users                │
-│  ┌─────────────────────────────────┐│
-│  │ [👤] John [💎20]      [Cancel Invite] ││  ← Gray-black background button
-│  │ [👤] Alice [💎32]     [Invite Co-Host] ││  ← Blue background button
-│  │ [👤] Bob   [💗99]     [Invite Co-Host] ││
-│  └─────────────────────────────────┘│
-└─────────────────────────────────────┘
-
-```
-
-#### C. PK Button Interaction Constraints
-
-* **Pre-check**: When clicking bottom [PK] button, MUST check current co-host status (`CoHostStore.connectedUsers.isEmpty()`).
-* **Status Handling**:
-* **Not Connected**: ❌ Prohibit navigation, use Toast to prompt: `"Please start co-host first"`.
-* **Connected**: ✅ Pop up PK invitation panel.
-
-* **Custom View**: Implement `VideoWidgetBuilder.battleWidgetBuilder` to display PK opponent info and scores.
-
----
-
-## 📋 Agent Final Checklist
-
-* [ ] **Build Verification**: Executed `flutter build apk --debug` with SUCCESS result.
-* [ ] **API Accuracy**: Did not modify Import, did not fabricate APIs, verified `LiveInfo` field names.
-* [ ] **Timeout Compliance**: Co-guest timeout 5-1800s, co-host timeout ≤30s.
-* [ ] **Extension Compliance**: Audio effect enums correct, beauty range 0-9, barrage layout overlays and keyboard adapted.
-* [ ] **Gift Compliance**: Both anchor and audience have implemented full-screen gift animation display.
-* [ ] **Credential Injection**: Test UserSig has been auto-injected.
-* [ ] **Dependency Complete**: Checked and fixed `pubspec.yaml` and platform permission configurations.
-
----
-
-## 🚨 Security Reminder (Code Comment Template)
-
-```dart
-/**
- * ⚠️ Test Credential Notice
- * - Current userSig is auto-generated by development tool, valid for 7 days
- * - ❌ Production environment MUST NOT generate userSig on client side
- * - ✅ Must generate on backend service before going live
- * - Reference: https://trtc.io/document/live-overview?product=live&menulabel=uikit&platform=flutter
- */
-
-```