shishengliang/lingniu-vehicle-ingest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record source diagnosis release

Browse Source
This commit is contained in:
lingniu
2026-07-16 17:39:07 +08:00
parent 55f8fbe113
commit d6b857240c
3 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
vehicle-data-platform/docs/frontend-production-readiness.md
View File

@@ -323,6 +323,16 @@ Single-vehicle reverse geocoding is explicitly user-triggered and keyed by a rou
Vehicle-scoped track, history, mileage and alert actions are grouped together and filtered by the authenticated menu grants. Track/history/mileage preserve monitor return context. Tests assert information hierarchy, nested context, zero suppression and the absence of a geocoding request before user action. The full frontend gate passed 49 files and 252 tests plus the production build. ECS smoke verified the real vehicle `LNXNEGRR7SR318212`, the live-first bundle markers, production health and all three services; the release gate served 23 current and 60 compatibility assets.
## 2026-07-16: operator source diagnosis workspace
Release `source-diagnosis-stable-20260716173740` makes the operations page a single-vehicle evidence workspace before the existing global health panels. Vehicle candidates use bounded fuzzy search with 20-result pagination. Source evidence is fetched only after selection and is not attached to the recurring health/readiness polls.
Every real location candidate exposes a provider label, masked terminal, protocol, first/latest report evidence, protocol interval, position/mileage, online and quality state, policy priority and a human-readable election explanation. The page distinguishes an independently configurable source from a read-only canonical fusion snapshot. Only administrators can save enablement, priority and a reason; operators are read-only and viewers cannot call the diagnostic endpoint.
The browser never receives a gateway `source_key`. The API emits an opaque SHA-256 `sourceRef`, resolves it back to the current candidate server-side and writes the existing gateway policy table through optimistic platform-owned versions and immutable audits. The gateway election algorithm is unchanged and a saved policy is documented as taking effect on the next valid report.
The V2 gate passed 49 files and 253 tests, the TypeScript/Vite production build and release-installer tests. Production migration `015` was applied before traffic switched. A real multi-source vehicle returned two location candidates without leaking source keys. A no-op admin save kept version `1`, audit count `0` and the GB32960 recommendation unchanged. Viewer/operator/admin authorization returned 403/200/200, 20 diagnostic calls measured about 70 ms median and 79 ms P95, and all three services remained active.
## Release evidence template
- Commit and release identifier