@@ -22,25 +22,23 @@ immutable `<commit>.site.tar.gz` containing only the two PNG figures,
 artifact retention. `combined_report`, containing `report.pb`, remains a CI
 artifact for decomp.dev.
 
-`docs.yml` runs after successful CI and dispatches `alchemy-docs` with the
-exact source commit, CI run ID and generator revision from `docs.ref`.
-`alchemy-docs` verifies them, builds Doxygen and the fonts, and owns the Pages
-deployment at <https://pascalpixel.github.io/alchemy-docs/>. Changes to that
-repository run build checks; publication waits for a successful Alchemy CI.
-There is no schedule and no generated Git branch. Both repositories reject
-superseded source revisions before publication; Pages keeps the last
-successful deployment on failure.
+`docs.yml` runs after successful CI on main, refuses a superseded revision and
+starts the site build through the Vercel deploy hook in the `VERCEL_DEPLOY_HOOK`
+secret. Vercel builds `alchemy-docs` at its main branch: it clones Alchemy's
+main, generates the pages from the source and takes the accepted figures from
+the release, then serves them at <https://alchemy.pascalpixel.com/>, where
+README shows the figures. A push to `alchemy-docs` builds the same way. There
+is no schedule and no generated Git branch; Vercel keeps the last successful
+deployment on failure.
 
 ## Setup and recovery
 
-Alchemy's `ALCHEMY_DOCS_TOKEN` secret is a fine-grained GitHub token restricted
-to `PascalPixel/alchemy-docs`, with **Actions: read and write** permission.
-It dispatches a workflow; Pages uses alchemy-docs' own short-lived token.
-Renew the secret before its chosen expiration. Configure Pages in
-alchemy-docs to build with GitHub Actions.
+The `VERCEL_DEPLOY_HOOK` secret is the URL of a deploy hook on the `alchemy`
+Vercel project for branch `main`; anyone holding it can start a build, nothing
+more. To replace it, create a new hook with `vercel deploy-hooks create`,
+store its URL in the secret and remove the old hook.
 
-To publish a generator change, verify and push it in alchemy-docs, update
-`docs.ref` here to its full commit SHA, then make a normal verified landing.
+A generator change publishes when it is pushed to `alchemy-docs`.
 To retry publication, rerun the failed job. The `Publish docs` workflow also
 accepts the ID of a successful main CI run; it refuses a superseded revision.
 If the build fails before reports are archived, fix the build first.
 
@@ -17,11 +17,11 @@ permissions:
   contents: read
 
 concurrency:
-  group: docs-dispatch
+  group: docs-deploy
   cancel-in-progress: false
 
 jobs:
-  dispatch:
+  deploy:
     if: >-
       github.repository == 'PascalPixel/alchemy' &&
       (github.event_name == 'workflow_dispatch' ||
@@ -41,29 +41,16 @@ jobs:
           jq -e '.path == ".github/workflows/build.yml" and .head_branch == "main" and .conclusion == "success" and (.event == "push" or .event == "workflow_dispatch") and .head_repository.full_name == "PascalPixel/alchemy"' "$RUNNER_TEMP/run.json"
           source=$(jq -r .head_sha "$RUNNER_TEMP/run.json")
           latest=$(gh api repos/PascalPixel/alchemy/commits/main --jq .sha)
-          echo "sha=$source" >> "$GITHUB_OUTPUT"
-          echo "run=$RUN_ID" >> "$GITHUB_OUTPUT"
           if test "$source" = "$latest"; then
             echo "current=true" >> "$GITHUB_OUTPUT"
           else
             echo "Skipping a superseded source revision."
           fi
 
-      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
-        if: steps.source.outputs.current == 'true'
-        with:
-          ref: ${{ steps.source.outputs.sha }}
-          persist-credentials: false
-
-      - name: Trigger the pinned docs generator in its own repository
+      - name: Start the site build on Vercel
         if: steps.source.outputs.current == 'true'
         env:
-          GH_TOKEN: ${{ secrets.ALCHEMY_DOCS_TOKEN }}
-          SOURCE_SHA: ${{ steps.source.outputs.sha }}
-          SOURCE_RUN: ${{ steps.source.outputs.run }}
+          HOOK: ${{ secrets.VERCEL_DEPLOY_HOOK }}
         run: |
-          test -n "$GH_TOKEN" || { echo 'Set ALCHEMY_DOCS_TOKEN: a fine-grained token for alchemy-docs with Actions write permission.' >&2; exit 1; }
-          docs=$(cat .github/docs.ref)
-          [[ "$docs" =~ ^[0-9a-f]{40}$ ]]
-          gh workflow run pages.yml --repo PascalPixel/alchemy-docs --ref main \
-            -f alchemy_commit="$SOURCE_SHA" -f alchemy_run="$SOURCE_RUN" -f docs_commit="$docs"
+          test -n "$HOOK" || { echo 'Set VERCEL_DEPLOY_HOOK: the deploy hook of the alchemy Vercel project.' >&2; exit 1; }
+          curl --fail --silent --show-error --request POST "$HOOK"
@@ -70,7 +70,7 @@ Never: commit or publish a ROM or game files (L1); use another project's Golden
 
 - **C1** A function counts only when its whole extent, literal pool included, compiles exactly and every edition stays byte-identical, and in an edition only when that edition links its C. _Check: make compare-editions._
 - **C2** DONE is pret's calcrom over the linker maps, by folder: bytes placed from `games/` are done, from `recon/` not yet. Each image counts from its first to its last placed byte (overlays once, unpacked). Code is `.text` (C, assembly, 8-byte stubs and the compiler library reported apart); data is everything else. A game's figure sums its six editions; 100% needs both at 100% in all six.
-- **C3** Every push to main carries its measurement: stage all source changes, then `make land` compares, tests and measures the same tree; the pre-push hook uploads immutable reports and their timestamped receipt to `decomp-reports`. After the public build passes, CI validates the receipt, archives the figures and accepts the measurement. Successful CI triggers the pinned `alchemy-docs` generator, which owns Pages and README's figures. The old `progress` branch is a frozen archive, never updated. `.github/publication.md` describes publication and recovery.
+- **C3** Every push to main carries its measurement: stage all source changes, then `make land` compares, tests and measures the same tree; the pre-push hook uploads immutable reports and their timestamped receipt to `decomp-reports`. After the public build passes, CI validates the receipt, archives the figures and accepts the measurement. Successful CI starts the `alchemy-docs` site build on Vercel through a deploy hook; that site serves the docs and README's figures. The old `progress` branch is a frozen archive, never updated. `.github/publication.md` describes publication and recovery.
 
 ### The oracle stays out of the build
 
@@ -103,7 +103,7 @@ The reference ROM judges the build and never feeds it. Reconstructing Camelot's
     - A trailing note on any declaration (a field, enumerator, table column, macro or global) is `///<`, its continuation lines too.
     - FAKEMATCH tags, `// BUG:`, `// DEAD:` and comments inside function bodies stay as they are: they describe matching, not the interface. So do a block a blank line separates from what follows, a section heading or label over a run of declarations, a comment above `#if` or `#include`, and `// clang-format off` and `on`, which clang-format reads only in that form.
     - A folder's README.md is its page: it opens with a `#` heading unique across the repository that names the folder (`# Battle effects`), with a `{#label}` only where something links to it. Links between READMEs and code use relative paths and plain function names.
-    - Doxygen's settings live with the docs tooling, never as markup in the source beyond these.
+    - The docs site's settings live in `alchemy-docs`, never as markup in the source beyond these.
   - Formatting: clang-format's LLVM style, as `.clang-format` records it; include order is left alone, since it decides which declarations are in scope.
   - Numbers stay numbers until evidence gives them a meaning; a constant never invents an address or table id. Messages are linker symbols written by bare name, `MSGNO(name)` their number. Flags and sounds come from `flags.h` and `songs.h`: `FLAG_`, `MUS_`, `SE_`, only proven names, an unproven sound its kind and number (`SE_138`); a temporary flag is `FLAG_SCENE_TEMP_xx` with a comment per scene.
   - Values are in the author's units (scene coordinates in pixels). Scenes are written in `event.h` commands.
 
@@ -23,12 +23,12 @@ Alchemy is a hobby project I started in July 2026 to enjoy making things again a
 - **The Broken Seal** builds entirely from this repository, in all six languages. No ROM needed.
 - **The Lost Age** builds too and is well on its way. The parts not yet rewritten still come from your own cartridge dump.
 
-<img src="https://pascalpixel.github.io/alchemy-docs/PROGRESS_CHART.png" width="838" alt="How much of each game's code and data is rebuilt, day by day since 16 July 2026" />
-<img src="https://pascalpixel.github.io/alchemy-docs/PROGRESS.png" width="838" alt="A map of the project's files by size" />
+<img src="https://alchemy.pascalpixel.com/PROGRESS_CHART.png" width="838" alt="How much of each game's code and data is rebuilt, day by day since 16 July 2026" />
+<img src="https://alchemy.pascalpixel.com/PROGRESS.png" width="838" alt="A map of the project's files by size" />
 
 ## Try it
 
-[Read the documentation](https://pascalpixel.github.io/alchemy-docs/) to browse the games' code and folder guides.
+[Read the documentation](https://alchemy.pascalpixel.com/) to browse the games' code and folder guides.
 
 [INSTALL.md](INSTALL.md) has the few commands to build it on Linux, macOS or Windows. Anyone with their own cartridges can check the result against these hashes: