[voiys]

# @currentEnv=$APP_ENV
# ---
# @type=enum(development, production)
APP_ENV=development

# @required=forEnv(prodution) @type=url
API_URL=

$ APP_ENV=production varlock load
main:
  ✅ API_URL
     └ undefined                                 (exit 0, nothing says the url is missing)
here:
  🧐 API_URL
     └ undefined
     - [WARNING] forEnv(): "prodution" is not a possible value of APP_ENV
       (the @currentEnv item: development, production), so it can never match.
       Did you mean "production"?

only checked when the @currentEnv item is a plain enum(...) with literal members and the arg is written out literally. forEnv($OTHER) and computed enums are left alone.

it's a warning, not an error, so a schema with a stale env name still loads.

the "did you mean" uses the same edit-distance helper the CLI already had for mistyped flags, moved to lib/suggest-closest.ts.

test: forenv-env-names.test.ts.

[pullfrog]

✅ No new issues found.

Reviewed changes: Reviewed the literal forEnv() argument checks, their graph lifecycle integration, and the shared suggestion helper.

• Enum diagnostics: Warns about impossible literal arguments while preserving warning-only behavior and parent-versus-child environment selection.
• Shared suggestions: Extracts edit-distance matching, preserves CLI dash normalization, and bounds suggestion input lengths.
• Coverage and docs: Adds regression tests and documents when arguments are checked. All 194 focused and adjacent tests passed.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}