fix website build issue

[adamavenir]

…ated having run first

[Copilot]

Pull request overview

Updates the GitHub Pages deployment workflow to ensure the documentation site build has all required project artifacts available during CI.

Changes:

• Renames the website build step for clarity.
• Adds root-level dependency install and project build steps to generate required artifacts.
• Adds an explicit LLM docs build step prior to copying llms*.txt outputs into the deployed site root.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

npm run build (root) already runs npm run build:docs as part of the build pipeline (see scripts/build-quiet.js). Running npm run build:docs again here is redundant and increases CI time; consider removing this step, or alternatively replace npm run build with a narrower set of commands if the intent is to only generate LLM docs for Pages.

Suggested change

	- name: Build llms docs
	run: npm run build:docs

[Copilot]

This workflow now runs both npm ci in website/ and npm ci at the repo root, but actions/setup-node caching is keyed only off website/package-lock.json. To avoid unnecessary cache misses and keep caching aligned with both installs, update the node cache key to include the root package-lock.json as well (or remove cache-dependency-path if you want the default behavior).