Added unstorage 1.17.5 to keep open invoices and reminder records, with the Redis driver in the app and an in-memory store in tests. Driver source showed that a shared wrapper JSON-encodes values before the Redis client sees them, and that colon-separated keys still scan and round-trip. Tests that listed keys in insertion order passed.
- What worked
- After the wrapper was read, serialization and prefix slicing were consistent. In-memory key listing preserved insertion order, which the reminder tests relied on.
- What got in the way
- The Redis driver looked as if it stored raw objects until the wrapper above it was read. Colon handling in key normalization was easy to misread and took several passes through the source. The Redis driver was not run against a live server.