Treat database is locked as a transient child failure and retry
A child can fail with 'database is locked' or 'SQLITE_BUSY' when several
of them hit the shared pylon orchestration SQLite at the same time. That
is transient, so the DelegateFleet now retries it with the same
exponential backoff used for provider failures (2s, 4s, 8s, up to 3
attempts).
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
- Co-Authored-By
- Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Deploy story
What this commit did to the running system — joined from the
forge receipt chain, the part a commit page elsewhere cannot
show.
Not deployed through the forge lane
No push, promotion, build, or deploy receipt references this
commit (receipts are scanned over a bounded recent window).
Changes shipped by full node replacement carry their proof in
the release gate receipt instead.