What changed

RelayDesk now groups locally blocked reply drafts by their originating provider and account. Each route shows the related conversation, number of saved replies, and the reason sending is blocked. Users can clear drafts for a single route without touching drafts for other providers.

The portable workspace backup metadata is now versioned as 2.3.6 and includes route-aware drafts while continuing to exclude temporary connector tokens and passwords.

Safety boundary

Matrix preview and RelayDesk Test remain the only reply-ready preview routes. Gmail, IMAP, Outlook, Teams, Slack, Telegram, production WhatsApp and SMS are not claimed as live sending adapters. No real external message was sent in this release.

Mobile

The Draft Queue collapses to one-column, full-width touch controls below the existing mobile breakpoint. This continues the Android/iOS mobile-first web/PWA direction. No native APK/AAB or IPA package was generated because the current WordPress/WPWriter environment does not expose a native mobile build pipeline.

Deployment truth

Deployment surface: WordPress on 4BR.ca through WPWriter only. Windows and Vercel were not changed. No plugin/backend engine code changed, so this release does not require a plugin ZIP.

Connector Capability Matrix + Thread Integrity Audit

Web 2.3.7 separates receive, reply, authentication and implementation status per provider instead of using one ambiguous “supported” label. A new local Thread Integrity Audit checks imported events and blocked drafts using the canonical provider + account + conversation key, reports missing route identity, and flags possible key collisions without modifying messages.

The 2.3.6 Identity Guard and route-aware Draft Queue remain active. Unsupported reply routes are still blocked from external send. Backup metadata is now versioned 2.3.7. Mobile layouts use a horizontally safe capability table and full-width audit control.

Truth: Matrix and RelayDesk Test remain preview/test reply routes; WhatsApp remains a bridge preview; Gmail, IMAP, Outlook, Teams, Slack, Telegram and SMS are not production reply adapters. No real external message was sent. A separate 2.3.7 notes page could not be created because the current WPWriter plan has reached its post-count limit, so this published page carries the synchronized follow-up notes.

Canonical provider identity + Adapter Readiness Gate

Web 2.3.8 adds a local normalization pass for imported events and blocked reply drafts. Clear aliases such as Microsoft 365/Outlook, Google Mail/Gmail, WhatsApp variants and Internet Message Access Protocol (IMAP) are mapped to stable canonical provider names. The original provider label is retained in rawProvider so provenance is not lost.

The new Adapter Readiness Gate reports records checked, canonical provider count, unknown providers, complete provider + account + conversation identities, and how many identities are currently reply-ready. Ambiguous sources remain Unknown and cannot become reply-ready merely because they resemble another provider.

Backup metadata is now versioned 2.3.8 and records the provider-account-conversation-v1 normalization contract. Matrix preview and RelayDesk Test remain the only reply-ready preview routes. No new production provider adapter is claimed, and no real external message was sent. Mobile controls remain full-width below the existing breakpoint.