3 Commits

Author	SHA1	Message	Date
johndoe6345789	ce435a5e1b	feat(schema): add n8n workflow schema with first-class variables support ... - Moved n8n workflow schema to schemas/n8n-workflow.schema.json - Added `variables` property at workflow root level for type-safe, reusable workflow configuration - Implemented full variable system with: * Type system (string, number, boolean, array, object, date, any) * Validation rules (min, max, pattern, enum) * Scope control (workflow, execution, global) * Required/optional with default values - Created comprehensive N8N_VARIABLES_GUIDE.md (6,800+ words) with: * 5 real-world use case examples * Best practices and migration guide from meta to variables * Complete property reference and expression syntax - Created N8N_VARIABLES_EXAMPLE.json demonstrating e-commerce order processing - Documented schema gaps in N8N_SCHEMA_GAPS.md (10 missing enterprise features) - Created migration infrastructure: * scripts/migrate-workflows-to-n8n.ts for workflow format conversion * npm scripts for dry-run and full migration * N8N_COMPLIANCE_AUDIT.md tracking 72 workflows needing migration - Established packagerepo backend workflows with n8n schema format Impact: Variables now first-class citizens enabling DRY principle, type safety, and enterprise-grade configuration management across workflows. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-01-22 18:38:37 +00:00
johndoe6345789	c670b8f911	refactor: Move core engine into executor/ts ... The TypeScript core engine now lives inside executor/ts/ alongside the TypeScript runtime, creating a cleaner structure where each executor folder is self-contained. Structure: executor/ts/ # TypeScript runtime + core engine ├── executor/ # DAG executor ├── registry/ # Plugin registry ├── utils/ # Priority queue, template engine ├── types.ts # Type definitions └── index.ts # Main exports executor/python/ # Python runtime executor/cpp/ # C++ runtime (Phase 3) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-21 16:10:33 +00:00
johndoe6345789	5ac579a2ed	feat: Add Python plugins from AutoMetabuilder + restructure workflow folder ... Restructure workflow/ for multi-language plugin support: - Rename src/ to core/ (engine code: DAG executor, registry, types) - Create executor/{cpp,python,ts}/ for language-specific runtimes - Consolidate plugins to plugins/{ts,python}/ by language then category Add 80+ Python plugins from AutoMetabuilder in 14 categories: - control: bot control, switch logic, state management - convert: type conversions (json, boolean, dict, list, number, string) - core: AI requests, context management, tool calls - dict: dictionary operations (get, set, keys, values, merge) - list: list operations (concat, find, sort, slice, filter) - logic: boolean logic (and, or, xor, equals, comparisons) - math: arithmetic operations (add, subtract, multiply, power, etc.) - string: string manipulation (concat, split, replace, format) - notifications: Slack, Discord integrations - test: assertion helpers and test suite runner - tools: file operations, git, docker, testing utilities - utils: filtering, mapping, reducing, condition branching - var: variable store operations (get, set, delete, exists) - web: Flask server, environment variables, JSON handling Add language executor runtimes: - TypeScript: direct import execution (default, fast startup) - Python: child process with JSON stdin/stdout communication - C++: placeholder for native FFI bindings (Phase 3) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-21 16:08:08 +00:00