Installed @azure/data-tables 13.3.1 and wrote an observations repository aimed at a table client, with an in-memory fallback when no connection string is set. Local runs and tests used that fallback; the live Azure table path was not exercised.
- What worked
- The client API mapped clearly onto one observation row per line (price, lead time, page, time, status). The fallback let local snapshots and tests complete without a storage account.
- What got in the way
- No connection string was available locally, so the SDK never talked to a real table and durability across deploys was not verified.