List view
SaaS messaging providers abstract away the underlying transport protocol, but they also introduce dependency, cost, and constraints. This milestone adds connectors that speak raw industry protocols directly — SMPP for SMS, SMTP for email, APNs for Apple push — so that teams with direct carrier or Apple developer relationships can use the framework without any SaaS intermediary.
No due date•0/4 issues closedWith a stable, well-documented framework in place, this milestone extends the connector ecosystem to cover additional major cloud messaging providers. Each new connector implements the full `IChannelConnector` contract, declares its capabilities honestly in its channel schema, and ships with the same xUnit test helper package pattern established by the existing connectors.
No due date•0/5 issues closedA messaging connector that fails silently, cannot be monitored, or brings down dependent services on provider outages is not production-ready. This milestone adds the operational layer that connectors need to be trusted in production: structured retry and circuit-breaker policies, distributed tracing and metrics via OpenTelemetry, health check endpoints, and consistent structured logging across all connectors.
No due date•0/4 issues closedAll preceding milestones establish the framework's core capabilities: a complete bidirectional message model, rich interactive content, a sender identity abstraction, and production-grade resilience and observability. Version 1.0.0 is not a feature release — it is a commitment. The API is frozen, documentation is complete, test coverage meets a defined bar, and all packages are published as stable NuGet releases. From this point, breaking changes require a new major version.
No due date•10/10 issues closed