debugging-zedclaw-tui-commands

TUI slash commands fail across interfaces due to mismatches between the Python command registry, gateway dispatch, and Ink TypeScript frontend. Resolving this requires validating COMMAND_REGISTRY entries, ensuring gateway dispatch alignment, and verifying local handler state propagation.

To restore TUI autocomplete correctness, you must ensure command definitions in the Python COMMAND_REGISTRY propagate properly to the frontend autocomplete data. This involves checking cross-layer command drift between the backend registry and Ink UI logic.

Live UI behavior fails to update when gateway dispatch routing and Ink TypeScript local handler state propagation are misaligned. You must verify gateway dispatch routing and confirm TUI state updates occur immediately rather than only persisting config.

Debug a failing slash command by checking its canonical name against Ink frontend handlers, the TUI autocomplete registry, and Python and gateway dispatch paths. This diagnoses whether the command is missing, mis-registered, or inconsistently handled.

Yes, fixing ZedClaw TUI slash-command bugs requires validating Python COMMAND_REGISTRY entries and verifying Ink TypeScript local handler behavior. You must reconcile command definitions and handlers across both backend and frontend layers.

Debugging command drift is limited to scenarios where commands are missing from autocomplete, work in CLI but not TUI, or update persisted config without live UI changes. It requires validating Python registry, gateway dispatch, and TypeScript handler alignment.