`manifests/tools/key_press.yaml` and `manifests/tools/key_sequence.yaml` do not declare `routing.stateful: true`, while every other UI automation tool in the same workflow — `tap`, `swipe`, `touch`, `long_press`, `type_text`, `batch`, `snapshot_ui`, and `wait_for_ui` — does. In `src/runtime/tool-catalog.ts` the catalog reads `toolManifest.routing?.stateful ?? false`, and `src/runtime/tool-invoker.ts` uses `tool.stateful` to decide whether the CLI path routes through the daemon. As a result, CLI invocations of `key-press` and `key-sequence` silently fall back to direct in-process invocation, bypassing the daemon session that owns the AXe HID connection used by the sibling tools. This violates the skill guardrails 'Stateful CLI tools route through daemon only when routing.stateful requires it' and 'Avoid silent fallbacks and parallel invocation paths.'