[gimlichael]

This pull request makes 10.1.2 a patch release that restores library coverage lost by automatically generated MTP exclusions and by a framework assembly-resolution failure. Dependencies now exclude only their own assemblies, and the runtime netstandard.dll facade is bound to the resolver that owns it, so project assemblies and .NET Framework modules are instrumented again. Package identity, public APIs, dependency versions, and the netstandard2.0;net9.0;net10.0 targets are unchanged.

Dependency exclusion correction:

• Exclusion filters are generated from the managed runtime asset filenames declared by non-project deps.json libraries, including RID-specific assemblies, instead of from package IDs widened to a two-segment prefix.
• Project runtime assets take precedence when the SDK lists the same DLL again in a reference entry, so a runner declared twice stays in coverage.
• Hyphenated exact names such as xunit.v3.mtp-v2 are accepted as valid filters, and the xUnit build assets copied without runtime entries remain excluded by exact name.
• Explicit CLI exclusions or an authoritative configuration file still bypass dynamic discovery and merge with the permanent baseline.

Framework resolver correction:

• The runtime netstandard.dll facade is loaded lazily per resolver with that resolver attached, so forwarded enum types resolve through Coverlet's framework fallbacks and configured search directories.
• The facade shares the resolver cache lifetime, leaving disposal, facade identity checks, and search order unchanged, with no consumer-specific branches.

Regression coverage:

• Dependency discovery tests build real deps.json inputs and assert that only dependency assemblies are excluded when names share a prefix, including differing package and assembly names and duplicate project or reference entries.
• Resolver tests resolve forwarded enums through a private search path and write optional enum metadata, covering the .NET Framework failure without requiring that framework.
• Existing filter, discovery, and dynamic-exclusion tests now assert exact filters and hyphenated names.

Coverage advisory:

• A new advisory records the affected versions, both upstream origins, the historical CI evidence that concealed the loss, and the consumer revalidation collected for seven repositories.
• The readme and integration guide warn about the affected range, link the advisory, and describe the corrected exclusion precedence.

Upstream provenance:

• A new ledger pins the original upstream marker, the 10.1.1 comparison base, and the branch commits behind each correction, keeping fork fixes distinct from upstream adoption.

Release notes:

• The 10.1.2 changelog entry describes both fixes and warns that restored modules change totals, percentages, and quality gates.

[greptile-apps]

Confidence Score: 5/5

[High impact] The PR appears safe to merge; no actionable new issues were found.

Summary

This patch restores project coverage through exact dependency exclusions and fixes forwarded enum resolution through the runtime netstandard.dll facade.

• MTP exclusions name dependency assemblies without hiding similarly named projects.
• Forwarded framework types use the resolver that owns the netstandard facade.
• CI checks release-branch pull requests and can include macOS runs.
• Contributor guidance records which fixes came from upstream and where they originated.

_{Reviews (3) · Last reviewed commit: "💬 document optional macOS validation" · Reviewed by Greptile}