fix: correctly classify format-rejected ports as 'not-numeric' instead of 'out-of-range'

When Number() produces a finite integer that is within the valid port range
(1-65535) but Schema.NumberFromString still rejected the input (e.g. '+8080',
'0x50'), the reason should be 'not-numeric' (format issue) rather than
'out-of-range'.

Author: cursoragent

scripts/build-desktop-artifact.ts

@@ -910,7 +910,9 @@ function invalidMockUpdateServerPortReason(
 ): typeof InvalidMockUpdateServerPortReason.Type {
   const parsed = Number(configuredPort);
   if (!Number.isFinite(parsed)) return "not-numeric";
-  return Number.isInteger(parsed) ? "out-of-range" : "not-integer";
+  if (!Number.isInteger(parsed)) return "not-integer";
+  if (parsed >= 1 && parsed <= 65535) return "not-numeric";
+  return "out-of-range";
 }
 
 const resolveBooleanFlag = (flag: Option.Option<boolean>, envValue: boolean) =>