feat: Support plain file paths for workflow loading

[louis030195]

Summary

This PR makes workflow loading more intuitive by allowing plain file paths to be passed to the url parameter in execute_sequence, without requiring the file:// prefix.

Changes

• Modified server_sequence.rs: Updated URL handling logic to accept plain file paths (any path that doesn't start with http:// or https://)
• Updated utils.rs: Enhanced schema description for ExecuteSequenceArgs.url to document support for plain paths
• Backwards compatible: Still supports file://, http://, and https:// URLs

Examples

Before (required file:// prefix):

{
  "tool_name": "execute_sequence",
  "arguments": {
    "url": "file://C:/workflows/myworkflow.yml"
  }
}

After (plain paths now work):

{
  "tool_name": "execute_sequence",
  "arguments": {
    "url": "myworkflow.yml"
  }
}

Or with absolute path:

{
  "tool_name": "execute_sequence",
  "arguments": {
    "url": "C:/workflows/myworkflow.yml"
  }
}

Benefits

1. More intuitive: Users can specify workflows like regular files
2. Less verbose: No need to remember file:// prefix for local files
3. Backwards compatible: Old code using file:// still works
4. Consistent with CLI: Most tools accept plain file paths

Testing

Build passes with cargo build --release and changes are minimal, focused on URL detection logic.

Co-Authored-By: Claude [email protected]