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

docs: record monitor context release

Browse Source
This commit is contained in:
lingniu
2026-07-16 17:10:02 +08:00
parent 1cfc9c2bdd
commit 3e5c5772df
3 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -307,6 +307,14 @@ The export workspace is owner-aware: each row shows the creating account, author
The production gate exported 1,274 location rows for one real VIN. The 215,212-byte CSV contained export audit, vehicle Scope and quality-reason metadata. A guessed ID returned 404, the API restarted successfully, and the file SHA-256 remained `00a4b1a877364f048a06e8bf6d80828e0dacaddd2f946b39b6cd00cfb2e9013e` with no partial file left behind. The release passed all 241 production frontend tests and the TypeScript/Vite build gate.
## 2026-07-16: monitor investigation context continuity
Release `monitor-context-continuity-20260716170911` makes the global monitor URL the canonical owner of its operator workspace: map/list mode, search and source/status filters, selected VIN, detail visibility, list page and limit, and map zoom/bounds. Child links carry only a validated same-application `/monitor` return path; malformed bounds, unsupported routes and external origins are discarded instead of becoming redirects.
Vehicle detail, track replay, history and mileage render one shared return bar only when monitor context exists. Track/history/statistics query changes preserve the return parameter, and vehicle-detail investigation links forward it. Direct menu entry remains clean. FleetMap restores the saved WGS-84 bounds midpoint and zoom at construction time and suppresses the selected-vehicle recenter that would otherwise overwrite a restored viewport; fractional zoom levels remain valid and are serialized to two decimal places.
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.
## Release evidence template
- Commit and release identifier