From 7e9f46db2ae2b5076182d6194125fc840a2be92c Mon Sep 17 00:00:00 2001 From: lingniu Date: Thu, 16 Jul 2026 17:15:28 +0800 Subject: [PATCH] docs: record live-first vehicle release --- .../docs/frontend-production-readiness.md | 8 ++++++++ .../docs/vehicle-data-platform-meeting-todo.md | 12 +++++++++++- 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/vehicle-data-platform/docs/frontend-production-readiness.md b/vehicle-data-platform/docs/frontend-production-readiness.md index c20ef5af..3f9c43a9 100644 --- a/vehicle-data-platform/docs/frontend-production-readiness.md +++ b/vehicle-data-platform/docs/frontend-production-readiness.md @@ -315,6 +315,14 @@ Vehicle detail, track replay, history and mileage render one shared return bar o Route and component tests cover exact context round trips, direct-entry behavior, same-origin validation, malformed viewport rejection, browser-history navigation, four child workflows and saved-map restoration. The complete frontend gate passed 49 files and 251 tests, followed by TypeScript/Vite production build verification. ECS smoke verified 23 current assets, 58 compatibility assets across three generations, all three active services, the authenticated production health release, six SPA routes and both context bundles. +## 2026-07-16: live-first single-vehicle detail + +Release `vehicle-live-priority-20260716171441` moves current operational state ahead of the static vehicle archive in both DOM and visual order. The first-screen live overview exposes speed, SOC, total/today mileage, recommended source, source availability, report time, coordinates and address state. Availability flags take precedence over compatibility numeric fields so an unsupported metric cannot appear as a fabricated zero. + +Single-vehicle reverse geocoding is explicitly user-triggered and keyed by a rounded coordinate. The ten-second realtime poll therefore does not create an address request per position update; after the vehicle moves, the existing address stays visible until the user elects to refresh it. Invalid or unavailable coordinates are excluded from the one-vehicle map and displayed as unavailable. + +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. + ## Release evidence template - Commit and release identifier diff --git a/vehicle-data-platform/docs/vehicle-data-platform-meeting-todo.md b/vehicle-data-platform/docs/vehicle-data-platform-meeting-todo.md index e1ee9aa9..4c25c931 100644 --- a/vehicle-data-platform/docs/vehicle-data-platform-meeting-todo.md +++ b/vehicle-data-platform/docs/vehicle-data-platform-meeting-todo.md @@ -246,7 +246,17 @@ ### P0-07 单车详情信息优先级调整 -状态：`进行中` +状态：`已完成` + +已上线结果（release `vehicle-live-priority-20260716171441`）： + +- 单车页面首屏改为“车辆身份 → 最新上报 → 来源证据 → 地图/事件/遥测 → 车辆主档”，固定档案不再排在动态数据之前；Web 与移动端使用同一 DOM 信息层级。 +- 最新上报全宽展示速度、SOC、总里程、当日里程、推荐协议/位置来源、在线来源数、完整上报时间和当前经纬度；无效坐标不会进入单车地图或显示成真实位置。 +- 速度、SOC、总里程和当日里程显式遵循后端 availability 标记，来源不提供时显示 `—`，即使底层兼容字段为 `0` 也不会冒充真实值。 +- 地理位置采用单车按需解析：打开详情不会调用高德，点击后才读取；坐标变化时保留旧地址并提示“车辆已移动 · 更新地址”，避免跟随 10 秒实时轮询持续消耗 API。 +- 轨迹、历史、里程和告警入口围绕当前车辆统一排列，并按当前账号菜单权限显示；前三个入口继续携带全局监控返回上下文。 +- 自动化验证动态区在车辆主档之前、里程入口上下文、按需地址调用及缺失值展示；全量前端 49 个文件、252 项测试与生产构建通过。 +- ECS 发布门禁验证 23 个当前资源与 60 个前三代兼容资源；真实车辆 `LNXNEGRR7SR318212` 的实时接口和单车路由烟测通过，三个服务均为 active，鉴权健康接口确认 production 数据模式和当前 release。 目标：