The Navigation API scroll restoration logic doesn't go through the normal Navigation algorithm, instead flowing through the process scroll behavior steps. There's two cases:

1. The NavigateEvent.scroll() method called by an author
2. Finishing an intercepted navigation/"transition"

The fix for #186 will fix force-load-at-top for the normal navigation flow but it's not clear to me how it should affect these navigation API paths yet.