feat: add pricing refresh worker boundary

docs/IMPLEMENTATION-STATUS.md

@@ -149,6 +149,7 @@ Work through one bounded vertical slice at a time. The linked documentation rema
 - No initial User/Seller is provisioned in the development database yet. Run `npm run provision:admin` after setting its required local `.env` variables.
 - Listings are partially implemented: draft creation, seller-scoped reads, publication gating, lifecycle writes, archive behavior, sold/archived inventory checks, and item-owned image metadata are complete; storage-backed processing remains.
 - Concrete provider adapters, asynchronous pricing refresh transport, richer exports/settings, full integration CI services, and deployment/backup automation remain incomplete to varying degrees.
+- The pricing refresh worker boundary now has explicit completed/failed outcomes and routes provider observations through the pricing service; persistent refresh-job storage and a configured external provider remain deployment work.
 - `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

@@ -104,6 +104,12 @@ Refresh:
 
 Bulk refresh runs through BullMQ in the worker.
 
+The worker-side refresh boundary is implemented with explicit `COMPLETED` and
+`FAILED` outcomes. It resolves a registered provider, persists normalized
+observations through the pricing service, and recalculates the valuation. A
+provider that is missing or fails does not produce a fabricated value. Durable
+refresh-job storage and external provider configuration remain deployment work.
+
 Provider failure should not invalidate other valid observations. The failed provider is recorded for admin diagnostics.
 
 ## Overrides