OpenCode adds which-key-style plugin keymaps

Hot take: this is less about a cosmetic keymap tweak and more about OpenCode laying the groundwork for a real input architecture, where discoverability and extensibility become first-class.

• –Consolidating key/cmd handling into OpenTUI should make the interaction model more consistent and easier to extend.
• –A which-key-like layer is a strong UX move for a dense terminal app because it lowers the learning curve without removing power-user shortcuts.
• –Plugin-extensible keymaps point to a larger ecosystem play, not just internal refactoring.
• –The mention of vim motions suggests OpenCode is aiming for serious keyboard-driven workflows, which fits its terminal-first audience.
• –The main risk is complexity: flexible key handling can become hard to reason about unless the plugin contract stays tight and predictable.