docs: define WPCodeSpace OpenVSCode image strategy - #11
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
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
Defines the WPCodeSpace OpenVSCode image strategy after successful source compile and server archive validation.
Decision
WPCodeSpace will use a dedicated OpenVSCode image produced from the DXBMARK OpenVSCode fork.
Target image:
Initial tagging:
Scope
Documentation only.
No source changes.
No workflow changes.
No Docker changes.
No generated runtime files committed.
No WPCodeSpace consumption changes.
Next phase
Add a validation-first image build workflow or script that uses the proven server archive candidate output path, builds a test image, runs it locally, and verifies the official Chat panel copy before WPCodeSpace consumes the image.