2a9f5b3476
An enterprise deployment hit sustained SQLite write-lock contention on a shared multi-gigabyte state.db (gateway + CLI processes writing concurrently). Turns correctly failed closed with session_persistence_failed, but the only user-facing wording claimed the disk was full and the gateway rendered a generic failure. The fast-fail semantics are deliberate and unchanged. This adds a pure classifier (locked / disk / unknown) applied where the SQLite error is still visible, threads the cause through the turn-completion explainer, and stamps a machine-readable failure_reason (session_persistence_failed:<cause>) plus a guaranteed non-empty error on the result for downstream surfaces. The cron scheduler's explainer-text suppression now matches every cause variant so refined wording cannot leak into scheduled-job deliveries.