microsoft-extensions

# Microsoft.Extensions for .NET ## Trigger On - wiring dependency injection, configuration, logging, or options - introducing Generic Host patterns into non-web .NET apps - cleaning up service registration, typed HTTP clients, or shared infrastructure code ## Workflow 1. Prefer the Generic Host for apps that need configuration, DI, logging, hosted services, or coordinated startup. 2. Keep service registration predictable: composition at the edge, concrete implementations hidden behind interfaces only where that abstraction buys flexibility. 3. Use options binding for structured configuration and validate configuration at startup when bad settings would fail later at runtime. 4. Prefer `IHttpClientFactory` and typed or named clients for outbound HTTP instead of ad-hoc singleton or per-call `HttpClient` usage. 5. Use logging categories and config-driven log levels rather than scattered ad-hoc logging behavior. 6. For Kubernetes-hosted services, prefer the stable `Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes` package from the 10.7+ line when CPU/memory request and limit metrics should come from pod resource quotas. 7. Avoid building mini-frameworks over Microsoft.Extensions unless the repo genuinely needs reusable composition primitives. ## Current Upstream Notes - `dotnet/extensions` `v10.8.1` is an AI-library servicing release for approval-resume ordering and stateless reasoning state; it does not change the Generic Host, dependency injection, configura...