Can I vibecode Robomotion?

Build a deliberately narrow personal substitute for Robomotion, focusing on a core robotic process automation (RPA) engine.
Use exactly this stack: Next.js 15, TypeScript, PostgreSQL, and BullMQ for background job processing; do not offer alternative stacks.
Your primary job is to build a visual or JSON-based workflow automation engine with explicit triggers (e.g., webhook, schedule), validated execution steps (e.g., HTTP request, data parsing), retries, comprehensive execution logs, and a manual replay button for failed jobs.
Start from an empty folder and create the complete working project. Make the default mode single-user and private.
Store all execution data and workflow definitions in the self-hosted PostgreSQL database. Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete, such as a dummy workflow that fetches data from a public API and logs it.
Implement the smallest polished interface that completes the core loop end to end: defining a workflow, triggering it, and viewing the real-time execution logs and results.
Include clear empty, loading, validation, success, and failure states. Add workflow import and export (as JSON) so the user is not trapped in the app.
Use accessible keyboard navigation, labels, focus states, and sensible contrast. Validate untrusted input and never log secrets or sensitive payload contents in the execution logs.
Deliberately exclude these paid-product advantages: hundreds of maintained proprietary connectors, OAuth app verification, and durable execution at massive scale.
Write focused unit tests for the workflow runner logic and data model. Add one end-to-end smoke test that proves a simple webhook-triggered workflow executes successfully.
Create a README with setup, architecture, database migrations, backup, and limitations.
Finish by running the tests and listing the exact commands used.