Repository navigation
docs: align published Server528 installation and scoped acceptance - #290
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.
Documentation only: published Server528 / Engine346 / unchanged Web183. Numeric Docker and Compose installation examples; immutable component identity kept separate. Sixteen scoped native Link/Container reads, 32 matched audit events, unchanged DB projection and owned cleanup, plus separate QA526-to528 start/restart. No full-role/matrix, active-node, company-site, image rebuild or test-replay claim. Normal signed merge and required CodeQL checks are retained.