meridian-provider-builder

Scaffolding Meridian data providers requires implementing streaming, historical, or symbol search adapters that satisfy ADR-001/ADR-004/ADR-010/ADR-014 requirements. Generated implementations include rate limiting, CancellationToken propagation on all async paths, IOptionsMonitor<T> configuration, and source-generated JSON serialization.

Rate limiting and WebSocket reconnect logic are built into the scaffolding process for streaming providers. The generated IMarketDataClient implementations include required reconnection behavior and rate limiting controls to ensure resilient market data streaming.

Test scaffolds for historical providers include matching test cases for success, rate limiting, HTTP error handling, cancellation, and empty responses. These are generated alongside the IHistoricalDataProvider implementation to verify all required failure and edge-case paths.

Extending existing Meridian providers with new capabilities is supported by the scaffolding skill. It applies whether you are adding new streaming, historical, or symbol search functionalities while maintaining compliance with existing architectural contracts.

IOptionsMonitor<T> and source-generated JSON serialization are required by ADR-014 and ADR-004 to ensure configuration changes are detected dynamically and JSON contracts are enforced at compile time. The scaffolding process applies these conventions automatically.