Repository navigation
Add one-command native Windows startup - #21
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.
Windows users could not launch Compass with the existing Unix bootstrap. Running
.\compassin PowerShell now installs the required runtime and frontend dependencies and starts the same dashboard, matching./compasson macOS/Linux.The shared launcher supports Windows locks, private storage permissions, contained connector processes, cooperative restart, verified Node downloads, and native route separators. A platform workflow checks Windows, macOS, and Linux startup.
Validation: native platform CI passed on all three operating systems. Windows passed 68 tests with six POSIX-only cases skipped, plus actual fresh and cached
.\compass --setup-onlyruns with uv and Node absent from PATH. Local macOS launcher/platform/startup/queue tests passed (70 tests, four Windows-only cases skipped), database regression passed (152 tests), and actual macOS setup/build, PowerShell syntax validation, Ruff, and scoped type checks passed. Interactive LinkedIn sign-in was not exercised. Broader pre-existing test failures and validation limits are documented indocs/reviews/windows-startup.md.