Reference

Tables and lookup material — what's seeded per car, capability bit positions, error codes.

Long tables that don't belong in concept docs but mini-app authors want at hand:

Trim × capability matrix — what every BYD trim seeds in VehicleCapability by default, with the empirical caveats per sub-trim.

More tables move here as the platform matures (error-code reference, host-version compatibility matrix, etc.).

Run a session

Connect with a code, record with consent, run DashDoctor recovery, and the low-level relay commands.

Targets — trims, WebView & host

Which BYD trims run ES modules, which need a classic bundle, and how minHostVersion gates launch. One table before you build.