docs: add validation check on key ordering

Author: Yuxiang-Huang

__meta/validators/README.md

@@ -27,6 +27,8 @@ and running `taplo fmt --check` and `taplo check`.
 
 We also include several other checks to ensure integrity:
 
+- The key orderings in a TOML file must match the the ordering of `properties` in the corresponding schema file.
+
 - The `github-username` field for contributors must match the filename.
 
 - The `slug` field for teams must match the filename.

__meta/validators/governance/src/loader.rs

@@ -26,9 +26,7 @@ pub fn load_from_dir<T: DeserializeOwned + Debug + HasKeyOrder>(
         // Calculate the key order for the item.
         let mut item: T = toml::from_str(&content)
             .with_context(|| format!("Failed to parse {} file: {}", item_name, path.display()))?;
-
-        // Parse into IndexMap to get key order.
-        let index_map: IndexMap<String, Value> = from_str(&content)?;
+        let index_map: IndexMap<String, Value> = from_str(&content)?; // Parse into IndexMap to get key order.
         let key_order: Vec<String> = index_map.keys().cloned().collect();
         item.set_key_order(key_order);