Document AI attribution labels for curated entries

[Copilot]

Adds a consistent way to label AI-authored or AI-assisted projects in the curated list. This clarifies when AI provenance should be called out and standardizes the phrasing contributors should use in entry descriptions.

• AI attribution guidance

  • Adds an AI Attribution section to contributing.md
  • Defines the approved labels:
    • AI-generated
    • AI-assisted
    • Built with AI assistance
  • Limits use to cases where AI provenance materially helps readers assess the project
  • Recommends concise, evidence-based wording and discourages ad hoc alternatives like AI-made, vibe-coded, or LLM-written

• Description style

  • Clarifies that entries should describe the project first, then append AI attribution only when useful
  • Keeps the guidance aligned with the existing awesome-list entry style

• Examples

  • Adds concrete examples contributors can copy when writing new entries

- [foo/bar](https://github.com/foo/bar) - Static site generator written in Zig. AI-generated.
- [foo/bar](https://github.com/foo/bar) - HTTP toolkit for Zig, maintained by humans. AI-assisted.
- [foo/bar](https://github.com/foo/bar) - Terminal game written in Zig. Built with AI assistance.

[Copilot]

Pull request overview

This PR updates the repository’s contribution guidelines to standardize how curated entries should disclose AI provenance, improving consistency and reducing ad hoc phrasing across the list.

Changes:

• Adds an AI Attribution subsection to define when and how to mention AI provenance in entry descriptions.
• Standardizes approved attribution labels (AI-generated, AI-assisted, Built with AI assistance) and discourages inconsistent alternatives.
• Provides example entry descriptions contributors can copy.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.