oj v0.2.36

Fixed

• A TanStack Start client bundle no longer fails at random on an image or stylesheet import with [UNLOADABLE_DEPENDENCY] ... stream did not contain valid UTF-8 (or Bundling CSS is no longer supported for a .css file). oj's asset plugin tagged asset imports while resolving them and passed private markers through rolldown's this.resolve custom option, which concurrent resolves can swap: rolldown keys each call's saved options by the size of a map, so a finished call frees an index another call still holds. An aliased @/logo.png resolving next to a ./pov.css import from the same file could then skip the asset plugin and hand rolldown the bare file to read as source, and the overlay stayed until the next edit. Asset, stylesheet, worker and ?raw/?url/?inline imports are now classified by their resolved id when they load, as Vite's asset and css plugins do, .svg?react loads by its id too, and oj's Start bundle plugins pass nothing through custom. This applies to Start builds as well.
• TanStack Start dev honors server.hmr.overlay: false. A failed client bundle mounted the full-page error overlay on every page whatever the config said; now, as in Vite's client (__HMR_ENABLE_OVERLAY__), the error is only logged to the browser console when the overlay is off.
• A served compile or transform failure prints a human line to the terminal (oj: internal server error: <message>), as Vite logs Internal server error. It only reached the browser overlay and, under OJ_LOG_JSON=1, the NDJSON diagnostics line, so a supervisor that keeps the NDJSON record out of its stored logs lost the error entirely.