|
|
@@ -181,6 +181,11 @@ final whole-branch review. When you fill a reviewer template:
|
|
|
findings in the progress ledger as you go, and point the final
|
|
|
whole-branch review at that list so it can triage which must be fixed
|
|
|
before merge. A roll-up nobody reads is a silent discard.
|
|
|
+- A finding labeled plan-mandated — or any finding that conflicts with
|
|
|
+ what the plan's text requires — is the human's decision, like any plan
|
|
|
+ contradiction: present the finding and the plan text, ask which governs.
|
|
|
+ Do not dismiss the finding because the plan mandates it, and do not
|
|
|
+ dispatch a fix that contradicts the plan without asking.
|
|
|
- The final whole-branch review gets a package too: run
|
|
|
`scripts/review-package MERGE_BASE HEAD` (MERGE_BASE = the commit the
|
|
|
branch started from, e.g. `git merge-base main HEAD`) and include the
|