feat(extension): Chrome Web Store readiness — popup UI, privacy policy, CSP#415
Merged
feat(extension): Chrome Web Store readiness — popup UI, privacy policy, CSP#415
Conversation
… Store - Add popup.html/popup.js showing daemon connection status (Connected / Reconnecting / No daemon connected) - Add message listener in background.ts to expose WebSocket state - Add PRIVACY.md with full privacy policy covering all permissions - Add content_security_policy to manifest.json - Update description to be clearer for CWS reviewers
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.
Summary
Prepare the Chrome extension for Chrome Web Store submission.
Changes
Connected to daemon(green dot)Reconnecting...(orange dot)No daemon connected(red dot)PRIVACY.md) — covers all permissions, data flow, cookie accesscontent_security_policyin manifest.jsongetStatusfor popup communicationCWS Submission Notes
The
debuggerpermission remains the main review risk. The privacy policy and popup UI should help justify it by showing:Test plan
tsc --noEmitpassesvite buildsucceeds