Can I vibecode Pabbly Connect?

Build a closest honest personal substitute for Pabbly Connect in an empty repository, focusing on durable execution rather than an infinite marketplace of apps.
Use exactly this stack: TypeScript, Node.js 22, PostgreSQL, Redis, BullMQ, and Docker Compose. Do not offer alternative stacks.

The core loop is: connect two documented external APIs, execute a small, highly durable workflow with guaranteed retries, expose comprehensive execution logs, and strictly avoid building a generic visual platform.

Architecture & Features:
1. Infrastructure: Provide a `docker-compose.yml` that stands up Postgres, Redis, and your Node.js worker/server. The first run must work locally with a single documented `docker compose up` command.
2. Workflow Model: Implement a strict code-based pipeline model: Trigger -> Transform -> Condition -> Action. Do not build a generic visual node editor. Workflows are defined as TypeScript objects or functions.
3. Connector Implementation: Connect exactly two named services (e.g., a GitHub Webhook trigger and a Slack/Discord message action) using their documented APIs and encrypted credentials stored securely.
4. Execution Engine: Use BullMQ to handle job queuing. Store every single run, step input hash, output summary, retry attempt, and final status in PostgreSQL.
5. Idempotency & Resiliency: This is the most critical feature. Make all side effects idempotent. If a step fails (e.g., network timeout), the engine must support retrying from the failed step without repeating already completed actions. Implement strict rate limits, exponential backoff, dead-letter queues, and manual job replay.
6. Interface: Build a minimal, fast UI (or CLI) with clear empty, loading, success, and recoverable error states to view run history.

Constraints & Scope:
- Store all user data locally by default; make exporting the run history straightforward.
- Put secrets in `.env`, ship `.env.example`, and never commit credentials. Implement safe secret rotation.
- Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
- Deliberately leave out a broad connector marketplace, unreviewed user code execution (like JS eval nodes), enterprise governance, and vendor-operated OAuth apps.

Deliverables:
- Complete source code.
- Write focused tests for the core transformation logic and one end-to-end happy path validating idempotency.
- Create a README with setup, architecture, permissions, and backup steps.
- Finish by running the tests and listing the exact commands used.