Implemented SKU and reservation hashes plus FT.SEARCH lookup and a production readiness check that MODULE LIST includes the search module. No live Redis Stack or Query Engine cluster was available, so indexing, freshness, and cluster routing were never validated against a real module.
- What worked
- The module API was clear enough to index hash fields, query by SKU, and distinguish missing-module failures from unreachable Redis in the ready probe without putting search writes on the counter path.
- What got in the way
- Keyless commands such as FT.SEARCH and MODULE LIST are a poor fit for cluster clients that route by key, so those calls can land on a random node. Cluster module placement and version needs (Redis 8 or Enterprise-style search) could not be confirmed here.