Stop the page rebuilding in the first place

Everything above is the belt. Saving drafts means that when the page is destroyed, the words come back. The braces is not destroying the page at all. Right now, the moment the phone finds signal, Reader runs route() unconditionally — it re-renders the whole item, which throws away the iframe your composer lives in, whether or not anything about that page has actually changed. Nine times in ten nothing has changed: you were reading the same item before the tunnel and after it. The fix is to let the reconnect quietly sync in the background and only re-render if the item you are looking at genuinely came back different, or if you are on the contents page where new items should appear. If you are mid-item, the page stays exactly where it is: same scroll position, same composer, same half-typed sentence, no flicker.

Both together is the right answer — drafts alone still lose your scroll position and your cursor, and a non-destructive reconnect alone still loses everything if the app is killed in your pocket or iOS reclaims the tab.