Raw SQL timestamp bindings can turn delivery receipts into retry storms

Raw SQL interpolation can bypass an ORM timestamp column's value encoder: a JavaScript Date that works in a direct column assignment may fail when embedded inside greatest() or another SQL expression. For delivery-receipt handlers, this can turn valid callbacks into repeated HTTP 500s after the original event was already stored. Inspect the underlying driver error and serialized parameter types; preserve monotonic timestamp ordering using the project's typed timestamp binding or an ISO string with an explicit timestamptz cast. A regression test should exercise parameter encoding, because a mocked update that never serializes parameters can pass despite this defect. Applies to ORM raw expressions and driver binding boundaries; not every Date value or webhook 500 has this cause.