review: clarify finding-ID numbering (I1) + tighten D1<->D2 test assertion (M1)

Author: Jon Langevin

skills/adversarial-design-review/SKILL.md

@@ -158,7 +158,7 @@ inherits the design's blast radius) and adds:
 **Findings (Minor):**
 - `D3` [class] [section/line]: <description>. Recommendation: <concrete fix>. _Resolution: <optional>._
 
-Design-phase finding IDs are `D1, D2, …`; plan-phase `P1, P2, …`. IDs are the durable anchor `post-merge-retrospective` correlates against; the optional `Resolution` is a scoring hint (retro falls back to downstream evidence when omitted). Each finding has a **stable finding ID** as its first token.
+Design-phase finding IDs are `D1, D2, …`; plan-phase `P1, P2, …`, numbered **sequentially across all findings regardless of severity** (`D1` is the first finding overall, not the first Critical). IDs are the durable anchor `post-merge-retrospective` correlates against; the optional `Resolution` is a scoring hint (retro falls back to downstream evidence when omitted). Each finding has a **stable finding ID** as its first token.
 
 **Bug-class scan transcript:**
 | Class | Result | Note |

tests/pipeline-evidence-doc-sync.sh

@@ -24,8 +24,10 @@ has "$ADR" "Write AND commit the report" \
 hasE "$ADR" 'stable finding ID|stable .*ID' \
   && pass "#69 ADR defines stable finding IDs" \
   || bad  "#69 ADR missing stable finding IDs"
-# P4: guard the load-bearing D1<->D2 path contract -- retro must cite the same derivation
-hasE "$RETRO" 'same deterministic rule|-plan-review\.md' \
+# P4/M1: guard the load-bearing D1<->D2 path contract -- retro must cite the SAME derivation.
+# Assert the specific load-bearing phrase only (dropping the broad '-plan-review.md' OR branch,
+# which is ambient vocabulary that could false-pass on an incidental path mention).
+has "$RETRO" "same deterministic rule" \
   && pass "#69/#70 retro derives the report path by the same rule (D1<->D2 contract)" \
   || bad  "#69/#70 retro missing the shared path-derivation rule"