docs: clarify public orchestration and connection ownership - #76
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
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.
Clarify the public CDB modules’ responsibilities after the connection lifecycle and notification changes in #75. The architecture now shows connection replacement, subscription disposal and the boundary between broker orchestration, host policy and optional Chrome bindings.
Updated the README and agent guidance to match those boundaries, including headless notifications and the optional default renderer. This follow-up changes documentation only; it does not change browser behavior or release readiness.
Validation: reviewed the module paths and exported interfaces against the implementation. Full verification runs in CI. The outstanding downstream functional TNR and performance results remain separate release gates.