feat: launch Vibeflow n8n v0.5.0

clients/openclaude/README.md

@@ -0,0 +1,11 @@
+# OpenClaude / Community Forks
+
+This target is community / best-effort.
+
+If your fork supports MCP, adapt one of the sample configurations from the primary clients and point it at your n8n MCP server.
+
+Recommended approach:
+- start from the Claude Code or OpenCode examples
+- verify your client supports local MCP servers
+- confirm environment variable names for the n8n MCP process
+- test a simple read-only operation before creating workflows

clients/openclaude/config-snippets.md

@@ -0,0 +1,23 @@
+# OpenClaude and community forks: config notes
+
+This target is best-effort.
+
+Use these guidelines only if your fork supports:
+- MCP connections
+- custom instruction or skill layers
+- conversational follow-up questions
+
+## Minimal strategy
+
+1. Point your client to the n8n MCP endpoint.
+2. Load `templates/system-prompt.md`.
+3. Keep `docs/conversation-contract.md` and `schemas/plan.schema.json` available.
+4. Test with one simple recipe before using real workflows.
+
+## Compatibility contract
+
+The client should be able to:
+- use an MCP server by name
+- ask follow-up questions
+- emit a structured plan before building
+- complete a final handoff report