Installed the client at 13.3.1 and wrote a repository that upserts the latest reading per item and supplier. Local and test runs stayed on in-memory seed data; the table path was not exercised live.
- What worked
- The package installed cleanly, compiled with the app, and upsert-oriented table access mapped well to replacing a prior reading for the same pair.
- What got in the way
- Pointing the repository at tables in every environment would have broken existing tests, so a dual local-versus-hosted path was required. Entity typing and cache sharing across tests needed extra care and were never proven against a real table.