BYDMate Waze 3.16.0-dev.10

BYDMate Waze 3.16.0-dev.10 (development pre-release)

Development channel. After the Tang L drive on dev.9: arrows, roundabouts, the street name
and the lane strip all render on the instrument panel. Next up are the two things that do not:
cameras and the speed limit.

Speed limit on the panel

The live path now sends openbyd's sendSpeedLimitInfo whenever the limit read from Waze changes:
both segment-speed statistics plus the CAMERA_TYPE_SPEED_LIMITED call that actually draws the
roundel (state 1 while a limit is known, 0 when it goes away). Only on change, like the donor, and
the trip log carries a PANEL speed limit line for every one of them.

HUD Tester: camera row

A type picker over the SDK's twenty CAMERA_TYPE_* constants, a distance and a state, "Send
camera" and "Clear camera" (the donor's type 0 / distance -1 / state 1). The raw SDK status is on
screen. Nothing but a parked car and a look at the glass can say which of those twenty signs this
cluster really draws — that is what the row is for.

Waze node discovery

The camera and speed-limit alerts are drawn by Waze views nobody has named yet, and the existing
per-maneuver tree dump is rate-limited and carries no text, so a panel that appears for ten
seconds never shows up in it. Every Waze read now writes one TREE new id=… line the first time
it sees a view id in a session — id, text, description, class — capped at 200 ids per session.
Diagnostics build only; the trip log stays on the car.