service-omni-service-channel-configure

Ensure exactly one ServiceChannel is present for a routable sObject, reusing whatever is already bound (Salesforce standard or a pre-existing custom channel) and deploying the skill's canonical v66 template only when none exists. Salesforce enforces one ServiceChannel per RelatedEntity, so the skill detects first and never deploys blindly — deploying a second channel for an sObject that already has one fails with "This Salesforce object is already in use by another Service channel." It handles one sObject per call; callers configuring multiple sObjects invoke it once for each sObject, after service-omni-base-settings-configure has enabled Omni-Channel.

sObject	Standard channel (if any)	Canonical asset
`Case`	`Cases`	`Cases.serviceChannel-meta.xml`
`Incident`	none (Incident Management sObject)	`Incidents.serviceChannel-meta.xml` — deployed on first run
`MessagingSession`	`sfdc_livemessage`	`MessagingSessions.serviceChannel-meta.xml` — deployed only if the standard channel is missing
`VoiceCall`	`sfdc_phone`	`VoiceCalls.serviceChannel-meta.xml` — deployed only if the standard channel is missing

Inputs

bash scripts/deploy-and-report.sh <org-alias> [Case|Incident|MessagingSession|VoiceCall]

org-alias (required).
sobject_type (optional, default Case) — one of Case | Incident | MessagingSession | VoiceCall.