@cometchat/skills 4.4.2 → 5.0.1

package/skills/cometchat-react-native-bare-patterns/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: cometchat-react-native-bare-patterns
+description: "Bare React Native CLI wiring for the CometChat UI Kit v5 — pod install, Android manifest permissions, and the gesture-handler import that must be the first line of your entry file. Triggers: CometChat React Native CLI, pod install CometChat, RN chat crashes on Android build, gesture handler crash release build, AndroidManifest CometChat permissions."
+license: "MIT"
+compatibility: "React Native >=0.77 (CLI / bare); @cometchat/chat-uikit-react-native ^5.4.0"
+metadata:
+  author: "CometChat"
+  version: "1.0.0"
+  tags: "chat cometchat react-native cli bare pods gradle manifest gesture-handler"
+---
+
+> **Ground truth:** `@cometchat/chat-uikit-react-native@5` + catalog `rn-v5.json`.
+> Docs: `/ui-kit/react-native/react-native-cli-integration` · `react-native-conversation` ·
+> `react-native-tab-based-chat`.
+
+## Companion skills (read first)
+- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.
+- `cometchat-react-native-expo-patterns` — the Expo equivalent. Use that one for an Expo project.
+
+## Use this skill when
+- the project has real `ios/` and `android/` directories and **no** `expo` key in `app.json`
+- "add chat to my React Native CLI app" · "Android build fails after installing CometChat"
+
+## Prerequisites & install
+
+```bash
+npm install @cometchat/chat-uikit-react-native@5 @cometchat/chat-sdk-react-native@4
+npm install @react-native-clipboard/clipboard \
+  react-native-svg react-native-video react-native-localize react-native-gesture-handler \
+  react-native-safe-area-context @react-native-async-storage/async-storage@^2.1.2 dayjs
+cd ios && pod install && cd ..
+```
+
+You own `ios/` and `android/`, so native config is edited **directly** — the opposite of Expo, where
+those directories are generated and hand-edits get overwritten.
+
+## The four native steps that are not optional
+
+### 1. `react-native-gesture-handler` must be the FIRST import of your entry file
+```js title="index.js"
+import 'react-native-gesture-handler';
+// …every other import after this
+```
+Not at the top of a screen — the **very top of `index.js`**, before anything else. Getting this wrong
+often works in debug and **crashes in release**, which is the worst possible failure shape: it passes
+local testing and breaks for users.
+
+### 2. iOS Podfile needs modular headers for two transitive pods
+`@cometchat/chat-uikit-react-native` is a **Swift** pod that depends on `SPTPersistentCache`
+and `DVAssetLoaderDelegate`, neither of which defines a module. On a static-library build —
+the React Native default — `pod install` **fails outright**:
+
+> The Swift pod `react-native-cometchat-ui-kit` depends upon `SPTPersistentCache` and
+> `DVAssetLoaderDelegate`, which do not define modules.
+
+Add these inside your target in `ios/Podfile`, then re-run `pod install`:
+
+```ruby title="ios/Podfile"
+target 'YourApp' do
+  pod 'SPTPersistentCache', :modular_headers => true
+  pod 'DVAssetLoaderDelegate', :modular_headers => true
+  # …
+end
+```
+
+Both official CometChat sample apps carry exactly these two lines. The integration docs do
+not mention them (**RN-G14**), so a first `pod install` fails with an error that names two
+pods the developer has never heard of.
+
+### 3. Android permissions in the manifest
+`android/app/src/main/AndroidManifest.xml` — `INTERNET` at minimum; the camera/audio set only if you
+add calling. Fetch the exact list from the integration page rather than copying a partial set.
+
+## Calling on bare RN
+```bash
+npm install @cometchat/calls-sdk-react-native@5
+# 6 REQUIRED peer deps — the calls SDK's declared peerDependencies. Pinned; do NOT float them.
+npm install @react-native-async-storage/async-storage@^2.1.2 react-native-background-timer@^2.4.1 \
+  react-native-performance@^5.1.2 react-native-svg@^15.12.0 react-native-url-polyfill@2.0.0 \
+  react-native-webrtc@124.0.7
+cd ios && pod install && cd ..
+```
+⚠️ `react-native-url-polyfill` + `react-native-performance` are **bundle-critical** (the UIKit
+module-scope `require()`s the calls SDK, so Metro resolves its peers even in a chat-only build). Keep
+`react-native-performance` on **5.x** (a floated `^6` breaks later `npm install` with ERESOLVE).
+`@react-native-community/netinfo` / `react-native-callstats` are NOT declared peers — do not add them.
+
+iOS permissions go in `ios/<YourApp>/Info.plist`:
+
+```xml
+<key>NSCameraUsageDescription</key>
+<string>Camera access for video calls</string>
+<key>NSMicrophoneUsageDescription</key>
+<string>Microphone access for voice/video calls</string>
+```
+
+Simulators cannot capture camera or microphone — verify calls on a real device.
+
+## After any native change — rebuild, don't reload
+Metro reload only refreshes JavaScript. A new native module, a Gradle edit or a plist change needs a
+full rebuild (`npx react-native run-ios` / `run-android`). "I installed it and nothing changed" is
+almost always a missed rebuild.
+
+## What is the same as Expo
+Everything above the native layer: providers, `init → login → render`, components, theming,
+navigation. Only install and native config differ.
+
+## Common pitfalls
+1. **`gesture-handler` imported late** — works in debug, crashes in release.
+2. **Missing the Podfile modular-headers lines** — `pod install` fails, naming two unfamiliar transitive pods.
+3. **Skipping `pod install`** after adding a package — iOS fails to link.
+4. **Reloading instead of rebuilding** after a native change.
+5. **Copying Expo's `app.json` permission block** into a bare app — it does nothing there.
+
+## Verify it works
+- `index.js` starts with the gesture-handler import.
+- iOS and Android both build clean from scratch.
+- `npm run verify:fences:rn-v5` is green.
+- On device: chat renders, gestures respond, the composer survives the keyboard. Test a **release**
+  build too — the gesture-handler ordering bug only shows there.

package/skills/cometchat-react-native-calls/SKILL.md

@@ -0,0 +1,200 @@
+---
+name: cometchat-react-native-calls
+description: "Voice and video calling in the CometChat React Native UI Kit v5 — the RN calls SDK, the native permissions and version floors it needs, and why installing the package is itself the enable switch. Triggers: add video calling React Native, CometChat voice call RN, incoming call screen RN, calls not ringing React Native, webrtc CometChat."
+license: "MIT"
+compatibility: "React Native >=0.77; @cometchat/chat-uikit-react-native ^5.4.0; @cometchat/calls-sdk-react-native ^5.0.4; Android minSdk 24; iOS 13.0"
+metadata:
+  author: "CometChat"
+  version: "1.0.0"
+  tags: "chat cometchat react-native calls voice video webrtc permissions"
+---
+
+> **Ground truth:** `@cometchat/calls-sdk-react-native@5` + catalog `rn-calls-v5.json` (58 symbols) +
+> `features.rn-v5.json` → `voice-video-calls`. Docs: `/ui-kit/react-native/calling-integration` ·
+> `call-features` · `call-buttons` · `call-logs` · `incoming-call` · `outgoing-call`.
+
+## Companion skills (read first)
+- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.
+
+## Use this skill when
+- "add voice/video calling" · "incoming call screen" · "calls aren't ringing" · "call logs"
+
+## Prerequisites & install
+
+⚠️ **React Native has its OWN calls SDK.** `@cometchat/calls-sdk-javascript` is the web package and
+will not work here.
+
+```bash
+npm install @cometchat/calls-sdk-react-native@5
+# 6 REQUIRED peer deps — the SDK's declared peerDependencies. Versions are pinned; do NOT float them.
+npm install @react-native-async-storage/async-storage@^2.1.2 react-native-background-timer@^2.4.1 \
+  react-native-performance@^5.1.2 react-native-svg@^15.12.0 react-native-url-polyfill@2.0.0 \
+  react-native-webrtc@124.0.7
+# ⚠️ react-native-performance MUST stay 5.x — 6.x is published, and a floated `^6` makes every later
+#    `npm install` in the app fail with ERESOLVE. react-native-url-polyfill + react-native-performance
+#    are BUNDLE-critical: the UIKit does a module-scope require() of the calls SDK, so Metro resolves
+#    them even for a chat-only build — omit either and the bundle fails with "Unable to resolve module".
+#    (NOT react-native-community/netinfo or react-native-callstats — those are not declared peers.)
+cd ios && pod install && cd ..     # bare RN;  Expo: npx expo run:ios
+```
+
+## Enabling calls — there is no flag
+
+**Installing the package IS the switch.** The kit does a `try { require("@cometchat/calls-sdk-react-native") }`
+at startup; if it resolves, calling is enabled automatically.
+
+React's `setCallingEnabled(true)` **does not exist in this kit** — do not emit it. There is likewise **no
+opt-out on the `initFromSettings` golden path** — the `CometChatSettings` file/object has no calling field,
+and `CometChatUIKit.initFromSettings()` never reads one. `disableCalling: true` exists **only** as a field
+on the `UIKitSettings` object you pass to the legacy `CometChatUIKit.init(uiKitSettings)` — so to disable
+calling while the package stays installed you must switch to that `init()` entry point (or simply not
+install the calls SDK).
+
+Consequence worth knowing: a half-finished install (package added, pods not run) can leave calling
+"enabled" in JS while the native side is missing — which surfaces as a crash on first call rather than
+a clear error at startup.
+
+## Native floors — below these it will not build
+
+| Platform | Requirement | Where |
+|---|---|---|
+| Android | `minSdkVersion 24` | `android/app/build.gradle` |
+| iOS | `IPHONEOS_DEPLOYMENT_TARGET` 13.0 | Xcode target or a Podfile `post_install` |
+
+## Permissions — camera and microphone
+
+**Bare RN** — `ios/<App>/Info.plist`:
+```xml
+<key>NSCameraUsageDescription</key><string>Camera access for video calls</string>
+<key>NSMicrophoneUsageDescription</key><string>Microphone access for voice/video calls</string>
+```
+Android: `CAMERA` · `RECORD_AUDIO` · `MODIFY_AUDIO_SETTINGS` · `BLUETOOTH_CONNECT` (Android 12+, Bluetooth audio routing) in `AndroidManifest.xml`.
+
+**Expo** — the same values go in `app.json` (`ios.infoPlist`, `android.permissions`), then rebuild.
+Never hand-edit the generated native projects.
+
+## Components (from `catalogs/rn-v5.json`)
+
+| Component | Purpose |
+|---|---|
+| `CometChatCallButtons` | audio/video triggers — the message header shows these by default |
+| `CometChatIncomingCall` | the ring screen — **mount once above the navigator** |
+| `CometChatOutgoingCall` | the dialling screen |
+| `CometChatOngoingCall` | the in-call surface (**no React equivalent**) |
+| `CometChatCallLogs` | call history **list** |
+
+`CometChatIncomingCall` mounted inside one screen means calls only arrive while that screen is open —
+the commonest "calls don't ring" cause after a missing permission.
+
+The table above is not enough to copy — wire it:
+
+```tsx
+// App.tsx — IncomingCall sits ABOVE the navigator so a call rings on any screen.
+function App() {
+  const incomingCall = useRef<CometChat.Call | null>(null);
+  const [callReceived, setCallReceived] = useState(false);
+
+  useEffect(() => {
+    const listenerId = "APP_CALL_LISTENER";
+    CometChat.addCallListener(
+      listenerId,
+      new CometChat.CallListener({
+        onIncomingCallReceived: (call) => {
+          incomingCall.current = call;
+          setCallReceived(true);
+        },
+        onOutgoingCallRejected: () => setCallReceived(false),
+        onIncomingCallCancelled: () => setCallReceived(false),
+      }),
+    );
+    return () => CometChat.removeCallListener(listenerId);   // or it fires after unmount
+  }, []);
+
+  return (
+    <GestureHandlerRootView style={{ flex: 1 }}>
+      <NavigationContainer>{/* … */}</NavigationContainer>
+      {callReceived && incomingCall.current ? (
+        <CometChatIncomingCall
+          call={incomingCall.current}
+          onDecline={() => { incomingCall.current = null; setCallReceived(false); }}
+        />
+      ) : null}
+    </GestureHandlerRootView>
+  );
+}
+```
+
+```tsx
+// Call triggers — the message header renders these by default; mount them yourself only
+// when you build a custom header. onError is the ONLY callback: success is an event
+// (ccOutgoingCall), not a promise.
+<CometChatCallButtons user={user} group={group} onError={(e) => console.error(e)} />
+
+// Dialling screen — driven by the Call object you created.
+{call && <CometChatOutgoingCall call={call} />}
+
+// Call history list. Detail screens do NOT ship (see below).
+<CometChatCallLogs onItemPress={(log) => openCallDetail(log)} />
+```
+
+```tsx
+// The in-call surface. sessionID comes from the accepted Call; callSettingsBuilder is a
+// CometChatCalls builder, NOT a chat-SDK one.
+<CometChatOngoingCall
+  sessionID={sessionId}
+  callSettingsBuilder={callSettings}
+  onError={(e) => console.error(e)}
+/>
+```
+
+> **DOCS GAP (RN-G15 — narrowed upstream, verified 2026-09-09):** `CometChatOngoingCall` is exported by
+> the RN kit and is now **listed** on `/ui-kit/react-native/call-features` (the Components row), but it
+> still has **no dedicated props page** — only Incoming / Outgoing / Buttons / Logs get their own pages.
+> The fence above is a **STOPGAP built from the kit's own types** — replace it once a props page ships.
+> Flagged for the docs team; do not conclude the component is unavailable on RN.
+
+## Call logs: the list ships, the detail screens do not
+Kit v5 removed `CometChatCallLogDetails` / `History` / `Participants` / `Recordings`. For a custom detail
+view, fetch the history yourself with the **Calls-SDK** `CallLogRequestBuilder` — a static on
+`CometChatCalls`, reachable only from `@cometchat/calls-sdk-react-native`:
+
+```ts
+// Call history — CometChatCalls.CallLogRequestBuilder from the CALLS SDK.
+// There is NO CallLogRequestBuilder on the Chat SDK (@cometchat/chat-sdk-react-native).
+import { CometChat } from "@cometchat/chat-sdk-react-native";
+import { CometChatCalls } from "@cometchat/calls-sdk-react-native";
+// fetchNext() REJECTS without an auth token ("`Auth Token` is required") — no fallback. Pass the
+// logged-in user's token, exactly as the kit's own CometChatCallLogs does.
+const authToken = (await CometChat.getLoggedinUser())?.getAuthToken() ?? "";
+const req = new CometChatCalls.CallLogRequestBuilder().setLimit(30).setAuthToken(authToken).build();
+const logs = await req.fetchNext();
+
+// Transcript opt-in — same builder + token. setHasTranscriptions(true) filters to transcribed calls
+// AND makes the server attach each call's transcripts to the log.
+const treq = new CometChatCalls.CallLogRequestBuilder().setLimit(30).setAuthToken(authToken).setHasTranscriptions(true).build();
+```
+
+> **RN-G9 (verified 2026-09-10 vs `@cometchat/calls-sdk-react-native@5`):** `CallLogRequestBuilder` is a
+> static on `CometChatCalls` (calls SDK) — `new CometChatCalls.CallLogRequestBuilder()`. It does **not**
+> exist on the Chat SDK: there is no `CometChat.CallLogRequestBuilder` in `@cometchat/chat-sdk-react-native`
+> (any version). Use the Calls-SDK builder for history, always with `.setAuthToken(...)` (without it `fetchNext()`
+> rejects — verified in `@cometchat/calls-sdk-react-native@5.0.5`); add `setHasTranscriptions(true)` only when you need
+> transcripts. It is reachable as a static on the module, not as a bare named import.
+
+## Verification requires a real device
+**Simulators and emulators cannot capture camera or microphone.** A green simulator run proves the
+screens render, not that a call connects. Media, permissions and ringing must be checked on hardware.
+
+## Common pitfalls
+1. **Installing the web calls SDK** — wrong package.
+2. **Emitting `setCallingEnabled(true)`** — does not exist; installation is the switch.
+3. **`CometChatIncomingCall` inside a screen** — calls only ring there.
+4. **Skipping `pod install` / rebuild** — crash on first call, not at startup.
+5. **Below the version floors** — build failure, not a runtime message.
+6. **Signing off from a simulator** — no media capture.
+
+## Verify it works
+- Every emitted symbol is in `catalogs/rn-v5.json` or `catalogs/rn-calls-v5.json`.
+- `npm run verify:fences:rn-v5` is green.
+- **On two real devices:** call connects both ways, permission prompts appear on first use, the
+  incoming screen shows while the app is on any tab, and the call log records the call.

package/skills/cometchat-react-native-components/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: cometchat-react-native-components
+description: "The closed list of CometChat React Native UI Kit v5 components, what each one is for, and how to put custom UI INSIDE a component's view slot instead of stacking it on top. Triggers: which CometChat component React Native, custom header RN chat, add a button to the conversation list, custom list item RN, CometChat component list, add an avatar to my chat, show a profile picture, status indicator RN, badge RN, list item RN."
+license: "MIT"
+compatibility: "React Native >=0.77; @cometchat/chat-uikit-react-native ^5.4.0"
+metadata:
+  author: "CometChat"
+  version: "1.0.0"
+  tags: "chat cometchat react-native components slots views composition"
+---
+
+> **Ground truth:** catalog `rn-v5.json` (216 public symbols) — the closed list below IS the catalog.
+> A component not in it does not exist. Fetch props per component via `core/references/docs-map.md`.
+
+## Companion skills (read first)
+- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.
+
+## Use this skill when
+- "which component do I use for X" · "add a button to the conversation list header"
+- "custom list row" · "replace the message bubble" · "what components ship in v5"
+
+## Prerequisites & install
+None beyond `core`.
+
+## Component catalog (closed list)
+
+**Lists**
+| Component | Purpose |
+|---|---|
+| `CometChatConversations` | recent-conversations list — the usual entry screen |
+| `CometChatUsers` | user directory |
+| `CometChatGroups` | group directory |
+| `CometChatGroupMembers` | **active** members of a group (not banned — see below) |
+
+**Message pane**
+| Component | Purpose |
+|---|---|
+| `CometChatMessageHeader` | title, presence, back, call buttons |
+| `CometChatMessageList` | the scrollback; renders bubbles, receipts, reactions |
+| `CometChatMessageComposer` | input, attachments, voice notes |
+| `CometChatCompactMessageComposer` | single-line composer for tight layouts |
+| `CometChatThreadHeader` | thread replies — a **screen** on RN, not a side panel |
+| `CometChatMessageInformation` | per-message delivery/read detail |
+
+**Search · AI · notifications**
+| Component | Purpose |
+|---|---|
+| `CometChatSearch` | message + conversation search |
+| `CometChatAIAssistantChatHistory` · `CometChatAIAssistantTools` | AI assistant surfaces |
+| `CometChatConversationStarter` · `CometChatSmartReplies` · `CometChatConversationSummary` | AI suggestions |
+| `CometChatNotificationFeed` | in-app notification feed |
+
+**Calling** — needs `@cometchat/calls-sdk-react-native`
+| Component | Purpose |
+|---|---|
+| `CometChatCallButtons` | audio/video call triggers |
+| `CometChatIncomingCall` · `CometChatOutgoingCall` · `CometChatOngoingCall` | call lifecycle screens |
+| `CometChatCallLogs` | call history **list** (detail views were removed in v5) |
+
+**Bubbles** — the list renders these itself; place them only in a custom template
+`CometChatTextBubble` · `CometChatImageBubble` · `CometChatVideoBubble` · `CometChatAudioBubble` ·
+`CometChatFileBubble` · `CometChatVoiceNoteBubble` · `CometChatStickerBubble` ·
+`CometChatCollaborativeDocumentBubble` · `CometChatCollaborativeWhiteBoardBubble` · `CometChatMeetCallBubble`
+
+**Multi-attachment — RN only, no React equivalent**
+`CometChatAttachmentPreview` · `CometChatAttachmentPreviewItem` · `CometChatAttachmentTile` ·
+`CometChatAttachmentTray` · `CometChatAttachmentViewer` and the **plural** bubbles
+`CometChatImagesBubble` · `CometChatVideosBubble` · `CometChatAudiosBubble` · `CometChatFilesBubble`.
+> **DOCS GAP (RN-G4):** all nine are undocumented. Build from the kit source and say so.
+
+**Not components — but public and load-bearing**
+`ChatConfigurator` · `DataSourceDecorator` · `CometChatMessageTemplate` (custom message types →
+`customization`) · `CometChatThemeProvider` + `useTheme()` · `CometChatI18nProvider` ·
+`CometChatUIEventHandler` · `CometChatUiKitConstants`.
+
+**Primitives & building blocks** — exported, and what you reach for when composing a custom row,
+header or bubble yourself. Existence is baked here; **fetch each one's props from the docs**
+(`core/references/docs-map.md`) — do not infer them from `.d.ts`.
+| Group | Exports |
+|---|---|
+| Identity | `CometChatAvatar` · `CometChatStatusIndicator` · `CometChatBadge` · `CometChatDate` |
+| Row shell | `CometChatListItem` |
+| Overlays | `CometChatActionSheet` · `CometChatBottomSheet` · `CometChatConfirmDialog` · `CometChatReportDialog` · `CometChatMediaViewer` |
+| Composer add-ons | `CometChatEmojiKeyboard` · `CometChatMediaRecorder` · `CometChatInlineAudioRecorder` · `CometChatCreatePoll` · `CometChatSuggestionList` · `CometChatMessagePreview` · `CometChatMessageComposerAction` · `CometChatMessageOption` |
+| Reactions | `CometChatReactions` · `CometChatQuickReactions` · `CometChatReactionList` |
+| Text formatters | `CometChatTextFormatter` · `CometChatMentionsFormatter` · `CometChatUrlsFormatter` · `CometChatRichTextFormatter` |
+| Helpers | `CometChatUIKit` · `CometChatUIKitHelper` · `CometChatSoundManager` |
+
+> Changing a user's own avatar/name is **not** a component — it is the SDK call
+> `CometChat.updateCurrentUserDetails()`; see `cometchat-react-native-sdk`.
+
+### Components that do NOT exist in v5
+`CometChatErrorBoundary` · `CometChatDetails` · `CometChatAddMembers` · `CometChatBannedMembers` ·
+`CometChatTransferOwnership` · `CometChatContacts` · every `*WithMessages` composite ·
+`CometChatCallLogDetails` / `History` / `Participants` / `Recordings`.
+They were removed in kit v5. Each has an SDK-fallback path in `core/references/docs-map.md` —
+**banned members has no UI surface at all**, so an app that bans must also wire view + unban.
+
+## Custom UI goes IN a slot, not on top
+
+Every list and header exposes **view slots**. Custom UI belongs inside the slot so the component keeps
+its own layout, scrolling and empty/error states. Stacking a sibling above the list is the classic
+mistake — it double-renders headers and breaks scroll.
+
+⚠️ **RN slot props are PascalCase.** React's are camelCase; a ported snippet silently does nothing
+because an unknown prop is simply ignored.
+
+| Component | Slots |
+|---|---|
+| `CometChatConversations` | `ItemView` · `TitleView` · `SubtitleView` · `LeadingView` · `TrailingView` · `SearchView` · `EmptyView` · `ErrorView` · `LoadingView` |
+| `CometChatUsers` / `CometChatGroups` | `ItemView` · `TitleView` · `SubtitleView` · `LeadingView` · `TrailingView` · `EmptyView` · `ErrorView` · `LoadingView` |
+| `CometChatMessageHeader` | `ItemView` · `TitleView` · `SubtitleView` · `LeadingView` · `TrailingView` · `AuxiliaryButtonView` |
+| `CometChatMessageList` | `HeaderView` · `FooterView` · `EmptyView` · `ErrorView` · `LoadingView` |
+| `CometChatMessageComposer` | `HeaderView` · `SendButtonView` · `AuxiliaryButtonView` · `CustomView` |
+
+```tsx
+import { CometChatConversations } from "@cometchat/chat-uikit-react-native";
+import { Pressable, Text } from "react-native";
+
+<CometChatConversations
+  TrailingView={() => (
+    <Pressable onPress={onArchive}>
+      <Text>Archive</Text>
+    </Pressable>
+  )}
+/>;
+```
+
+Slot names differ per component — fetch the exact list from that component's docs page rather than
+copying from a sibling.
+
+## Common pitfalls
+1. **camelCase slot props** — `itemView` is ignored silently. RN uses `ItemView`.
+2. **Rendering a sibling above a list** instead of using its slot — duplicate headers, broken scroll.
+3. **Placing a bubble component directly** — the list renders bubbles; use a template (`customization`).
+4. **Reaching for a removed component** — check the closed list above before emitting.
+5. **Assuming `CometChatGroupMembers` covers banned users** — it lists active members only.
+
+## Verify it works
+- Every emitted component appears in `catalogs/rn-v5.json`.
+- `npm run verify:fences:rn-v5` is green.
+- On device: custom slot content renders inside the component, and the list still scrolls.