Car support and guides

A supported car package can include guide data that maps pieces of the iRacing paint template into useful areas. That data lets Builder identify panels instead of treating every UV island as anonymous paint space.

The package is local. The app should use the installed data for the selected car and avoid falling back to another car's guides.

• Panel definitions for selectable paint regions.
• Guide overlays that help explain where template pieces appear on the car.
• Car-specific metadata used by the library and iRacing output flow.

Every iRacing car template is different. The same texture coordinate area can mean a hood on one car, a door insert on another, or nothing useful at all.

That is why guide data has to follow the selected car. Reusing another car's panel map would make the UI look populated while producing misleading selections.

If a downloaded car does not show panel guides, the first thing to check is whether its support package actually installed guide data. The editor can still open the car, but it cannot invent reliable panel segmentation without that data.

A missing guide state should be visible and understandable. It should not silently show a demo car, a bundled fallback, or old data from the previous car.