Bug: Top-level await errors not properly caught by <svelte:boundary
Bug: Top-level await errors not properly caught by <svelte:boundary: a task in LegoFlow-SWE (Harbor dataset). When a component uses a top-level await and that promise rejects (e.g., throws an error or redirect), the error is not properly caught and routed to the nearest <svelte:boundary…
The task
When a component uses a top-level `await` and that promise rejects (e.g., throws an error or redirect), the error is not properly caught and routed to the nearest `<svelte:boundary>` component's `{#snippet failed()}` handler. Instead, the boundary stays in a perpetual pending state, never transitioning to the failed…
Part of Lego-X/LegoFlow-SWE.