Feature Request: External Workspace for XPipe Resources

This feature request was organized with the help of AI.

Not sure whether something similar already exists.

I'd like to have a human-friendly external workspace representation for XPipe resources that can be edited from an external IDE and used with normal Git workflows.

The current vault format works well for XPipe to manage resources, but it is difficult to work with directly as a developer project. In particular, it is not easy to organize, review, or modify scripts and connections using standard development tools.

A workspace representation could expose XPipe resources in a structure that is easier for humans and AI agents to understand, for example:

All connections/
    Production/
    Development/

All scripts/
    deploy.sh
    backup.sh
    lib/
        common.sh

The workspace should allow users to:

• Develop scripts in an external IDE.
• Organize reusable script libraries and related files.
• Manage connections and scripts together as part of the same workflow.
• Review and modify changes using normal filesystem tools and Git.
• Allow AI agents to understand and modify XPipe resources through a standard project structure.

XPipe-specific metadata and functionality should continue to work, including:

• Connection organization and references.
• Script types and dependencies.
• Init scripts and shell environments.
• Categories, ordering, icons, and other presentation-related settings.

Example workflow

A user is developing an automation workflow for a new service.

1. Create or update scripts in the external workspace.
2. Add shared helper scripts or templates used by multiple workflows.
3. Add or update the required connections.
4. Commit the changes together through Git.
5. Open XPipe and use the updated resources with the normal XPipe experience.

The goal is to make XPipe resources easier to develop, review, automate, and collaborate on while preserving the existing XPipe experience.