#83 docs(creating-cloud-persona): optional integrations + dual-transport pattern

Documents the workforce#252 optional integrations feature in the creating-cloud-persona skill, which previously described PersonaIntegrationConfig as just { source, scope, config } and had no dual-transport guidance.

• Adds optional?: boolean + enabledByInput?: string to the type signature in §3.
• New §3b covering opt-in integrations (persona-kit ≥4.1.12): how enabledByInput prunes a provider's connection/trigger/mount when the input is empty, the gate-on-id semantics, keeping data sources non-optional, and the version requirement.
• Documents the canonical dual-transport agent (one agent declaring both slack + telegram, dispatch by event.type, reply-on-origin) — the pattern now shipping in the agents repo (inbox-buddy, joke-bot, spotify-releases, hn-monitor).

Companion to AgentWorkforce/agents#91.

🤖 Generated with Claude Code