From b481f39ca3626ef826f0058d11835c513e1eda24 Mon Sep 17 00:00:00 2001 From: "A.Shakhmatov" Date: Sun, 9 Aug 2026 19:40:47 +0300 Subject: [PATCH] docs/plan: all 19 aggregate skips are environmental, not 13 The scorecard collapses a whole-file skip into a single `*` line, so counting the reason lines undercounted the cases they cover. Every one of the 19 is version- or topology-gated, which is why the gate reads *0 fail* rather than *all pass*. --- PLAN.md | 5 +++-- docs/M2_DESIGN_REVIEW.md | 8 +++++--- 2 files changed, 8 insertions(+), 5 deletions(-) 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*. ---