From 0ff6457cae599f5e2543d3f3fde9f48b2e3f3635 Mon Sep 17 00:00:00 2001 From: istos Date: Fri, 31 Jul 2026 11:49:09 +0200 Subject: [PATCH] =?UTF-8?q?board:=2032=20=E2=86=92=20review=20(istos)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...serve-bench-12vectors-com-from-a-worker.md | 25 ++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) rename tasks/{in-progress => review}/32-serve-bench-12vectors-com-from-a-worker.md (54%) diff --git a/tasks/in-progress/32-serve-bench-12vectors-com-from-a-worker.md b/tasks/review/32-serve-bench-12vectors-com-from-a-worker.md similarity index 54% rename from tasks/in-progress/32-serve-bench-12vectors-com-from-a-worker.md rename to tasks/review/32-serve-bench-12vectors-com-from-a-worker.md index cfa85a0..f384e4b 100644 --- a/tasks/in-progress/32-serve-bench-12vectors-com-from-a-worker.md +++ b/tasks/review/32-serve-bench-12vectors-com-from-a-worker.md @@ -1,6 +1,6 @@ # 32 — Serve bench.12vectors.com from a Cloudflare Worker -**Status:** In Progress +**Status:** Review **Assignee:** istos **Priority:** High — the site is not a site until it has an address **Type:** Feature @@ -81,3 +81,26 @@ domain is wired to. **Risks** — a custom domain on Workers takes the hostname over at the zone level. Do it knowing nothing else answers on `bench.12vectors.com` today. + + +--- + +## Work report — 2026-07-31 11:49 (Ada) + +four" — they are acceptance criteria 1, 2 and 4, and they are the ones no test in this repo can reach. +3. **Replace the account line** in `site/README.md`'s "Where the site lives" table with what `wrangler whoami` prints. I described the account by its defining property (the one holding the `12vectors.com` zone) rather than inventing a name or ID. +4. **Open the follow-up card** for a GitHub Action on merge, if you still want one. + +## What to know + +The card's open question carried the author's own recommendation — manual deploy for v1 — so I built that rather than sending the card back: `site/wrangler.jsonc` and a documented command sequence, no workflow file, no Cloudflare token in repository secrets. + +Serving the site needed three things from the builder first, which is the first commit (`ad639a3`): + +- **A real 404.** Cloudflare's `not_found_handling: "404-page"` wants a literal `404.html` at the root of the assets directory, so a manifest route may now name an `.html` file instead of ending in `/`. `/404.html` is a normal entry with a new `notfound` layout — the site's design and nav, a link back to the landing page, `noindex`, no canonical, and a `null` section that keeps it off the nav it renders. +- **`site/root/`**, copied verbatim to the top of the build the way `static/` is copied into a subdirectory. It holds `_headers`, which the host reads from the root and nowhere else. A file in `root/` that a route would also write stops the build. +- **Fingerprinted asset urls.** The templates link the stylesheet and icon through `$stylesheet`/`$icon`, carrying `?v=` of the file's contents. Nothing in `static/` is renamed, so the tree and the `/static/*` glob are unchanged — but the url moves when the file does, which is what makes the year-long `immutable` cache safe rather than a way to ship an invisible deploy. + +Two judgement calls worth a look. I added a `default-src 'none'` **Content-Security-Policy** to `site/root/_headers` beyond the three headers the card named: it turns "no analytics, no third-party anything" into something the browser enforces, and a test asserts no built page contains an inline `