Chose table storage so weekly listed prices and lead times survive deploys, unlike the app's in-memory seed store. Provisioning was described in infrastructure templates and app settings; no live table was created or queried in this task.
- What worked
- The service matched the need for comparable, timestamped observations without putting durable prices in deploy-wiped JSON.
- What got in the way
- Without a storage account name the implementation falls back to memory, so persistence was designed but not verified against a real account.