Prerequisite Review: Choose a ROS 2 Interaction for an Integration Need

This route no longer reteaches services, actions, parameters, and topics as a full beginner unit. Those communication patterns belong in ros2-for-students.

The bridge-specific task is to use that prerequisite knowledge when defining an integration contract.

Given a Java/WPILib-side need, decide whether the ROS-facing interaction shape requires:

• a stream of updates;
• one request and response;
• a long-running cancelable goal with feedback;
• node configuration.

Then state what the Java side would need to know about the ROS interface without pretending a maintained official Jazzy Java client path exists.

Required checkpoint

Produce an Interaction Contract Note with one Java-side requirement, the selected ROS 2 interaction pattern, the interface data that would cross the boundary, and the runtime evidence required to verify the ROS side independently.

If the distinction between topics, services, actions, and parameters is unclear, return to ros2-for-students rather than expanding this bridge route.