[Angnuo (angnuoli)]

Description

After installing a build that prepares OpenClaw from ASAR, npm run dev still searches only the old npm installation locations. When those are absent it returns a nonexistent ~/.openclaw-node/.../openclaw.mjs path, causing downstream startup code to fail while reading the host package metadata.

Development now reuses the installer's prepared runtime under Electron's userData/runtime/openclaw, including its built-in skills directory. Missing runtimes produce an actionable error directly from the path resolver.

Related Issue

None.

Changes

• Resolve the existing prepared runtime in development without extracting or replacing it.
• Require the entry, package metadata and preparation marker; retain the incomplete-upgrade guard and reject inconsistent version metadata.
• Preserve the packaged-app path and legacy npm fallback locations.
• Add regression cases for prepared-runtime reuse, matching skills paths, inconsistent metadata and missing runtime errors.

Type of Change

• Bug fix

Testing

• Local tests, builds and application startup validation were not run, as requested by the user.
• Regression cases were added/updated but have not been executed locally.
• Diagnosis confirmed the installed prepared runtime exists while the legacy npm package path is absent; this is not a successful post-fix startup test.

Checklist

• Reviewed the diff and limited this PR to the runtime resolver and its regression cases.
• Updated the corresponding path-resolution comments.
• Tests pass locally.
• Build succeeds locally.
• Manual post-fix startup validation is complete.