Repository navigation
Conversation
added 17 commits
September 24, 2026 23:03
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.
Summary
Combines the reviewed Web changes from #88, #89, and #90 into one branch, then refines the three screens called out in user feedback:
This branch starts from the king test host's deployed
89bd542db2143240effd92078d290938763e267a. It intentionally excludes the later Core write-audit migration onmain; no Core, daemon, Runtime, or database code is changed here.Validation
49b5a237bcc696dde37151a9053d4dfb14cff2d4: 781 Web unit tests, 15 onboarding browser tests, TypeScript typecheck, and production Web build passed.make checkpassed Core Console, 108 installer tests, 12 manifest tests, and distribution build, then stopped because the dedicatedPARSAR_AGENTS_API_TEST_DATABASE_URLis not configured locally. The latest CI check is the complete gate.Deployment scope
Web assets only on the king test host. The current Core, Console binary, managed Runtime image, private configuration, and database remain paired with the deployed base release. New remote node installation still requires a matching distribution payload and a node-reachable HTTPS Console origin.