[DevomB]

Summary

A full redesign of the landing page, built around the real training run instead of marketing copy. It also brings the play-in-the-browser work to main: #2 merged into the v3 branch after that branch had already been merged, so those two commits never reached main. They're the first two commits here, unchanged.

What's on the page now

• New look. Warm paper, ink and a vermilion accent instead of the generic dark purple template. Bricolage Grotesque, Instrument Serif and JetBrains Mono are self-hosted (OFL, licenses in web/fonts/). The wooden board is drawn on canvas, with shaded stones that drop into place and captures that fade out.
• Hero. Replays Gofer's win over GNU Go level 10 with Gofer's own analysis of every position: candidate moves with their share of the search, a live win estimate, and whether GNU Go played the move Gofer expected.
• 01 How it learns. The self-play → train → evaluate loop, with a self-play game running live, the policy loss falling from 4.41 to 2.39, and generation 16's results as win/loss tallies.
• 02 Watch it learn. Scrub through all 18 networks with a slider, the chart or thumbnails. For each one you see a self-play game it played, its raw opening policy before any search (uniform at gen 0, structured by gen 17), its Elo with GNU Go and rollout anchors, and its match results, including the dips at gens 9 and 14. The section sweeps from gen 0 to gen 17 the first time it scrolls into view.
• 03 Play. The WebAssembly engine, with Gofer's candidate moves drawn live on the board while it thinks. You can start a game from the board itself on phones.
• 04 Under the hood. A spec sheet with measured numbers, replayed terminal sessions, and a quick start with a copy button.

Every number comes from the run: cmd/sitedata writes web/data/*.json from a run directory (make site-data RUN=…). The hero game is committed as docs/results/games/gnugo-l10-vs-gofer.sgf.

Engine fix: the page froze while Gofer thought

The in-browser search ran on the page's only thread and never yielded, so the page froze for the whole search: about 1 s at 400 visits and 4.5 s at 1600. No progress or candidates showed, and scrolling stopped. The search now yields every 16 visits, so the page runs at 24–28 fps while Gofer thinks, at a cost of about 16% search time. Because of that yield, "New game" or "Undo" could arrive mid-search, so a reset now cancels the running search instead of letting it play into the next game.

Housekeeping

• Tailwind is removed (web/src/, tailwind.config.js). The page is plain HTML, CSS and JS, and make site only rebuilds the WebAssembly engine and copies the model.
• CI now vets with the onnx build tag (covers cmd/sitedata) and checks that the site scripts and data parse.
• New icons and social image. README and CHANGELOG updated.

Test plan

• go test -short ./...; go vet ./..., -tags onnx, and GOOS=js GOARCH=wasm; gofmt; node --check
• Headless Chromium play flow against the real engine, with onnxruntime-web 1.26.0 served from the pinned npm package:
  • starts from the board overlay
  • page stays responsive mid-search (progress and candidates update)
  • an occupied point is rejected
  • "New game" during a search starts clean and gets exactly one reply
  • undo works
  • White with Gofer opening works
  • passes end the game with a result
  • no page errors
• Frame rate during search: 0 fps before this change, 24–28 fps after
• Full-page screenshots at 1440 px and 390 px; no horizontal scroll at 320, 390, 768, 1024 or 1440 px; 25 s of the animated hero with no errors; reduced motion shows final states
• Look at the Vercel preview on a real phone and desktop

---

Generated by Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
gofer	Ready	Preview	Oct 23, 2026 5:53pm UTC