v0.40.1

Fixed

• Recall reward-resolution no longer deadlocks the database. resolve_rewards issued its UPDATEs and bandit-weight save without committing (missing with db:), unlike every other archivist write path. In WAL mode that left a write transaction open on the archivist's connection, holding the write lock indefinitely — so every other writer (server presence/lease updates, /memory/search) failed with "database is locked" (blanket 500s) and the archivist stepped down. Now wrapped in a single committing transaction, with a regression test asserting no transaction is left open.

Only affects deployments with recall_bandit_enabled=true and ripe recall events; the resolution short-circuits (no writes) otherwise.