debugging-bmb-tui-commands

TUI slash command failures usually stem from mismatches between the Python command registry, the JSON-RPC gateway dispatch layer, and the Ink frontend handlers. Reconciling command definitions across all three layers restores missing autocomplete entries and correct dispatch behavior.

To debug inconsistent slash commands, validate canonical command and alias registration in the Python command registry, verify gateway known-command dispatch, and ensure frontend local state updates propagate through the correct rendering paths.

TUI state fails to update when frontend local handlers diverge from persisted config. Confirm TUI-local commands update nanostore state immediately through correct rendering paths, rather than relying solely on backend config propagation.

Yes, the debugging process specifically reconciles command definitions across Python registries, JSON-RPC gateway bridges, and Ink TypeScript frontend handlers. It validates that slash command definitions match what the TUI expects to show in autocomplete.

The best way to synchronize autocomplete is ensuring canonical command definitions, subcommands, and aliases in the Python command file match the TUI gateway dispatch handler and frontend slash handler expectations across all layers.

Validate JSON-RPC gateway dispatch by checking that known-command dispatch handlers match the canonical command names defined in the Python registry, ensuring slash exec and command dispatch routes align with frontend handler expectations.