Repository navigation
Build MSD Impact Monitor with event-only telemetry preview - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the first working MSD Impact Monitor prototype to this previously empty repository, with explicitly separated live-simulation and event-only preview modes. No hardware, phone gateway, or cloud database is connected.
Validation on the updated implementation: production build and TypeScript checks, all 37 unit tests, all 14 Chromium browser tests, production-browser smoke check for both modes with no runtime errors, mobile checks at 390px, and Prettier check. Tests cover exact threshold boundaries, source isolation, sparse packets, stale/disconnected streams, event silence never confirming green, preserved event severity after demo-threshold edits, automatic impact coalescing, sessions, and JSON exports. Map tiles are blocked in browser tests to exercise the offline fallback.
All settings/history are in memory and reset on refresh. Export JSON to keep a copy. No deployment, hardware calibration, authentication, cloud persistence, or merge is included.