Prerequisite Checkpoint: Establish the Startup Baseline

This bridge assumes launch-file fundamentals from ros2-for-students.

Before using launch, prove the expected runtime can be started and inspected manually or from supplied evidence.

Record:

• required package(s);
• expected node names;
• expected topic/service relationships;
• shell/overlay state;
• one manual or supplied startup result.

Bridge rule

A launch failure is much easier to diagnose when the underlying package and runtime expectations are already known.

Do not use launch as a magic wrapper around an unverified baseline.

If launch syntax itself is unfamiliar, return to the prerequisite course. This route focuses on repeatability and evidence.