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

Author: samtrion

CODE_OF_CONDUCT.md

@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -59,8 +59,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-info@daily-devops.net.
+reported to the community leaders responsible for enforcement at [info@daily-devops.net](mailto:info@daily-devops.net).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -106,7 +105,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within
@@ -115,14 +114,11 @@ the community.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+version 2.0, available at [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
 
 Community Impact Guidelines were inspired by [Mozilla's code of conduct
 enforcement ladder](https://github.com/mozilla/diversity).
 
 [homepage]: https://www.contributor-covenant.org
 
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+For answers to common questions about this code of conduct, see the [Frequently Asked Questions](https://www.contributor-covenant.org/faq).

CONTRIBUTING.md

@@ -3,13 +3,15 @@
 All contributions must follow the rules below to stay consistent with our automation and downstream consumers.
 
 ## Expectations
+
 - Use English for all code, documentation, and commit messages.
 - Follow the trunk-based workflow implied by GitVersion; prefer short-lived feature branches merged via pull requests.
 - Keep production code under `src/` and test projects under `tests/` using the `{ProjectName}.Tests.Unit` / `{ProjectName}.Tests.Integration` pattern.
 - Add NuGet packages without versions in project files; define versions centrally in `Directory.Packages.props` only.
 - Leave repository-wide config files (e.g., `.editorconfig`, `Directory.Build.props`, `Directory.Packages.props` structure) unchanged unless explicitly requested.
 
 ## Commit messages (required)
+
 Commit messages **must** follow the [Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/) format:
 
 ```text
@@ -19,20 +21,24 @@ Commit messages **must** follow the [Conventional Commits 1.0.0](https://www.con
 Allowed types include `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `build`, `ci`, `perf`, and `revert`. Indicate breaking changes with `!` after the type/scope or a `BREAKING CHANGE:` footer.
 
 ## Development workflow
+
 - The `global.json` file pins test runner and in some cases the required SDK version; see README.md for the required .NET SDK version and any additional prerequisites.
 - Restore, build, and test from the solution root before opening a pull request: `dotnet restore`, `dotnet build`, `dotnet test`.
 - Execute code formatting using `csharpier format .` from the solution root.
 - Keep code and documentation clear and concise; prefer small, focused pull requests.
 - Update documentation when behavior or public surface changes.
 
 ## Pull requests
+
 - Provide a short summary, the motivation for the change, and any relevant issue links.
 - List the tests you ran and the outcomes.
 - Ensure new code includes appropriate tests (unit or integration) placed under the matching `tests/` project.
 - Avoid reformatting unrelated code or introducing drive-by changes.
 
 ## Dependency updates
+
 We use Renovate Bot to create automated dependency update pull requests using conventional commit prefixes. When adding new dependencies manually, follow the same conventions:
+
 - Declare the version in `Directory.Packages.props`.
 - Reference the package in the project file without a version attribute.
-- Prefer the smallest viable dependency set; remove unused packages.
+- Prefer the smallest viable dependency set; remove unused packages.