Drop an unverified claim about who enables the option

The doc comment named a specific vendor's build as shipping with
SQLITE_ENABLE_UPDATE_DELETE_LIMIT. I could not verify it, so it goes; the
part that carries the argument -- the option rewrites the parser tables,
so it lives in a build meyer cannot detect from the SQL -- stands on its
own.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019kZMPnsTWywB5icVh1wJrA

Author: claude

parser/parser.go

@@ -91,10 +91,10 @@ type Options struct {
 	// UpdateDeleteLimit accepts ORDER BY and LIMIT on UPDATE and DELETE,
 	// as SQLITE_ENABLE_UPDATE_DELETE_LIMIT does. The pinned build defines
 	// neither it nor SQLITE_UDL_CAPABLE_PARSER, so those clauses are a
-	// syntax error by default -- but the option is common enough (Android's
-	// SQLite ships with it, and it is what updateDeleteLimitError in
-	// parse.y exists to complain about) that the clauses have to be
-	// parseable on request.
+	// syntax error by default. The option selects grammar rules, so a
+	// database built with it can only be built from canonical sources --
+	// which also means meyer cannot tell from the SQL alone, and the caller
+	// has to say.
 	//
 	//	cmd ::= with DELETE FROM xfullname indexed_opt where_opt_ret
 	//	        orderby_opt limit_opt.