Can I vibecode Integrately?

Build a closest honest personal substitute for Integrately in an empty repository.
Use TypeScript, Node.js 22, PostgreSQL, Redis, BullMQ, and Docker Compose; do not offer alternative stacks.
The core loop is: connect two specific services through a fixed trigger and action, execute a small durable workflow, expose retries and logs, and avoid claiming a general integration platform.
Start from an empty folder and create the complete working project.

Functional Requirements:
- Workflow Engine: Implement a robust, background-job based workflow engine using BullMQ. Support a single fixed trigger polling an API, and pushing to an action API.
- Integration Implementation: Hardcode exactly two named services (e.g., GitHub to Slack) using documented APIs. Do not build a dynamic marketplace of connectors.
- Execution State: Store every run, step input hash, output summary, retry attempt, and final status in PostgreSQL.
- Idempotency & Retries: Make side effects idempotent where possible. Support manually or automatically retrying from the failed step without repeating successfully completed prior actions.
- Resilience: Add rate limits, exponential backoff, dead-letter queue handling, and secret rotation for the chosen APIs.

Architecture & State:
- Store all user data locally by default and make export straightforward.
- Put secrets in .env, ship .env.example, and never commit credentials.
- Use Docker Compose for a reliable, reproducible local execution environment with PostgreSQL and Redis.

UI/UX & States:
- Build a minimalistic dashboard to view workflow runs, logs, and a manual "replay" button.
- Include clear empty, loading, success, and recoverable error states.
- Add input validation, safe filenames, and graceful handling of unavailable APIs in the UI.

Security & Constraints:
- Validate untrusted input. Encrypt credentials at rest if stored in the database.
- Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
- Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
- Deliberately leave out a broad connector marketplace and visual node editors.
- Deliberately leave out unreviewed user code execution.
- Deliberately leave out enterprise governance, guaranteed execution SLAs, and vendor-operated OAuth apps.

Testing & DevOps:
- Write focused tests for the core transformation and one end-to-end happy path.
- Create a README with setup, architecture, permissions, data location, and backup steps.
- Ship Docker Compose, health checks, sample workflows, tests, backups, and connector-limit documentation.
- Finish by running the tests and listing the exact commands used.