That comparison table is misleading because it mixes implementation details with user-facing behavior, and for example Neovim uses inotify or platform-specific filesystem watchers to surface external changes so marking that row as 'no' is incorrect without platform and config qualifiers.

Keybinding coherence is an engineering tradeoff, and if Ki wants consistent behavior it should expose orthogonal primitives like operators and motions plus AST-aware textobjects using Tree-sitter style node names, then provide discoverability tools such as a which-key overlay and explicit node prefixes so power users get composability while newcomers have a fighting chance.