[roshanjonah]

This candidate adds connection recovery release copy to current Docs main without replacing the paid-team caps correction or earlier product updates. It describes connection availability, final provider quota checks after resets, mixed-size connection reuse and preserving confirmed send results if unused allowance return fails.

This is a source-only candidate. The announcement date remains <<TBD: verified publication date>>; merge and publication remain held until the release owner binds the deployed source, relevant live acceptance, verified publication date/order and exact publication approval. Present-tense draft copy does not qualify current live behaviour.

PR65 includes this candidate and adds direct SMTP acceptance/credit guidance to the same new update. Both existing PR identities and original commits remain; no duplicate changelog entry or force-push.

Validation: confidentiality, external-link, Mintlify validation and broken-link gates passed; current-main changelog preservation passed. Actual local changelog preview returned HTTP200, matching heading/copy, zero console errors and no failed requests. Hosted checks/review qualify this exact head separately.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one): 1

• major

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Team
• Run ID: 28711804-eba7-48f9-bda8-22f69acf31e7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[roshanjonah]

Superseded by #65, squash-merged as 01a830f3e550a5b2f014dae22f1e6a3753ea0abb and published. Verified the live page and RSS on 17 October 2026 (NZDT).

Every user-facing claim added by #64 is present in the 16 October product update, under Bug fixes:

Claim from #64	Where it lives in the published update
Connection recovery	First Bug fixes paragraph: "Queued emails resume sooner when a sending connection becomes available"
Final provider quota checks after resets	Same paragraph: "Sendmux rechecks provider quotas immediately before sending, including after a quota reset."
Mixed-size connection reuse	Second Bug fixes paragraph: "Emails of different sizes can reuse a sending connection"
Preserved confirmed results	Same paragraph: "confirmed sends keep their result if returning unused provider allowance fails."

All four claims are covered verbatim. No exclusions or supported claims unique to #64 remain. The final quota-check statement does not claim the deferred retry scheduling bug was fixed. This closure makes no 60,000/min qualified-capacity claim and preserves the accepted rollout's existing limits.

Closing #64 as superseded under Ops Watch's conditional approval. No branch, file or other resource will be deleted.