[kvlonge]

Why

The playground's first impressions had three rough edges:

• The "Syntax error" example, a condition left open before GROUP BY, put its error one token late, at BY.
• A statement ending where an expression belongs, such as an empty WHERE, said "Unexpected token: Where".
• An unaliased column's SQ0009 label named an internal node kind (j_s_o_n_extract). Its help guessed a wrong alias for paths ("PAYLOAD" for payload:page) and a quoted copy for literals.

Changes

One commit each:

• GROUP or ORDER directly before BY always starts the clause and is never read as a name, so the error points at GROUP or ORDER.
• A statement that ends where an expression belongs says what is missing: a condition after WHERE, HAVING, QUALIFY or ON, otherwise an expression.
• The SQ0009 label reads "Snowflake names this column after its text". A literal or path says its quotes or path are part of the name, and its help asks for an alias without guessing one. Statements are still refused.

Verification

• The GROUP BY span test fails on main (the error points at BY) and passes here. New tests pin the empty-clause wording, and the CLI expectations are updated for the SQ0009 label.
• The six playground examples and the basics, everyday and everyday-models corpora (2,956 queries) went through the playground's own analyze with its default settings. No outcome or converted SQL changed; 67 messages changed, all as above.
• make check-ci passes.