Earlier quoted context omitted.
I think that the mechanism I suggested elsewhere would handle this best: each tab's complete state (DOM, JavaScript &c.) should be marshalled to disk at quit (and checkpointed periodically, in case of crashes); on startup, all tabs are loaded and their DOM & JavaScript contexts restored. If a tab's context had it set to update periodically, then that periodic-update context would be restored; if not, then the remote…
> This seems so obviously correct to me that I wonder what I'm missing. You are missing that > should be marshalled to disk at quit is not easily doable.
I'd think it's the sort of thing which ought to be child's play.