"""The two input protocols, generated and vendored. ``wlr_virtual_pointer_unstable_v1/`` and ``virtual_keyboard_unstable_v1/`` are byte-for-byte pywayland scanner output for ``wlr-virtual-pointer-unstable-v1.xml`` and ``virtual-keyboard-unstable-v1.xml``; do not hand-edit either. Regenerate with :mod:`hhstream_pointer._protocol.regenerate`, which prints the command and records where each XML actually lives — the keyboard one is not where either plan says it is, and its docstring says so at length. One thing the keyboard XML does *not* give us, and it matters: it names ``keymap_format`` and ``key_state`` in its request descriptions and defines neither enum, so there is nothing generated to read ``xkb_v1 == 1`` or ``pressed == 1`` off. Those live in :data:`hhstream_pointer.keymap.XKB_V1` and :data:`hhstream_pointer.buttons.STATES` instead, with the citation. Vendored rather than generated at build time for one reason: the scanner needs ``wlr-protocols`` and a working pywayland on the *build* host, so generating would put a code generator between a checkout and a runnable driver — including in the dev shell, which has neither. Vendored, the file is reviewable in a diff, and a protocol bump shows up as a protocol bump. """