Add integration test guarding event-log reducer registration

[jschick04]

Summary

Adds a Runtime.Tests integration test that exercises the real Fluxor reducer registration for the EventLog feature, so a dropped [ReducerMethod] attribute or a broken RegisterStateLibrary() assembly scan is caught.

Why

The existing EventLogStoreTests call Reducers.ReduceAddEvent(...) (and the other reducers) directly as static methods, so they stay green even if a reducer is no longer registered with the store - the silent-break class behind live-tail "Load New Events" not rendering. This test resolves IFeature<EventLogState> from a real AddFluxor(o => o.RegisterStateLibrary()) container and applies AddEventAction + NewEventBufferConsumedAction through the registered reducer path (ReceiveDispatchNotificationFromStore), asserting the buffer fills newest-first then drains.

Verification

• Stripping [ReducerMethod] from ReduceAddEvent fails this test while the 52 existing direct-call reducer tests stay green (the gap it fills).
• Runtime.Tests: 2031/2031 pass (baseline 2030 + this test).
• Test-only; no production code changed.

[Copilot]

Pull request overview

Adds a new Runtime test that validates Fluxor’s assembly scanning and reducer registration for the EventLogState feature by exercising the reducer pipeline end-to-end (via IFeature<EventLogState>), ensuring regressions like a removed [ReducerMethod] attribute are caught even when existing direct-call reducer tests remain green.

Changes:

• Adds an integration-style test that resolves IFeature<EventLogState> from a real AddFluxor(...RegisterStateLibrary()) container.
• Exercises AddEventAction buffering (newest-first) and NewEventBufferConsumedAction draining through the registered reducer path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.