Hot fix/182 fix version and post extraction

[agusPatrito]

Summary

• Fix false "new version available" warning: VITE_APP_VERSION was only defined in .env.development, so production builds had undefined as the current version, triggering the warning on every launch. Fixed by injecting the version from package.json at build time via Vite's define option.

• Fix frozen spinner after frame extraction: riverCli() was fire-and-forget, causing the IPC handler to return before extraction finished. Also, on extraction failure the catch block returned undefined, triggering a TypeError in the renderer that left isLoading = true indefinitely. Fixed by awaiting riverCli() and returning a proper error object from the catch block.

• Version bump: 3.5.0 → 3.5.1

[gemini-code-assist]

Code Review

This pull request bumps the application version from 3.5.0 to 3.5.1 across several configuration and documentation files, and improves error handling when extracting the first frame. Specifically, the Electron IPC handler now returns caught errors, and the frontend hook throws an error and resets loading states accordingly. Feedback on these changes includes a recommendation to check if the IPC result is nullish to prevent a potential TypeError when accessing its properties, and a suggestion to use path.resolve with __dirname when reading package.json in the Vite configuration to avoid issues with varying working directories.

[gemini-code-assist]

If result is null or undefined (e.g., due to an IPC failure), result?.error will evaluate to undefined and no error will be thrown here. However, on line 230, result.initial_frame is accessed directly, which will trigger a TypeError. Checking if result itself is nullish prevents this potential crash.

Suggested change

	if (result?.error) {
	throw new Error(result.error);
	}
	if (!result || result.error) {
	throw new Error(result?.error || 'Failed to extract first frame');
	}

[gemini-code-assist]

Using a relative path like './package.json' relies on the current working directory (CWD) of the process running Vite. If Vite is executed from a different directory (e.g., the repository root or via a monorepo task runner), this read will fail. Resolving the path relative to __dirname using path.resolve is much more robust.

Suggested change

	const { version } = JSON.parse(readFileSync('./package.json', 'utf-8'));
	const { version } = JSON.parse(readFileSync(path.resolve(__dirname, 'package.json'), 'utf-8'));