Can I vibecode Octoparse?

Build a deliberately narrow, code-centric personal substitute for Octoparse's core functionality, avoiding the complexity of a full visual scraping clone.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + PostgreSQL + BullMQ + Playwright.

Primary job: Build an explicit web scraping engine focusing on one highly reliable workflow. It needs a trigger mechanism, validated sequential scraping steps, robust retry logic, execution logs, and a manual replay button.
Start from an empty folder and create the complete working project.
Make the default mode single-user and private. Store user data in the provided PostgreSQL database.

Feature Requirements:
1. Workflow Definition: Workflows are defined in code. Create a robust interface for defining a Playwright scraping script that can navigate, wait for selectors, extract data, and handle pagination.
2. Job Queue: Use BullMQ (backed by Redis) to manage scraping jobs. This is crucial for handling timeouts, rate limits, and avoiding blocking the main server thread.
3. Resilience: Implement robust retries for failed steps (e.g., handling CAPTCHAs, network timeouts, or missing DOM elements) with exponential backoff.
4. Dashboard: Build a Next.js interface to view configured scraping workflows, trigger them manually, and monitor the BullMQ job queue. 
5. Execution Logs: Store detailed logs of every run in PostgreSQL, including start/end times, extracted JSON payloads, and detailed error stack traces for failed runs. Include a clear "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`.
- Deliberately exclude these paid-product advantages: a drag-and-drop CSS selector builder, hundreds of maintained site-specific templates, proxy rotation infrastructure, and durable execution at massive scale.
- Where proxy rotation or CAPTCHA solving is optional, keep the app useful without it and document how the user might add it later.

Deliverables:
- Complete source code.
- Write focused unit tests for the data extraction logic (using mocked HTML).
- Add one end-to-end smoke test that runs a headless Playwright instance against a static test page and verifies the DB record.
- 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. Ensure all types pass and fix errors before finishing.