Session-aware Node routing skill

Summary

Add a skill/agent behavior that understands when the Gateway is running inside a constrained Session and, when the Node advertises the needed capability and policy permits it, prefers executing the operation on the Windows Node.

This addresses the documented problem where a Gateway may fail to intelligently select/use a Node, especially when Gateway and Node are on different devices.

Scope

• Detect when Gateway is running inside a constrained MXC Session
• Query Node advertised capabilities and policy permissions
• Routing logic: prefer Node execution when Gateway is constrained and Node has the capability
• Integrate with existing node capability declarations and system.run path
• Handle fallback when Node is unavailable or policy denies

Related

• #1236 (session-backed OpenClaw: items 5 and 6 provide the containment context)
• #1199 (Node favoring/routing investigation: prior research)
• #1155 (capability state truthfulness: prerequisite for routing decisions)

Start by reading the existing node capability declarations and the system.run path, then review issues #1236, #1199, and #1155 for the containment and routing context. Done means constrained-session detection, capability and policy checks, Node preference, and fallback behavior are integrated without routing operations when the Node is unavailable or denied.