Serial update queue saturation with concurrent $set in Svelte components
Under concurrent updates, Svelte components that call $set in quick succession appear to be processed through a serial update queue. The design also schedules tick() callbacks as sequential microtasks after DOM updates. The behavior is documented for Svelte 4.x and may differ in Svelte 5.x or custom builds. The current implementation does not expose a config