What
Running a local slash command and appending its result has been factored into one shared function, now used both for normal command invocation and for commands dispatched over a remote/bridge connection. Bridge-originated commands are tagged with dispatchedOverBridge: true so they can be distinguished.
Command dispatch now special-cases commands of type local to run directly through this shared path and log a tengu_immediate_command_executed telemetry event, without ever opening a panel or going through the dialog-host's JSX-building step. Only local-jsx commands (ones that render their own interactive UI) still go through the dialog-host path.
Why
This removes duplicated logic between direct and bridge-originated command execution and avoids unnecessary UI/panel overhead for plain local commands that don't need one.