Prerequisite Verification: Repeatable Startup Evidence

This route no longer teaches launch-file authoring as a full beginner unit. General ROS 2 launch concepts belong in ros2-for-students.

The bridge question is narrower:

Can you prove that startup configuration is repeatable enough to support cross-layer failure diagnosis?

Use an existing bringup package and launch file to verify:

• which nodes/processes are requested;
• which parameters, remaps, namespaces, or arguments affect the graph;
• whether installed launch resources are discoverable;
• whether the launched graph matches the declared startup contract;
• which Java/WPILib integration claims remain unproven.

Do not confuse a successful ros2 launch with proof that a Java robot application is connected to ROS 2. The launch result establishes ROS-side startup evidence only.

Required checkpoint

Produce a Startup Contract Record with the launch entry point, declared configuration, observed graph, one mismatch/failure case, and one explicit Java-to-ROS non-integration statement.

If launch mechanics are unfamiliar, return to ros2-for-students. Week 16 uses this verified prerequisite for actual cross-layer recovery work.