Can I vibecode Activepieces Cloud?

Build a comprehensive, self-hosted replacement for Activepieces Cloud in a fresh repository.
Use TypeScript, Node.js 22, PostgreSQL, Redis, BullMQ, and Docker Compose to wire it all together; do not offer alternative stacks or languages.
The core loop is: visually or programmatically connect two specific services, execute a small durable workflow, expose detailed logs for every step, and provide granular retry capabilities. Do not aim to be a general integration platform with hundreds of apps; focus on deep, reliable integration of two specific services.
Ensure the first run works locally with a single documented command (e.g., `docker compose up --build`).
Store all user data locally by default, avoiding any external SaaS dependencies for core functionality, and make data export straightforward via a dedicated API endpoint or script in standard formats like CSV or JSON.
Put all secrets, API keys, and database credentials in a `.env` file, ship a `.env.example`, and implement checks to ensure credentials are never accidentally committed to version control.
Implement a rigid workflow model: Trigger, Transform, Condition, and Action. Avoid a general visual programming language in favor of strict, predictable step execution. Connect exactly two named external services using their documented APIs and securely encrypt OAuth tokens or API keys at rest in PostgreSQL.
Store every run's execution path, step input hashes, output summaries, retry attempts, and final status (success/failure/timeout) in the local database for auditability and durability.
Design all side effects to be idempotent and resilient. Support resuming or retrying a workflow from the exact failed step without ever repeating successfully completed actions.
Build in rate limiting, exponential backoff for API errors, dead-letter queues for unprocessable tasks, manual replay UI, execution cancellation, and a mechanism for secret rotation.
Ship a complete Docker Compose setup with health checks for all services, sample seed data, comprehensive test suites, database backup scripts, and clear documentation.
Design a minimal but polished web UI with clear states for empty, loading, success, and recoverable errors, ensuring accessible keyboard navigation, focus states, and sensible contrast.
Implement strict input validation using modern libraries, enforce safe data handling, and gracefully handle external API outages without crashing the application.
Write focused unit tests for the core logic and at least one robust end-to-end happy path test using an automated testing framework.
Create an exhaustive README detailing the setup process, system architecture, permission models, data storage locations, backup/restore steps, and limitations.
Strictly avoid adding multi-tenant user accounts, billing systems, telemetry, tracking analytics, or any hosted control plane.
Deliberately leave out a broad connector marketplace—hardcode the two essential integrations.
Deliberately leave out unreviewed user code execution (no arbitrary eval or script steps).
Deliberately leave out enterprise governance features, SLA-guaranteed execution, and vendor-operated OAuth app credentials.
Finish by running the test suite, building the application, and outputting the exact commands used to verify the system. Fix errors rather than merely describing them.