fix: use semver.satisfies for Node version check, drop minimum-node field

The major-only comparison would pass Node 22.0–22.17 despite them violating
the ^22.18.0 requirement. Now reads engines.node directly so the check stays
in sync with package.json automatically.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: kriszyp

launchServiceScripts/utility/checkNodeVersion.js

@@ -1,6 +1,6 @@
 'use strict';
 
-const semverMajor = require('semver/functions/major');
+const semver = require('semver');
 const { packageJson } = require('../../utility/packageUtils.js');
 const INSTALLED_NODE_VERSION = process.versions && process.versions.node ? process.versions.node : undefined;
 
@@ -9,9 +9,9 @@ module.exports = checkNodeVersion;
 function checkNodeVersion() {
 	// Skip Node version check when running on Bun
 	if (typeof globalThis.Bun !== 'undefined') return;
-	const minimumHdbNodeVersion = packageJson.engines['minimum-node'];
-	if (INSTALLED_NODE_VERSION && semverMajor(INSTALLED_NODE_VERSION) < semverMajor(minimumHdbNodeVersion)) {
-		const versionError = `The minimum version of Node.js Harper supports is: ${minimumHdbNodeVersion}, the currently installed Node.js version is: ${INSTALLED_NODE_VERSION}. Please install a version of Node.js that is withing the defined range.`;
+	const requiredRange = packageJson.engines.node;
+	if (INSTALLED_NODE_VERSION && !semver.satisfies(INSTALLED_NODE_VERSION, requiredRange)) {
+		const versionError = `Harper requires Node.js ${requiredRange}, but the currently installed version is ${INSTALLED_NODE_VERSION}. Please install a compatible version.`;
 		return { error: versionError };
 	}
 }

package.json

@@ -103,8 +103,7 @@
 		}
 	},
 	"engines": {
-		"node": "^22.18.0 || >=24.0.0",
-		"minimum-node": "22.18.0"
+		"node": "^22.18.0 || >=24.0.0"
 	},
 	"devEngines": {
 		"runtime": {