feat: enqueue pricing refresh jobs
Quality / test (push) Canceled after 0s

This commit is contained in:
2026-09-09 12:35:17 -04:00
parent 409d2cd0ca
commit 72346130ed
8 changed files with 68 additions and 14 deletions
+6
View File
@@ -64,6 +64,7 @@ POST /api/v1/admin/inventory/:id/list
POST /api/v1/admin/inventory/:id/archive
POST /api/v1/admin/inventory/:id/relist
POST /api/v1/admin/inventory/:id/pricing/refresh
GET /api/v1/admin/jobs/:id
GET /api/v1/admin/listings
GET /api/v1/admin/listings/:id
@@ -123,6 +124,11 @@ records an audit event. Pricing observations remain private; public listing
detail exposes only the latest calculated or manually overridden market value,
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.
## Provider matching
The API must expose Product-level operations for:
+1
View File
@@ -150,6 +150,7 @@ Work through one bounded vertical slice at a time. The linked documentation rema
- 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 now has durable PostgreSQL refresh jobs with row-locked claim, completed/failed persistence, and provider observations routed 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.
- `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