docs: note that analyze, parse and fmt are in beta

Add a GitHub alert at the top of each command's page so readers know the
flags and output are still subject to change, and that fmt rewrites query
files in place.

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

Author: claude

docs/howto/analyze.md

@@ -1,5 +1,10 @@
 # `analyze` - Analyzing query result types
 
+> [!NOTE]
+> `analyze` is in beta. Its flags and JSON output may change in a
+> future release, and the types it reports can differ from the ones
+> `generate` produces.
+
 `sqlc analyze` analyzes a query against a schema and prints the inferred result
 columns and parameters as a single JSON document.
 

docs/howto/fmt.md

@@ -1,5 +1,10 @@
 # `fmt` - Formatting queries
 
+> [!NOTE]
+> `fmt` is in beta. It rewrites your query files in place, so commit
+> or back them up first. The formatting it produces may change in a
+> future release.
+
 `sqlc fmt` rewrites the query files referenced by your configuration file in a
 canonical format. Each query is parsed with the engine's parser and printed
 back from the syntax tree, so formatting never depends on how the query was

docs/howto/parse.md

@@ -1,5 +1,9 @@
 # `parse` - Parsing SQL into an AST
 
+> [!NOTE]
+> `parse` is in beta. Its flags and the shape of the JSON AST it
+> prints may change in a future release.
+
 `sqlc parse` parses SQL from a file or standard input and prints the abstract
 syntax tree (AST) as a single JSON document. It does not require a configuration
 file or a database connection.