fix: fallback to global inboundMeta.sender_id when LarkTicket unavailable

[subaochen]

Summary

When ToolClient is created in sub-agent scheduling scenarios (e.g. PA dispatching), the AsyncLocalStorage (LarkTicket) context is lost, causing ticket.senderOpenId to be undefined. This triggers unnecessary fallback to the app owner and generates excessive "Using app owner as fallback user" logs.

Fix

Adds a secondary fallback path that reads sender_id from global.openclaw.inboundMeta (set by the OpenClaw runtime), ensuring correct user identity is used even when LarkTicket context is missing.

Changes

• src/core/tool-client.ts: In createToolClient(), added fallback to global.openclaw.inboundMeta.sender_id when ticket.senderOpenId is unavailable
• Type-safe: uses (global as any).openclaw?.inboundMeta?.sender_id to avoid TypeScript type dependency on OpenClaw internals

Testing

Verified locally: after restart, no new "Using app owner as fallback user" logs appear in sub-agent scenarios.

Fixes: excessive fallback logs in sub-agent scheduling

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}