v1.2.10

v1.2.10

Released: 2026-05-16

What’s changed

Fixed tauri:install regression (loader stall + legacy :4321 confusion)

When reproducing the issue from /Applications, desktop logs showed current app startup succeeded (Backend ready — navigating to bundled frontend), while a separate orphan legacy frontend process was still listening on :4321 from old sidecar-based runtime (front/dist/server/entry.mjs).

This release hardens install/runtime behavior:

• scripts/tauri-install.sh now runs strict post-install runtime checks and fails loudly when they do not pass.
• Legacy stale frontend listener cleanup is applied before validation when process command matches old sidecar entrypoint.
• Validation now asserts:
  • backend sidecar starts on :3456,
  • bundled-frontend readiness marker is logged,
  • no legacy frontend sidecar is listening on :4321/:6543,
  • backend sidecar stops after app quit.

Robust desktop navigation fallback

src-tauri/src/lib.rs now performs direct WebView session bootstrap + redirect (/app/) via window.eval(...) when backend is ready, in addition to emitting the backend-ready event. This reduces startup fragility if the loader event listener fails to bind in certain launch contexts.

Validation summary

• Backend unit coverage: ✅ (cd backend && npm run test:cov)
• Backend e2e: ✅ (cd backend && npm run test:e2e)
• Frontend unit coverage: ✅ (cd front && npx vitest run --coverage)
• Frontend e2e: ✅ (cd front && npm run test:e2e)
• Docs build: ✅ (cd docs && npm run build)
• Desktop install/runtime gate: ✅ (npm run tauri:install with strict post-install checks)

Commits

• c1d01a2 — fix(desktop): harden tauri install runtime checks
• b91ebe1 — chore: release v1.2.10