Fix monitor event handling, responsive views, and deployment docs - #23
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
1 participant
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.
Signal IDs are local to each upstream, so Algora, AO, and Bridge could lose events when their IDs collided. Registry and health requests could also outlive teardown when their polling cycles overlapped. This change fixes both and adds regression coverage.
The UI now fits the compact mobile Bridge layout, keeps the tablet map visible below a scrolling panel, preserves keyboard focus between unchanged registry updates, refreshes tooltip metadata, and keeps hidden map effects hidden. Health tooltips use the actual status colour. English and Korean READMEs and the About text now distinguish reported data from conceptual belt animations.
Static serving returns 404 for missing assets, and PM2 starts the installed server directly. The lockfile updates compatible security patches, and the Node requirement matches the test runner.
Validation: 18 tests, typecheck, production build, and npm audit (0 vulnerabilities). Browser checks used real service data at desktop, tablet, and mobile widths; local serving returned 200 for the page/health JSON and 404 for missing assets. Existing PM2 deployments must recreate this application's process from ecosystem.config.cjs to apply its new executable; deployment remains manual.