Repository navigation
feat(desktop): establish secure Electron foundation - #128
Merged
Merged
Conversation
Owner
Author
E2E verification
|
This was referenced Jul 18, 2026
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
Establish the first secure Electron foundation for the macOS-first desktop roadmap. This slice adds the main-process lifecycle, a one-method context-isolated preload bridge, hardened BrowserWindow defaults, local-only shell loading, navigation and popup denial, and the build step required to bundle a sandbox-compatible CommonJS preload.
Motivation
The desktop roadmap needs a real Electron process boundary before renderer layout, terminal continuity, and live workbench behavior can be added safely. Keeping this boundary in its own PR makes the security contract independently reviewable.
Reviewer Test Plan
Verification
Linux Xvfb interaction and the macOS runner screenshot remain separate governed desktop slices.
Closes #127
Part of #106