Register RegisterWaiter only through AddSignalWait (4.4.1)

[ognjenkatic]

Problem

Since 4.0.0, an app that calls AddConductorSharpPatterns() or AddCSharpLambdaTasks() but not AddSignalWait<T>() fails at startup when DI validation is on:

Unable to resolve service for type 'ConductorSharp.Patterns.Services.ISignalStore'
while attempting to activate 'ConductorSharp.Patterns.Tasks.RegisterWaiter'.

Both methods register MediatR handlers by scanning the whole Patterns assembly, and that scan also picks up RegisterWaiter. Its ISignalStore dependency is only registered by AddSignalWait.

Change

• AddConductorSharpPatterns() and AddCSharpLambdaTasks() scan with a MediatR TypeEvaluator that excludes RegisterWaiter.
• AddSignalWait<T>() is unchanged and still registers the handler, in either call order.
• Version bumped to 4.4.1.
• SKILL.md says the signal store is only needed with AddSignalWait.

Tests

New PatternsRegistrationTests build the provider with ValidateOnBuild:

• Patterns + lambda tasks without SignalWait build cleanly, and RegisterWaiter is not registered. This test fails on master with the error above.
• With AddSignalWait, called before or after the other two, the RegisterWaiter handler is registered and validation passes.

dotnet test: 73/73 passed.

3.x has no SignalWait, so no backport is needed.

🤖 Generated with Claude Code