archetech / archon / 34640817526

87%

push

github

fix(keymaster-service): Point at the shell when the wallet will not open (#1124)

* fix(keymaster-service): Point at the shell when the wallet will not open

Docker Compose substitutes an exported shell variable in preference to
the same name in .env, and the reader takes the first of
ARCHON_PASSPHRASE / ARCHON_ENCRYPTED_PASSPHRASE that is set rather than
the one that works. So an export left in a shell profile displaces a
correct .env, the wallet refuses to decrypt, and the service crash-loops
with "Incorrect passphrase." -- naming neither the value it tried nor
where that value came from (#1121).

Warn at startup when both names hold different values, and print the same
guidance, with the two commands that settle it, before the failure ends
startup. Both service flavors.

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

* docs(keymaster-service): Trim the passphrase comments to the fact

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

* fix(keymaster-service): Diagnose the shell export without printing it

The suggested `docker compose config | grep ARCHON_PASSPHRASE` renders
environment values, so following the advice put the wallet and /login
secret into terminal scrollback, CI output and any support log the
operator pasted it into.

`env | grep -c '^ARCHON_PASSPHRASE='` answers the same question -- a
shell export is the only way the shell value can win -- and reports 1 or
0 rather than the secret. Both ports, the docs, and the tests, which now
also assert the leaky command is absent.

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

* fix(keymaster-service): Diagnose the variable that actually failed

The advice named ARCHON_ENCRYPTED_PASSPHRASE as the source when that is
the one in use, then told the operator to in... (continued)

4133 of 4750 branches covered (87.01%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

8791 of 9228 relevant lines covered (95.26%)

749.56 hits per line