Can I vibecode ParseHub?

Build a deliberately narrow, robust personal substitute for ParseHub, focusing on the core value of reliable data extraction without the complexity of a full visual clone.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + PostgreSQL + BullMQ + Puppeteer.

Primary job: Build an explicit, code-driven web scraping workflow engine with trigger mechanisms, validated steps, aggressive retries, detailed logging, and a manual replay button.
Start from an empty folder and create the complete working project. Make the default mode single-user and private.

Feature Requirements:
1. Workflow Engine: Instead of a point-and-click UI, workflows are written as modular Puppeteer scripts. Build a framework that standardizes how these scripts return data and report errors.
2. Queueing & Concurrency: Use BullMQ (backed by Redis) to schedule and queue scraping tasks. Ensure tasks don't overwhelm the target server or the local machine (e.g., limit concurrent browser instances).
3. Resiliency: Scraping is flaky. Implement robust error handling for common issues (timeouts, missing selectors, navigation failures) with configurable retry policies (e.g., 3 retries with backoff).
4. Dashboard: Build a Next.js interface to view configured workflows, trigger them manually, and monitor the job queue.
5. Storage & Logging: Store all extracted data in PostgreSQL as structured JSON. Keep detailed execution logs for every run, including screenshots of failures (stored locally) to aid in debugging. Include a manual "Replay Job" button.

Constraints & Scope:
- Do not add analytics, telemetry, ads, or third-party accounts.
- Put every secret and external credential in `.env` and provide `.env.example`. Use realistic, clearly labelled sample data.
- Implement the smallest polished interface that completes the core loop end to end, with clear empty, loading, success, and failure states.
- Deliberately exclude these paid-product advantages: massive proxy rotation infrastructure, machine-learning based schema drift handling, enterprise access controls, and visual CSS selector generation.
- Where an external API is optional, keep the app useful without it and explain the degraded mode.

Deliverables:
- Complete source code.
- Write focused unit tests for the data parsing functions.
- Add one end-to-end smoke test that runs a workflow against a dummy HTML file.
- Create a README with setup, architecture, Redis/Postgres requirements, data location, and limitations.
- Add scripts for install, development, test, build, and a production-style local run. Fix any errors before finishing.