Actually, I'm sorry, one follow up to cement my understanding, does this mean that framework-based s
Actually, I'm sorry, one follow up to cement my understanding, does this mean that framework-based static assets workers are also boiled down to one worker that is composed of all the static assets, the SSR calls, AND one conventional worker definition deployed as one bundle? I guess this is a roundabout way of asking how static asset routing works in that case since my vague mental model is that SSR elements in a framework are neither asset routes nor calls to the main worker definition. Like are those routes treated as, to coin a terrible confusing phrase, static dynamic assets?
