V1 interest list — homepage subscribe form, Pages Function, D1

[unforced]

Closes #25.

Replaces Substack as the entry point with a direct subscribe path on parachute.computer. Email captures from the homepage POST to a Cloudflare Pages Function that writes to D1.

What's in the PR

• functions/api/subscribe.ts — Pages Function. POST handler, validates email (lowercase + trim, basic regex, 254-char cap), captures source_path from Referer, inserts into D1, returns a 303 redirect to /subscribe/thanks/. Bounces back to /?subscribe_error=1 on validation/insert failure (a tiny inline script on index.njk toggles a discreet error message). No Resend, no de-dup, no admin UI — V2 territory.
• migrations/0001_interests.sql — interests table. Matches LVB's post-feat(site): /deploy/render/ page + homepage surface (closes #42) #44 schema; user_id and resend_contact_id are reserved (NULL in V1) so V2/V3 don't need a migration.
• wrangler.toml — [[d1_databases]] binding (DB), pages_build_output_dir = "_site", compatibility_flags = ["nodejs_compat"]. database_id is a PLACEHOLDER that Aaron fills in after wrangler d1 create.
• index.njk — inline subscribe section sits between the Notes aside and the Principles row. Mirrors the hero rhythm: serif lead heading, muted palette, accent-green button. Plain browser POST → 303 redirect, no JS for the happy path.
• subscribe/thanks.njk — success page extending _includes/base.njk.
• CLAUDE.md — new "Interest list / backend" section documenting the new pieces.
• INFRASTRUCTURE.md — step-by-step CF setup for Aaron (project create, D1 create, migration apply, binding, DNS swap, GH Pages workflow archive).
• eleventy.config.js — ignores functions/, migrations/, wrangler.toml, INFRASTRUCTURE.md so the static build doesn't try to copy or template them.
• package.json — adds wrangler + @cloudflare/workers-types as devDeps; adds dev:pages, db:migrate:local, db:migrate:remote scripts.

Worth a closer look

• Form placement — went between the Notes aside and Principles row (rather than directly under the hero) so the page still leads with the value prop and product story. The issue said "below the value prop" — happy to move it higher into the hero column if you'd rather.
• No de-dup is intentional — matches LVB/RegenHub V1, preserves return-visit signal. Easy to add a UNIQUE on email later if it becomes noise.
• Error handling — homepage shows a quiet "that didn't go through" line via inline JS reading ?subscribe_error=1. The form itself uses native required + type="email" validation so most bad inputs never POST.
• Substack link on /blog/ — left untouched in this PR (blog/index.njk still says "Subscribe on Substack"). Updating that link to point at the new subscribe section is a small but separate change; happy to do as a follow-up so this PR stays one-concern.

Build sanity

npx @11ty/eleventy builds cleanly. _site/index.html contains the form posting to /api/subscribe; _site/subscribe/thanks/index.html exists; backend files are not copied into the static output.

What's left for Aaron

(See INFRASTRUCTURE.md for the full version.)

1. Create the Cloudflare Pages project, point at this repo, build = npx @11ty/eleventy, output = _site.
2. wrangler d1 create parachute-db → paste the database_id into wrangler.toml and push.
3. wrangler d1 migrations apply parachute-db --remote to create the interests table (pause-and-confirm prompt).
4. Bind D1 → DB to the Pages project in the dashboard (production scope).
5. Custom domain parachute.computer on Pages → DNS swap from GitHub Pages.
6. Disable / delete .github/workflows/deploy.yml once CF deploys are healthy.
7. Smoke-test: submit a real email, confirm row in D1.

🤖 Generated with Claude Code