Fixes #905

@@ -123,4 +106,0 @@
-[do not replicate the name in your functions or
-variables](https://developers.google.com/style/inclusive-documentation#write-around).
-
-In addition to language, write and code with the user experience in mind. This

@@ -36,6 +26,10 @@ You can run these checks locally by installing [prefligit](https://github.com/j1
 
 
 ```bash
+# Requires UV:

@@ -48,6 +42,8 @@ prefligit --all-files
 
 Alternatively, you can use [pre-commit](https://pre-commit.com/):
 ```bash
+# Requires python

@@ -0,0 +118,4 @@
+Use appropriate log levels:
+
+- `error!`: Unrecoverable errors that affect functionality
+- `warn!`: Potentially problematic situations that don't stop execution

@@ -0,0 +184,4 @@
+Use the `WithLock` trait from `continuwuity-core::utils::with_lock`:
+
+```rs
+use continuwuity_core::utils::with_lock::WithLock;

@@ -0,0 +205,4 @@
+For async contexts, use the async variant:
+
+```rs
+use continuwuity_core::utils::with_lock::WithLockAsync;

@@ -0,0 +318,4 @@
+
+The following types of language are explicitly forbidden in all code, comments, documentation, and commit messages:
+
+**Ableist language:** Avoid terms like "sanity check", "crazy", "insane", "cripple", or "blind to". Use alternatives like "validation", "unexpected", "disable", or "unaware of".

@@ -0,0 +328,4 @@
+
+Use diverse examples in documentation that avoid culturally-specific references, assumptions about user demographics, or unnecessarily gendered language. Design with accessibility and inclusivity in mind by providing clear error messages and considering diverse user needs.
+
+This software is intended to be used by everyone regardless of background, identity, or ability. Write code and documentation that reflects this commitment to inclusivity.