fix(spec): the null ordering-comparand refusal and the vocabulary assertion name only faces that exist

The schema-door refusal for a null $gt/$gte/$lt/$lte comparand gave, as its
example of the evaluation faces disagreeing, driver-memory's reference matcher,
which has been deleted. The parenthesis now names two faces that exist and were
measured to disagree: driver-memory's query path admits a stored-null row for
{"$gte": null}; driver-sql compares against SQL NULL and admits no row. The
first sentence, the prescription and the ruling sentence are unchanged.

The filter-operator vocabulary assertion message no longer lists the deleted
reference matcher among driver-memory's faces.

Claude-Session: https://claude.ai/code/session_01YDt3PzwfrkuFzUBF89WPmM
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/21397-null-ordering-message-faces.md

@@ -0,0 +1,20 @@
+---
+'@objectstack/spec': patch
+---
+
+fix(spec): the null ordering-comparand refusal names only evaluation faces that exist
+
+Clause-②: no
+
+`FieldOperatorsSchema` and `ComparisonOperatorSchema` refuse a `null` comparand of `$gt` / `$gte` /
+`$lt` / `$lte` with a pointed message. Its example of the evaluation faces disagreeing named
+driver-memory's reference matcher, which has been deleted, so an author or agent reading the
+refusal went looking for a face that no longer exists. The example now names two faces that exist
+and were measured to disagree: driver-memory's query path reads a stored `null` as equal to the
+comparand, so `{"$gte": null}` admits that row, while driver-sql compares against SQL `NULL` and
+admits no row.
+
+Text only: the first sentence (`null is not a valid $gt comparand.` and its siblings), the prescription
+(`{"$eq": null}` / `{"$ne": null}`) and the ruling sentence are unchanged, and the schemas accept
+and refuse exactly the same filters. A client or log filter that matches the old parenthesis needs
+the new spelling.

packages/spec/src/data/filter-operator-vocabulary.test.ts

@@ -83,8 +83,8 @@ describe('the declaration surface and the enforcement surface', () => {
         + 'so declaring ahead of the arms is the correct staging. To stage one: declare it in '
         + 'FieldOperatorsSchema, add it to the array THIS assertion compares against, and note on '
         + 'FILTER_OPERATORS which issue implements it. To clear one: implement it on EVERY face '
-        + 'in ONE PR — spec word list, driver-memory (query path, reference matcher, analytics '
-        + 'face), driver-mongodb, service-analytics (3 compilers), objectql `having`, formula — '
+        + 'in ONE PR — spec word list, driver-memory (query path, analytics face), '
+        + 'driver-mongodb, service-analytics (3 compilers), objectql `having`, formula — '
         + 'then empty this list. #6520 is the worked example of the clearing direction.',
     ).toEqual(STAGED_AHEAD_OF_BACKENDS);
   });

packages/spec/src/data/filter.zod.ts

@@ -466,8 +466,9 @@ const ORDERING_COMPARAND_DESCRIPTION =
 function nullOrderingComparandMessage(op: string): string {
   return (
     `null is not a valid ${op} comparand. null is not ordered, and no two evaluation faces `
-    + 'agree on what an ordering against it matches (driver-memory\'s live path reads two '
-    + 'absences as equal; its reference matcher compares through JS coercion). State absence '
+    + 'agree on what an ordering against it matches (driver-memory\'s query path reads a '
+    + 'stored null as equal to it, so {"$gte": null} admits that row; driver-sql compares '
+    + 'against SQL NULL and admits no row). State absence '
     + 'with the null predicate instead: {"$eq": null} is "has no value", {"$ne": null} is '
     + '"has a value". Ruled 2026-09-01: a null ordering comparand is refused at the validation '
     + 'entrance.'