Per ARCH-BINDINGS §7.1 v1.2 retry-service asymmetry note + RFC-WS-6 §Q3 v1.3 addition 2. recordFailure() now mirrors ApplyBindingsOnFormSubmit's outer-transaction failure path: 1. failure_response_code via FormBindingExceptionClassifier::classify($e). Same classification logic as the listener — single behaviour-change point per the v1.3-delta D1 design. 2. apply_completed_at = now() — closes the asymmetry where the listener wrote this column on both happy and failure paths but the retry service only wrote it on the success path. recordSuccess() unchanged — already writes apply_completed_at via the shared transaction block in retry(). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
6.2 KiB
6.2 KiB