chore: remove YAML workflow legacy code

- Remove output_parser.rs (YAML-only JavaScript output parsing)
- Remove workflow_format.rs (YAML vs TypeScript detection)
- Remove serde_yaml dependency from mcp-agent and cli
- Simplify server_sequence.rs to TypeScript-only execution
- Preserve full MCP event streaming (WorkflowEvent, peer notifications)
- Remove YAML example workflows
- Update tests to remove YAML-specific test cases
- CLI now only supports JSON workflow definitions

TypeScript workflows continue to work with all MCP notification features
including progress tracking, logging, and event streaming.

Author: louis030195

Cargo.lock

@@ -23,7 +23,6 @@ path = "src/bin/cargo-terminator.rs"
 [dependencies]
 serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0.140"
-serde_yaml = "0.9"
 clap = { version = "4.4", features = ["derive", "env"] }
 tokio = { version = "1", features = [
     "rt",

crates/terminator-cli/Cargo.toml

@@ -2165,7 +2165,7 @@ fn parse_workflow_content(content: &str) -> anyhow::Result<serde_json::Value> {
     }
 
     // Strategy 2: Try direct YAML workflow
-    if let Ok(val) = serde_yaml::from_str::<serde_json::Value>(content) {
+    if let Ok(val) = serde_json::from_str::<serde_json::Value>(content) {
         // Check if it's a valid workflow (has steps field)
         if val.get("steps").is_some() {
             return Ok(val);
@@ -2185,17 +2185,17 @@ fn parse_workflow_content(content: &str) -> anyhow::Result<serde_json::Value> {
     }
 
     // Strategy 4: Try parsing as YAML wrapper first, then extract
-    if let Ok(val) = serde_yaml::from_str::<serde_json::Value>(content) {
+    if let Ok(val) = serde_json::from_str::<serde_json::Value>(content) {
         if let Some(extracted) = extract_workflow_from_wrapper(&val)? {
             return Ok(extracted);
         }
     }
 
     Err(anyhow::anyhow!(
-        "Unable to parse content as JSON or YAML workflow or wrapper object. Content must either be:\n\
+        "Unable to parse content as JSON workflow or wrapper object. Content must either be:\n\
         1. A workflow with 'steps' field\n\
         2. A wrapper object with tool_name='execute_sequence' and 'arguments' field\n\
-        3. Valid JSON or YAML format"
+        3. Valid JSON format"
     ))
 }
 

crates/terminator-cli/src/main.rs

@@ -54,7 +54,6 @@ hostname = "0.4"
 reqwest = { version = "0.12.5", features = ["json", "blocking"] }
 
 # YAML parsing support
-serde_yaml = "0.9"
 
 # File search support for search_terminator_api tools
 glob = "0.3"

crates/terminator-mcp-agent/Cargo.toml

@@ -6,7 +6,7 @@ pub mod expression_eval;
 pub mod helpers;
 pub mod mcp_types;
 pub mod omniparser;
-pub mod output_parser;
+
 pub mod prompt;
 pub mod scripting_engine;
 pub mod sentry;
@@ -17,7 +17,7 @@ pub mod tool_logging;
 pub mod tree_formatter;
 pub mod utils;
 pub mod vision;
-pub mod workflow_format;
+
 pub mod workflow_typescript;
 
 // Re-export ui_tree_diff from terminator crate (single source of truth)