What

Add DingTalk as a first-class managed channel using the existing bundled runtime plugin flow.

Why

The qqbot/wecom branch already establishes the new managed-channel path. This PR adds DingTalk on top of that same architecture so it can be configured from the dashboard and included in the bundled plugin/runtime flow without using the old vendor path.

How

• add dingtalk channel schemas, controller routes, store methods, service logic, and OpenClaw config compilation
• bundle @dingtalk-real-ai/dingtalk-connector as a managed runtime plugin and map the canonical runtime key to dingtalk-connector
• add dashboard setup UI, homepage/channel entry points, and a reused DingTalk icon asset from the reference projects
• include compatibility handling needed for the current OpenClaw/runtime path so DingTalk can connect, report status, and persist conversations
• merge latest main into feat/qqbot-wecom-main before opening the PR to reduce follow-up conflicts

Affected areas

• Desktop app (Electron shell)
• Controller (backend / API)
• Web dashboard (React UI)
• OpenClaw runtime
• Skills
• Shared schemas / packages
• Build / CI / Tooling

Checklist

• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes
• pnpm generate-types run (if API routes/schemas changed)
• No credentials or tokens in code or logs
• No any types introduced (use unknown with narrowing)

Notes for reviewers

• pnpm test currently has one unrelated existing failure in tests/desktop/skill-dir-watcher.test.ts (detects new SKILL.md and syncs ledger after debounce).
• The branch now contains the prior 7 qqbot/wecom commits plus feat: add dingtalk channel support as the 8th feature commit.