jp --no-persist query --new "..." writes QUERY_MESSAGE.md into a fresh user-local <id>/ directory (preserve_query_message_file, gated only on user storage being configured). The lock backend is null under --no-persist. If the turn fails, the draft is kept for recovery. remove_empty_conversation_dir leaves the non-empty directory alone, and the next run trashes it as missing metadata.json.
Reproduced by .config/loop/run.sh's rate-limit probe, which leaves one directory per failed probe.
--no-persist never writes the preserved draft
Decide what an editor-composed --no-persist query does with its draft file