fix: ensure all terminal command tags are parsed but not displayed in UI

- Add dyad-run-backend-terminal-cmd and dyad-run-frontend-terminal-cmd to parser arrays
- Make all terminal command tags return null in render (silent execution)
- Remove unused DyadRunTerminalCmd component
- Terminal commands now execute silently in terminals without UI clutter

All terminal command tags (<run_terminal_cmd>, <dyad-run-backend-terminal-cmd>, <dyad-run-frontend-terminal-cmd>) are properly processed by the backend but no longer appear in the chat interface.

Author: SFARPak

dyad/src/components/chat/DyadMarkdownParser.tsx

@@ -124,6 +124,9 @@ function preprocessUnclosedTags(content: string): {
     "dyad-codebase-context",
     "think",
     "dyad-command",
+    "dyad-run-backend-terminal-cmd",
+    "dyad-run-frontend-terminal-cmd",
+    "run_terminal_cmd",
   ];
 
   let processedContent = content;
@@ -191,6 +194,9 @@ function parseCustomTags(content: string): ContentPiece[] {
     "dyad-codebase-context",
     "think",
     "dyad-command",
+    "dyad-run-backend-terminal-cmd",
+    "dyad-run-frontend-terminal-cmd",
+    "run_terminal_cmd",
   ];
 
   const tagPattern = new RegExp(
@@ -429,6 +435,16 @@ function renderCustomTag(
       // Don't render anything for run_terminal_cmd
       return null;
 
+    case "dyad-run-backend-terminal-cmd":
+      // Terminal commands should be executed silently by the backend
+      // Don't render anything for dyad-run-backend-terminal-cmd
+      return null;
+
+    case "dyad-run-frontend-terminal-cmd":
+      // Terminal commands should be executed silently by the backend
+      // Don't render anything for dyad-run-frontend-terminal-cmd
+      return null;
+
     default:
       return null;
   }