ci(permit): rubric denies on P0/P1 only; add severity discipline

scripts/autonomous_release_permit.py

@@ -365,13 +365,24 @@ def prepare(args: argparse.Namespace) -> None:
 breakage, missing negative tests, and ways the change could weaken required gates.
 
 VERDICT
-- ALLOW only when you found no P0, P1, or P2 issue.
-- DENY when any P0, P1, or P2 issue exists or evidence is insufficient for a safety-critical change.
+- ALLOW when you found no P0 and no P1 issue. P2 and P3 findings do not change
+  an ALLOW: report them and still return ALLOW.
+- DENY when any P0 or P1 issue exists, or evidence is insufficient for a
+  safety-critical change.
 - P0: immediate catastrophic compromise or irreversible loss.
 - P1: exploitable security, authorization, data-integrity, or release-gate failure.
 - P2: material correctness, reliability, compatibility, or test-coverage defect.
+  Deferred, not blocking — it is recorded on the permit and owed a follow-up.
 - P3: non-blocking maintainability or polish issue.
 
+SEVERITY DISCIPLINE
+Assign the severity the defect actually carries; do not raise a P2 to P1 to
+force attention, and do not lower a real P1 because the change is large or
+mostly good. A finding that asks for work outside this change's stated scope
+is at most P2. Scope is set by the change itself, not by what a complete
+implementation would eventually need — a library-only or phase-1 change is not
+deficient for lacking an integration it does not yet claim.
+
 OUTPUT
 Return exactly one JSON object and no markdown or prose:
 {{"verdict":"ALLOW|DENY","findings":[{{"severity":"P0|P1|P2|P3","code":"STABLE_CODE","summary":"concise evidence-backed finding","path":"optional/repo/path","line":1}}]}}