@tencent-rtc/mcp 1.3.5 → 1.3.7

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

@@ -0,0 +1,353 @@
+
+# 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
+ */
+
+```

package/resource/doc/tuicallkit/flutter/workflow.md

@@ -0,0 +1,331 @@
+# Flutter TUICallKit Audio/Video Call Application Code Generation Workflow Instructions
+
+## 📋 Purpose
+
+To provide Agents with a **code generation blueprint for implementing Flutter TUICallKit core audio/video call features**, and guide Agents to **prioritize using the latest documentation content retrieved in real-time by tools**, specifically for Flutter audio/video call application scenarios.
+
+---
+
+## 🛑 Agent Execution Hard Constraints (Guardrails)
+
+Agents must strictly follow these instructions when generating code:
+
+### 0. 🚨 Core Principles (Highest Priority)
+
+- ✅ Strictly generate code according to the sample code in the integration documentation, do not modify arbitrarily
+- ✅ Fully implement login, one-on-one call, and group call features
+- ✅ Use the `get_usersig` tool to generate UserSig for test accounts
+- ✅ Use the latest version of the `tencent_calls_uikit` package (use `any` for version number)
+
+### 1. Documentation-Driven Integration
+- Strictly follow the steps in `llm_code_generation_instructions_md` returned by the tool
+- Follow best practices and sample code from the integration documentation
+
+### 2. Package Import Method
+- **Configure pubspec.yaml**: Directly edit the file to add dependencies (avoid issues with flutter command not found)
+  ```yaml
+  dependencies:
+    tencent_calls_uikit: any  # ⚠️ Use any by default to automatically get the latest version
+  ```
+- Import statement: `import 'package:tencent_calls_uikit/tencent_calls_uikit.dart';`
+- **⚠️ Prohibited**: `latest`, `^latest` and similar notations (not supported by Flutter, will cause installation failure)
+
+### 3. Silent Integration Execution
+- After all code writing is complete, automatically install dependencies and start the project in the final step
+- **Dependency Installation Method**: Directly edit `pubspec.yaml` to add `tencent_calls_uikit: any`
+- **Do not use `flutter pub add` command** (avoid failure due to flutter command not found)
+- **Flutter Command Execution Strategy (Multi-level Degradation to Ensure Success)**:
+  1. **First Priority**: Try to execute `flutter pub get` directly
+  2. **Second Priority**: If failed, use `which flutter` to get the full path and execute
+  3. **Third Priority**: If still failed, try common paths:
+     - macOS/Linux: `$HOME/flutter/bin/flutter`
+     - macOS (Homebrew): `/opt/homebrew/bin/flutter`
+  4. **Final Degradation**: If all fail, **guide user to execute manually** (see guidance below)
+- After successful startup, prompt the user to run the app on simulator or physical device
+
+#### 📋 Manual Execution Degradation Guidance
+
+**When automatic execution fails, guide the user to execute manually**:
+
+```bash
+# 1. Install dependencies
+flutter pub get
+
+# 2. iOS project additional execution
+cd ios && pod install && cd ..
+
+# 3. Start project
+flutter run
+```
+
+**Common Issues**: flutter command not found → Check PATH environment variable; pod install failed → Execute `pod repo update`
+
+### 4. Authentication Credentials Configuration (Important)
+- Call the `get_usersig` tool to get SDKAppID, UserID, and UserSig
+- Generate UserSig for 4 test accounts (user001/002/003/004)
+- Authentication information can be hardcoded during testing, but must be annotated as test-only
+- ⚠️ Security Warning: Inform users that UserSig must be generated on the server side in production environment
+
+### 5. LoginPage Implementation Constraints 🔴
+
+**⚠️ Priority Check: Whether Login Page Already Exists in Project**:
+- Before implementing the login page, **must first check whether a login page already exists in the project**
+- If a login page already exists, **must ask the user whether to execute default behavior**:
+  - **Option 1**: Use default behavior (create new LoginPage with dropdown, 3 test accounts, etc.)
+  - **Option 2**: Modify based on existing login page (keep user's UI and interaction logic, only add necessary TUICallKit login logic)
+- If user chooses Option 2, should:
+  - Keep user's existing login page UI and interaction logic
+  - Only call `TUICallKit.instance.login` for secondary login after successful login
+  - Do not force use of dropdown and 3 test accounts
+- If no login page exists in the project, or user chooses Option 1, implement according to default behavior below
+
+**Default Login Page Implementation Requirements**:
+- **Must implement login page**, including the following features:
+  1. **Dropdown to select UserID**: Provide four options: user001, user002, user003, user004
+  2. **Display SDKAppID**: Get from `get_usersig` and display (read-only, not editable)
+  3. **Auto-generate UserSig**: Automatically match from pre-generated UserSig based on selected UserID
+  4. **Login button**: Call `TUICallKit.instance.login` to login
+- **Login interface must call `TUICallKit.instance.login`**, passing complete credentials obtained from `get_usersig`
+- Automatically navigate to home page (HomePage) after successful login
+
+**LoginPage Core Implementation Points**:
+
+```dart
+// 1. Define test account mapping table (obtained from get_usersig)
+final Map<String, String> userSigMap = {
+  'user001': 'xxx', 'user002': 'xxx', 'user003': 'xxx', 'user004': 'xxx'
+};
+
+// 2. UI Components
+// - SDKAppID display (read-only TextField)
+// - UserID dropdown (DropdownButtonFormField, options generated from userSigMap.keys)
+// - Login button
+
+// 3. Login logic see integration documentation
+```
+
+### 6. HomePage Implementation Constraints 🔴
+
+**Must implement home page**, including the following features:
+
+1. **Display current logged-in UserID**
+2. **Audio/Video call features** (unified user selection):
+   - **User list (multi-select)**: Display selectable users (user002, user003, user004, excluding current logged-in user)
+   - **Smart call type determination**:
+     - Select **1 user** → Automatically initiate **one-on-one call**
+     - Select **multiple users** → Automatically initiate **group call**
+   - **Voice call button**: Call `TUICallKit.instance.calls` to initiate voice call
+   - **Video call button**: Call `TUICallKit.instance.calls` to initiate video call
+   - **Implementation method**: Use `CheckboxListTile` for multi-select, supporting single and multiple selection
+3. **Logout button**: Call `TUICallKit.instance.logout` to logout
+
+**HomePage Core Implementation Points**:
+
+```dart
+// 1. Display current logged-in user (Card + ListTile)
+
+// 2. User selection area (unified one-on-one/group calls)
+// - User list: List<String> availableUsers = ['user002', 'user003', 'user004'].where((u) => u != currentUserId).toList();
+// - Multi-select checkbox: CheckboxListTile (supports selecting 1 or multiple users)
+// - Selected users: List<String> selectedUsers = [];
+
+// 3. Call button area
+// - Voice call button: ElevatedButton
+// - Video call button: ElevatedButton
+
+// 4. Initiate call and logout logic see integration documentation
+```
+
+### 7. MaterialApp Configuration Constraints 🔴
+
+**Must add TUICallKit.navigatorObserver in MaterialApp**:
+
+```dart
+MaterialApp(
+  navigatorObservers: [TUICallKit.navigatorObserver], // ⚠️ Must be added
+  home: const LoginPage(),
+)
+```
+
+### 8. Platform Configuration 🔴
+
+**Android and iOS platform configuration please refer to integration documentation**:
+- Android obfuscation rules and Multidex configuration see integration documentation "Step 2: Project Configuration - Android" section
+- iOS permissions configuration (camera, microphone) see integration documentation "Step 2: Project Configuration - iOS" section
+
+**⚠️ Android Obfuscation Configuration Syntax Check (Important)**:
+Before configuring Android obfuscation rules, **must first check the build script type used in the project**, and choose the correct syntax based on actual situation:
+
+| Build Script File | Syntax Type | Obfuscation Configuration Syntax |
+|-------------------|-------------|----------------------------------|
+| `android/app/build.gradle` | Groovy DSL | `minifyEnabled true` |
+| `android/app/build.gradle.kts` | Kotlin DSL | `isMinifyEnabled = true` |
+
+**Check Steps**:
+1. Check the build script file name in `android/app/` directory
+2. If it's `build.gradle` → Use Groovy syntax: `minifyEnabled true`
+3. If it's `build.gradle.kts` → Use Kotlin DSL syntax: `isMinifyEnabled = true`
+
+**⚠️ iOS Podfile Platform Version Configuration (Important)**:
+When configuring iOS project, **must set minimum platform version to iOS 14.0 in `ios/Podfile`**:
+
+```ruby
+platform :ios, '14.0'
+```
+
+**Configuration Location**: Add this line at the top of Podfile, before the target configuration
+
+### 9. Flutter Project Specifications
+- Use Flutter >= 3.24.0, Dart >= 3.5.0 versions
+- Follow Flutter official code style and best practices
+
+### 10. Environment Dependency Preparation
+- Ensure user has installed Flutter SDK
+- **Flutter command execution follows multi-level degradation strategy in Section 3**
+- iOS platform requires additional execution of `cd ios && pod install && cd ..` to install Pods dependencies
+- **If automatic execution fails, must generate degradation script for user to execute manually**
+
+---
+
+## 📦 Core Version Requirements
+
+| Tool/Platform | Minimum Version Requirement |
+|---------------|----------------------------|
+| **Flutter** | >= 3.24.0 |
+| **Dart** | >= 3.5.0 |
+
+**For detailed tool version requirements (Android Studio, Gradle, JDK, Xcode, etc.), please refer to integration documentation "Preparation - Environment Requirements" section**
+
+---
+
+## 📦 Automated Execution Commands
+
+After Agent code generation is complete, execute in order:
+
+```bash
+FLUTTER_PATH=$(which flutter)  # Get actual path
+$FLUTTER_PATH pub get          # Get dependencies (based on edited pubspec.yaml)
+cd ios && pod install && cd .. # iOS dependencies (macOS)
+$FLUTTER_PATH run              # Start project
+```
+
+**Dependency Addition Method**: Directly edit `pubspec.yaml` to add `tencent_calls_uikit: any`, avoid executing `flutter pub add` command
+
+**Degradation Strategy**: `which flutter` fails → Try `$HOME/flutter/bin/flutter` → Guide user to execute manually
+
+---
+
+## 📱 Physical Device Debugging Guide (User Instructions)
+
+### iOS Physical Device Debugging
+1. Connect device via USB, trust computer
+2. **Open `ios/Runner.xcworkspace`** (not .xcodeproj)
+3. Xcode configure signing (Automatically manage signing + Apple ID + modify Bundle ID)
+4. Execute `flutter run -d ios` or `flutter devices` to view device then specify run
+5. First run requires trusting developer on device: Settings → General → VPN & Device Management → Trust
+
+### Android Physical Device Debugging
+1. Connect device via USB
+2. Enable developer mode (tap build number 7 times) + USB debugging
+3. Device authorize USB debugging (allow)
+4. Execute `adb devices` to verify connection, then `flutter run -d android`
+
+---
+
+## 🔄 Complete Automation Workflow
+
+```mermaid
+graph TD
+    A[Receive user requirements] --> B[Get Flutter actual path: which flutter]
+    B --> C[Check Flutter environment]
+    C --> D[Edit pubspec.yaml to add tencent_calls_uikit: any]
+    D --> E[Configure Android platform: obfuscation rules, Multidex]
+    E --> F[Configure iOS platform: Info.plist permissions]
+    F --> G[Configure main.dart: add navigatorObserver]
+    G --> H[Call get_usersig tool to generate UserSig for 3 accounts]
+    H --> I[Implement LoginPage: dropdown to select UserID]
+    I --> J[Implement HomePage: one-on-one and group calls]
+    J --> K[Call record_result to record integration results]
+    K --> L[Execute with full path: $FLUTTER_PATH pub get]
+    L --> M{iOS platform?}
+    M -->|Yes| N[Execute pod install]
+    M -->|No| O[Skip pod install]
+    N --> P[Guide user to connect physical device for debugging]
+    O --> P
+    P --> Q{Choose run method}
+    Q -->|Simulator| R[Execute: $FLUTTER_PATH run]
+    Q -->|iOS physical device| S[Execute: $FLUTTER_PATH run -d ios]
+    Q -->|Android physical device| T[Execute: $FLUTTER_PATH run -d android]
+    R --> U[Project startup successful]
+    S --> U
+    T --> U
+```
+
+---
+
+## 📝 Key Points Summary
+
+| Category | Requirement |
+|----------|------------|
+| **Framework Version** | Flutter >= 3.24.0, Dart >= 3.5.0 |
+| **Integration Method** | pub package method (edit `pubspec.yaml` to add `tencent_calls_uikit: any`) |
+| **Documentation Priority** | ⚠️ Strictly follow sample code in integration documentation, do not modify arbitrarily |
+| **Silent Integration** | Automatically install dependencies and start project after code writing is complete, **must use `which flutter` to get actual path** |
+| **Credential Acquisition** | ⚠️ Must use `get_usersig` tool to generate UserSig for 4 test accounts (user001/002/003/004) |
+| **Login Page** | ⚠️ Must implement dropdown to select UserID, automatically match UserSig, prohibit manual input |
+| **Home Page** | ⚠️ Must support unified user list, selecting 1 user automatically initiates one-on-one call, selecting multiple users automatically initiates group call |
+| **Security Reminder** | ⚠️ Must inform user: Client-generated UserSig is only suitable for testing, production environment must generate on server side |
+| **Result Recording** | ⚠️ Must call `record_result` tool to record results after integration is complete |
+| **Platform Configuration** | ⚠️ Android and iOS platform configuration see integration documentation "Step 2: Project Configuration" section |
+| **Navigator Observer** | ⚠️ Must add `TUICallKit.navigatorObserver` in MaterialApp |
+
+---
+
+## 🎯 Agent Execution Checklist
+
+After completing code generation, Agent must confirm all the following items:
+
+### Project Initialization
+- [ ] Edited `pubspec.yaml` to add `tencent_calls_uikit: any` dependency
+- [ ] Configured Android and iOS platforms according to integration documentation (see "Step 2: Project Configuration")
+
+### Code Generation
+- [ ] Configured `main.dart`, added `TUICallKit.navigatorObserver`
+- [ ] Called `get_usersig` tool to generate UserSig for 4 accounts
+- [ ] Implemented LoginPage (dropdown to select UserID, no manual input fields)
+- [ ] Implemented HomePage (unified user list, select 1 for one-on-one call, select multiple for group call)
+
+### Final Check
+- [ ] Called `record_result` tool to record integration results
+- [ ] Executed `flutter pub get` and `pod install` (iOS)
+- [ ] Started project, prompted user to choose device
+- [ ] Informed user: Production environment must generate UserSig on server side
+
+---
+
+## 🔗 Required Tools
+
+### `get_usersig` - Get Test Authentication Information
+Get SDKAppID, UserID (user001/002/003/004), UserSig.
+- LoginPage: Dropdown to select UserID
+- HomePage: Display selectable user list (excluding current logged-in user)
+- Prohibit manual input of SDKAppID/SecretKey/UserSig
+
+### `record_result` - Record Integration Results
+Call after completing all integration steps and successfully starting project
+
+---
+
+## 📚 Related Resource Links
+
+- **TUICallKit Flutter Pub Package**: https://pub.dev/packages/tencent_calls_uikit
+- **Tencent Cloud Real-Time Communication TRTC Console**: https://console.cloud.tencent.com/trtc
+- **Server-side UserSig Generation**: https://cloud.tencent.com/document/product/647/17275
+- **Activate TRTC Service**: https://cloud.tencent.com/document/product/647/16788
+- **Flutter Official Documentation**: https://flutter.dev/docs
+
+---
+
+**Applicable Platforms**: Flutter (Android & iOS)  
+**TUICallKit Version**: tencent_calls_uikit (latest version)  
+**Minimum Requirements**: Flutter >= 3.24.0, Dart >= 3.5.0