Geocode Batch Plan and Normalize

Reliability

The same request always gives the same plan or the same normalised answers, on any machine and under any locale, time zone or default charset: percent-encoding is written out over UTF-8 bytes and credential name matching folds at the root locale, so neither moves with the host. projectedWallClockMs is (requestCount - 1) x minIntervalMs, arithmetic over the hints you supplied rather than a measurement, because this skill reads no clock. Under NORMALIZE a malformed entry is per-entry and a miscounted one is fatal: an entry that does not parse, that lacks the array at resultPath, or that carries a latitude outside -90 to 90 or a longitude outside -180 to 180 lands in rejected[] and the call still succeeds with partial true, because one bad provider row must not discard 999 good ones and a coordinate is never clamped; but a response whose result count disagrees with the addresses of the request it answers is refused outright, since positional realignment is the one error that attaches the right coordinates to the wrong address. A provider precision absent from precisionMapping normalises to UNKNOWN rather than into a neighbouring band. Fifteen refusals, none retryable unchanged: GEOCODE_MODE_UNSUPPORTED when mode is not PLAN or NORMALIZE, so choose one of those two values; GEOCODE_ADDRESSES_INVALID, GEOCODE_ADDRESS_LIMIT_EXCEEDED above 1000 and GEOCODE_ADDRESS_TOO_LONG above 1024 code points, so shorten or split the address list before retrying; GEOCODE_PROFILE_INVALID and GEOCODE_PROFILE_KEY_UNSUPPORTED for the profile, whose key set is closed; GEOCODE_CREDENTIAL_FORBIDDEN when a parameter name matches the credential vocabulary in staticParameters, in parameterMapping or already inside the endpoint query; GEOCODE_ENDPOINT_INVALID for a non-https endpoint, a missing host or userinfo; GEOCODE_PLACEHOLDER_UNSUPPORTED outside the four placeholders; GEOCODE_PARAMETER_UNSUPPORTED outside the request vocabulary or for a role nothing supplies; GEOCODE_BATCH_SIZE_INVALID outside 1 to 100, so set a supported provider batch size; GEOCODE_RESPONSES_REQUIRED and GEOCODE_RESPONSES_FORBIDDEN when the mode and the payload disagree; GEOCODE_RESPONSE_CARDINALITY_MISMATCH when response counts cannot align positionally, so supply exactly one response per planned request with one result per address; and GEOCODE_OUTPUT_TOO_LARGE when the plan or the answers would not fit the inline response ceiling.