@cometchat/skills 4.2.1 → 4.4.0

package/skills/cometchat-flutter-v5-testing/SKILL.md

@@ -3,7 +3,6 @@ name: cometchat-flutter-v5-testing
 description: Testing patterns for CometChat Flutter UIKit v5 (GetX-based). Covers flutter_test (built-in), mocktail for SDK mocking, widget tests around CometChat widgets, integration_test for real-device flows, golden tests for theming, and CI on GitHub Actions / Codemagic. Sister skill of cometchat-flutter-v6-testing — the cohorts have different state-management primitives (GetX vs Bloc) so test patterns differ.
 license: "MIT"
 compatibility: "Flutter >= 2.5, Dart >= 2.17; flutter_test (built-in); mocktail >= 1.0; integration_test (built-in); cometchat_chat_uikit ^5.2; cometchat_calls_uikit ^5.0"
-allowed-tools: "shell, file-read, file-search, file-list, ask-user"
 metadata:
   author: "CometChat"
   version: "4.0.0"
@@ -18,7 +17,7 @@ Test recipes for Flutter UIKit v5. Covers the GetX-flavored patterns; v6 (Bloc)
 - `cometchat-flutter-v5-core` — UIKitSettingsBuilder, init/login order, GetX scope rules
 - `cometchat-flutter-v5-events` — event subscription patterns the tests assert against
 
-**Ground truth:**
+**Ground truth:** **Official docs:** https://www.cometchat.com/docs/ui-kit/flutter/v5/overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP).
 - flutter_test — https://api.flutter.dev/flutter/flutter_test/flutter_test-library.html
 - mocktail — https://pub.dev/packages/mocktail
 
@@ -91,12 +90,15 @@ class CometChatServiceImpl implements CometChatService {
   }
 
   @override
-  User? getLoggedInUser() => CometChatUIKit.getLoggedInUser();
+  // Sync accessor → the static field. CometChatUIKit.getLoggedInUser() is async
+  // (Future<User?>) and would not satisfy this `User?` signature.
+  User? getLoggedInUser() => CometChatUIKit.loggedInUser;
 
   @override
   Future<TextMessage> sendMessage(TextMessage message) async {
     final completer = Completer<TextMessage>();
-    CometChatUIKit.sendTextMessage(textMessage: message, onSuccess: completer.complete, onError: completer.completeError);
+    // sendTextMessage takes message as positional, not named (verified cometchat_ui_kit.dart:357).
+    CometChatUIKit.sendTextMessage(message, onSuccess: completer.complete, onError: completer.completeError);
     return completer.future;
   }
 }
@@ -164,7 +166,8 @@ void main() {
 
     expect(find.byType(CircularProgressIndicator), findsOneWidget);
 
-    loginCompleter.complete(User(uid: 'cometchat-uid-1'));
+    // User constructor requires both uid AND name (verified User constructor in chat-sdk-flutter).
+    loginCompleter.complete(User(uid: 'cometchat-uid-1', name: 'Alice'));
     await tester.pumpAndSettle();
 
     expect(find.byType(CircularProgressIndicator), findsNothing);
@@ -273,7 +276,15 @@ testWidgets('chat bubble renders correctly in light theme', (tester) async {
     theme: ThemeData.light(),
     home: Scaffold(
       body: ChatBubble(
-        message: TextMessage(text: 'Hello', senderUid: 'alice'),
+        // TextMessage requires: text, receiverUid, type, receiverType + sender (User object).
+        // senderUid is NOT a TextMessage constructor param — set via sender (User).
+        message: TextMessage(
+          text: 'Hello',
+          receiverUid: 'bob',
+          type: 'text',
+          receiverType: 'user',
+          sender: User(uid: 'alice', name: 'Alice'),
+        ),
       ),
     ),
   ));

package/skills/cometchat-flutter-v5-theming/SKILL.md

@@ -3,13 +3,14 @@ name: cometchat-flutter-v5-theming
 description: "Use when customizing the visual appearance of CometChat Flutter UIKit v5 components. Triggers on CometChatThemeHelper, CometChatColorPalette, CometChatSpacing, CometChatTypography, Style classes, merge()."
 license: "MIT"
 compatibility: "cometchat_uikit_shared ^5.2.3; flutter >=2.5.0"
-allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"
   tags: "cometchat flutter v5 theme colors typography spacing dark-mode styling"
 ---
 
+> **Ground truth:** `cometchat_chat_uikit: ^5.2` (legacy/maintenance-only; calls via raw `cometchat_calls_sdk ^5.0.2`) — pub-cache source + `ui-kit/flutter/v5`. **Official docs:** https://www.cometchat.com/docs/ui-kit/flutter/v5/overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP). Verify symbols against the installed package/source before relying on them.
+
 # CometChat Flutter UIKit v5 — Theming & Styling
 
 How to customize the visual appearance of all CometChat v5 components.

package/skills/cometchat-flutter-v5-troubleshooting/SKILL.md

@@ -3,13 +3,14 @@ name: cometchat-flutter-v5-troubleshooting
 description: "Use when debugging CometChat Flutter UIKit v5 issues. Symptom-to-cause lookup, verify checks, common errors, drift detection."
 license: "MIT"
 compatibility: "cometchat_chat_uikit ^5.2.14; cometchat_calls_uikit ^5.0.15; cometchat_uikit_shared ^5.2.3"
-allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"
   tags: "cometchat flutter v5 troubleshooting debug errors fix"
 ---
 
+> **Ground truth:** `cometchat_chat_uikit: ^5.2` (legacy/maintenance-only; calls via raw `cometchat_calls_sdk ^5.0.2`) — pub-cache source + `ui-kit/flutter/v5`. **Official docs:** https://www.cometchat.com/docs/ui-kit/flutter/v5/overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP). Verify symbols against the installed package/source before relying on them.
+
 # CometChat Flutter UIKit v5 — Troubleshooting
 
 Symptom-to-cause lookup and verification checks.
@@ -66,8 +67,8 @@ Symptom-to-cause lookup and verification checks.
 
 | Symptom | Cause | Fix |
 |---------|-------|-----|
-| No push notifications | Token not registered | Call `PNRegistry.registerPNService(token, isFcm, isVoip)` |
-| Notifications after logout | Token not unregistered | Call `PNRegistry.unregisterPNService()` before logout |
+| No push notifications | Token not registered | Call `CometChatNotifications.registerPushToken(PushPlatforms.FCM_FLUTTER_ANDROID, fcmToken: token, ...)` after login (`PNRegistry.registerPNService` is a v5 sample-app extension, not a kit API — must be copied in; see cometchat-flutter-v5-push) |
+| Notifications after logout | Token not unregistered | Call `CometChatNotifications.unregisterPushToken(onSuccess:, onError:)` before logout |
 | Duplicate notifications | Foreground notification shown for active conversation | Check `conversationId` match before showing |
 | VoIP call notification doesn't show | Background handler not top-level | Use `@pragma('vm:entry-point')` on top-level function |
 | Tap doesn't navigate | `CallNavigationContext.navigatorKey.currentContext` is null | Ensure `navigatorKey` is set on MaterialApp |
@@ -78,8 +79,8 @@ Symptom-to-cause lookup and verification checks.
 | Symptom | Cause | Fix |
 |---------|-------|-----|
 | Release build crash | Missing ProGuard keep rules | Add `-keep class com.cometchat.** { *; }` |
-| Build fails with minSdk error | minSdk too low | Set `minSdk 26` in `android/app/build.gradle` |
-| AndroidX conflict | Missing AndroidX migration | Set `android.useAndroidX=true` in `gradle.properties` |
+| Build fails with minSdk error | minSdk too low | Set `minSdk 24` in `android/app/build.gradle` (matches vendor sample apps; bump to 26 ONLY if calls + min-SDK runtime errors) |
+| AndroidX conflict | Missing AndroidX migration | Set BOTH `android.useAndroidX=true` AND `android.enableJetifier=true` in `gradle.properties` |
 
 ## iOS Build Issues
 
@@ -108,7 +109,7 @@ If you see any of these in a v5 project, it's a v6 pattern that was accidentally
 | `extends Equatable` | Not used in v5 |
 | `ServiceLocator.get<T>()` | `Get.find<T>()` or let widget manage |
 | Single `cometchat_chat_uikit` with calls built-in | Separate `cometchat_calls_uikit` package |
-| Per-widget feature flags only — no `BuilderSettings` | `BuilderSettings`, `BuilderColor`, `BuilderTypography` |
+| Per-component style classes (e.g. `CometChatConversationsStyle`, `CometChatMessageListStyle`) + theme via `CometChatTheme` | Per-widget feature flags only (no BuilderSettings/BuilderColor/BuilderTypography in v5 — those are v4 leftovers) |
 | `enableCalls: true` + `CallingConfiguration()` on UIKitSettingsBuilder | `..callingExtension = CometChatCallingExtension()` |
 
 ## Verify Checklist

package/skills/cometchat-flutter-v5-users-groups/SKILL.md

@@ -3,13 +3,14 @@ name: cometchat-flutter-v5-users-groups
 description: "Use when working with CometChat Flutter UIKit v5 user and group list components. Triggers on CometChatUsers, CometChatGroups, CometChatGroupMembers, CometChatChangeScope."
 license: "MIT"
 compatibility: "cometchat_chat_uikit ^5.2.14; cometchat_uikit_shared ^5.2.3"
-allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"
   tags: "cometchat flutter v5 users groups members scope contacts"
 ---
 
+> **Ground truth:** `cometchat_chat_uikit: ^5.2` (legacy/maintenance-only; calls via raw `cometchat_calls_sdk ^5.0.2`) — pub-cache source + `ui-kit/flutter/v5`. **Official docs:** https://www.cometchat.com/docs/ui-kit/flutter/v5/overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP). Verify symbols against the installed package/source before relying on them.
+
 # CometChat Flutter UIKit v5 — Users & Groups
 
 Components for displaying and managing users, groups, and group members.
@@ -112,7 +113,7 @@ CometChatGroupMembers(
 )
 ```
 
-Key props: `group` (required), `groupMembersRequestBuilder`, `groupMembersStyle`, `subtitleView`, `trailingView`, `onItemTap` (`Function(GroupMember)?` — **no BuildContext**), `selectionMode`, `onSelection`.
+Key props: `group` (required), `groupMembersRequestBuilder`, **`style`** (`CometChatGroupMembersStyle?` — prop name is `style`, NOT `groupMembersStyle`; verified `cometchat_group_members.dart:25/88`), `subtitleView`, `trailingView`, `onItemTap` (`Function(GroupMember)?` — **no BuildContext**), `selectionMode`, `onSelection` (`Function(List<GroupMember>?)?` — no BuildContext).
 
 ## CometChatChangeScope
 

package/skills/cometchat-flutter-v6/SKILL.md

@@ -10,14 +10,15 @@ description: >
   authentication null. Also for adding chat to Flutter, customizing bubbles, theming,
   real-time messages. Use whenever user mentions CometChat or says "chat UI".
 license: "MIT"
-compatibility: "flutter >=2.5.0; dart >=2.17.0; cometchat_chat_uikit 6.0.0-beta2"
-allowed-tools: "shell, file-read, file-search, file-list, grep"
+compatibility: "flutter >=2.5.0; dart >=2.17.0; cometchat_chat_uikit ^6.0.1 (GA on pub.dev; resolves 6.0.x — 6.0.1 fixed the BLoC transition bug)"
 metadata:
   author: "CometChat"
   version: "3.0.0"
   tags: "cometchat flutter chat uikit messaging conversations bloc clean-architecture"
 ---
 
+> **Ground truth:** `cometchat_chat_uikit: ^6.0` — pub-cache source + `ui-kit/flutter`. **Official docs:** https://www.cometchat.com/docs/ui-kit/flutter/overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP). Verify symbols against the installed package/source before relying on them.
+
 # CometChat Flutter UIKit v6 — Orchestrator
 
 Entry point skill for the `cometchat_chat_uikit` package. Routes to feature skills based on context.
@@ -27,14 +28,14 @@ Entry point skill for the `cometchat_chat_uikit` package. Routes to feature skil
 Confirm the project uses CometChat UIKit by checking `pubspec.yaml` for:
 ```yaml
 dependencies:
-  cometchat_chat_uikit:
-    hosted: https://dart.cloudsmith.io/cometchat/cometchat/
-    version: 6.0.0-beta2
+  cometchat_chat_uikit: ^6.0.1   # V6 GA — plain pub.dev (do NOT use a `hosted:` Cloudsmith stanza)
 ```
 
+> **V6 GA lives on pub.dev, NOT Cloudsmith.** Cloudsmith (`dart.cloudsmith.io/cometchat/cometchat/`) only hosts the pre-GA `6.0.0-beta*` builds; a `--hosted-url`/`hosted:` Cloudsmith install of `^6.0.x` fails with "version solving failed". Use plain pub.dev. (Cloudsmith is only for the legacy **V5** packages — see `cometchat-flutter-v5`.) The GA range resolves `6.0.1`/`6.0.2`/`6.0.3`.
+
 If missing, install via:
 ```bash
-dart pub add cometchat_chat_uikit:6.0.0-beta2 --hosted-url https://dart.cloudsmith.io/cometchat/cometchat/
+dart pub add cometchat_chat_uikit:^6.0.1
 ```
 
 Call functionality is built into `cometchat_chat_uikit` — no separate package needed. To use call-specific types, import the calls barrel:
@@ -152,9 +153,9 @@ CometChatConversations(
   },
 )
 
-// 4. Messages screen (MUST use resizeToAvoidBottomInset: false)
+// 4. Messages screen — on ^6.0.1 use resizeToAvoidBottomInset: true (or omit it)
 Scaffold(
-  resizeToAvoidBottomInset: false, // REQUIRED
+  resizeToAvoidBottomInset: true, // ^6.0.1: composer clamps to viewInsets (ENG-34434); `false` is the pre-6.0.1 stopgap only. See cometchat-flutter-v6-core SCAFFOLD_NO_RESIZE.
   appBar: CometChatMessageHeader(
     user: user,
     group: group,
@@ -259,10 +260,10 @@ class _LoginScreenState extends State<LoginScreen> {
 
     CometChatUIKit.login(uid,
       onSuccess: (_) {
-        if (mounted) widget.onLoginSuccess();
+        if (mounted) { widget.onLoginSuccess(); }
       },
       onError: (e) {
-        if (mounted) setState(() { _loggingIn = false; _error = e.message; });
+        if (mounted) { setState(() { _loggingIn = false; _error = e.message; }); }
       },
     );
   }
@@ -341,7 +342,7 @@ class MessagesScreen extends StatelessWidget {
   @override
   Widget build(BuildContext context) {
     return Scaffold(
-      resizeToAvoidBottomInset: false, // REQUIRED — composer handles keyboard
+      resizeToAvoidBottomInset: true, // ^6.0.1: composer clamps to viewInsets (ENG-34434); `false` is the pre-6.0.1 stopgap only
       appBar: CometChatMessageHeader(
         user: user,
         group: group,
@@ -362,20 +363,20 @@ Key points in this scaffold:
 - `CometChatUIKit.loggedInUser` is checked synchronously after `init()` — no separate `getLoggedInUser()` call
 - State is managed at the `MyApp` level so login/logout transitions are clean
 - `LoginScreen` uses `CometChatUIKit.login(uid)` with auth key (set in UIKitSettings)
-- `MessagesScreen` has `resizeToAvoidBottomInset: false`
+- `MessagesScreen` has `resizeToAvoidBottomInset: true` (or omits it — `true` is the default; the composer clamps to `viewInsets` on ^6.0.1 per ENG-34434). `false` was the pre-6.0.1 stopgap only.
 - Logout calls `CometChatUIKit.logout()` and resets state
 
-## Top 10 Error Debugging
+## Common Error Debugging
 
 | Symptom | Cause | Fix |
 |---------|-------|-----|
 | "Authentication null" | `CometChatUIKit.init()` not called | Call init before login/components |
 | "APP ID null" | appId not set in UIKitSettingsBuilder | Set `..appId = 'YOUR_APP_ID'` |
-| Double keyboard compensation | Scaffold `resizeToAvoidBottomInset` is true | Set to `false` when using composer |
+| Double keyboard gap on `^6.0.1+` | Leftover pre-6.0.1 `resizeToAvoidBottomInset: false` workaround | Set it to `true` (or omit) — the composer clamps the keyboard internally on 6.0.1+ (ENG-34434); `false` is what now double-compensates. Upgrade the kit if you still see a gap with `true`. |
 | No typing indicators / presence | `subscriptionType` not set | Set `..subscriptionType = CometChatSubscriptionType.allUsers` |
 | Theme jank during keyboard | Theme looked up in `build()` | Cache in `didChangeDependencies()` with `_themeInitialized` flag |
 | Listener leak / duplicate events | Listener not removed in `dispose()` | Always remove with same ID used to register |
-| "ERR_ALREADY_LOGGED_IN" | Calling login when session exists | Check `CometChatUIKit.getLoggedInUser()` first |
+| "ERR_ALREADY_LOGGED_IN" | Calling login when session exists | Check `CometChatUIKit.loggedInUser != null` first (synchronous static field — aligns with §85 rule) |
 | Messages not updating in real-time | SDK listener not registered | BLoC registers automatically; check component is mounted |
 | Stale user/group data | Passing widget params instead of mutable state | Keep mutable `_user`/`_group` in State, update from listeners |
 | Region error | Uppercase region string | Use lowercase: 'us', 'eu', 'in' |
@@ -389,7 +390,7 @@ Key points in this scaffold:
 
 - If `pubspec.yaml` has `cometchat_chat_uikit` → proceed without asking
 - If credentials exist in code → reuse them, don't ask
-- If user says "messages screen" → generate Scaffold + Header + List + Composer with `resizeToAvoidBottomInset: false`
+- If user says "messages screen" → generate Scaffold + Header + List + Composer with `resizeToAvoidBottomInset: true` (or omit it — `true` is correct on ^6.0.1+)
 - Always add `subscriptionType` to UIKitSettingsBuilder
 - Always use `CometChatThemeHelper` for colors, never hardcode
 

package/skills/cometchat-flutter-v6-calls/SKILL.md

@@ -1,18 +1,17 @@
 ---
 name: cometchat-flutter-v6-calls
-description: CometChat Calls integration for Flutter UIKit v6 (Bloc-based, beta). ⚠️ Partially working at v6.0.0-beta2 (2026-05-13) — chat + calls init OK, outgoing call API succeeds, but TWO vendor bugs block end-to-end calling: (1) MaterialApp MUST set `navigatorKey: CallNavigationContext.navigatorKey` or the outgoing-call screen never renders ("Context is not mounted for navigation" — undocumented hard requirement); (2) even with the navigatorKey wired, the outgoing-call screen does NOT transition to the in-call view when peer accepts — call goes to `ongoing` at server level but UI stays on "Calling…" indefinitely, no client-side workaround. Customers shipping calls on Flutter today must stay on V5 cohort (cometchat_calls_uikit ^5.0.+). Covers UIKitSettings calling block, CometChatUIKitCalls.init() after CometChatUIKit.init() (CALLS_INIT_AFTER_CHAT_INIT), the kit's Bloc-driven CometChatCallButtons / CometChatIncomingCall / CometChatOutgoingCall / CometChatOngoingCall / CometChatCallLogs / CometChatCallBubble widgets, CallingConfiguration, native_call_kit module (iOS CallKit + Android ConnectionService), CallOperationsServiceLocator lifecycle, FCM + PushKit VoIP push, and additive-vs-standalone modes.
+description: "CometChat Calls integration for Flutter UIKit v6 (Bloc-based, stable). Production-ready at v6.0.1 GA (validated 2026-05-27 on Pixel 3) with ONE explicit MaterialApp wiring requirement still active from v6.0.0-beta2 — MaterialApp MUST wire navigatorKey to CallNavigationContext.navigatorKey or the outgoing-call screen never renders. (Vendor's own 6.0.1 sample is missing this line and broken out-of-the-box — file a vendor ticket if you find that sample first.) The earlier outgoing-to-in-call BLoC transition bug from beta2 is FIXED in 6.0.1 GA per the v6.0.0 changelog's 'Refreshed BLoC implementations across ongoing call flows' entry. Customers can now use V6 for calls. Covers UIKitSettings calling block, CometChatUIKitCalls.init() after CometChatUIKit.init() (CALLS_INIT_AFTER_CHAT_INIT), the kit's Bloc-driven CometChatCallButtons / CometChatIncomingCall / CometChatOutgoingCall / CometChatOngoingCall / CometChatCallLogs / CometChatCallBubble widgets, CallingConfiguration, CallOperationsServiceLocator lifecycle, VoIP push via external packages (FCM + PushKit + flutter_callkit_incoming — there is NO bundled native_call_kit module in the kit), and additive-vs-standalone modes."
 license: "MIT"
-compatibility: "Flutter >= 2.5, Dart >= 3.0; cometchat_chat_uikit ^6.0.0-beta2 (calls bundled in); minSdk 26+ on Android; iOS 13+"
-allowed-tools: "shell, file-read, file-search, file-list, ask-user"
+compatibility: "Flutter >= 2.5, Dart >= 3.0; cometchat_chat_uikit ^6.0.1 (calls bundled in); minSdk 26+ on Android; iOS 13+"
 metadata:
   author: "CometChat"
   version: "4.0.0"
-  tags: "cometchat flutter v6 beta calls voice video webrtc bloc incoming outgoing ongoing call-logs callkit pushkit connectionservice fcm voip-push native-call-kit call-operations service-locator"
+  tags: "cometchat flutter v6 ga calls voice video webrtc bloc incoming outgoing ongoing call-logs callkit pushkit connectionservice fcm voip-push native-call-kit call-operations service-locator"
 ---
 
 ## Purpose
 
-Production-grade voice + video calling for Flutter UIKit v6 (beta, Bloc-based). Loaded by `cometchat-calls` when `framework === "flutter"` and `flutter_version === "v6"`. Operates in two modes:
+Production-grade voice + video calling for Flutter UIKit v6 (stable, Bloc-based). Loaded by `cometchat-calls` when `framework === "flutter"` and `flutter_version === "v6"`. Operates in two modes:
 
 - **Standalone** — calls is the product. Chat SDK + Calls SDK without the v6 UI Kit (rare today, since the UI Kit ships calling bundled). Custom call screens on the SDKs.
 - **Additive** — calls layered onto an existing v6 chat integration. The v6 UI Kit ships call widgets in the same package (`cometchat_chat_uikit`) — no extra dependency. The skill enables calling on `UIKitSettings`, calls `CometChatUIKitCalls.init()` in the chat-init success callback, mounts the global incoming-call overlay at app root.
@@ -29,43 +28,64 @@ Production-grade voice + video calling for Flutter UIKit v6 (beta, Bloc-based).
 - V6 `CometChatUIKitCalls.init(appId, region)` must run AFTER `CometChatUIKit.init()` succeeds; V5 hides this via `CometChatCallingExtension`
 
 **Ground truth:**
-- SDK source — installed `cometchat_chat_uikit@6.0.0-beta2` artifacts under `~/.pub-cache/`
-- Sample app — `~/Downloads/calls-sdk/calls-sdk-flutter-5/sample-apps/` (V5 sample; V6 sample app may not exist yet — verify before citing)
+- SDK source — installed `cometchat_chat_uikit@6.0.1` artifacts under `~/.pub-cache/`
+- Sample app — `calls-sdk-flutter-5/sample-apps/` (V5 sample; V6 sample app may not exist yet — verify before citing)
 - Public docs — https://www.cometchat.com/docs/calls/flutter/overview (note: V6 docs may still reference V5 module split)
 
 ---
 
 ## 1. The seven hard rules — Flutter v6 specialization
 
-### 1.0 Calls SDK login is its own step (v5+)
+### 1.0 Calls SDK login — handled automatically when `enableCalls: true` (ENG-35699)
 
-Same as v5 cohort — the v5 Calls SDK has its own auth state, separate from the Chat SDK. After `CometChat.login` succeeds, you MUST also call `CometChatCalls.login` — without it, the FIRST calls API call throws **"auth token cannot be null"**.
+> **Single source of truth, verified against installed `cometchat_chat_uikit-6.0.1` source on 2026-06-01:** when you set `..enableCalls = true` on `UIKitSettingsBuilder` AND use `CometChatUIKit.init`/`login` (i.e. the V6 UIKit shape, the recommended path), **the kit's `CallEventService` calls `CometChatCalls.init()` AND `CometChatCalls.loginWithAuthToken(...)` for you internally** — once Chat SDK login resolves, the kit hands the auth token to the Calls SDK and brings it online. You do NOT need to call `CometChatCalls.login` yourself. See `lib/call_ui/src/call_event_service.dart` lines 87-197 in the installed package.
+>
+> The earlier version of this skill said "Same as v5 cohort — you MUST also call `CometChatCalls.login`." That's wrong for V6 UIKit usage. It IS correct only when the integration is **raw SDK (no UIKit)** — i.e. the developer imported `cometchat_calls_sdk` directly without going through `CometChatUIKit`. Most integrations don't.
 
-V6's `CometChatUIKitCalls.init()` initializes the SDK but does not handle login. Login still needs to happen explicitly after the user signs in via `CometChatUIKit.login`:
+**The V6 UIKit recipe (recommended — 99% of integrations):**
 
 ```dart
-import 'package:cometchat_sdk/cometchat_sdk.dart';
+final settings = (UIKitSettingsBuilder()
+      ..subscriptionType = CometChatSubscriptionType.allUsers
+      ..region = REGION
+      ..appId = APP_ID
+      ..authKey = AUTH_KEY
+      ..enableCalls = true)              // <-- this flag wires CallEventService
+    .build();
+
+CometChatUIKit.init(
+  uiKitSettings: settings,
+  onSuccess: (_) async {
+    await CometChatUIKit.login(uid);     // kit logs Chat SDK
+    // Calls SDK login fires INTERNALLY here via CallEventService.
+    // No manual CometChatCalls.login needed.
+  },
+  onError: (e) { /* surface */ },
+);
+```
+
+**Raw-SDK fallback (only if NOT using `CometChatUIKit`):**
+
+```dart
+// You should rarely need this in V6 — only when you've opted out of the UIKit
+// entirely and are wiring chat-sdk + calls-sdk by hand.
 import 'package:cometchat_calls_sdk/cometchat_calls_sdk.dart';
 
-// After CometChatUIKit.login resolves
+// Chat SDK login is POSITIONAL (cometchat.dart:843 — login(String uid, String authKey, {onSuccess, onError}))
+await CometChat.login(uid, AUTH_KEY, onSuccess: (User u) {}, onError: (CometChatException e) {});
+// Calls SDK login uses NAMED params; onError is CometChatCallsException (cometchatcalls.dart:224-228)
 CometChatCalls.login(
   uid: uid,
   authKey: AUTH_KEY,
   onSuccess: (User? callUser) { /* both ready */ },
-  onError: (CometChatException e) { /* surface to user */ },
-);
-
-// Production:
-CometChatCalls.loginWithAuthToken(
-  authToken: tokenFromBackend,
-  onSuccess: (User? user) { /* … */ },
-  onError: (CometChatException e) { /* … */ },
+  onError: (CometChatCallsException e) { /* surface */ },
 );
 ```
 
 **Surprises:**
-- Chat SDK persists login via shared preferences. The **Calls SDK does NOT** — always check `CometChatCalls.getLoggedInUser()` on app start and re-login if it returns null.
-- Even though V6 bundles the call UI into `CometChatUIKit`, the underlying Calls SDK login is still mandatory and separate.
+- The kit waits to log the Calls SDK in until Chat SDK login resolves; this is internal — your code only awaits Chat SDK login.
+- If you set `enableCalls = true` but Chat-SDK login never fires (init error, network), call buttons silently render but the internal `CometChatCalls.startSession` flow throws "auth token cannot be null" (there is no `startCall` method — the lifecycle is `startSession`/`joinSession`). The fix is to surface the Chat SDK login error, not to add a manual `CometChatCalls.login`.
+- Cross-reference: `references/add-calls-to-existing-chat.md` (additive-mode recipe) shows the same canonical pattern.
 
 ### 1.1 Dual-SDK contract — `CometChatUIKitCalls.init` after `CometChatUIKit.init`
 
@@ -94,19 +114,21 @@ CometChatUIKitCalls.init(appId, region);         // race — chat auth not ready
 
 After logout: the calls SDK session is invalidated; on next login, call `CometChatUIKitCalls.init()` again. Treat this as a "first run" of the calls subsystem.
 
-### 1.2 VoIP push — `native_call_kit` module + FCM + PushKit bridge
+### 1.2 VoIP push — external packages (FCM + CallKit/PushKit bridge)
+
+> **There is NO bundled `native_call_kit` module in `cometchat_chat_uikit` v6.** (Verified against the published `cometchat_chat_uikit` 6.0.1 source — no `native_call_kit` directory, and no `flutter_callkit_incoming` / CallKit / ConnectionService dependency in its `pubspec.yaml`.) VoIP push is wired with the SAME external packages the v5 family uses — the kit does not provide an OS-ring-UI module of its own.
 
-V6 ships a `native_call_kit` sub-module inside `cometchat_chat_uikit` that wraps CallKit (iOS) and ConnectionService (Android). The skill still wires:
+Wire VoIP push with:
 
-- **`firebase_messaging`** — FCM data messages on Android
-- **iOS PushKit** — same platform-channel bridge as v5 (Flutter has no first-party PushKit plugin)
-- **`native_call_kit` API** — Dart-side handlers for incoming-call payloads → OS-level ring UI
+- **`firebase_messaging`** — FCM data messages on Android (and iOS data path)
+- **`flutter_callkit_incoming`** — cross-platform OS-level incoming-call ring UI (iOS CallKit + Android ConnectionService); you add this package yourself
+- **iOS PushKit** — platform-channel bridge for VoIP pushes (Flutter has no first-party PushKit plugin) — same approach as v5
 
-In additive mode, opt-in. In standalone, mandatory.
+The Dart-side handler decodes the incoming-call payload from FCM/PushKit, shows the ring UI via `flutter_callkit_incoming`, and on accept routes into the kit's call surface. In additive mode this is opt-in; in standalone, mandatory.
 
 ### 1.3 Foreground service — same Android 14+ rules
 
-**⚠️ Android build prerequisite — Jetifier is mandatory.** One of the `cometchat_calls_uikit` transitive deps still pulls in the legacy `com.android.support:support-compat:26.1.0` AAR in V6. Without Jetifier, AGP fails with `Duplicate class android.support.v4.*` errors. Set in `android/gradle.properties`:
+**⚠️ Android build prerequisite — Jetifier is mandatory.** In V6 calls are bundled in `cometchat_chat_uikit` (there is no separate `cometchat_calls_uikit` package); one of its transitive deps still pulls in the legacy `com.android.support:support-compat:26.1.0` AAR. Without Jetifier, AGP fails with `Duplicate class android.support.v4.*` errors. Set in `android/gradle.properties`:
 
 ```properties
 android.useAndroidX=true
@@ -143,37 +165,34 @@ The kit's call widgets handle the basic teardown automatically; custom WebRTC su
 V6 ships an internal `CallPermissions` helper that wraps the standard permission flow:
 
 ```dart
-final granted = await CallPermissions.requestCallPermissions(callType: CallType.video);
+final granted = await CallPermissions.requestMicrophoneAndCamera(); // video; use requestMicrophone() for audio-only
 if (!granted) { /* surface a clear UI message */ }
 ```
 
 Native config (Info.plist + AndroidManifest) is identical to V5 (rule 1.6 in `cometchat-flutter-v5-calls`).
 
-### 1.7 IncomingCall mounted at app root
+### 1.7 IncomingCall — automatic when `enableCalls = true` (ENG-35698)
 
-V6 exposes the incoming-call overlay via `CometChatDisplayIncomingCallOverlay` mounted in `MaterialApp`'s `builder`:
+> **Canonical truth from `cometchat_chat_uikit-6.0.1`:** the kit's `CallEventService` automatically calls `IncomingCallOverlay.show(...)` from `lib/call_ui/src/incoming_call/cometchat_display_incoming_call_overlay.dart` whenever a foreground incoming call fires AND `enableCalls = true` is set on `UIKitSettingsBuilder`. You do NOT mount the overlay yourself. There is NO `CometChatDisplayIncomingCallOverlay` widget — that was a fictional class name from earlier drafts. The real class is `IncomingCallOverlay` (in `cometchat_display_incoming_call_overlay.dart`) and it's an imperative singleton (`.show(...)` / `.dismiss()`).
+
+**The correct V6 wiring is just the navigatorKey:**
 
 ```dart
 MaterialApp(
   navigatorKey: CallNavigationContext.navigatorKey,  // ⚠️ REQUIRED — see warning below
-  builder: (context, child) {
-    return Stack(
-      children: [
-        child!,
-        const CometChatDisplayIncomingCallOverlay(),
-      ],
-    );
-  },
+  home: const AppRoot(),                              // your existing root
 );
 ```
 
-**⚠️ `navigatorKey: CallNavigationContext.navigatorKey` is REQUIRED on MaterialApp at v6.0.0-beta2.** The kit's `CometChatCallButtons` and outgoing-call flow navigate via `CallNavigationContext.navigatorKey.currentContext`. Without this line, `CometChat.initiateCall` succeeds but the outgoing-call screen never renders — kit logs `"Context is not mounted for navigation"` and silently drops the navigation. Symptom: user taps call button, peer rings, but the Flutter app shows nothing.
+That's it. No `Stack`, no `builder` wrapper, no mounting of an "overlay widget" — once `enableCalls = true` is in your `UIKitSettingsBuilder`, the kit's `CallEventService` shows + dismisses `IncomingCallOverlay` for you when foreground rings happen.
+
+**⚠️ `navigatorKey: CallNavigationContext.navigatorKey` is REQUIRED on MaterialApp — still active in v6.0.1 GA.** The kit's `CometChatCallButtons` and outgoing-call flow navigate via `CallNavigationContext.navigatorKey.currentContext`. Without this line, `CometChat.initiateCall` succeeds (CALL-TRAP confirms `onSuccess` fires with a valid sessionId) but `currentContext` is null so `CometChatOutgoingCall` never mounts. Symptom: user taps call button, peer rings, but the Flutter app shows nothing. **Note: the vendor's own 6.0.1 sample app (`examples/sample_app`) is broken for calls on mobile out-of-the-box** — its `main.dart` sets `navigatorKey: kIsWeb ? CallNavigationContext.navigatorKey : null`, i.e. it wires the key **only on web** and passes `null` on Android/iOS, so the outgoing-call screen never mounts on a device (validated on Pixel 3). The kit's *other* sample (`examples/ai_sample_app`) sets it **unconditionally** (`navigatorKey: navigatorKey` + `CallNavigationContext.navigatorKey = navigatorKey`) — that is the correct, device-safe form this skill prescribes. **Wire `navigatorKey: CallNavigationContext.navigatorKey` unconditionally** (do NOT gate it on `kIsWeb` like `sample_app` does); don't copy `sample_app`'s `main.dart` verbatim.
 
 Import: `import 'package:cometchat_chat_uikit/cometchat_calls_uikit.dart' show CallNavigationContext;` (use `show` to avoid a name collision with kit-exported `IncomingCallOverlay`).
 
-**⚠️ Outgoing → in-call screen transition is broken at v6.0.0-beta2.** When the peer accepts, the call's status moves to `ongoing` at the server level — but the kit's outgoing-call screen does NOT transition to the in-call view. Users see the "Calling…" ring spinner indefinitely while the call is actually live. Pressing the reject button fires `CometChat.rejectCall` which the server rejects with `"The call status cannot be updated from ongoing to cancelled"`. **No client-side workaround known** — vendor needs to fix the outgoing-call BLoC's `onOutgoingCallAccepted` handler to push the in-call route. Validated on 2026-05-13 against a Next.js web peer.
+**✅ Outgoing → in-call screen transition is FIXED in v6.0.1 GA.** (It was broken in v6.0.0-beta2 — the outgoing-call screen stayed on "Calling…" indefinitely after the peer accepted.) Validated end-to-end 2026-05-27 on Pixel 3 with full CALL-TRAP instrumentation: with the navigatorKey wired (above), when the peer accepts, the kit's `OutgoingCallBloc` swaps the outgoing screen for the in-call surface automatically (via the kit's internal call-overlay — `CallScreenOverlay.show()`), transitioning from `CometChatOutgoingCall` ("Calling…") to the in-call view — observed call-duration timer ticking + WebRTC rendering frames @ ~27 fps. The v6.0.0 changelog's "Refreshed BLoC implementations across … call buttons, and ongoing call flows" was the fix. No client-side workaround needed beyond the navigatorKey wiring.
 
-In standalone mode, `native_call_kit` owns the OS-level ring UI; the in-app overlay only fires when the app is foregrounded.
+In standalone mode, `flutter_callkit_incoming` (the external package you add) owns the OS-level ring UI; the kit's in-app overlay only fires when the app is foregrounded.
 
 ---
 
@@ -184,19 +203,14 @@ In standalone mode, `native_call_kit` owns the OS-level ring UI; the in-app over
 dependencies:
   flutter:
     sdk: flutter
-  cometchat_chat_uikit: ^6.0.0-beta2     # calls bundled in
+  cometchat_chat_uikit: ^6.0     # calls bundled in
   permission_handler: ^11.0.0
   flutter_callkit_incoming: ^2.0.0       # standalone — VoIP UI bridge
   firebase_messaging: ^14.0.0            # standalone — Android FCM
   firebase_core: ^2.0.0
 ```
 
-If pub.dev resolution lags, use the Cloudsmith hosted pin:
-```yaml
-  cometchat_chat_uikit:
-    hosted: https://dart.cloudsmith.io/cometchat/cometchat/
-    version: ^6.0.0-beta2
-```
+> **V6 GA is on pub.dev — use the plain dependency above, NOT a Cloudsmith `hosted:` stanza.** Cloudsmith (`dart.cloudsmith.io/cometchat/cometchat/`) only hosts the pre-GA `6.0.0-beta*` builds, so a `hosted:` install of `^6.0.x` fails with "version solving failed". The GA range resolves `6.0.1`/`6.0.2`/`6.0.3` from pub.dev. (Cloudsmith is only for the legacy **V5** packages.)
 
 Init (additive mode):
 
@@ -207,7 +221,7 @@ import 'package:cometchat_chat_uikit/cometchat_calls_uikit.dart';
 void main() async {
   WidgetsFlutterBinding.ensureInitialized();
 
-  final settings = (UIKitSettings.builder()
+  final settings = (UIKitSettingsBuilder()
     ..appId = CometChatConfig.appId
     ..region = CometChatConfig.region
     ..authKey = CometChatConfig.authKey
@@ -247,7 +261,6 @@ call_ui/src/
 ├── call_operations/       # Shared DI / use cases / repositories (CallOperationsServiceLocator)
 ├── call_bubble/           # CometChatCallBubble — call-event bubble in message list (auto-rendered)
 ├── call_settings/         # CometChatUIKitCalls, CallNavigationContext
-├── native_call_kit/       # iOS CallKit / Android ConnectionService bridge
 ├── utils/                 # CallUtils, CallStateService, CallPermissions
 ├── call_event_service.dart  # Centralized call event handling
 └── calling_configuration.dart  # Top-level config object
@@ -258,9 +271,9 @@ call_ui/src/
 | Widget | Purpose | Notes |
 |---|---|---|
 | `CometChatCallButtons(user:, group:)` | Voice + video buttons | Mutually exclusive `user` / `group`. Use `group:` for group calls (meetings). |
-| `CometChatIncomingCall(call:, user:, onAccept:, onDecline:)` | In-app foreground ring UI | `onAccept`/`onDecline` are `(BuildContext, Call) -> void`. Custom view slots: `titleView`, `subTitleView`, `leadingView`, `trailingView`. |
+| `CometChatIncomingCall(call:, user:, onAccept:, onDecline:)` | In-app foreground ring UI | `onAccept`/`onDecline` are `(BuildContext, Call) -> void`. Custom view slots: `titleView`, `subTitleView`, `leadingView`, `trailingView`. ⚠️ **Param-name quirk:** this widget's settings param is `callSettingsBuilder:` (takes a `SessionSettingsBuilder`), NOT `sessionSettingsBuilder:` like Ongoing/Outgoing — verified `lib/call_ui/src/incoming_call/cometchat_incoming_call.dart`. |
 | `CometChatOutgoingCall(call:, user:, outgoingCallStyle:)` | Dialing UI | Auto-mounted when `initiateCall` is called via the kit. |
-| `CometChatOngoingCall(callSettingsBuilder:, sessionId:, callWorkFlow:)` | Active call view | `callWorkFlow: CallWorkFlow.directCalling` or `CallWorkFlow.defaultCalling`. Set `resizeToAvoidBottomInset: false` on host Scaffold. |
+| `CometChatOngoingCall(sessionSettingsBuilder:, sessionId:, callWorkFlow:)` | Active call view | **Param is `sessionSettingsBuilder:` NOT `callSettingsBuilder:`** (verified `lib/call_ui/src/ongoing_call/cometchat_ongoing_call.dart` constructor). `callWorkFlow: CallWorkFlow.directCalling` or `CallWorkFlow.defaultCalling`. Set `resizeToAvoidBottomInset: false` on host Scaffold. |
 | `CometChatCallLogs(onItemClick:, callLogsStyle:)` | Paginated history | Clean Architecture + BLoC; `CallLogsServiceLocator` is initialized automatically when the widget mounts. |
 | `CometChatCallBubble` | Call-event message bubble | Auto-rendered for call-type messages in `CometChatMessageList`. |
 
@@ -314,7 +327,7 @@ When `product === "voice-video"` and there is no v6 chat integration.
 Calls SDK ONLY. NO Chat SDK, NO UIKit. Same SDK as v5 (`cometchat_calls_sdk`). Scaffold:
 
 1. **`pubspec.yaml`** — `cometchat_calls_sdk: ^5.0.0` + `flutter_bloc` + `equatable` + `permission_handler` ONLY.
-2. **`lib/main.dart`** — `CometChatCalls.init(appId, region, authKey)`. Permission requests. NO Chat SDK init.
+2. **`lib/main.dart`** — `CometChatCalls.init((CallAppSettingBuilder()..appId = APP_ID..region = REGION).build(), onSuccess: ..., onError: ...)` (named-callback form; `CallAppSettingBuilder` exposes only `appId`/`region`/host overrides — there is NO `authKey` field. Verified `cometchat_calls_sdk-5.0.2` `src/builder/call_app_settings_request.dart` + `src/plugin/cometchatcalls.dart:172`). Permission requests. NO Chat SDK init.
 3. **`lib/cubits/call_session_cubit.dart`** — Cubit implements `SessionStatusListeners`. `CometChatCalls.joinSession(sessionId:, sessionSettings: SessionSettingsBuilder().build(), onSuccess:, onError:)`. Renders the returned `Widget?` via `SizedBox.expand`. See `references/call-session.md`.
 4. **`lib/screens/call_room.dart`** — `BlocConsumer` for auto-pop on idle transition.
 5. **Native config** — Camera + microphone permissions only.
@@ -326,20 +339,20 @@ Calls SDK ONLY. NO Chat SDK, NO UIKit. Same SDK as v5 (`cometchat_calls_sdk`). S
 Dual-SDK + UIKit. Scaffold:
 
 1. **`lib/main.dart`** — Chat SDK + Calls SDK init (no UIKit), permission requests, `flutter_callkit_incoming` + Firebase setup.
-2. **`lib/services/voip_service.dart`** — FCM + PushKit + `native_call_kit` bridge.
+2. **`lib/services/voip_service.dart`** — FCM + PushKit + `flutter_callkit_incoming` bridge (you write this; the kit ships no VoIP/ring-UI module).
 3. **`lib/widgets/call_button.dart`** — Voice + video buttons next to a contact.
 4. **`lib/screens/ongoing_call_screen.dart`** — `CometChatCalls.joinSession(sessionId:, sessionSettings:, onSuccess:, onError:)` with Widget rendered via `SizedBox.expand`. Cubit-driven state.
 5. **`lib/screens/call_logs_screen.dart`** — `/calls` route.
-6. **`MaterialApp.builder`** — `CometChatDisplayIncomingCallOverlay` for foreground rings (rule 1.7).
+6. **`MaterialApp`** — `navigatorKey: CallNavigationContext.navigatorKey` wired; `enableCalls = true` on UIKitSettingsBuilder shows the foreground overlay automatically (rule 1.7). No widget mount needed.
 7. **Native config** — same as V5 standalone (Info.plist + AndroidManifest + Firebase config files).
 
 ## 5. Additive integration
 
 When chat is already integrated. The skill:
 
-1. Confirms `cometchat_chat_uikit` is on `^6.0.0-beta2` — calls are already bundled.
+1. Confirms `cometchat_chat_uikit` is on `^6.0.1` — calls are already bundled.
 2. Patches the `CometChatUIKit.init` call to add `CometChatUIKitCalls.init` in the success callback (rule 1.1).
-3. Adds `CometChatDisplayIncomingCallOverlay` to `MaterialApp.builder` (rule 1.7).
+3. Confirms `..enableCalls = true` is set on UIKitSettingsBuilder (rule 1.0) so foreground overlay fires automatically; ensures `navigatorKey: CallNavigationContext.navigatorKey` is on MaterialApp (rule 1.7).
 4. Confirms `CometChatMessageHeader` shows call buttons by default (`hideVoiceCallButton: false`, `hideVideoCallButton: false`).
 5. Optionally adds `CometChatCallLogs` as a tab/screen.
 6. VoIP push: opt-in.
@@ -359,10 +372,11 @@ When chat is already integrated. The skill:
 
 **Static:**
 
-- [ ] `cometchat_chat_uikit ^6.0.0-beta2` in pubspec.yaml (V6 bundles calls — no separate calls package)
+- [ ] `cometchat_chat_uikit ^6.0.1` in pubspec.yaml (V6 bundles calls — no separate calls package)
 - [ ] `CometChatUIKitCalls.init` called inside `CometChatUIKit.init`'s `onSuccess` (rule 1.1)
 - [ ] `CometChatUIKitCalls.init` called exactly once per app lifecycle
-- [ ] `CometChatDisplayIncomingCallOverlay` mounted in `MaterialApp.builder` (rule 1.7)
+- [ ] `..enableCalls = true` on UIKitSettingsBuilder + `navigatorKey: CallNavigationContext.navigatorKey` on MaterialApp (rule 1.7) — no manual overlay widget mount
+- [ ] No reference to `CometChatDisplayIncomingCallOverlay` (fictional class — does NOT exist; ENG-35698)
 - [ ] iOS `Info.plist`: NSCameraUsageDescription + NSMicrophoneUsageDescription + UIBackgroundModes (audio + voip + remote-notification)
 - [ ] Android `minSdk = 26`, ProGuard rules `-keep class com.cometchat.** { *; }`
 - [ ] Android manifest: four FOREGROUND_SERVICE_* permissions + MANAGE_OWN_CALLS + BIND_TELECOM_CONNECTION_SERVICE
@@ -384,6 +398,7 @@ When chat is already integrated. The skill:
 
 ## 8. Pointers
 
+- `references/advanced-features.md` — Recording, Virtual Background, Audio Modes, Picture-in-Picture, Screen-share (receive) — source-verified against `cometchat_calls_sdk` 5.0.2
 - `cometchat-calls` — dispatcher
 - `cometchat-flutter-v6-core` — UIKitSettings, init/login order, init guard rules
 - `cometchat-flutter-v6-events` — Bloc event streams
@@ -394,5 +409,5 @@ When chat is already integrated. The skill:
 
 ## Known external SDK gotchas (worth surfacing in any agent message)
 
-- `startSession` on Android can return `null` with a 5-second timeout and no error feedback — known platform issue; retry once before surfacing failure.
-- `SessionType.audio` is ignored on Android in some V6 SDK builds — always opens with video. External SDK bug; track upstream.
+- `startSession` on Android can return `null` with a 5-second timeout and no error feedback — **field-observed on Pixel 3, not confirmed in the SDK source**; retry once before surfacing failure. (Audio vs video is driven by the Chat-SDK `Call.type` string — there is no `SessionType` enum in the calls SDK.)
+- Audio-only calls have been observed opening with video on Android in some builds (field-observed; verify against your installed SDK version) — set the call type explicitly via the Chat-SDK `Call(type: "audio")` and confirm the rendered surface.