DOC-7263 Fill missing client signatures in the command-API mapping

Classified all 1,495 empty signature lists across 14 client IDs against the released
clients, then filled the 448 that were real gaps: redis_py 35, node_redis 63, go-redis 23,
jedis 20, php 20, lettuce 47 per variant, nredisstack 46 per variant, redis_rs 26 sync and
28 async. 1,047 stay empty on purpose: 782 are reachable only through a generic call, 180
are unsupported or client-managed, 77 were skipped deliberately (bare container rows and 35
ioredis gaps the tab never renders), and 8 are other cases found while authoring. The skill
and its client-quirks reference now record the classification rules and the non-obvious
receivers. DOC-7266 adds the per-client reason for the generic-only and unsupported rows.

Every filled signature was checked against the released artifact: inspect.signature for
redis-py 8.1.0, javac against Lettuce 7.9.0 and Jedis 8.0.2, go vet against go-redis v9.23.0
and v9.22.0, dotnet build against StackExchange.Redis 3.3.1 and 3.4.31, cargo check against
redis 1.8.1 and 1.6.0, PHP reflection on Predis v3.7.1 and v3.5.1. node-redis was checked by
loading the installed 6.3.1 package and running each command's parseCommand; tsc was not
available. The classification pass first used name matching and was wrong often enough to
matter: it called SSUBSCRIBE unsupported in NRedisStack (it works through
RedisChannel.Sharded), treated SlaveOf and ReplicaOf as callable (both are obsolete errors
in StackExchange.Redis), and put CLIENT SETINFO on go-redis Cmdable (it is on
StatefulCmdable). Reading the method, not the name, is what caught these.

A missing client key and an empty list render the same "No method signature available"
text, so deleting keys would change nothing. The tab also lists a fixed set of clients:
ioredis, RedisVL and Ruby never render, so their 97 empties were not filled.

Fragments were applied by script that only replaced lists that were already [], refused any
file that did not round-trip through json.dumps(indent=2), and kept each file's trailing
whitespace, so the diff is the 448 new lists and nothing else. Judgment calls kept: Jedis
UNSUBSCRIBE, PUNSUBSCRIBE and SUNSUBSCRIBE are authored on the callback objects where they
live, Lettuce clusterSlaves and ftTagvals are deprecated in 7.9.0 but included, NRedisStack
SAVE uses an obsolete SaveType member (a warning), and Predis QUIT is authored although
quit() only disconnects.

Learned: name matching misclassifies; read the method and its receiver before calling a gap
Constraint: only replace lists that are currently [], so existing entries are never overwritten
Directive: do not delete empty client keys to tidy the tab, it renders identically and loses the record
Gaps: generic-only and unsupported verdicts rest on finding no method, none were run against a server
Gaps: node-redis signatures were not type-checked with tsc
Ticket: DOC-7263
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Author: andy-stark-redis

.claude/skills/command-api-mapping/SKILL.md

@@ -76,6 +76,35 @@ For each command in the set you're mapping:
    ```
    Spot-check one command in the rendered table if you can run the site.
 
+## Sweeping empty lists (DOC-7263)
+
+An empty list (`"redis_py": []`) renders "No method signature available for this client."
+A missing key renders the same text, so removing a key changes nothing on the page. The tab
+only lists the clients in `$clientOrder` in `api-methods-tab.html`: ioredis, RedisVL and
+Ruby never render, so filling them has no visible effect.
+
+Classify each empty (command, client) against the **released** client, not the file:
+
+- `real_gap`: a typed method exists but the mapping has no signature. Fill it.
+- `generic_only`: reachable only through `execute_command`, `call`, `Do`, `sendCommand`,
+  `executeRaw`, `redis::cmd` or container magic dispatch with no typed `@method`. Leave empty.
+- `unsupported`: no way to call it, the method throws or panics (`Quit`/`Sync` in go-redis,
+  `memory_doctor` in redis-py), it is `[Obsolete(error: true)]` (SE.Redis `SlaveOf`), or it
+  is client-side and sends no command (`SELECT` as `GetDatabase`, `CLUSTER KEYSLOT`).
+- Bare container rows (`ACL`, `CLIENT`, `CLUSTER`, `CONFIG`, `LATENCY`, `MEMORY`, `MODULE`,
+  `SLOWLOG`, `FUNCTION`, `SCRIPT`, `PUBSUB`) stay empty: the subcommand rows carry the
+  signatures. `HOTKEYS` is not one: check whether its subcommand files already exist.
+
+A name match is a hypothesis. Read the method, and check a sample of hits before trusting a
+count. Typed methods on a non-obvious receiver (`StatefulCmdable`, `IServer`, a `PubSub`
+object, a callback object) still count as `real_gap`: cite the receiver in your report.
+
+To fill many at once, write one fragment per client (`{command: [signatures]}`) outside the
+repo, verify every signature by compiling or reflecting against the released artifact, then
+apply with a script that replaces only lists that are currently `[]`, refuses any file that
+does not round-trip through `json.dumps(indent=2, ensure_ascii=False)`, and keeps each
+file's trailing whitespace. Assert the before and after empty counts.
+
 ## Guardrails
 
 - **Match the live client IDs exactly**, including `go-redis` (hyphen) and `node_redis`,

.claude/skills/command-api-mapping/reference/client-quirks.md

@@ -151,6 +151,32 @@ Translation rules:
 - Return type is generally `RedisResult<T>` (sync) / a future of it (async).
 - `///` doc comments → descriptions when present.
 
+## Receivers that aren't the obvious client (DOC-7263)
+- **redis_py:** `cluster_*` methods exist only on `RedisCluster`; subscribe methods are on the
+  `PubSub` object (`r.pubsub()`); FT.HYBRID is `r.ft(...).hybrid_search`. Some methods are
+  stubs that raise `NotImplementedError`. Read the body, not the name.
+- **node_redis:** `select`, `quit`, `reset`, `monitor` and the subscribe family are methods on
+  `RedisClient`, not command files, and are `undefined` on a cluster client. `LOLWUT` is
+  registered uppercase only. Commands in `@redis/search` and similar need that package.
+- **go-redis:** `CLIENT SETINFO` and `HELLO` are on `StatefulCmdable`/`*Conn`, not `Cmdable`.
+  `HotKeys*` is on `*Client` only. `Monitor` is on the `cmdable` struct but not the
+  `Cmdable` interface. Subscribe methods return `*PubSub`; unsubscribe is on `*PubSub`.
+- **jedis:** `cluster*` methods are on `Jedis` only (not `UnifiedJedis` or `RedisClient`).
+  `unsubscribe`/`punsubscribe`/`sunsubscribe` are on the callback objects
+  (`JedisPubSubBase`, `JedisShardedPubSubBase`), `ssubscribe`/`spublish` on the cluster clients.
+- **lettuce:** subscribe methods are on the pub/sub connection interfaces. `RediSearchCommands`
+  takes only `K` (no `V`).
+- **nredisstack:** server commands are on `IServer` (`FooAsync` twins), subscribe on
+  `ISubscriber`, sharded pub/sub through `RedisChannel.Sharded(...)`. `Save(SaveType)` covers
+  SAVE, BGSAVE and BGREWRITEAOF.
+- **php (predis):** a container subcommand reached only through `__call` (no `@method` in
+  `src/Command/Container/*.php`) is `generic_only`, not a typed method. Consumer methods
+  (`pubSubLoop()`) are the typed home for PSUBSCRIBE/PUNSUBSCRIBE.
+- **redis_rs:** methods come from `implement_commands!` and are generated for four traits.
+  `HotkeysCommands`/`AsyncHotkeysCommands` are separate traits. Some methods need a feature
+  (`acl`, `script` default on; `search_unfinished` is not stable). Async cluster connections
+  carry SSUBSCRIBE/SUNSUBSCRIBE.
+
 ## General
 - **Never invent descriptions.** Empty string beats a plausible-but-unverified sentence.
 - **Confirm the command exists** in the client before adding it; preview commands may be