The clause keywords: keyword tokens that start or continue a clause
(MATCH, ORDER BY, AS, DISTINCT, …). is_ident_like() rejects
them as variables, aliases and map keys, so (WHERE ...) does not read
WHERE as the element variable. ADR-0169: they are still label and
relationship-type names (is_schema_name()).
The reserved-keyword clause-starter tokens: the keyword tokens that
start a new clause at clause position (MATCH, CREATE, UNWIND,
FOR (CIP-250), …). The grammar authority is the clause dispatch
(Parser::parse_clause_inner); this table is the derived vocabulary
every lookahead over the same fact consults instead of re-spelling a
second hand-maintained list – through [is_clause_boundary], by
Parser::group_by_ends_clause (whose round-5 comment records the
LOAD/DROP drift that motivated it) and the simple-CASE lookahead – and
the dispatch-coverage pin test. A new clause-start dispatch arm
extends this one table. OPTIONAL is a member: it starts a clause
only immediately before MATCH/CALL (the arm that checks what
follows). The contextual (identifier-spelled) starters are the
separate CONTEXTUAL_CLAUSE_WORDS below.
The contextual (non-reserved, identifier-spelled) clause keywords:
words that start or continue a clause when they appear as a plain
Identifier at clause position, recognized by spelling – the same
role as CLAUSE_KEYWORDS, but these stay usable as ordinary
variable/label names everywhere else (MATCH (show) RETURN show).
Single-sourced here so the clause dispatcher
(Parser::parse_clause_inner) and the SHOW SETTINGS-style
filter-expression starter (Parser::peek_starts_show_filter_expr,
which excludes exactly this set so a following composed clause is not
swallowed as a filter expression) can never drift apart.