mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
Cursor Agent
3f19aaca39
Every client navigation in the observability UI blocked on two server round-trips before the destination page could render: 1. a lazy React Router `/__manifest` route-discovery request, and 2. a root-loader `.data` request that re-ran getPublicServerConfig() on every navigation even though the config is static for the server's lifetime. React Router keeps the previous page on screen until these resolve, so against a remote/cold dashboard backend the whole detail page appears to hang for seconds on each navigation. Ship the full route manifest on initial load (routeDiscovery: 'initial') and skip revalidating the root config loader on navigation (shouldRevalidate -> false). Measured against a throttled 150ms/1.5Mbps profile, home->run nav drops from ~339ms (two blocking round-trips) to ~23ms with zero blocking server requests; the page now renders immediately and only its own data loads afterward.