feat: resolve refresh providers from mappings

docs/API.md

@@ -130,7 +130,8 @@ condition label, and public image URLs.
 Pricing refresh returns `202 Accepted` with a durable job identifier and
 `PENDING` status. Poll the job endpoint for `PROCESSING`, `COMPLETED`, or
 `FAILED`; job status reads are seller-scoped and expose only safe status/error
-metadata.
+metadata. Refresh enqueue resolves the provider from an active Product-level
+mapping and returns `409` when no mapping exists.
 
 ## Provider matching
 

docs/IMPLEMENTATION-STATUS.md

@@ -152,6 +152,7 @@ Work through one bounded vertical slice at a time. The linked documentation rema
 - The pricing refresh worker now claims durable PostgreSQL jobs with row locking, persists completed/failed outcomes, and routes provider observations through the pricing service; configured external providers remain deployment work.
 - Pricing refresh requests now enqueue seller-scoped jobs and expose a safe `GET /api/v1/admin/jobs/:id` polling contract instead of doing provider work inline.
 - 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.
 - `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