Fix dev blank screen and remote cron/dashboard API routing

[dataguybobby]

Problem

Dev blank screen (npm run dev)

Running Hermes Desktop locally could show a white window because the renderer failed during Vite module evaluation:

• @react-three/drei (~3.5MB) pre-bundle races with Electron startup — Electron loads before the dep optimizer finishes.
• Corrupt .vite cache (.map present without .js) after interrupted re-optimizes.
• Stale optimize-dep URLs return 504 on first load.
• Opening the Office tab discovered SkeletonUtils.js, triggering mid-session re-optimize that invalidated drei mid-request.

Chat startup also eagerly imported the Office 3D stack, coupling startup to drei.

Remote cron and gateway readiness

Remote/dashboard mode had two related failures:

• Cron HTTP calls hit gateway /api/jobs, which returns 405 when the active transport is the dashboard (/api/cron/jobs).
• isApiServerReady treated dashboard SPA HTML responses on /health as a healthy gateway, causing false positives during remote connection setup.

Resolution

Dev loading

• Lazy-load the Office tab in Layout and Office3D in Office so Chat mounts without drei.
• Pre-bundle @react-three/drei, fiber, three, troika, and SkeletonUtils via optimizeDeps.include.
• scripts/ensure-vite-deps.mjs clears corrupt drei cache entries before npm run dev.
• scripts/vite-wait-for-drei.ts blocks the first HTML response until drei pre-bundle completes.
• Bounded dev recovery: vite:preloadError reload in the renderer; main process reloads once if #root is still empty after 4s.
• Added npm run dev:clean for stale cache resets.

Remote API routing

• listCronJobs and mutations prefer dashboard /api/cron/jobs, falling back to gateway /api/jobs on 404/405.
• Map dashboard /trigger to gateway /run on fallback.
• isApiServerReady rejects text/html /health responses.
• Remote connection tests prefer /api/status when chat transport is not legacy.

Test plan

• npm test — 1822 passed
• npm run dev — Chat tab loads on first launch (no blank screen)
• Open Office tab — 3D scene loads without dynamic import failures
• Remote mode — cron jobs list/create/delete against dashboard URL
• Remote mode — legacy gateway-only host still works via /api/jobs fallback
• Remote connection test — dashboard HTML /health no longer marks gateway ready

Made with Cursor

[greptile-apps]

Greptile Summary

This PR improves development startup, remote API routing, and session rename persistence. The main changes are:

• Lazy-loads the Office 3D stack and waits for Vite dependency prebundling.
• Adds bounded renderer recovery and a cross-platform cache-clean command.
• Routes cron requests across dashboard and legacy gateway APIs.
• Rejects dashboard HTML when checking gateway health.
• Persists validated session titles before updating the local cache.

Confidence Score: 5/5

This looks safe to merge.

• The renderer reload cooldown persists across reloads and stops the reported loop.
• The cache-clean command now uses cross-platform Node filesystem APIs.
• No blocking follow-up issue was found in these fixes.

Important Files Changed

Filename	Overview
src/renderer/src/main.tsx	Adds a persistent cooldown that prevents repeated preload-error reloads.
scripts/ensure-vite-deps.mjs	Adds cross-platform cleanup for stale or corrupt Vite dependency caches.
scripts/vite-wait-for-drei.ts	Delays the first development document until the drei prebundle is available.
src/main/cronjobs.ts	Supports dashboard cron routes with legacy gateway fallback and response normalization.
src/main/hermes.ts	Uses transport-aware readiness probes and rejects HTML gateway health responses.
src/main/session-cache.ts	Validates and persists session renames before updating the JSON cache.

_{Reviews (3): Last reviewed commit: "fix: address review feedback on dev-relo..." | Re-trigger Greptile}