feat: scaffold outreach engine monorepo on the novelpad-desktop stack

Workspaces: config (copied), outreach-core (schema + actions/queries +
hard gates), outreach-ai (Gemini client + embeddings copies, profiler and
mission-fit-judge agent stubs), outreach-worker (DBOS executor with
nightly ingest + hourly expiry workflows), outreach-review (RR7 review
queue v0). Initial drizzle migration incl. pgvector extension.

Stack contract: Yarn 4.5.0 + Turbo, Node 22.16, Drizzle 0.44.6 +
pgvector, DBOS 4.17.6, @google/genai on Vertex, gemini-embedding-001
@1536, React Router v7. Files copied from novelpad-desktop carry
provenance headers @ 62c56b87.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

README.md

@@ -0,0 +1,40 @@
+# HelmDocs Grant-Match Outreach Engine
+
+Automated pipeline that matches open grants to NH nonprofits, then runs a personalized email drip whose success metric is a booked demo call. The grant match **is** the lead magnet — match accuracy is the prime engineering directive.
+
+Architecture doc: `docs/plan.md`. Build plan and phase status: `~/.claude/plans/helmdocs-outreach.md`.
+
+## Relationship to novelpad-desktop
+
+This repo deliberately mirrors the [novelpad-desktop](https://gitea.stephenmann.io/NovelPad/novelpad-desktop) stack so a future merge is a directory move, not a rewrite:
+
+- Yarn 4.5.0 + Turbo monorepo, Node 22.16 (volta), TypeScript ^5.9.3
+- Postgres + pgvector + Drizzle (0.44.6, pinned via `resolutions`), actions/queries pattern
+- DBOS for durable jobs/cron (worker-app pattern)
+- `@google/genai` on Vertex; embeddings `gemini-embedding-001` @ 1536 dims (identical to HelmDocs RAG — never mix embedding models)
+- React Router v7 for the review UI
+
+**Merge rules**: all packages stay in the `@novelpad/` scope with names that never collide with novelpad-desktop workspaces (`outreach-*`). Files copied from novelpad-desktop carry a provenance header (`source path @ commit`) — diff against origin at merge time. No live code sharing; drift is fixed at merge, by design.
+
+**Boundary**: separate repo and separate Postgres on purpose — outreach tooling and sourced contact data stay outside the compliance-scoped product repo/DB.
+
+## Workspaces
+
+| Workspace | Purpose |
+|---|---|
+| `packages/config` | Shared tsconfig/tailwind base (copied from novelpad-desktop) |
+| `packages/outreach-core` | Drizzle schema (grants, orgs, profiles, contacts, matches, pipeline_events), actions/queries, hard gates |
+| `packages/outreach-ai` | Gemini client, embeddings, org-profiler + mission-fit-judge agents |
+| `apps/outreach-worker` | DBOS executor: ingestion crons, expiry sweep, scoring runs, Apollo sync |
+| `apps/outreach-review` | Human review queue (RR7). No auth by design — run behind IAP/localhost |
+
+## Development
+
+```
+yarn install
+yarn build
+yarn typecheck
+yarn test
+```
+
+Migrations: `yarn create:migration <name>` inside `packages/outreach-core` (server-only — no client DB in this repo).