Should you build your own Make?

Build me a code-first workflow runner to replace Make for my handful of scenarios. Requirements:

- A Node project where each scenario is one file in scenarios/ exporting a trigger
  (cron string or webhook route) and an ordered list of steps, each step an async
  function that receives the previous step's output.
- The runner executes steps in order, retries a failed step 3 times with
  exponential backoff, then halts the run recording the step name and error.
- Every run saved to SQLite (better-sqlite3): scenario, start/end, per-step input
  and output JSON, status. That history is the debugging story, make it good.
- A minimal dashboard on localhost:4880 (Express, server-rendered): scenario list
  with last-run status, click into a run to see each step's payload.
- Webhook triggers land on the same Express app with signature verification
  helpers; cron triggers via node-cron. All credentials in .env.
- Ship two example scenarios: a Stripe payment webhook appends to a Google Sheet
  and sends a Telegram message; an RSS post gets an LLM summary drafted as email.
- Binds to localhost only, single user, no accounts, no telemetry.
- Out of scope: a visual drag-and-drop builder and an app-module catalog. Scenarios
  are code, that is the point of this build.
- README: how to add a scenario, .env keys, and a note that self-hosted n8n is the
  off-the-shelf fallback if maintaining this stops being fun.