Overture website update

AGENTS.md

@@ -16,6 +16,16 @@ The canonical task→convention dispatch table lives in `~/.claude/agentics/temp
 ## Project context
 Overture Docs is the **centralized documentation site for the Overture stack**, built with [Docusaurus](https://docusaurus.io/). It aggregates Markdown from the `/docs` directory of each Overture project repository (pulled in as git submodules) and renders them as one navigable site. The point of the setup is that documentation stays with its source project while readers get a single hub. Full overview in [README.md](README.md); planned work lives in `.dev/roadmap.md`.
 
+## Verifying a UI change
+
+A clean `npm run build` says a page compiled, not that it looks right. Before calling any visual change done, render it and look at it.
+
+- Build and serve: `cd website && npm run build && npm run serve --port <port>`. `npm start` renders in the browser, so its HTML is an empty shell and tells you nothing.
+- Screenshot with a real browser at a real viewport. Chrome's `--headless --screenshot --window-size` is unreliable: the window size is not the CSS viewport, and it will show you clipping and overflow that do not exist. Drive it with `puppeteer-core` and `page.setViewport` instead, pointing `executablePath` at the installed Chrome. Install it outside this repo (the scratchpad), never as a dependency here.
+- Check the widths that change behaviour, not just the one you are working at. The marketing navbar collapses at 1160px.
+- When something looks wrong, measure it in the page (`getComputedStyle`, `getBoundingClientRect`, `scrollWidth` against `clientWidth`) before changing CSS. Reading a screenshot is guessing.
+- Check a documentation page too whenever marketing styles or theme components change, since both sites share one build.
+
 ## Project-specific constraints
 - **Public repository** (`overture-stack/docs`): no credentials, secrets, tokens, or private URLs in any committed file, ever.
 - **Documentation content is owned by the submodules, not this repo.** Each project's docs live in `submodules/<project>/docs/` and are symlinked into `website/docs/`. Edit the **source** file under `submodules/<project>/`, never the symlinked copy under `website/docs/`: editing through the link mutates the vendored submodule's working tree in a way that is easy to lose and confusing to review. Symlinks are (re)generated by `symlinker.sh`.
@@ -24,7 +34,10 @@ Overture Docs is the **centralized documentation site for the Overture stack**,
 
 ## Repository orientation
 - `submodules/` — vendored Overture repos as git submodules: `arranger`, `lectern`, `lyric`, `maestro`, `score`, `song`, `stage`, and `.github`. Each carries its own `/docs`. Defined in `.gitmodules` (see `.dev/roadmap.md`: release-branch tracking is not yet configured, so `git submodule update --remote` currently follows each repo's default branch).
-- `website/` — the Docusaurus site: `docs/` (aggregated, symlinked from submodules), `community/`, `guides/`, and `src/` (`components/`, `css/`, `theme/`, `pages/`).
+- `website/` — the Docusaurus site: `docs/` (aggregated, symlinked from submodules), `community/`, `guides/`, and `src/` (`components/`, `css/`, `marketing/`, `theme/`, `pages/`).
+- `website/src/marketing/`: the overture.bio marketing pages ported from the Gatsby site: components, constants, case-study data, and the Sass tree. Its styles are all imported inside `.marketing` by `styles/index.scss`, and only `MarketingPage.tsx` imports that file, which is what keeps Bulma off the documentation pages in the same build. Add marketing styles as a partial imported there, never as a stray `import "./styles.scss"` in a component.
 - `symlinker.sh` — regenerates the symlinks that bring selected submodule `/docs` files into `website/docs/`.
+- `website/netlify/` — configuration staged for stage 3 of the overture.bio port, not read by anything today. This repo has no live `netlify.toml`: `docs.overture.bio` is configured through the Netlify UI, and committing one would move that configuration out from under a working site. See the README in that directory before adding anything to it.
+- `website-legacy/` is **gone** as of 2026-08-07. It was a staged copy of the [overture-stack/website](https://github.com/overture-stack/website) Gatsby site, kept while the port ran. Everything it held is either ported into `website/` or still in that repo, which is what serves overture.bio until stage 3 and is cloned locally at `~/Desktop/website`. Changes that need to reach the live site go there, not here.
 - `README.md`, `preview.png` — human-facing project overview and screenshot.
 - Local setup: Node 18+, `npm ci`, then `npm start` (see `README.md` § Getting Started).