Ordered Deployment Configuration Validator

Validate a four-element string array values in this exact order: app_name, port, debug_mode, and max_connections. Stop at the first failed field.
app_name must be non-empty and contain at most 50 characters. Otherwise use app_name must be non-empty and max 50 characters.
port must be a strict base-10 integer string from 1024 through 65535, inclusive. Otherwise use port must be between 1024 and 65535.
debug_mode is case-insensitive and must be true or false. Otherwise use debug_mode must be true or false.
max_connections must be a strict base-10 integer string from 1 through 10000, inclusive. Otherwise use max_connections must be between 1 and 10000.
Inputs are not trimmed. A strict integer string contains an optional leading + or - followed by one or more digits.
Encode a successful typed configuration as ["ok", app_name, port, debug_mode, max_connections], using normalized decimal integers and a lowercase boolean. Encode a failure as ["error", message].

Function
validateDeploymentConfig(values: String[]) → String[]

Examples
Example 1
values = ["payments","8080","TRUE","250"]
return = ["ok","payments","8080","true","250"]
All four fields pass in order. The integer strings are normalized and TRUE becomes true.
Example 2
values = ["","80","maybe","0"]
return = ["error","app_name must be non-empty and max 50 characters"]
Validation stops immediately at the empty app_name, even though later fields are also invalid.
Example 3
values = ["api","65536","false","100"]
return = ["error","port must be between 1024 and 65535"]
The application name is valid, but 65536 is one above the allowed port range.

Constraints
values.length == 4.
Each element of values is a non-null string.
Inputs are validated exactly as received, except debug_mode is converted to lowercase.

This is a pure simulation problem. Write one small helper that checks a strict integer string: optional + or -, then one or more digits, nothing else. Parse it only after that check passes, then compare against the range. The common pitfalls are using a parser that accepts spaces or underscores, forgetting that "+8080" is valid and must be output as "8080", and letting "-0" or "007" slip through unnormalized. Normalize by converting to an integer and back to a string. Lowercase debug_mode before comparing, and output the lowercase form. Check order matters: return on the first failure so example 2 yields only the app_name error. Length check is on raw characters, with no trimming, so a string of spaces is non-empty and valid. Copy the four error messages character for character. If a single typo in a message costs you, StealthCoder is your hedge in the live OA.

Drill it cold or hedge it with StealthCoder. Either way, don't walk into the OA hoping you remember the trick.