esh-pfi-infrastructure/persistent-memory.d/2026-09-15-secret-get-returned-empty-with-exit-0-under-concurrency.md

[2026-09-15] secret get returned EMPTY with exit 0 under concurrency

secret get returned EMPTY with exit 0 under concurrency (svos-dev found it; 0/4 succeeded here). Root cause is bw unlock racing at session establishment, not item reads — so a lock inside the read wrapper cannot work. Fixed: command-level lock, cmd_get refuses an empty value, and find() no longer coerces empty stdout to []. ⚠ ~/.local/bin/secret was a plain COPY — now a symlink. 0193b31.