feat(platform): expose no-data vehicles

vehicle-data-platform/docs/api-contract.md

@@ -94,6 +94,8 @@ GET /api/vehicles/coverage?keyword=粤AG18312&serviceStatus=degraded&limit=20&of
 
 Returns VIN-level source coverage rows for the vehicle service list. Each row includes the canonical vehicle-level `serviceStatus` so frontend, exports, and external integrations share the same health definition. `serviceStatus` accepts `healthy`, `degraded`, `offline`, and `identity_required`.
 
+Coverage summary also exposes `noDataVehicles`, so UI can show vehicles that exist in identity binding but have no GB32960, JT808, or Yutong MQTT source evidence. `/api/vehicles/coverage?serviceStatus=no_data` returns those bound vehicles for follow-up source onboarding.
+
 ### History Locations
 
 ```http

vehicle-data-platform/docs/product-spec.md

@@ -28,6 +28,8 @@ Vehicle service lists and dashboard previews should label protocol coverage as `
 
 Dashboard and vehicle-list summary cards should expose both `单源车辆` and `多源车辆`. Single-source vehicles are operationally important because they cannot be cross-checked across sources, so they must be one-click filter targets rather than hidden behind the generic coverage filter.
 
+`暂无来源车辆` is also a first-class governance entry. It represents bound vehicles that have no current GB32960, JT808, or Yutong MQTT source evidence, and should route directly to the `no_data` vehicle service filter.
+
 ## Interaction Rules
 
 - Tables are the default data surface.