Argon2 hashes embed multiple $-delimited fields. When pasted into a
docker-compose-loaded .env, compose treats $argon2id, $v, $m, etc. as
variable references and silently substitutes empty strings, corrupting
the hash on its way to the container. Login then 401s with no obvious
hint.
Add a "Common pitfalls" entry calling out the escape ($ → $$) for
compose's .env, and note that Kubernetes secrets / AWS Secrets Manager /
shell export pass values through verbatim.
Caught during local PR1 verification.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>