Can I vibecode Make?

Build a code-first, developer-centric workflow automation runner to replace Make (formerly Integromat) for my personal scenarios. The goal is to build a robust, observable local engine that handles webhook and cron triggers without a complex visual drag-and-drop builder. 

Stack requirements:
- Language & Runtime: TypeScript on Node.js (v20+).
- Web Server: Express.js for handling webhooks and serving the dashboard.
- Database: SQLite (via better-sqlite3) to store workflow executions, step logs, and status.
- Scheduling: node-cron for time-based triggers.

Architecture & Features:
1. Scenario Definition: Each automation scenario should be a single TypeScript file in a `scenarios/` directory. A scenario exports a configuration object containing:
   - A `trigger` (either a cron expression or a specific webhook path/method).
   - An ordered array of `steps`, where each step is an async function that receives the output of the previous step.
2. Execution Engine: The runner must load all scenarios on startup. When triggered, it should execute steps sequentially. Implement a robust retry mechanism: if a step fails, retry up to 3 times using exponential backoff before halting the scenario. Record the exact step name and error message if it ultimately fails.
3. Observability & Logging: Every execution must be logged to SQLite. Store the scenario name, start/end timestamps, overall status, and a JSON payload of every step's input and output. This history is critical for debugging.
4. Minimal Dashboard: Serve a simple HTML dashboard on localhost (port 4880). It should list all loaded scenarios, show their latest run status, and provide a detailed view of past runs, allowing me to inspect step-by-step inputs, outputs, and errors.
5. Security & Config: All secrets must live in `.env`. Bind the server to localhost only (no remote access by default). Webhooks should have helpers to verify HMAC signatures (e.g., for Stripe or GitHub).

Deliverables:
- The complete source code, fully typed.
- Two working example scenarios:
  1. A webhook trigger from Stripe that formats a message and pushes it to a Discord/Telegram channel.
  2. A cron trigger that checks an RSS feed, summarizes it with a mock LLM call, and outputs an email draft.
- A comprehensive README explaining how to add new scenarios, handle credentials, and view logs. Explicitly note that this is a code-first alternative to Make and recommend self-hosted n8n if a UI becomes necessary.