An open source design system that's fully customizable and agent ready
TypeScript
Document review scope preservation (#6403)
Cindy Zhangdf835ceb645b
diff --git a/docs/contributing/pull-requests.md b/docs/contributing/pull-requests.mdindex 508be8875e..79d9d37917 100644--- a/docs/contributing/pull-requests.md+++ b/docs/contributing/pull-requests.md@@ -49,6 +49,20 @@ Before requesting review, partition every observable delta:Remove or split tagalongs. A bug fix does not become a feature because a nearby affordance could also improve. A feature does not absorb unrelated cleanup because the same file is open.+## Reviews contract scope; they do not expand it++The opening primary intent sets the scope ceiling. The first submitted+implementation is a baseline for detecting later review-driven growth, not approval+for its tagalongs. A review request may make that intent correct and safe, require+evidence it needs, or remove/split a delta already in the pull request. It must not make a narrow+change absorb adjacent policy, migrations, sibling conformance, new API, or cleanup+merely because review discovered them.++If an earlier review caused the pull request to grow, the next pass should unwind or+split those additions rather than treating them as the new primary intent. Broader+work stays only when the original change cannot be correct or safe without it; then+request the smallest safe correction or a narrower mechanism.+## Use specifications last, not firstReview should produce the smallest ideal change that can land: