feat: generalized channel config + openclaw passthrough

[TimBeyer]

Summary

• ChannelDef system: Data-driven channel definitions (like CapabilityDef) that drive validation, wizard rendering, bootstrap, and secret sanitization from a single source. Ships with Telegram, Discord, Slack, WhatsApp.
• channels config key: Replaces the old top-level telegram key. Each channel has an explicit enabled toggle and channel-specific fields.
• openclaw passthrough: Arbitrary dotpath-to-value config applied via openclaw config set during bootstrap — users can configure anything OpenClaw supports without waiting for a ChannelDef.
• DynamicSection abstraction: Unifies capabilities and channels in the wizard. One registry, typed lookups, no scattered string prefix parsing.
• toggle field type: New configDef field type rendering as [x]/[ ] checkbox, used for channel enabled toggles.
• Wizard group headers: Non-interactive visual separators (Infrastructure, Channels, Identity) for better section grouping.

Adding a new channel

Add a ~15-line ChannelDef entry in packages/types/src/channels.ts. Everything else (wizard, validation, bootstrap, sanitization) is automatic.

Config shape

{
  "channels": {
    "telegram": { "enabled": true, "botToken": "123:ABC-..." },
    "discord": { "enabled": true, "token": "MTIz..." },
    "whatsapp": { "enabled": true }
  },
  "openclaw": {
    "channels.discord.streaming": "partial",
    "session.dmScope": "per-channel-peer"
  }
}

Test plan

• bun test — 260 pass, 0 fail
• clawctl-dev create — interactive wizard renders channel sections with group headers and toggle fields
• clawctl-dev create --config examples/config.full.json — headless mode with channel config
• Verify disabled channel (enabled: false) is skipped during bootstrap

🤖 Generated with Claude Code