Repository navigation
docs: prepare unpublished VS Code Scanner guidance - #13
Draft
1jovansimon wants to merge 1 commit into
Draft
1jovansimon wants to merge 1 commit into
1jovansimon wants to merge 1 commit into
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.
Prepare documentation for the unpublished VS Code extension while keeping the verified no-build CLI archive as the current installation method. Describe the tested local workflow, platform limits, privacy boundaries and planned PatchWRK Pro without adding an unavailable Marketplace install link.
Final extension acceptance remains blocked: a rapid consecutive installed-test sequence lost the active history association. Screenshots and live publisher authority verification are also pending. This draft does not authorize or announce a release, and adds no extension implementation.
Validation: relative documentation links/anchors and diff whitespace checks passed; existing CLI command blocks remain unchanged. Scanner regression baseline passed 454 tests, lint, typecheck, build, benchmark and package verification. Founder review required before merge.