ReplyScreen looked up CommentsProvider with context.read from its own element context, but the screen is pushed on the root navigator where no CommentsProvider ancestor exists (the instance is handed in as widget.commentsProvider and only provided BELOW, to the preview subtree). Every saveDraft/getDraft/clearDraft threw ProviderNotFoundException and was swallowed by the debug-log catch, so cancel-with-draft silently lost the text. Use widget.commentsProvider directly. Verified on emulator via .maestro/e4_reply_draft.yaml: type, Cancel, reopen -> draft restored; Send -> reply lands in the thread. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>