Filed from the IronCache pre-implementation coverage audit (2026-06-13): no existing issue adequately owned this.
Why this is needed
Specify the introspection families operators and clients depend on beyond the handshake: CLIENT LIST field fidelity (addr/age/idle/flags/lib-name/lib-ver/tot-net-in), CLIENT INFO, CLIENT KILL filter forms, CLIENT PAUSE/UNPAUSE (WRITE|ALL), CLIENT NO-EVICT/NO-TOUCH runtime behavior, and the COMMAND family (DOCS/INFO/COUNT/GETKEYS) that drives client-side arity validation and tooling, defining which fields are byte-faithful vs synthesized for the thread-per-core model. #15 requires only that Tier-0 CLIENT subcommands 'respond without error so handshakes succeed' and hangs deeper design off children, leaving RESET an open decision; no issue owns the COMMAND introspection family or CLIENT LIST/INFO field fidelity; #40 covers only OBJECT ENCODING/DEBUG OBJECT. A distinct compatibility-and-observability surface with no owner.
Context
Relates to / partially overlaps #15. Part of the vision EPIC #1.
Why this is needed
Specify the introspection families operators and clients depend on beyond the handshake: CLIENT LIST field fidelity (addr/age/idle/flags/lib-name/lib-ver/tot-net-in), CLIENT INFO, CLIENT KILL filter forms, CLIENT PAUSE/UNPAUSE (WRITE|ALL), CLIENT NO-EVICT/NO-TOUCH runtime behavior, and the COMMAND family (DOCS/INFO/COUNT/GETKEYS) that drives client-side arity validation and tooling, defining which fields are byte-faithful vs synthesized for the thread-per-core model. #15 requires only that Tier-0 CLIENT subcommands 'respond without error so handshakes succeed' and hangs deeper design off children, leaving RESET an open decision; no issue owns the COMMAND introspection family or CLIENT LIST/INFO field fidelity; #40 covers only OBJECT ENCODING/DEBUG OBJECT. A distinct compatibility-and-observability surface with no owner.
Context
Relates to / partially overlaps #15. Part of the vision EPIC #1.