diff --git a/PLAN.md b/PLAN.md
index 45ae8ce..2b61653 100644
--- a/PLAN.md
+++ b/PLAN.md
@@ -403,8 +403,9 @@ inside `crud` and test the aggregate *command* — cursor and `batchSize`,
 `readConcern` routing, the write semantics of `$out`/`$merge`, `collation`,
 `let`. They touch stages barely and expressions not at all; `$lookup`,
 `$unwind`, `$facet`, `$addFields` and `$replaceRoot` appear nowhere in the
-pinned corpus. A literal "green" is unreachable besides, since 10 of the skips
-are version- or topology-gated and cannot pass on a standalone.
+pinned corpus. A literal "green" is unreachable besides: all 19 skips are
+version- or topology-gated and none can pass on a standalone, so the gate is
+stated as *0 fail* rather than *all pass*.
 
 So one milestone name was covering two milestones, and they are split.
 
diff --git a/docs/M2_DESIGN_REVIEW.md b/docs/M2_DESIGN_REVIEW.md
index edfe378..5b723a5 100644
--- a/docs/M2_DESIGN_REVIEW.md
+++ b/docs/M2_DESIGN_REVIEW.md
@@ -52,9 +52,11 @@ aggregate-*.json overall     9 pass   13 fail   19 skip
 | `collation` in aggregate | 1 |
 | `let` | 1 |
 
-Of the 19 skips, 13 are environmental (`needs topology replicaset`, `needs
-server >= 5.0`, `needs server >= 8.2.0`) and can never turn green on a
-standalone. A literal reading of "green" is unreachable for that reason alone.
+All 19 skips are environmental -- 10 distinct requirements, some covering a
+whole file at once (`needs topology replicaset`, `needs server >= 5.0`, `needs
+server >= 8.2.0`, `needs server <= 4.2.99`). Not one can turn green on a
+standalone, so a literal reading of "green" is unreachable for that reason
+alone, and the gate has to be stated as *0 fail* rather than *all pass*.
 
 ---