feat(wecom): migrate WeCom trust config to first-class [wecom] section (Phase 1)

[chaodu-agent]

Summary

Migrate WeCom adapter trust configuration from gateway env vars to a first-class [wecom] section in config.toml.

Current State

• Gateway env vars only (GATEWAY_ALLOW_ALL_USERS, GATEWAY_ALLOWED_USERS)
• No per-platform granularity for WeCom

Target State

[wecom]
allowed_users = ["zhangsan", "lisi"]
trusted_bot_ids = ["bot_app_1"]
# allow_all_users = true  # explicit opt-in only

Tasks

• Add [wecom] section to config schema (feat(trust): [wecom]/[googlechat]/[teams] first-class trust sections (Phase 1) #1366)
• Wire WeCom trust through PlatformTrustConfigs registry (feat(trust): [wecom]/[googlechat]/[teams] first-class trust sections (Phase 1) #1366 — embedded/unified path)
• trusted_bot_ids for is_bot derivation (no enter_agent — that is user-initiated)
• Deprecate gateway env vars for WeCom (feat(trust): [wecom]/[googlechat]/[teams] first-class trust sections (Phase 1) #1366)
• Update docs and config.toml.example (feat(trust): [wecom]/[googlechat]/[teams] first-class trust sections (Phase 1) #1366)

Follow-ups from external review (canyugs/openab#18)

• ADR + platform-facts correction: WeCom callback mode is DM-only (ADR v2 branch c2e6223 + docs(platforms): wecom quirks — DM-only L2, ISV id formats, is_bot no-op #1386) (channel_type always "direct", per-user channel id wecom:{corp}:{user}) — L2 scope is effectively allow_dm only; allowed_channels is meaningless. Drop/futurize "group routing" in the ADR's WeCom EXPECTED box
• Sender-id caveat: plain UserID ("zhangsan") applies to self-built apps only — verified against official docs, recorded in ADR v2 + docs(platforms): wecom quirks — DM-only L2, ISV id formats, is_bot no-op #1386; external-contact/ISV modes see wmXXXX/OpenUserID formats — document in the ADR table and docs/platforms/schema/wecom.toml
• is_bot is hardcoded false (wecom.rs:1071) — documented in ADR v2 wording + docs(platforms): wecom quirks — DM-only L2, ISV id formats, is_bot no-op #1386 quirk; implementation (populating from SenderInfo.is_bot) remains open with bot detection so the L3 bot-bypass is a no-op for WeCom; GatewayEvent.SenderInfo.is_bot already exists as a ready source when bot detection lands

Notes

• WeCom UserIDs are freeform strings (tenant-admin-assigned: letters, digits, -, _, @, .)
• enter_agent (member-enter event) is user-initiated — must NOT be classified as is_bot
• WeCom UserIDs could match reserved synthetic values — this is why cron bypass only checks platform, not sender_id

Refs

• Umbrella: umbrella: Phase 1 trust migration — per-platform [section] for all adapters #1356
• ADR: docs(adr): revise identity-trust-none — three-layer architecture #1291

[github-actions]

⚠️ This issue is missing the following required information and will not be processed until completed:

• Use Case

Please edit this issue to fill in the missing fields. Thank you!

Tip: Use headings like ## Description or ### Description — common synonyms (e.g. ## Problem, ## Reproduction, ## Motivation) are also accepted.