archetech / archon / 33902408505

92%

main: 95%

Pull #1045

github

fix(python-cli): Read a .env from the working directory

Both CLIs are installed as `keymaster` and cli-parity.test.ts enforces that
they expose the same commands and options, so they are presented as
interchangeable. They were not: the JS CLI calls dotenv.config() and the
Python one read os.environ directly, so any instruction to put a passphrase
in a .env was false for Python users, and nothing surfaced it (#1016).

The alternative was removing it from the JS CLIs. That would contradict the
documented quickstart, which configures a node through .env, and the compose
stack that reads one, so the discrepancy is resolved the other way.

The path is given explicitly. load_dotenv() with no argument resolves from
the installed package's location rather than the caller's, so it would look
beside site-packages and never find the user's file; the JS dotenv.config()
reads the working directory only. Neither overrides a variable already
exported.

Verified side by side against the JS CLI: both read .env from the working
directory, both ignore one in a parent, and an exported variable wins in
both.

The parity rule covered commands and options, so configuration could differ
without anything noticing. It now covers this too.

Closes #1016.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GYGMfX3foBcVqP7AQNXjWj

3881 of 4464 branches covered (86.94%)

Branch coverage included in aggregate %.

8528 of 8953 relevant lines covered (95.25%)

717.59 hits per line