Mission Control for ros2_control

The project solves a common problem in robotics systems: ros2_control already gives teams strong building blocks for hardware and controller control, but it still leaves the coordination of full system transitions to the user. In practice, that means teams often write their own startup scripts, timing delays, and controller-switching logic by hand. My plan is to build a reusable orchestration layer that watches existing ros2_control status, applies YAML-defined presets, and moves controllers and hardware into the right states in a safe, deterministic order. The work will be delivered through five parts: a benchmark multi-robot scenario, a periodic status publisher in controller_manager, status topics on standard controllers, a YAML preset format with validation, and a Mission Control node that executes and verifies each transition without touching the real-time control loop.