curriculum-project-hub/.scratch/saas-production-readiness/issues/44-route-feishu-by-org-connection.md

Route Feishu identity and traffic by Organization connection

Type: task Status: open Blocked by: 20, 22, 43

Question

Make every Feishu OAuth, WebSocket/event, card action, directory sync, chat binding, API call, and outbound message start from an explicit active Organization Feishu Application Connection. Model external user, chat, event, and callback identifiers in that connection's namespace; bind OAuth state to the intended Organization/application; run and observe one listener/client lifecycle per configured app; and prove two customer-owned apps with colliding provider-local identifiers cannot authenticate, bind, authorize, deduplicate, rate-limit, or deliver across Organizations. Do not infer tenant from a global open_id, chat_id, or from the user's membership count.