Update the wasmer_registry::queries docs to mention backwards compati…

…bility and its low level nature

lib/registry/src/graphql.rs

@@ -106,7 +106,6 @@ pub(crate) mod proxy {
     }
 }
 
-
 #[cfg(target_os = "wasi")]
 pub fn whoami_distro() -> String {
     whoami::os().to_lowercase()

lib/registry/src/queries.rs

@@ -1,8 +1,20 @@
-//! The GraphQL queries used by this crate.
+//! Low-level GraphQL queries used by this crate.
 //!
-//! This module can be useful if you want to query the WAPM backend directly
-//! because the crate's high-level functions don't provide the exact
-//! operations/data you need.
+//! If possible, users should prefer the high-level functions exposed under
+//! [`crate`].
+//!
+//! This module is primarily used in combination with
+//! [`crate::graphql::execute_query()`] as an "escape hatch" for accessing
+//! information that may not be exposed via the high-level functions.
+//!
+//! # Backwards Compatibility
+//!
+//! Queries won't be deleted or have breaking changes to their inputs during
+//! patch releases, however new fields may be added to the response types
+//! generated by `graphql_client` at any time.
+//!
+//! Users should treat all response types as if they had the `#[non_exhaustive]`
+//! attribute.
 
 use graphql_client::*;