fix: Module 11 review round 1 (ON ALL: quote the Conditions page, label the course's meaning)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/research/baba-is-you.md

@@ -127,11 +127,12 @@ Loaded with curl through the MediaWiki API, as in §5: `https://babaiswiki.fando
 |---|---|---|
 | [ON](https://babaiswiki.fandom.com/wiki/ON) | 17403 (2025-10-05) | "ON is an infix condition that makes a rule apply when object is overlapping another object." / "FLAG ON BABA IS WIN makes flag WIN only when it's on a baba." / "FLAG ON BABA AND BABA IS WIN makes flag WIN only when it's on two babas." / "FLAG NOT ON BABA IS WIN makes flag WIN only when it's not on a baba." / "ON ignores FLOAT levels: FLAG ON BABA IS WIN makes flag WIN when it's on a baba even if BABA IS FLOAT and FLAG IS NOT FLOAT or vice versa." / "Objects are parsed in order of object priority; earlier on the list goes first." |
 | [NEAR](https://babaiswiki.fandom.com/wiki/NEAR) | 18131 (2026-04-11) | "NEAR is an infix condition that makes a rule apply when an object is on a target or in one of the eight spaces around it" / "PILLAR NEAR FLAG IS PINK makes Pillar turn PINK if a Flag is ON the Pillar, directly adjacent, or diagonally adjacent." / "FLAG NEAR BABA AND KEKE IS WIN makes flag WIN if NEAR both a baba and a keke." / "NEAR can be stacked: ROCK NEAR GRASS AND GRASS IS WIN requires at least 2 grass NEAR the Rock for it to be WIN." / "PILLAR NOT NEAR FLAG IS GREEN makes Pillar turn GREEN if there is no Flag ON the Pillar, directly adjacent, or diagonally adjacent." The page says nothing about FLOAT. |
-| [Conditions](https://babaiswiki.fandom.com/wiki/Category:Conditions) (redirects to Category:Conditions) | 18040 (2026-02-02) | "Conditions are operators that allow only some of a particular object to be impacted by a rule." / "They are parsed as noun1 condition noun2 verb thing, where noun1 verb thing only if the condition is true." / "Conditions can be negated by prefixing with NOT." / "AND in the noun1 part works like normal. For example, BABA AND KEKE ON SKULL IS DEFEAT expands into BABA ON SKULL IS DEFEAT and KEKE ON SKULL IS DEFEAT" / "AND in the noun2 part requires at least as many objects as are mentioned." / "BABA ON KEKE AND KEKE IS WIN makes a Baba WIN if it is ON two (stacked) Kekes." / "Multiple conditions can share objects between the conditions." / "It is not possible to write something like noun1 condition1 noun2 condition2 noun3 verb thing. This will parse as noun2 condition2 noun3 verb thing." / On matching AND-ed nouns with NOT: "it doesn't backtract to try matching" (sic) and "the game first claims objects for all non-NOT cases, then claims objects for the NOT cases in order with the first object that matches." Prefix conditions (LONELY, IDLE, POWERED, ...) are "parsed as condition noun verb thing". |
+| [Conditions](https://babaiswiki.fandom.com/wiki/Category:Conditions) (redirects to Category:Conditions) | 18040 (2026-02-02) | "Conditions are operators that allow only some of a particular object to be impacted by a rule." / "They are parsed as noun1 condition noun2 verb thing, where noun1 verb thing only if the condition is true." / "Conditions can be negated by prefixing with NOT." / "AND in the noun1 part works like normal. For example, BABA AND KEKE ON SKULL IS DEFEAT expands into BABA ON SKULL IS DEFEAT and KEKE ON SKULL IS DEFEAT" / "AND in the noun2 part requires at least as many objects as are mentioned." / "BABA ON KEKE AND KEKE IS WIN makes a Baba WIN if it is ON two (stacked) Kekes." / "Multiple conditions can share objects between the conditions." / "It is not possible to write something like noun1 condition1 noun2 condition2 noun3 verb thing. This will parse as noun2 condition2 noun3 verb thing." / On matching AND-ed nouns with NOT: "it doesn't backtract to try matching" (sic) and "the game first claims objects for all non-NOT cases, then claims objects for the NOT cases in order with the first object that matches." Prefix conditions (LONELY, IDLE, POWERED, ...) are "parsed as condition noun verb thing". / "ALL in the noun2 part requires one of every object in ALL, versus NOT TEXT or NOT EMPTY which requires any one object that is in ALL." / "BABA ON ALL AND ALL AND FLAG IS WIN requires that baba be ON two of everything in ALL (not counting itself) plus an extra flag." (re-checked 2026-11-11, fix round 1, same revision) |
 | [NOT](https://babaiswiki.fandom.com/wiki/NOT) (re-fetched) | 18314 | "When added after a verb it makes the corresponding rule not apply, overriding other instances of the rule it disables." / "ROCK ON BABA IS NOT PUSH makes ROCK that is on BABA not PUSHable." / "When added before a condition, it reverses the condition." / "FLAG ON NOT BABA IS WIN makes flag WIN when it is ON something other than baba" |
 | [Order of Operations](https://babaiswiki.fandom.com/wiki/Order_of_Operations) (re-fetched) | 17942 (2026-01-03) | Same text as §3 for the quotes recorded there. On conditions: "Conditions process when the game checks for what objects have a rule, which is usually right before it uses it." / "it completely finishes moving for a particular move stage before checking which units are in the next, so conditions (e.g. IT ON BABA IS YOU AND MOVE) reparse in between." / Under "Other considerations": "conditions on these rules are rechecked at the time of destruction, even if multiple destructions occur in the same turn." (about HAS). |
 
 - **What the pages do not say.** None of them says in so many words how a conditional `NOT` rule meets an unconditional one (`BABA IS YOU` with `BABA ON KEY IS NOT YOU`). The NOT page says a negation overrides "other instances of the rule it disables", and its example "ROCK ON BABA IS NOT PUSH makes ROCK that is on BABA not PUSHable" names only the rocks on a Baba. Module 11 reads the two together: the negation wins for each object its condition holds for, and only for those. That reading is the course's.
+- **`ALL` after a condition (stated, not followed by the course).** The Conditions page says `ON ALL` needs one of every object in ALL (not counting the object itself), where `NOT TEXT` would need any one. Module 11 gives `ON ALL` the simpler meaning "any other object that isn't text", as `ALL` names objects when it is a subject. That meaning is the course's choice, labelled in the lesson and scenarios.
 - **Whether an object can satisfy its own condition.** ON says "overlapping another object"; NEAR says "on a target or in one of the eight spaces around it". Neither says whether `ROCK ON ROCK` can be satisfied by the rock itself. The course counts only other objects.
 - **Course use (Module 11):** ON ignores float levels (stated). AND in the condition needs one distinct object per listed noun (stated: "at least as many objects as are mentioned"). The course's grammar has one condition per sentence, no `NOT` before a condition, and no prefix conditions; NEAR is the Expansion Drop.