Transient ROS 2 CLI nodes appear in entity tree

[mfaferek93]

Bug report

Steps to reproduce

1. Start gateway in runtime_only mode
2. Use ros2 param list or any ros2 CLI command that creates transient nodes
3. GET /api/v1/apps lists _param_client_node and _ros2cli_daemon_30_* as apps

Expected behavior

Transient/internal ROS 2 nodes (CLI daemons, parameter clients) should be filtered from the entity tree. They are not user-facing entities.

Actual behavior

_param_client_node and _ros2cli_daemon_30_* appear as apps in the entity tree. All endpoints for _param_client_node timeout (6s) because it's a short-lived node that may no longer exist.

Environment

• ros2_medkit version: main branch
• ROS 2 distro: Humble
• OS: Ubuntu 22.04 on Jetson Orin Nano (aarch64)

Additional information

Could be fixed with a node name filter/blacklist. Nodes starting with _ are typically internal. ros2cli daemon nodes follow the pattern _ros2cli_daemon_*.

Existing config discovery.runtime.topic_only_policy and discovery.runtime.min_topics_for_component might help but a dedicated node blacklist would be cleaner.