[Docs] Clarify public technical detail guidance - #1121
Closed
roomote-roomote[bot] wants to merge 1 commit into
Closed
[Docs] Clarify public technical detail guidance#1121roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
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
Clarified the open-source public-surface guidance so agents distinguish sensitive information from ordinary technical context. The guidance now explicitly permits useful non-sensitive details such as public URLs, error messages, stack traces, file paths, commands, and validation results, while directing agents to redact only sensitive portions.
Why this change was made
The previous instruction to omit private context could be interpreted too broadly, causing agents to suppress useful diagnostics merely because they appeared in a private task thread.
Impact
Public artifacts retain customer, credential, deployment, and internal-discussion protections while providing reviewers with the technical details needed to understand failures and verify changes.