Desktop predev should ensure Electron OS binary exists

[JackLuguibin]

Description

After a fresh clone—or when bun/npm install runs without lifecycle scripts for electron—desktop predev can run while the OS-specific Electron binary was never downloaded. The electron package normally writes node_modules/electron/path.txt only after install.js / postinstall succeeds. When that file is missing, later steps fail in ways that look unrelated to Electron.

Expected: Either document that installs must allow scripts, or have predev run the same step proactively.

Proposal: Before copy-icons, build-node, etc., if packages/desktop/node_modules/electron/path.txt is absent (after resolving the real electron package directory), spawn node install.js with cwd set to that directory and exit non-zero if it fails.

Plugins

None — desktop package / contributor dev setup.

OpenCode version

Local workspace on dev branch (not tied to a single released app version).

Steps to reproduce

1. Clone the repo or reinstall deps such that electron postinstall did not run (e.g. scripts disabled, or incomplete install).
2. Confirm path.txt is missing under the resolved electron install path (Bun may symlink under node_modules/.bun/...).
3. Run bun run dev:desktop from the repo root or bun run predev in packages/desktop.
4. Observe downstream failures (e.g. electron-vite / missing binary) instead of a clear electron install error.

Screenshot and/or share link

N/A — environment-specific; no /share link.

Operating System

Linux (any OS when the Electron binary was not downloaded).

Terminal

N/A

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. This appears to be a feature request/enhancement, so please use the Feature Request template (title should start with [FEATURE]:, include the verification checkbox, and describe the problem/need using the required fields).
• Alternatively, if this is a bug report about predev failing, please use the Bug Report template and include a Description field with reproduction steps.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue! It now follows the bug report template with clear reproduction steps and context. The compliance label has been removed.