844e5f2610
The serve-support resolver caches the probe outcome per resolved runtime for the process lifetime. That is right for a genuine "unknown subcommand" exit, but a probe that died by timeout says nothing about the runtime — only that this machine was slow right then (cold AV scan on Windows, first Python import after boot). Caching that as `false` routed a modern runtime through the legacy `dashboard` form until the app was relaunched. Export isTimeoutError from backend-probes and evict the cache entry on a timeout so the next check re-probes; non-timeout failures stay cached. One vitest case covers timeout → re-probe; the existing case still pins non-timeout failure → cached. Also replace the last synchronous read on the discovery path (dashboard.py fast path) with fs.promises.readFile, matching the stack's goal of keeping runtime discovery off the main event loop.