cometchat-ios-v5-sdk

Ground truth: CometChatCallsSDK v5 + catalog ios-calls-v5.json (the closed symbol list — every type below is in it). Official docs: /calls/ios/** = v5 · Docs MCP. Fetch exact SessionSettings fields, event names and signatures from the docs (references/docs-map.md) — never memory. ⚠️ Twelve doc pages contain symbols that DO NOT COMPILE — see "Doc corrections" below; prefer THIS skill's names over the page's. APPEND to the user's app — additive wiring only.

Companion skills (read first)

• Standalone/headless entry — owns its own package (the Calls SDK), no -core sibling, never depends on the iOS UI Kit. 1:1 ringing additionally drives the Chat SDK (CometChatSDK v4) for signaling.
• App wants chat too, or the prebuilt call UI? cometchat-ios-core + cometchat-ios-calls — not this skill.

Use this skill when

"add calling from scratch / without the UI Kit", "standalone voice/video on iOS", "build my own call screen", "headless calls SDK", "meeting-room join by session id", "one-on-one ringing".

ASK FIRST (BAKED) — two choices, and NOTHING upstream asks them

Ask whichever the request has not already settled, then WAIT. Never infer from silence — each answer means a different SDK set and a different screen.

1. Prebuilt call UI, or build your own? Prebuilt (drop-in, themeable) → STOP, route to cometchat-ios-calls. Build your own → continue here.
2. Meet-style room, or 1:1 ringing? Room — everyone joining the same session id lands in one call; Calls SDK only. Ringing — you call a specific user and their device rings; adds CometChatSDK v4 for signaling (signatures: references/docs-map.md § "1:1 RINGING"), plus CometChatPushNotifications to ring while the app is backgrounded/closed.

Only EXPLICIT wording settles a question — "from scratch"/"my own call screen" → 1, "ringing"/"call a user" → 2. "Add calling to my iOS app" settles NEITHER — ask both.