Verified against 9ccbd4e46c.
#1809 added the guard that hands off to a real page load when a fetched fragment needs a runtime the current page has not loaded. It sits inside the fragment branch and nowhere else:
packages/router/src/client.ts:588: if(isFragment){
packages/router/src/client.ts:592: if(!window.stx&&fragmentNeedsRuntime(html,declaredRuntime)){:592 is the only call site of fragmentNeedsRuntime in the file. The full-document swap path has no equivalent check.
Nor is the store bundle re-executed on that path:
$ grep -rn 'data-stx-stores\|data-stx-composables' packages/router/
0Symptom
Navigating from a runtime-free page to a runtime-needing one via the full-document path leaves the destination's client script dead. In a real app (stacksjs/analyticshq) that is /compare → /dashboard: the destination throws defineStore is not defined, its onMount never runs, so the /api/me call never fires and the auth redirect never happens. The page renders and is quietly inert. No error surfaces to the user.
I have a solid reproduction of the symptom and the source read above; I have not isolated the exact mechanism by which the document path skips the runtime, so treat the trace as "guard is missing here" rather than a full diagnosis.
Why it is about to matter more
The same app has five pages whose layout group is contradicted by a hand-written stx-layout meta, which routes ordinary in-app navigation down the full-document path rather than the fragment path — i.e. straight into the unguarded branch. See stacksjs/analyticshq#35.
Suggested fix
Apply the same fragmentNeedsRuntime-style handoff before a full-document swap, and re-execute the store/composable bundles when the destination declares them.
Related
#1809 (the fragment-path fix this extends).