Clarify the post-OSMF Polly strategy for Microsoft.Extensions.Resilience

> Drafted with assistance of GitHub Copilot

Polly [will adopt the Open Source Maintenance Fee](https://thepollyproject.org/2026/07/14/polly-osmf-announcement.html) for maintained binary releases beginning November 16, 2026.

This directly affects the .NET resilience packages:

- `Microsoft.Extensions.Resilience` explicitly references Polly packages.
_This alone requires Microsoft to take an OSMF license._
- `Microsoft.Extensions.Resilience` and `Microsoft.Extensions.Http.Resilience` expose Polly types through stable public APIs, including `ResilienceContext`, `ResiliencePipeline`, `Outcome`, and Polly strategy option classes.
_Although Polly is transitive in the package graph, that source-level use may be considered direct for our users. The [current OSMF guidance](https://opensourcemaintenancefee.org/consumers/which/#net-example) indicates that is not the case via its examples re: `using` statements, but it is [not airtight](https://github.com/orgs/opensourcemaintenancefee/discussions/22)._

Could the maintainers clarify:

1. Whether these packages will continue using official Polly binaries after November 16, with Microsoft licensing Polly.
2. Whether Microsoft is considering temporarily freezing the Polly version, building it from source, maintaining or adopting a fork, replacing it, or redesigning the affected APIs.
3. Whether consumers using exposed Polly types remain (or not) covered by the transitive-dependency exemption or be covered (or not) by custom Microsoft licensing.

A freeze may be a reasonable temporary measure, but it needs a servicing policy and an exit plan. Community forks such as [Fences](https://github.com/BrighterCommand/Fences) are beginning to appear, but none is yet an established replacement.

No files or tests are identified in the issue. Start by reviewing the Microsoft.Extensions.Resilience and Microsoft.Extensions.Http.Resilience package references and the exposed Polly types listed in the report. Done means publishing a clear post-November 16 strategy covering licensing, dependency handling, API direction, and consumer coverage.

Written by the indexing model from the issue text.