Prerequisite Review: Inventory Is Not Discovery

This route no longer teaches Java collection mechanics as new material. Lists, iteration, search, and collection mutation belong in java-programming.

The bridge distinction is narrower and more important:

A Java inventory of robot components is local application state. It is not a live discovery mechanism for WPILib or ROS 2.

Use a small component inventory only to reactivate prerequisite skills. Then compare:

• local Java membership and object identity;
• framework-owned registration/scheduling state where applicable;
• ROS 2 graph discovery and runtime identity;
• physical-device presence, which requires separate evidence again.

A component appearing in List<RobotPart> proves only that the JVM collection contains a reference. It does not prove a ROS node exists or a physical device is connected.

Required checkpoint

Produce an Inventory vs Discovery Note with one local Java inventory example, one ROS graph discovery example, and the evidence boundary between them.

If collection mechanics are the blocker, return to java-programming. Do not expand this bridge route into a second collections unit.