The tool resolves familiar aliases before broader catalog matching and sends clear requests through deterministic rules. Model-assisted planning remains optional, is disabled by default, and is reserved for requests that still need interpretation.
Scheduled actions persist a normalized route compatible with the immediate execution layer and reuse it when the action becomes due. This keeps aliases, confirmation, and execution behavior consistent without storing a complete planning object.