[Docs] Explain approval controls while browsing chat history - #53
Draft
zoomote[bot] wants to merge 1 commit into
Draft
[Docs] Explain approval controls while browsing chat history#53zoomote[bot] wants to merge 1 commit into
zoomote[bot] 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
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.
What changed
Why this change was made
The chat-interface guide should reflect the paired Zoo-Code fix for Zoo-Code-Org/Zoo-Code#1447 and set the correct expectation for manual approval workflows.
Impact
Users can understand that scrolling does not hide or defer a pending approval. The documentation build, type check, and lint pass. A new extension screenshot is not included because this task's approved proof browser exposes only the docs site, not the VS Code Extension Host surface.
Related PRs