@@ -16,4 +16,4 @@ Clause-②: no (narrowing)
 
 **Who is affected.** A caller of `engine.aggregate` or of the REST query door that grouped by such a field on the in-memory driver or on SQLite and read the merged or per-serialization groups as real ones. On PostgreSQL the same query was already a 500. The analytics service's aggregate path (a cube query the native-SQL strategy declines, such as a time dimension with a granularity, or any cube query on the in-memory driver) reaches the engine and answers this refusal too.
 
-**Unchanged.** A `groupBy` on any other type (`text`, `number`, a `multiple: true` select, a file field), a structured-JSON field as an AGGREGATED column (`count`, `count_distinct`, `min`, `max`), and an undeclared name, which the REST door answers `INVALID_FIELD` as unknown before the engine is reached.
+**Unchanged by this entry.** A `groupBy` on a scalar-stored type (`text`, `number`, a single-value file field), a structured-JSON field as an AGGREGATED column (`count`, `min`, `max`), and an undeclared name, which the REST door answers `INVALID_FIELD` as unknown before the engine is reached. A `groupBy` on a multi-value field and a `count_distinct` over a structured-JSON field are refused too, by the multi-value / JSON-stored entry of this same release.
Original file line number	Diff line number	Diff line change
`@@ -16,4 +16,4 @@ Clause-②: no (narrowing)`
`16`	`16`
`17`	`17`	Who is affected. A caller of `engine.aggregate` or of the REST query door that grouped by such a field on the in-memory driver or on SQLite and read the merged or per-serialization groups as real ones. On PostgreSQL the same query was already a 500. The analytics service's aggregate path (a cube query the native-SQL strategy declines, such as a time dimension with a granularity, or any cube query on the in-memory driver) reaches the engine and answers this refusal too.
`18`	`18`
`19`		-Unchanged. A `groupBy` on any other type (`text`, `number`, a `multiple: true` select, a file field), a structured-JSON field as an AGGREGATED column (`count`, `count_distinct`, `min`, `max`), and an undeclared name, which the REST door answers `INVALID_FIELD` as unknown before the engine is reached.
	`19`	+Unchanged by this entry. A `groupBy` on a scalar-stored type (`text`, `number`, a single-value file field), a structured-JSON field as an AGGREGATED column (`count`, `min`, `max`), and an undeclared name, which the REST door answers `INVALID_FIELD` as unknown before the engine is reached. A `groupBy` on a multi-value field and a `count_distinct` over a structured-JSON field are refused too, by the multi-value / JSON-stored entry of this same release.