#23725: Add Openclaw Code of Conduct

### Add Openclaw Code of Conduct ## Summary This pull request introduces the official Openclaw Code of Conduct to the repository. The goal of this addition is to clearly define the standards of behavior expected from all members of the Openclaw community, including founders, mentors, contributors, and participants. ## Purpose Establishing a Code of Conduct ensures that: The community remains welcoming and inclusive. All participants understand expected behavioral standards. Clear guidelines exist for reporting and addressing violations. The project fosters a respectful and productive environment. ## Changes Included Added a new CODE_OF_CONDUCT.md file. Defined behavioral expectations for all community members. Documented reporting procedures for violations. Included attribution to the original Speak Up! project text. ## Scope This Code of Conduct applies to: All project-managed spaces (IRC, mailing lists, issue trackers, events, forums). Community interactions within Openclaw environments. External behavior that may impact participation within project spaces. ## Impact This change does not affect application functionality or technical components. It strengthens governance, transparency, and community standards. ## References Original text courtesy of the Speak Up! project. <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a new `CODE_OF_CONDUCT.md` to the repository root, adapted from the Speak Up! project template. It is a documentation-only change with no impact on application functionality. - **Incomplete sentence on line 11**: The reporting section ends with "please see our " — the intended link or resource name was never filled in, leaving a broken sentence. - **Unadapted template reference**: Line 9 still references "DSF events" (Django Software Foundation), which was not updated to reflect OpenClaw. - **Naming convention mismatch**: The file uses "Openclaw" throughout, but the project convention (per `AGENTS.md`) is **OpenClaw** (camelCase C). All other community docs (`CONTRIBUTING.md`, `AGENTS.md`) use "OpenClaw" consistently. <h3>Confidence Score: 3/5</h3> - This is a documentation-only PR with no code changes, so there is zero risk to application functionality. However, the document has content issues that should be fixed before merging. - Score of 3 reflects that while the PR has no technical risk (documentation only), it contains an incomplete sentence (broken reporting instructions), an unadapted template reference ("DSF events"), and a naming convention mismatch. These are straightforward to fix but should be addressed before merging a governance document. - `CODE_OF_CONDUCT.md` — incomplete sentence on line 11, unadapted "DSF events" reference on line 9, and naming convention inconsistency throughout. _{Last reviewed commit: fb62f24} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13)) <!-- /greptile_comment -->