Vale construir sua versão de FlowHunt?

Build a personal replacement for one FlowHunt agent in an empty repository.
Use TypeScript, Node.js 22, SQLite via better-sqlite3, and the Vercel AI SDK; do not offer alternative stacks.
Scope: a single configurable AI agent, not a general no-code platform. Pick one job and do it well.
The core loop is: load a knowledge base, accept an input (webhook or CLI), route it through a chosen model with a system prompt and a fixed set of tools, take one action, and store the result.
agent.json defines the system prompt, the model (OpenAI or Anthropic, selectable), the tools it may call, and the schedule or trigger.
Ingest a local docs/ folder into a SQLite vector table for retrieval; re-index on a command.
Implement exactly two real tools, an HTTP fetch/POST to a named API using credentials from .env, and a write-to-file or write-to-db action; document how to add a third.
Run on a webhook endpoint and on a cron schedule; keep an immutable log of every run: input, retrieved chunks, model, tokens, tool calls, output, and errors.
Add retries with backoff on 429 and 5xx, a per-run token budget cap, and visible failed runs rather than silent drops.
Put all secrets in .env, ship .env.example, and never commit credentials.
Store all data locally by default and make CSV export straightforward.
Include clear empty, loading, success, and recoverable error states in a plain server-rendered run dashboard.
Write focused tests for retrieval, one tool call, and one end-to-end happy path.
Create a README with setup, the agent config schema, how to add a tool, data location, and cost notes.
Do not add accounts, billing, telemetry, a visual builder, or a connector marketplace.
Deliberately leave out multi-tenant workspaces and team permissions.
Deliberately leave out one-click OAuth for dozens of third-party apps.
Finish by running the tests and listing the exact commands used.