Clarify and extent contribution guidelines around AI usage

Co-authored-by: Sebastian Thiel <sebastian.thiel@icloud.com>

Author: codex

COLLABORATING.md

@@ -16,6 +16,15 @@
     - …and you _do know_ the cause, please fix it immediately. If necessary by reverting the offending commit until a more durable fix is possible.
     - …and you _do not know_ the cause, please open a PR to invite collaborators for their input. This is to avoid multiple collaborators
       trying to fix the issue independently, causing merge-conflicts and confusion. We use this PR as synchronization primitive.
+- **please disclose AI assistance when collaborating**
+   - if AI edits files for you, disclose it in the PR description and commit metadata, preferably with an AI author
+     such as `$agent $version <ai-agent@example.invalid>` or a `Co-authored-by: <agent-identity>` trailer.
+   - agents operating through a person's GitHub account must identify themselves in comments, for example with phrases
+     like `AI agent on behalf of <person>: ...`.
+   - fully AI-generated PR or issue comments must be disclosed. Undisclosed AI-generated comments may lead to the PR or
+     issue being closed.
+   - AI-assisted proofreading or wording polish does not need disclosure, but it is still courteous to mention it when
+     the AI materially influenced the final text.
 - **for crates _you own_**
     - feel free to make any kind of changes to it, including major ones.
     - please use `cargo smart-release` for publishing to crates.io as it will handle dependencies properly.

CONTRIBUTING.md

@@ -1,7 +1,18 @@
-### Please disclose the use AI…
+### Please disclose the use of AI
 
-…if it's editing files for you please let us know in the PR comment _or preferably_ using
-`Co-authored-by: <agent-identity>` message trailers.
+If AI edits files for you, disclose it in the PR description and commit metadata. Prefer making the
+agent identity part of the commit, for example by using an AI *author* such as `$agent $version <ai-agent@example.invalid>`
+or a *co-author* via `Co-authored-by: <agent-identity>` trailer.
+Recent commits in this repository use that pattern, often with a *human* `Co-authored-by` trailer when a person also contributed directly.
+
+Agents operating through a person's GitHub account must identify themselves. For example, comments
+posted by an agent should say so directly with phrases like `AI agent on behalf of <person>: ...`.
+
+Fully AI-generated comments on PRs or issues must also be disclosed. Undisclosed AI-generated
+comments may lead to the PR or issue being closed.
+
+AI-assisted proofreading or wording polish does not need disclosure, but it is still courteous to
+mention it when the AI materially influenced the final text.
 
 For everything else, please have a look at the respective section in the [README] file.
 

README.md

@@ -348,8 +348,10 @@ We recommend running `just test` during the development process to assure CI is
 A backlog for work ready to be picked up is [available in the Project's Kanban board][project-board], which contains instructions on how
 to pick a task. If it's empty or you have other questions, feel free to [start a discussion][discussions] or reach out to @Byron [privately][keybase].
 
-For additional details, also take a look at the [collaboration guide].
+For additional details, also take a look at the [collaboration guide]. If AI participates in a contribution, please
+follow the [AI disclosure requirements]. "Full-auto" contributions without a human on the other end may be closed unceremoniously.
 
+[AI disclosure requirements]: https://github.com/GitoxideLabs/gitoxide/blob/main/CONTRIBUTING.md#please-disclose-the-use-of-ai
 [collaboration guide]: https://github.com/GitoxideLabs/gitoxide/blob/main/COLLABORATING.md
 [project-board]: https://github.com/GitoxideLabs/gitoxide/projects
 [discussions]: https://github.com/GitoxideLabs/gitoxide/discussions