docs(agents): add community and character guidance to AGENTS.md

[yonib05]

Summary

Parallel to the harness-sdk change, inspired by p5.js's AGENTS.md — a great example of using the agent guide to grow and sustain an OSS community.

AGENTS.md today is technical (architecture, patterns, the PR quality bar). This adds the missing community and character layer: how an agent should treat the people contributing, not just the code.

What it adds

A "Working with the Community" section near the top, covering:

• Your role — a guide, not a gatekeeper or substitute author; point people to the Discord and Discussions; assume good faith.
• How to talk with people — with contributors not at them; one question at a time; warm, plain, concise; explain the why.
• What good looks like — a small change the contributor understands beats a large one they can't explain; good first issues bring newcomers in; generosity grows the community.

Testing

• N/A — docs only.

---

Merge order: lands after #258 (Creating a High-Quality PR), which this section links to via the #creating-a-high-quality-pr anchor.

[github-actions]

Assessment: Approve

Docs-only change (+19 lines) adding a "Working with the Community" section to AGENTS.md. The framing is clear, consistent with the existing document's voice, and complements CONTRIBUTING.md rather than overlapping with it. No blocking or substantive concerns.

Review notes

• Scope: Small, focused, docs-only — no code/API/test impact (N/A testing is correct).
• Links: Both the Discord and GitHub Discussions links resolve; Discord matches the badge/link already in README.md.
• Consistency: New section sits naturally at the top and doesn't duplicate CONTRIBUTING.md (which points contributors to Issues for bugs/features, while this routes design discussion to Discord/Discussions).
• Content: Guidance is constructive and actionable; no factual or structural issues.

Nicely written addition — the "guide, not gatekeeper" framing is a good north star for agent behavior.

[github-actions]

Assessment: Approve

Re-reviewed after the update — the section was tightened to three focused bullets (now +8 lines) and a quality-bar link was added. Reads even better than before. No blocking concerns.

Review notes

• Scope: Docs-only, small and focused; testing N/A is correct.
• Links: Discord and GitHub Discussions both resolve.
• Content: The trimmed wording is an improvement — "guide, not gatekeeper" plus the three bullets land cleanly without the prior repetition.

One non-blocking note — cross-PR anchor dependency: The new link [Creating a High-Quality PR](#creating-a-high-quality-pr) points to a heading that doesn't exist on main yet; it's introduced by #258 (which renames "PR and Commit Conventions" → "Creating a High-Quality PR"). I confirmed #258's diff produces exactly that anchor, so the link will resolve correctly as long as #258 merges first — which your PR description already calls out. Just flagging so the merge order isn't lost; if #261 were to land first, this would be a temporary dead anchor.

[github-actions]

Assessment: Approve

Re-reviewed after commit cb51bfa. This update swaps the same-file #creating-a-high-quality-pr anchor for a direct CONTRIBUTING.md link — which fully resolves the non-blocking note from my previous review and, as a bonus, removes the merge-order dependency on #258.

Review notes

• Prior feedback addressed: No same-file anchors remain in the section; the CONTRIBUTING.md target exists at the repo root, so the link resolves on main today.
• Links: Discord and GitHub Discussions both resolve.
• Scope: Docs-only, +8 lines, testing N/A correct.

No remaining concerns — this is ready from my side. 👍