Repository navigation
docs: keep scoped workspace acquisition and builds autonomous - #15
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.
Clarify that task-scoped, pinned and verified workspace-local acquisition, builds and isolated tests are normal authorized development steps and need no per-download permission. Preserve the prohibition on untrusted executables and the explicit approval boundary for global installation or permanent changes outside the workspace. Product update development does not itself grant outside-workspace installation rights. Private data, host-networking and project-opening restrictions remain unchanged.
This follows the previous instruction clarification without rewriting its history.
Validation: git diff --check; reviewed the AGENTS.md-only diff. No runtime behavior changed.