Topic-source components return 404 on detail endpoint but appear in list

[mfaferek93]

Bug report

Steps to reproduce

1. Start gateway in runtime_only mode
2. Topics like /imu/data_raw, /joy/set_feedback, /move_base/cancel create synthetic components from their namespace prefixes
3. GET /api/v1/components lists these components (fault_manager, imu, joy, move_base) with source: "topic"
4. GET /api/v1/components/imu returns 404

Expected behavior

Either:

• Components listed in /components should be accessible via /components/{id} (consistent)
• Or topic-source components should not appear in the components list if they don't have a detail endpoint

Actual behavior

Components appear in list but return 404 on detail. Sub-resources like /components/imu/data and /components/imu/logs return 200 which makes it even more inconsistent.

GET /components          -> 200 (lists imu, joy, move_base, fault_manager)
GET /components/imu      -> 404
GET /components/imu/data -> 200
GET /components/imu/logs -> 200

Environment

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

Additional information

Web UI shows loading spinner then error when clicking on these components. The component node exists in the entity tree but has no backing entity detail.