main ← fix/reply-as-linked-topic-stale-draft
merged 05:23PM - 11 Feb 26 UTC
When a user replies to a topic and then switches to "Reply as linked topic" via …the composer actions menu, the original reply draft was left behind as an orphan. This happened because `_replyFromExisting()` called `closeComposer()` which only nullifies the model without destroying the draft. The new linked topic composer then opens with a different draft key (`new_topic_<timestamp>`), leaving the old reply draft (`topic_<id>`) persisted in the database.
Fix this by calling `destroyDraft()` before closing and reopening the composer in `_replyFromExisting()`. This ensures the old draft is cleaned up when switching composer actions, regardless of whether the draft key changes.
https://meta.discourse.org/t/394431