# Changelog

## Score

- CAI 50 → 50 (+0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 85 → 87 (+2.4)
- Architecture 77 → 77 (+0.0)
- Maturity 40 → 40 (+0.0)
- Readiness 57 → 58 (+1.2)
- Security 54 → 54 (+0.0)
- Performance 60 → 60 (+0.0)

## Resolved (17)

- Conflicting configuration patterns. `On<TRequest>()` suggests a fluent, type-safe builder pattern for defining behavior, while `Add(...)` takes pre-constructed builder interfaces. It is unclear if these are mutually exclusive, complementary, or if `On` is just a helper for `Add`. The naming `On` vs `Add` is ambiguous regarding intent (subscription vs registration).
- End-of-life runtime: .NET netcoreapp2.2 (test/UnitTests/UnitTests.csproj)
- End-of-life runtime: .NET netcoreapp3.0 (samples/AspNetCore/test/UnitTests/UnitTests.csproj)
- Inconsistent builder registration methods. The main `IPipelineProviderBuilder` has an `On<TRequest>()` method, but the specific context builders (Sync, Async, Cancellable) all use `Add(...)`. This suggests a fragmented API where the root builder behaves differently from the specialized builders.
- Inconsistent naming for pipeline retrieval. The sync provider uses `GetPipeline`, the async provider uses `GetAsyncPipeline`, and the cancellable provider uses `GetCancellablePipeline`. This creates three different verbs for the same logical operation (retrieving a pipeline instance), increasing cognitive load.
- Inconsistent parameter ordering for async methods. The overload with CancellationToken places it before the optional pipelineName, while the simpler async overload places pipelineName before the implicit default cancellation. This forces users to remember specific overloads or use named arguments, breaking the standard .NET convention where CancellationToken is typically the last parameter.
- Low XML-doc coverage: Core (samples/AspNetCore/src/Core/Core.csproj)
- Low XML-doc coverage: Infrastructure (samples/AspNetCore/src/Infrastructure/Infrastructure.csproj)
- Low XML-doc coverage: PingPong (samples/SimpleConsoleApp/PingPong/PingPong.csproj)
- Low XML-doc coverage: WebApi (samples/AspNetCore/src/WebApi/WebApi.csproj)
- The PingHandler class contains multiple handler methods with inconsistent and non-descriptive naming conventions. 'MyMethodAsync', 'MyLongMethod', 'MyCustomBarMethod', 'MyCustomFooMethod', 'MyCustomFooBarAsync', and 'MyCancellableForAsync' do not follow a consistent pattern (e.g., verb-based or noun-based) and use generic prefixes like 'My' or 'Custom' which obscure the actual behavior or request type they handle. This makes it difficult to distinguish between handlers for different requests or behaviors.
- Vulnerable: Microsoft.AspNetCore.App
- Vulnerable: Microsoft.NETCore.App
- XML-doc coverage: FluentMediator (src/FluentMediator/FluentMediator.csproj)
- XML-doc coverage: FluentMediator.Microsoft.Extensions.DependencyInjection (src/FluentMediator.Microsoft.Extensions.DependencyInjection/FluentMediator.Microsoft.Extensions.DependencyInjection.csproj)
- redundant comment (samples/AspNetCore/test/UnitTests/UseCasesTests/RegisterTests.cs)
- redundant comment (test/UnitTests/MyCustomMediator.cs)

## New (4)

- End-of-life runtime: .NET netcoreapp2.2 (samples/SimpleConsoleApp/PingPong/PingPong.csproj)
- End-of-life runtime: .NET netcoreapp2.2 (test/UnitTests/UnitTests.csproj)
- End-of-life runtime: .NET netcoreapp3.0 (samples/AspNetCore/src/WebApi/WebApi.csproj)
- End-of-life runtime: .NET netcoreapp3.0 (samples/AspNetCore/test/UnitTests/UnitTests.csproj)

## API surface

- Unchanged — 1 HTTP endpoints
