feat: bound pricing job retries

docs/IMPLEMENTATION-STATUS.md

@@ -154,6 +154,7 @@ Work through one bounded vertical slice at a time. The linked documentation rema
 - Product-level provider mappings now persist seller-scoped `PRODUCT`/`SEARCH` relationships and support active listing and controlled disabling.
 - Pricing refresh enqueue now resolves its provider from an active Product mapping and rejects unmapped Products explicitly.
 - Local development and CI can enable a deterministic fixture provider for end-to-end refresh coverage; production provider adapters remain explicitly configured deployment boundaries.
+- Pricing refresh jobs have a bounded three-attempt retry policy with exponential backoff and an explicit completed-job purge operation for retention scheduling.
 - `npm install` currently reports dependency audit findings. Review and remediate them before production deployment; do not use `npm audit fix --force` without reviewing its changes.
 
 ## Local Commands

docs/PRICING.md

@@ -117,6 +117,11 @@ refresh-job storage and row-locked worker claim/complete/fail lifecycle are
 implemented in PostgreSQL. External provider configuration remains deployment
 work.
 
+Refresh jobs allow three attempts. Failed attempts requeue with short
+exponential backoff; the third failure becomes terminal `FAILED`. Completed-job
+retention is handled explicitly through the repository cleanup operation so a
+deployment can schedule cleanup according to its retention policy.
+
 Provider failure should not invalidate other valid observations. The failed provider is recorded for admin diagnostics.
 
 ## Overrides