Can I vibecode Retool?

Add dashboards to the admin panel in this folder. Requirements:

- A dashboard is a YAML file in ./dashboards/ listing saved queries from ./tools/
  and how to show each one: number, table, line chart or bar chart.
- Render dashboards at /d/:name in a grid of cards, each with its own refresh
  button and last-updated time.
- Optional auto-refresh interval per dashboard, never faster than 30 seconds.
- Queries on a dashboard always run read-only, even on writable connections.
- Update the README with an example dashboard file.

Add scheduled jobs to the admin panel in this folder. Requirements:

- A job is a YAML file in ./jobs/: a cron expression (node-cron), a saved query
  from ./tools/, and what to do with the result: post JSON to a webhook URL, send
  an email through SMTP settings in .env, or do nothing if the result is empty.
- A /jobs page lists jobs with their next run, last result and a Run now button.
- Keep a log of the last 200 runs in ./data/jobs.jsonl with duration and errors.
- Jobs that write to a database must name a connection without READONLY.
- Out of scope: multi-step branching workflows.
- Update the README.

Add REST API sources to the admin panel in this folder. Requirements:

- An API source is defined in .env: a base URL and an auth header value.
- Saved API calls live in ./tools/*.http files: method, path with {{named}}
  parameters, optional JSON body.
- Each saved call gets a page like a saved query: an input form and the
  response as a table when it is an array of objects, or as formatted JSON.
- Calls other than GET ask for confirmation and are written to ./data/audit.jsonl.
- Never log the auth header.
- Update the README with an example for a Stripe or GitHub token.

Add an importer for Retool app exports to the admin panel in this folder. Requirements:

- A command that takes the path to a JSON file exported from a classic Retool app
  (App actions > Export to JSON).
- Inspect the file's structure first and print every query it finds with its name,
  resource name and SQL, before writing anything.
- Convert {{ }} references in the SQL into {{named}} parameters for this panel and
  list the ones that pointed at components, so I can fix them by hand.
- Write each query to ./tools/<query-name>.sql and skip names that already exist.
- Update the README with the export steps and the import command.