debugging-gengar-tui-commands

Slash commands missing from autocomplete usually indicate a mismatch between the Python command registry and the frontend Ink/TypeScript handlers. Debugging requires checking each layer for command presence and comparing the canonical `COMMAND_REGISTRY` entry with frontend handler availability to resolve the sync drift.

To fix a slash command ignored by the JSON-RPC gateway dispatch, you must verify the command's presence across the Python registry and the tui_gateway dispatcher. Ensuring the canonical `CommandDef` is correctly updated in the `COMMAND_REGISTRY` resolves gateway dispatch failures.

Divergent behavior between CLI and TUI happens when the Python command registry, the JSON-RPC dispatcher, and the Ink/TypeScript slash handlers drift out of sync. You need to compare the registry entry with frontend handler availability and validate both dispatch and live state updates.

When a slash command persists configuration without applying live UI state changes, it indicates a frontend handler mismatch. You must validate live state updates after rebuilding the TUI and ensure the Ink/TypeScript handlers correctly process the JSON-RPC dispatch response.

Yes, you need to rebuild the TUI after updating the Python `COMMAND_REGISTRY` to validate both dispatch and live state updates. Rebuilding ensures the Ink/TypeScript frontend syncs with the updated command definitions and confirms the command appears in autocomplete and executes correctly.

The best way to debug missing slash commands across layers is to pinpoint whether autocomplete, dispatch, or frontend handling is inconsistent. Add or update the canonical `CommandDef` in the Python registry, ensure aliases are correct, and wire frontend handlers to verify end-to-end behavior.