Terminology Local Cache Adapter

This is a low-complexity component with no external service dependencies, making it one of the lowest-risk deliverables in the terminology subsystem. It should be built and unit-tested first since the Cache Adapter is a dependency of both the Repository and the Sync Service. The primary decision to resolve before implementation starts is the local storage technology choice—SharedPreferences is simpler but has size limits; Hive offers better performance for larger maps. Document this decision in the sprint as it affects the setup requirements for device testing.

The `evictAll()` interface must be wired into the account logout flow, which requires coordination with the authentication team.

Provides a key-value storage abstraction over a device-local persistence layer (SharedPreferences or Hive box). Each organization's map is serialized to JSON and stored under a namespaced key (e.g., `terminology_map_{organizationId}`), with the cache timestamp stored under a companion key (`terminology_ts_{organizationId}`). `write(organizationId, map, timestamp)` serializes and persists atomically where the storage layer allows. `read(organizationId)` deserializes and returns null on cache miss.

`has(organizationId)` enables fast existence checks before a full read. `evict(organizationId)` removes both the map and timestamp keys. Wrap all storage calls in try/catch to gracefully handle storage quota errors and return null rather than throwing. The adapter should be injected via Riverpod to allow substitution with an in-memory implementation during tests.