docs: add Code of Conduct

[mrizzi]

Summary

• Add Contributor Covenant v2.1 as the project's Code of Conduct
• Satisfies the GitHub Community Standards "Code of Conduct" requirement

Test plan

• Verify CODE_OF_CONDUCT.md appears in the repo root
• Confirm GitHub Community Standards page now shows Code of Conduct as present

🤖 Generated with Claude Code

Summary by Sourcery

Documentation:

• Introduce CODE_OF_CONDUCT.md with the Contributor Covenant v2.1 to document expected behavior and enforcement guidelines for project participants.

[sourcery-ai]

Reviewer's Guide

Adds a Contributor Covenant v2.1-based Code of Conduct to the repository as CODE_OF_CONDUCT.md to satisfy GitHub’s Community Standards requirement.

File-Level Changes

Change	Details	Files
Introduce a formal project Code of Conduct based on Contributor Covenant v2.1.	Add new CODE_OF_CONDUCT.md at the repository root containing the standard Contributor Covenant v2.1 text. Define expected community behavior, unacceptable conduct, enforcement responsibilities, scope, and enforcement guidelines with graduated consequences. Specify reporting channels (GitHub issue tracker or direct contact with maintainers) and state privacy expectations for reporters. Include attribution and reference links to Contributor Covenant documentation, FAQ, and translations.	CODE_OF_CONDUCT.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider specifying a concrete reporting channel (e.g., a dedicated email address or GitHub team alias) instead of the generic “project's GitHub issue tracker or by contacting a maintainer directly” to make the enforcement process clearer and safer for reporters.
• You may want to define who the “community leaders” are in the context of this project (e.g., specific roles or GitHub teams) so contributors know who is responsible for enforcement and how decisions are made.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider specifying a concrete reporting channel (e.g., a dedicated email address or GitHub team alias) instead of the generic “project's GitHub issue tracker or by contacting a maintainer directly” to make the enforcement process clearer and safer for reporters.
- You may want to define who the “community leaders” are in the context of this project (e.g., specific roles or GitHub teams) so contributors know who is responsible for enforcement and how decisions are made.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}