Context
On first load, app initialization blocks on rebuild before rendering the main UI. Rebuild always calls external model resolution, and there is no timeout/fallback path. If that async call stalls (network issues, registry slowness, blocked environment), the app can remain stuck in loading state.
Expected Behavior
If external model resolution is slow the app should:
- fail fast with a visible error, or
- continue with local model flow and show a warning,
instead of staying on spinner indefinitely.
Actual Behavior
Initialization waits for rebuild, and rebuild waits on external model update. In degraded network conditions this can block startup, keeping the spinner visible and delaying/locking access to the editor.
Steps to Reproduce
- Start app locally.
- Open browser DevTools and simulate offline or very poor network.
- Refresh app on root route.
- Observe spinner persists for long time (or indefinitely), main editing UI does not become usable.
Context
On first load, app initialization blocks on rebuild before rendering the main UI. Rebuild always calls external model resolution, and there is no timeout/fallback path. If that async call stalls (network issues, registry slowness, blocked environment), the app can remain stuck in loading state.
Expected Behavior
If external model resolution is slow the app should:
instead of staying on spinner indefinitely.
Actual Behavior
Initialization waits for rebuild, and rebuild waits on external model update. In degraded network conditions this can block startup, keeping the spinner visible and delaying/locking access to the editor.
Steps to Reproduce