fix(lark): route Goal Topic events directly to Agent

[maxliux5]

Summary

• route each provider event directly to the bound Goal Agent and forward the Agent output to the original Lark message
• preserve exact Topic routing when root_id is available; use a safe fallback only when the group has exactly one Goal Topic binding
• surface missing or ambiguous Topic context in connection health instead of silently dropping messages
• keep event processing independent from message-history readback and history permissions

Root cause

The installed Lark CLI event schema exposes stable message envelope fields but may omit Topic root metadata. The RFC runtime attempted message-history enrichment before invoking the Agent, so permission or readback failures stranded otherwise valid messages.

Safety

• no credential or profile model changes
• no automatic state write or Preview bypass
• ambiguous multi-Goal routing is rejected with a structured blocker
• public UI exposes only status and redacted error categories

Validation

• 46 focused Lark runtime, connection, inbox, and API tests passed
• Lark extension compile check
• personal workspace contract smoke
• dashboard TypeScript and Vite build
• personal workspace browser smoke
• public/private boundary and diff checks