update code of conduct as it relates to LLM's

Author: romainmenke

AUTHORING_GUIDELINES.md

@@ -12,3 +12,5 @@ We will not create plugins with features (or add features to plugins) that look
 We will make it clear that non-standard, pre-processor features are just that.
 
 We will only implement that which we know is correct and avoid side effects.
+
+We will not use LLM's to produce at best mediocre outcomes.

CODE_OF_CONDUCT.md

@@ -55,7 +55,7 @@ a project may be further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting Jonathan Neal <jonathantneal@hotmail.com>. All
+reported by contacting Romain Menke <romainmenke+csstools@gmail.com>. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.

CONTRIBUTING.md

@@ -50,6 +50,9 @@ We try our best to create a safe and welcoming environment for contributors.
 Your changes do not have to be complete and tests do not have to pass before opening a pull request.
 Receiving early feedback on your work will help you iterate more quickly in the right direction.
 
+We do ask that you do not use LLM's to produce code, pull requests or issues.  
+You can use any aid to do your own review before submission, we only ask that you are the author of your own submissions.
+
 1. To begin; [fork this project], clone your fork, and add our upstream.
    ```bash
    # Clone your fork of the repo into the current directory