Can I vibecode Albato?

Build a closest honest personal substitute for Albato in an empty 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: connect two specific services, execute a small durable workflow, expose every transformation and retry in the logs. Do not aim to be a general platform; focus on deep, reliable implementation of this specific core loop.
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 pre-commit hooks or CI checks to ensure credentials are never accidentally committed to version control.
Implement a fixed trigger, transform, condition, and action workflow model rather than a general visual language. Connect exactly two named services using documented APIs and securely encrypted credentials.
Store every run, step input hash, output summary, retry attempt, and final status in the PostgreSQL database for auditability and durability.
Design all side effects to be idempotent and resilient. Support retry from the failed step without repeating 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 workflows, comprehensive test suites, database backup scripts, and clear documentation on limits.
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 (like Zod), 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 and unreviewed user code execution.
Deliberately leave out enterprise governance, guaranteed execution SLAs, and vendor-operated OAuth apps.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
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.