fix(drivers): bundle the vehicle drivers that say where a car is plugged in

[frahlg]

Moves the device-drivers pin from 76ddd58 to 5cc7bb1a (srcfl/device-drivers#182) and bundles the vehicle drivers, so the next beta ships them with the Core side that reads them (#1660).

Supersedes #1449, the 26 September draft that proposed bundling teslamate_vehicle, tesla_cloud and vag_vehicle at an older pin. It can be closed.

What changes

• drivers/BUNDLED_SOURCE.json: the pin, and four drivers added to the list: home_assistant_vehicle, tesla_cloud, teslamate_vehicle and vag_vehicle. tesla_vehicle was already bundled.
• Between the two pins only these five drivers changed under drivers/lua. No other bundled driver moves.
• go/internal/fleetping/shipped_gen.go is regenerated from the pin, as feat(drivers): bundle the TeslaMate, Tesla Fleet and VW Group vehicle drivers #1449 found it must be.
• The end-to-end vehicle test from feat(cars): a car says when its cable went in and how far away it is #1660 now runs the bundled copies. The testdata copies it used go.
• Changeset minor: four drivers join the bundle.

Driver	Version	Cable	Place
home_assistant_vehicle	0.1.0, new	plugged, and plugged_since if the automation sends it	at_site from a tracker in zone home
tesla_cloud	0.2.0	plugged, no cable time	site_distance_m from location_data
teslamate_vehicle	0.2.0	plugged, dated only with a live healthy	at_site from the configured geofence, else site_distance_m
vag_vehicle	0.3.0	plugged, no cable time	none
tesla_vehicle	0.2.6	—	—

All five send a level of 1 % or less as a fraction. None wakes a car; each does nothing until configured.

Note on the place. host.site_location() answers only a driver whose signed catalog entry lists vehicle (#1660). A bundled copy runs without that signed entry, so a bundled tesla_cloud or teslamate_vehicle sends no site_distance_m. TeslaMate's geofence and Home Assistant's zone still give at_site. The same drivers installed from the signed channel get the distance. Extending the gate to bundled copies is a small Core change if wanted.

Evidence

• scripts/sync-bundled-drivers.sh wrote 44 drivers from 5cc7bb1a. All five vehicle drivers are byte-identical to device-drivers main.
• scripts/check-driver-versions.sh origin/master: "driver version changes verified across 44 bundled drivers".
• scripts/sync-bundled-drivers.sh --check: no driver source committed.
• go test -p 2 ./internal/drivers ./internal/fleetping: pass, including TestBundledDriversMeetStartupContract and the end-to-end tests for the Home Assistant, TeslaMate and Fleet API drivers.
• GOFLAGS=-p=2 make verify: clean on 022db9f (tests, vet, build).

After the beta, on a site

A site that runs home_assistant_vehicle.lua as a local file keeps its local copy until someone removes it. To use the bundled driver: remove the local file, and add plugged and at_site to the Home Assistant automation, as the driver's header shows. The message it already sends keeps working.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-16T09:28:46.337941Z	022db9f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.