docs: standardize release workflow and improve documentation quality

[nanotaboada]

• Add comprehensive Release Management section to AGENTS.md
• Document CHANGELOG-first release workflow (3-step process)
• Add XML documentation comments to all model properties
• Reframe Features section to highlight reference project value
• Reorder features by development lifecycle importance

Summary by CodeRabbit

• Documentation

  • Added API documentation for Player models.
  • Expanded release management and CHANGELOG guidance; updated README feature descriptions and release workflow.
  • Added an unreleased entry for token-efficiency improvements.

• Chores

  • Refined GitHub release metadata to append a stadium emoji.
  • Updated CI/CD documentation and bumped related workflow dependencies.

[coderabbitai]

Walkthrough

This pull request adds XML documentation comments to player model classes and updates release and documentation processes. Changes include revised release workflow metadata, expanded release management guidance in AGENTS.md, restructured CHANGELOG with dependency updates and new entries, reworked README features and release instructions, and documentation comments for Player, PlayerRequestModel, and PlayerResponseModel classes.

Changes

Cohort / File(s)	Summary
Release Workflow & Metadata .github/workflows/dotnet-cd.yml	Adjusted GitHub Release metadata formatting: moved/added stadium emoji and changed release body header spacing/placement. No control-flow logic changes.
Release & Docs Guidance AGENTS.md, CHANGELOG.md, README.md	Expanded release management and CHANGELOG guidance, added pre-release checklist and examples, reorganized unreleased sections, dependency bump entries, and updated README feature and release workflow text; CI notes tweaked (removed Codacy upload).
Model Documentation src/Dotnet.Samples.AspNetCore.WebApi/Models/Player.cs, src/Dotnet.Samples.AspNetCore.WebApi/Models/PlayerRequestModel.cs, src/Dotnet.Samples.AspNetCore.WebApi/Models/PlayerResponseModel.cs	Added XML documentation comments to public properties on player-related model classes; no signature or behavior changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~30 minutes

Possibly related PRs

• feat: implement tag-based deployment with stadium release names (#356) #357: Related edits to the CD workflow and release metadata formatting affecting dotnet-cd.yml.
• docs: optimize AI agent instructions for token efficiency #361: Overlapping updates to AGENTS.md for release and CHANGELOG guidance.
• chore: update status badges #186: Related README badge/content changes touching release/status presentation.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title follows Conventional Commits format with 'docs:' prefix, is 68 characters (under 80 limit), and accurately describes the main changes: standardizing release workflow documentation and improving overall documentation quality across multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/release-workflow-standardization

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/dotnet-cd.yml:
- Line 144: The Markdown heading line "#Release ${{ steps.version.outputs.semver
}} - ${{ steps.version.outputs.stadium }} 🏟️" is missing a required space after
the '#' so it doesn't render as a heading; update that line to add a space after
'#' (i.e., change "#Release ..." to "# Release ...") so the heading is valid
Markdown and still interpolates the same GitHub Actions variables.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud