Initial import of the X500 on the parts pipeline

[caguero]

Summary

Initial import of the Holybro X500 V2, built the same way as the BlueBoat in bluerobotics_models: a part library (holybro_parts) where each part declares its inertia, visuals, collisions, slots with accepted options and defaults, frames and, for propellers, a drive table. The default vehicle needs no configuration (four 1345 props, 4S battery, GPS mast); a config only states differences and is checked against the assembly manifest, failing the build or the launch with the reason. x500_gazebo places the motor plugins and the NavSat by the same resolution, generates the bridge from the manifest and supports launch time loadouts (config_file:=, no rebuild). The meshes are BSD 3 placeholders from PX4-gazebo-models; the assembly machinery is copied from bluerobotics_parts and marked for extraction into a shared package. All documentation lives under docs/ on the site.

How to test it?

Pull requests only build the docs, so run them locally and use them as the test script:

pip install -r docs/requirements.txt
sphinx-build -W docs _build/html && python3 -m http.server -d _build/html

Then open http://localhost:8000 and follow:

• Getting started: build the workspace, launch the default vehicle in Gazebo, echo the IMU and GPS topics, view the model in RViz.
• Vehicles / X500: the default loadout, the motor command bus (gz.msgs.Actuators, not bridged), the slot table.
• How to guides: change the loadout (gimbal in, gps out) and launch with config_file:=; try a typo, which must fail naming the problem; generate the artifacts with configure_vehicle.py and check a config with check_assembly.py.
• Reference and Design: the config schema, the parts catalog and the pipeline description.

colcon test runs 92 tests (unit, headless Gazebo and ROS launch, lint), all green locally.

🤖 Generated with Claude Code