website: vercel project config

Created and linked the `fnstools` project under functionstore1s-projects.

vercel.json loses its `//` comment block -- Vercel's schema rejects
unknown keys outright, so the deploy failed schema verification. The
rationale moved to the README, which is the only place it can live.

.vercelignore is the load-bearing addition: the deploy root is website/,
so the CLI never reads the repo-root .gitignore, and without it the
upload carries node_modules -- 61 MB instead of 1.8 MB. It also drops
tools/ (build and CMS scripts, never served) and .env.local, which the
CLI writes on link with a VERCEL_OIDC_TOKEN inside.

The CLI's own .gitignore and .vercel/ are ignored so neither the token
nor per-machine link state can be committed.

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

Author: function-store

.gitignore

@@ -81,3 +81,6 @@ packaging/publish/
 
 # website deps. website/docs/ IS committed -- Vercel serves it with no build step.
 website/node_modules/
+
+# vercel CLI link state (per-machine)
+.vercel/

website/.gitignore

@@ -0,0 +1,2 @@
+.vercel
+.env*

website/.vercelignore

@@ -0,0 +1,21 @@
+# The deploy is a static upload of this directory — see vercel.json, which
+# sets an empty build and install command. Nothing here is needed at runtime
+# except the pages, assets and the search index under docs/.
+#
+# Without this file the CLI would ship node_modules (~60 MB, pagefind's
+# binaries included): the repo .gitignore covers it, but it lives at the repo
+# root and the deploy root is website/, so the CLI never reads it.
+
+node_modules/
+package.json
+package-lock.json
+
+# build + CMS tooling; never served
+tools/
+
+# local scratch and CLI state. .env.local holds a VERCEL_OIDC_TOKEN the CLI
+# writes on link — git ignores it, and it has no business being uploaded.
+.DS_Store
+*.log
+.env*
+.vercel/

website/README.md

@@ -143,11 +143,21 @@ video: "https://youtu.be/j43gZ0MB2xo"
 
 ## Deploying
 
-Vercel project, **root directory `website`**. `vercel.json` declares
-`buildCommand` and `installCommand` as empty on purpose: `website/docs/` is
-generated and committed, so a deploy is a pure static upload. Without those,
-Vercel auto-detects the `build` script in `package.json` and runs pagefind at
-deploy time for nothing.
+Vercel project **`fnstools`**, root directory **`website`**.
+
+`vercel.json` declares `buildCommand` and `installCommand` as empty on
+purpose: `website/docs/` is generated and committed, so a deploy is a pure
+static upload. Without those, Vercel auto-detects the `build` script in
+`package.json` and runs pagefind at deploy time for nothing. (The file
+cannot carry comments — Vercel's schema rejects unknown keys, `//`
+included.)
+
+`.vercelignore` keeps `node_modules/` out of the upload: the repo
+`.gitignore` covers it, but it lives at the repo root while the deploy root
+is `website/`, so the CLI never reads it. That is the difference between a
+1.8 MB upload and a 61 MB one. It also excludes `tools/` (build and CMS
+scripts, never served) and `.env.local`, which the CLI writes on link with a
+`VERCEL_OIDC_TOKEN` in it.
 
 To stand it up before this branch is merged, point the project at this branch
 as its production branch, then switch it to the real one after the merge.

website/vercel.json

@@ -1,23 +1,11 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
-
-  "//": [
-    "Vercel project root directory must be `website`.",
-    "",
-    "Deploys are a pure static upload: website/docs/ is generated and",
-    "committed, so there is nothing to build here. The empty build and",
-    "install commands are load-bearing -- package.json has a `build`",
-    "script, and without these Vercel auto-detects it and runs pagefind",
-    "at deploy time for no reason. CI is where the build is verified."
-  ],
   "framework": null,
   "buildCommand": "",
   "installCommand": "",
   "outputDirectory": ".",
-
   "cleanUrls": true,
   "trailingSlash": true,
-
   "headers": [
     {
       "source": "/docs/pagefind/(.*)",