Add a fixed-scope Patchworks setup offer

[nahtnam]

What changed

• add a fixed-scope $750 founding setup page for one template, one new project, and two consecutive update PRs
• define prerequisites, exclusions, delivery timing, refund condition, credential handling, and the customer's merge responsibility
• add a read-only fit-check email CTA without activating billing
• link the offer from the docs navigation, homepage, Getting Started page, root README, and published-package README
• add a patch Changeset so the npm README can pick up the service path in a future separately approved release

Why

Patchworks 0.1.4 is already released and technically hardened. The next useful proof is commercial: one paid external setup whose first two updates succeed without history repair, branch deletion, or hand-editing Patchworks state. Downloads and existing internal consumers do not establish buyer demand.

Evidence boundary

This PR stages the offer only. It does not activate checkout or billing, invoice anyone, contact a prospect, access a consumer repository, merge changes, promote production, or publish npm. The repository's existing Vercel integration automatically created a preview deployment for this PR; production remains on e68b500. Paid validation remains unproven until one external customer pays and the two-cycle acceptance result is recorded.

Checks

• bun run --cwd docs typecheck (Bun 1.3.14)
• focused Oxlint on the two changed TSX files
• bun run changeset status
• git diff --check
• GitHub CI checks and Package artifacts (Node 18) passed on 3556ca1
• the Vercel preview returned HTTP 200 with the expected title, price, fit-check CTA, and one setup-page sidebar link

Visual browser verification was not requested or performed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
patchworks	Ready	Preview	Aug 12, 2026 9:50am