fragginwagon/pokemon-inventory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
fragginwagon
2026-09-09 11:53:14 -04:00
parent 39b4aab058
commit 409d2cd0ca
9 changed files with 136 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/IMPLEMENTATION-STATUS.md
+1 -1
View File
@@ -149,7 +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.
- 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.
- `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
+3 -1
View File
@@ -108,7 +108,9 @@ 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.
refresh-job storage and row-locked worker claim/complete/fail lifecycle are
implemented in PostgreSQL. External provider configuration remains deployment
work.
Provider failure should not invalidate other valid observations. The failed provider is recorded for admin diagnostics.