Can I vibecode Tray.io?

Build the closest honest, production-ready personal consolation tool inspired by Tray.io from scratch in an empty repository.
Use exactly this tech stack without deviation: Next.js 15 (App Router), TypeScript (strict mode), PostgreSQL for persistent data, and BullMQ for robust job queuing. Do not claim to replace Tray.io's structural moat or suggest alternative technologies.

Your primary objective is to build a highly reliable, single-purpose enterprise automation engine. The system must support creating exactly one explicit, multi-step integration workflow that includes a trigger, validated processing steps, automatic retries with exponential backoff, detailed execution logs, and a manual replay button for failed runs.

Data and Security:
- Make the default mode strictly single-user and private, running entirely on the local network or a private server.
- Store all user and execution data locally in the self-hosted PostgreSQL database.
- Keep every secret, webhook token, and external API credential in a `.env` file, ship a `.env.example`, and enforce that no credentials are ever committed or exposed in the UI.
- Validate all untrusted input thoroughly and ensure that secrets or sensitive payload contents are obfuscated in the execution logs.
- Use realistic, clearly labelled sample workflow data that is easy to delete during the onboarding process.

Core Features:
- Implement the smallest, most polished visual interface possible that allows a user to complete the core loop: view the workflow, monitor runs, inspect step-by-step logs, and trigger manual replays.
- Include crystal-clear empty states, loading indicators, input validation, and distinct success/failure states for workflow executions.
- Add a straightforward import and export mechanism (e.g., JSON) for the workflow definition and execution history so the user is never locked in.
- Ensure the UI uses accessible keyboard navigation, clear labels, distinct focus states, and sensible color contrast.

Explicit Exclusions & Constraints:
- Do NOT add analytics, telemetry, advertisements, or third-party user accounts.
- Deliberately exclude paid-product advantages such as OAuth app verification, durable execution at massive scale, automatic schema drift handling, and enterprise governance controls.
- Do NOT fake a massive catalog of integrations, network effects, or proprietary data mapping algorithms.
- If the external API required for the single workflow is unavailable, the application must degrade gracefully, queuing the job or explaining the degraded mode clearly in the UI.

Testing & Documentation:
- Write focused unit tests covering the PostgreSQL data model and the BullMQ job processing logic.
- Add at least one comprehensive end-to-end smoke test that proves the core automation loop (trigger -> process -> log -> replay) works as intended.
- Create an exhaustive README containing setup instructions, permission requirements, architectural overview, data location details, backup steps, and known limitations.
- Provide helper scripts for installation, development, testing, building, and running a production-style local instance.

Finalize your work by running the tests and build steps before finishing. If errors occur, fix them in code rather than merely describing what went wrong.