V10.7.1/service update

[gimlichael]

This pull request updates repository documentation, test infrastructure, and dependency versions to improve clarity, maintainability, and consistency. The most significant changes include a complete rewrite of the contributing guide, consolidation of test environments, and upgrades to several package dependencies.

Documentation and contribution process:

• The .github/CONTRIBUTING.md file has been completely rewritten for clarity and detail. It now provides explicit instructions for building, testing, and contributing, explains the repository structure, CI contract, and coding guidelines, and clarifies the process for issues and pull requests.

Test infrastructure and environment:

• The testenvironments.json file now consolidates Docker test environments into a single entry using the unified codebeltnet/ubuntu-testrunner:8-9-10-11 image, simplifying cross-version testing.

Dependency and package management:

• Several dependencies in Directory.Packages.props have been upgraded, including Codebelt.Extensions.Xunit (to 12.0.0), xunit.v3 (to 4.0.0), Microsoft.NET.Test.Sdk (to 18.9.0), and various Microsoft.* packages, ensuring compatibility and access to new features. [1] [2]

Editor configuration cleanup:

• Duplicate and unnecessary configuration for the IDE0036 analyzer has been removed from .editorconfig to avoid inconsistencies.

[greptile-apps]

Greptile Summary

The follow-up changes correct the changelog’s description of global.json and add .NET Standard 2.1 to Cuemon.IO’s 10.7.1 availability entry. One earlier, non-blocking documentation concern remains: the contribution guide’s Release-only test loop says it mirrors CI even though CI also runs Debug.

Confidence Score: 5/5

Safe to merge with respect to blocking issues; the remaining documentation mismatch is non-blocking.

The changelog and Cuemon.IO release-notes findings are fully fixed. One outstanding non-blocking finding remains in .github/CONTRIBUTING.md: its local test loop runs only Release while stating that it mirrors the CI matrix, which runs both Debug and Release. There are no blocking findings.

_{Reviews (6): Last reviewed commit: "📦 add .NET Standard 2.1 availability to..." | Re-trigger Greptile}

[greptile-apps]

Release loop misses Debug

The shown loop runs only with --configuration Release, but the text says it matches the automated checks, which also run Debug. Contributors can follow this guidance and miss a Debug-specific regression until it is caught remotely. This is a non-blocking documentation concern; either run both configurations locally or describe this as a Release-only validation pass.

Suggested change

	Run tests one project at a time so a failing or hanging project is attributable. This mirrors the CI matrix; it does not silently turn skipped integration tests into passing tests.
	Run tests one project at a time so a failing or hanging project is attributable. This provides a Release-only validation pass; it does not silently turn skipped integration tests into passing tests.

Artifacts

Evidence from the check

• Authored Bash script that extracts and compares the documented test configuration with the current workflow test matrices, ending with the configuration-parity result.

Command output from the check

• Captured output from executing the comparison script in `/home/user/repo`; it shows Release in the documentation and Debug,Release in CI, confirming the mismatch.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/CONTRIBUTING.md
Line: 33

Comment:
**Release loop misses Debug**

The shown loop runs only with `--configuration Release`, but the text says it matches the automated checks, which also run Debug. Contributors can follow this guidance and miss a Debug-specific regression until it is caught remotely. This is a non-blocking documentation concern; either run both configurations locally or describe this as a Release-only validation pass.

```suggestion
Run tests one project at a time so a failing or hanging project is attributable. This provides a Release-only validation pass; it does not silently turn skipped integration tests into passing tests.
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!