acp-router

Route plain-language requests to ACP runtime or direct acpx sessions by evaluating user intent, enforcing path rules, and mapping agentId with safety checks to ensure correct session management and reduce integration friction.

Spawning a coding-agent thread in an ACP harness requires reading the routing skill first in the same turn, enforcing preflight checks, and using only sessions_spawn for thread creation to maintain correct lifecycle behavior.

ACP harness session routing requires preflight safety checks to enforce ACP runtime and direct acpx path rules, ensuring correct agentId mapping and secure session management before spawning occurs.

Direct acpx sessions are used instead of the OpenClaw ACP runtime when plain-language user intent maps to direct acpx-driven workflows, guided by routing path rules and agentId mapping for proper session lifecycle management.

Coding-agent thread requests fail when the routing skill is not read first in the same turn or when sessions_spawn is bypassed, violating ACP runtime path rules and preflight safety checks required for thread creation.