openclaw - 💡(How to fix) Fix fix(a2a): resolve direct/dm announce target from session key fallback [1 pull requests]

Summary

A2A announce target resolution may fail for direct-session keys shaped like agent:main:<channel>:direct:<peerId> (including dm alias) when the primary session parser path returns null.

Impact

Direct announce delivery in A2A flows can miss the intended recipient for certain session-key formats.

Repro

1. Prepare a direct session key: agent:main:wecom:direct:<peerId> (or ...:dm:<peerId>).
2. Trigger announce target resolution from session key.
3. Observe unresolved/incorrect direct target in fallback cases.

Expected

Announce target resolves correctly for direct/dm key variants and stays safe when plugin-level delivery target resolution returns null.

Proposed Fix

• Add fallback parsing for agent-scoped direct/dm session keys.
• Reuse channel plugin resolveDeliveryTarget when available.
• Fallback to safe normalized user:<peerId> target when plugin resolution returns null.
• Add focused tests for direct, dm alias, and null delivery-target fallback.

Notes

• Scope is intentionally limited to announce target resolution.
• No behavior change for group/thread paths.

Evidence

Manual verification screenshots are available and will be attached in the linked PR with redaction where needed.