chore(template): sync with dailydevops/template-dotnet [skip ci]

Author: samtrion

decisions/2026-01-09-nuget-package-readme-template.md

@@ -70,7 +70,7 @@ The template provides a comprehensive structure including:
 * **Related Packages**: Cross-references to related packages in the ecosystem
 * **Documentation Links**: References to comprehensive documentation
 * **Contributing Guidelines**: Links to contribution processes
-* **Support Channels**: GitHub Issues, and documentation links
+* **Support Channels**: GitHub Issues and documentation links (GitHub Discussions is not used for project communication)
 * **License Information**: Clear license declaration and reference
 
 All URLs in package READMEs MUST be absolute URLs pointing to GitHub or NuGet.org to ensure compatibility across all platforms where the README may be displayed.
@@ -158,3 +158,4 @@ Use automated documentation generation tools (DocFX, Sandcastle) instead of manu
 
 * [English as Project Language](./2025-07-11-english-as-project-language.md) - All README content must be written in English following this decision
 * [Folder Structure and Naming Conventions](./2025-07-10-folder-structure-and-naming-conventions.md) - README files are placed at the root of each project directory following folder structure conventions
+* [No GitHub Discussions for Communication](./2025-11-01-no-github-discussions-for-communication.md) - GitHub Issues serve as the central point of contact for all project-related discussions

decisions/2026-01-10-standardized-solution-level-documentation.md

@@ -41,16 +41,17 @@ Adopt a standardized template for solution-level README files (`templates/readme
 
 The template includes:
 
-1. **Standard Structure**: Overview, Projects, Features, Getting Started, Development, Architecture, Contributing, Code of Conduct, Documentation, Versioning, Support, License, Maintainers, and Acknowledgments sections
+1. **Standard Structure**: Overview, Projects, Features, Getting Started, Development, Architecture, Contributing, Code of Conduct, Documentation, Versioning, Support, and License sections
 2. **Relative Links**: All internal references use relative paths (e.g., `[CONTRIBUTING.md](CONTRIBUTING.md)`)
 3. **Inline Guidance**: HTML comments provide detailed instructions for each section
 4. **Badge Support**: Standardized badges for license, build status, and contributors
 5. **Placeholder Patterns**: Consistent use of `YourRepo`, `ProjectName`, and similar placeholders for easy customization
-6. **Flexible Structure**: Optional sections (Maintainers, Acknowledgments, Configuration) can be removed if not needed
+6. **Flexible Structure**: Optional sections (Acknowledgments, Configuration) can be removed if not needed
 7. **Marker Preservation**: Support for preserving existing content markers (e.g., `<!-- packages:start -->`, `<!-- packages:end -->`) during modernization
-8. **GitVersion Integration**: Documents the use of automated semantic versioning
-9. **Conventional Commits Reference**: Links to commit message standards
-10. **ADR Integration**: References Architecture Decision Records with relative links to `decisions/` folder
+8. **Support Communication**: Directs users to GitHub Issues as the central point of contact (GitHub Discussions is not used)
+9. **GitVersion Integration**: Documents the use of automated semantic versioning
+10. **Conventional Commits Reference**: Links to commit message standards
+11. **ADR Integration**: References Architecture Decision Records with relative links to `decisions/` folder
 
 When modernizing existing README files:
 * MUST preserve all existing content markers (comments like `<!-- packages:start -->`)
@@ -145,3 +146,4 @@ When modernizing existing README files:
 * [English as Project Language](./2025-07-11-english-as-project-language.md) - Establishes language requirements for all documentation
 * [GitVersion Automated Semantic Versioning](./2025-07-10-gitversion-automated-semantic-versioning.md) - Referenced in the Versioning section of the template
 * [Conventional Commits](./2025-07-10-conventional-commits.md) - Referenced in Contributing and Versioning sections
+* [No GitHub Discussions for Communication](./2025-11-01-no-github-discussions-for-communication.md) - GitHub Issues serve as the central point of contact for all project discussions

templates/readme-project.md

@@ -160,7 +160,7 @@ Contributions are welcome! Please read the [Contributing Guidelines](https://git
 
 ## Support
 
-<!-- Replace 'YourRepo' with the actual repository name in all links below. -->
+<!-- Replace 'YourRepo' with the actual repository name in all links below. All communication related to bugs, features, and project coordination occurs through GitHub Issues. -->
 * **Issues**: Report bugs or request features on [GitHub Issues](https://github.com/dailydevops/YourRepo/issues)
 * **Documentation**: Read the full documentation at [https://github.com/dailydevops/YourRepo](https://github.com/dailydevops/YourRepo)
 
@@ -169,17 +169,6 @@ Contributions are welcome! Please read the [Contributing Guidelines](https://git
 <!-- Replace 'MIT License' and 'YourRepo' with actual values. Ensure the LICENSE file exists in the repository. -->
 This project is licensed under the MIT License - see the [LICENSE](https://github.com/dailydevops/YourRepo/blob/main/LICENSE) file for details.
 
-## Acknowledgments
-
-<!--
-Optional: Credit contributors, libraries, or resources that helped with this project.
-Remove this section if not needed.
-Examples:
-- Thank specific contributors or organizations
-- Credit libraries or tools used
-- Acknowledge inspiration or related projects
--->
-
 ---
 
 > [!NOTE] 

templates/readme-solution.md

@@ -256,6 +256,7 @@ This project uses [GitVersion](https://gitversion.net/) for automated semantic v
 <!--
 Provide information on how users can get help or report issues.
 Replace 'YourRepo' with actual repository name.
+All communication related to bugs, features, and project coordination occurs through GitHub Issues.
 -->
 
 * **Issues**: Report bugs or request features on [GitHub Issues](https://github.com/dailydevops/YourRepo/issues)
@@ -270,32 +271,6 @@ Replace 'MIT License' with actual license type if different.
 
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
 
-## Maintainers
-
-<!--
-Optional: List the primary maintainers or teams responsible for this solution.
-Include contact information or GitHub handles.
-Remove this section if not needed.
--->
-
-* **Team Name** - [@githubhandle](https://github.com/githubhandle)
-* **Individual Name** - [@githubhandle](https://github.com/githubhandle)
-
-## Acknowledgments
-
-<!--
-Optional: Credit contributors, libraries, or resources that helped with this solution.
-Remove this section if not needed.
-Examples:
-- Thank specific contributors or organizations
-- Credit important libraries or frameworks used
-- Acknowledge inspiration or related projects
--->
-
-* Special thanks to all [contributors](https://github.com/dailydevops/YourRepo/graphs/contributors)
-* Built with [.NET](https://dotnet.microsoft.com/)
-* Inspired by community best practices and patterns
-
 ---
 
 > [!NOTE]