Fix runtime type parity

[tmrp]

What changed

• make clientPrefix return types match the client runtime: exposed prefixed keys are parsed values and filtered server-only keys are undefined
• type every skipValidation result as unknown, including dynamic options and client-filtered values
• retain the legacy debug.skipValidationWarning option as a deprecated compatibility surface
• add exact type regression coverage and a pre-1.0 minor changeset

Root cause

The 0.4.3 type mapping placed undefined on prefixed client keys and declared filtered server keys present, which is the inverse of runtime behavior. The skip-validation mapping also reused parsed Zod output types even though validation, coercion, defaults, and transforms are explicitly bypassed.

User impact

TypeScript will no longer allow raw strings or missing values to masquerade as validated numbers and strings. Consumers using skipValidation must narrow raw values before use; client-prefixed values regain the same shape that the runtime already returns.

Validation

• Prettier check passed
• ESLint passed
• TypeScript typecheck passed
• 98 unit/type tests passed across 34 files
• package build and pnpm pack --dry-run passed
• Node, Bun 1.3.14, and Deno 2.9.4 runtime smoke tests passed
• Changesets resolves @tmrp/env as a minor bump
• git diff --check passed

[changeset-bot]

🦋 Changeset detected

Latest commit: 1927468

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@tmrp/env	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR