`ResolveEnvVar` (and by extension `resolveKey`) only searched for `.env` values
next to the vix executable and in the current working directory. The home config
directory (`~/.vix/.env`) was never checked.
Users who store credentials in `/.vix/.env` alongside their `/.vix/settings.json`
would find that API keys and base URLs are silently not found, even though the
location is a natural place to keep them.
Expected: `~/.vix/.env` is included in the env-file search order, checked after
the executable-adjacent `.env` and before the CWD `.env`.
`ResolveEnvVar` (and by extension `resolveKey`) only searched for `.env` values
next to the vix executable and in the current working directory. The home config
directory (`~/.vix/.env`) was never checked.
Users who store credentials in `
/.vix/.env` alongside their `/.vix/settings.json`would find that API keys and base URLs are silently not found, even though the
location is a natural place to keep them.
Expected: `~/.vix/.env` is included in the env-file search order, checked after
the executable-adjacent `.env` and before the CWD `.env`.