docs(redis): document Valkey compatibility

README.md

@@ -224,6 +224,8 @@ powershell -c "irm https://conductor-oss.github.io/conductor-skills/install.ps1
 | Postgres + ES7 | [config-postgres-es7.properties](docker/server/config/config-postgres-es7.properties) |
 | MySQL + ES7 | [config-mysql.properties](docker/server/config/config-mysql.properties) |
 
+**Using Valkey?** Conductor's Redis backend uses standard RESP commands only, so [Valkey](https://valkey.io) — the open-source, BSD-3-licensed fork of Redis — works as a drop-in replacement. Point any `config-redis*.properties` file's `conductor.redis.hosts` at your Valkey endpoint; `conductor.db.type` stays `redis_standalone`/`redis_cluster`/`redis_sentinel` since it selects the wire protocol, not the product. See [Redis configuration](docs/documentation/advanced/redis.md#valkey-compatibility) for details.
+
 </details>
 
 ---

docs/documentation/advanced/redis.md

@@ -50,3 +50,11 @@ conductor.redis.hosts=host0:6379:us-east-1c:my_str0ng_pazz;host1:6379:us-east-1c
 
 - In a cluster, all nodes use the same username and password.
 - In a sentinel configuration, sentinels and redis nodes use the same database index, username, and password.
+
+## Valkey compatibility
+
+Conductor's Redis backend (Jedis 6.0.0, Redisson 3.22.0) communicates using standard RESP commands only — no Redis modules (RedisSearch, RedisJSON, etc.) are used. This means [Valkey](https://valkey.io), the open-source, BSD-3-licensed fork of Redis, works as a drop-in replacement, including managed offerings such as AWS ElastiCache for Valkey and GCP Memorystore for Valkey.
+
+No new configuration is required. Point `conductor.redis.hosts` at your Valkey endpoint(s); `conductor.db.type` stays `redis_standalone`, `redis_cluster`, or `redis_sentinel` — these values select the wire protocol Conductor speaks, not the specific product serving it.
+
+Redisson, which backs Conductor's distributed locking, [officially supports Valkey 7.2.5 and above](https://github.com/redisson/redisson).