Perihelion

Use Plate's Perihelion, project perihelion, version 1.0.1, as the starting point.
Requested result: [my project name].
My changes: [describe the changes before beginning]
Before you edit anything, ask me for the project name and the changes I want. Do not invent a brand, a client, copy or a result.

Scope: Complete single-page website.
Use the existing source and assets. Read its README and licence notices first. Preserve unrelated work and make changes in a separate project folder.
The project is a Plate Pro pack. Download it from the Plate library (https://getplate.pages.dev/library.html?project=perihelion, "Download source") while signed in to Plate with Pro; the file comes from https://getplate.pages.dev/api/pack?slug=perihelion and only with Pro. If you cannot sign in, tell me and I will download the ZIP and put it in your workspace myself.
Verify SHA-256: a66a771b0590a7d037f8697fe31582c76a63c500bdb4ee0393be30d750c8ea73 (1059145 bytes, version 1.0.1). Extract into a new folder and follow its README to run it.
Make content changes in content.js as EDITING.md describes; the supported changes below live there. Do not rewrite the renderer or the layout to make a content change.

Supported changes:
- Studio name, tagline, mark (inline SVG), edition line and year — content.js identity
- Six colour tokens (bg, ink, accent, hot, magenta, teal) — content.js colors; all HUD, cards, arcs, plaque, reticle, favicon follow
- Two fonts (display, text): family, WOFF2 file, weight/range, fallback — content.js fonts
- Page title, description, lang, robots — content.js meta
- Every HUD label and unit; the accessible names of the regions — content.js hud
- The names of the four bodies (reticle labels, HUD target) — content.js bodies
- The five chapters: anchor id, nav label, HUD name, code, coords, title, lede, body, tags, plaque map label
- The ending copy; the manifest (six fixed columns, any number of rows, five status colours, optional price per row shown as its own column and always on phones)
- The booking action: email, subject, prefilled body, labels; the download: filename and labels
- The plaque: title, entries, diagram labels, scale text, end line; the flight-log strings

Requirements:
- Static HTTP hosting (no server code, no build); does not run from file://
- WebGL2 for the live flight (Chrome/Edge 56+, Firefox 51+, Safari 15+, iOS 15+); still plates without it
- A GPU that renders the scene at 0.66x canvas under 14 ms, else the site drops to 0.5x on its own
- Verified: Chromium 1440x900 and 390x844, RTX 3070 via ANGLE D3D11; Safari/Firefox paths written, not run

Limits:
- Adding, removing or reordering chapters (five holds on a baked flight path)
- Changing what is rendered — planet, rings, nebula, black hole, disc colours, stars, sun (GLSL in space.js)
- Changing the flight path, hold positions, exposure/velocity profiles (main.js KEYS/SC)
- A light theme (the glass and the render assume a dark ground)
- Layout, type sizes, breakpoints, HUD geometry (style.css)
- Video, photographs, textures or a CMS; server-rendered copy for SEO (copy mounts from content.js at load)

Run the whole website. Inspect the opening, middle and ending on desktop and phone. Check the actual motion, navigation, reduced motion and missing-media recovery.
Deliver the edited source, actual preview or render, exact start commands and any remaining limitations. Do not purchase services, invent claims, post or deploy without my instruction.