VDA State intermittently omits velocity field due to library-clearing and no forced state update

I am seeing an issue where the VDA5050 State intermittently omits the velocity field because the library stores it as an optional and clears it in the visualization cycle. Velocity is an optional value, so in theory this is not wrong. But i think it should either have the velocity object for all the state massages or none of them.

As I seet it, this happens because NavigationSink::setVelocity(...) sets StatusManager::velocity_, but VisualizationTimer::sendVisualization() reads and then resets it, so whether velocity appears depends on timing between setting, clearing, and the state update timer