This is a follow-up on the Kestrel 75 site in this folder. A recorded watch-through and an earlier review found six problems. Fix only these six, change nothing else, and keep the design, sections and colourways as they are.

1. Switches section: the heading, body text and spec numbers (Actuation, Pre-travel, Total travel, "Last key") sit on top of the close-up 3D keyboard and are hard to read, especially where the raised white spacebar runs behind the text. Make the text fully readable at 1440x900 and at 390x844. For example, frame the camera so the model keeps clear of the text column, or give the text a solid panel. It must stay readable while scrolling into and out of the section, in both directions.
2. Build section explode labels (Keycaps, Switches, Plate, PCB, Case): at the start and end of the explode they bunch up in a stack at the bottom right of the keyboard. Each label must track its own layer for the whole explode and reassembly, never overlap another label, and fade in only once its layer has separated.
3. Keypress: pressing a key on the real keyboard presses the matching 3D cap, but the 4 mm travel is barely visible at hero scale. Make a press clearly visible to a viewer in the hero, for example with deeper visual travel plus a short accent glow or highlight on the pressed cap, and keep it physically plausible.

4. Key legends: some keycap legends are cramped or run to the edge of the cap. Size and place every legend so it sits clear inside its cap and stays readable in the hero and Customize views.
5. Switches contrast: the Switches section text, including the spec labels like "45 g", has weak contrast against the background. Bring all text in that section to at least WCAG AA contrast in all three colourways.
6. Phone navigation: at 390x844 the nav links are hidden and only the button shows. Give phones a working, accessible way to reach Build, Switches, Customize and Specs. Also make sure no section heading ends up underneath the 3D stage on a phone.

Before you finish, check each of the six fixes yourself at 1440x900 and 390x844, scrolling down and back up.

Then run `npm run build` and make sure it passes cleanly. Don't start a dev server and don't deploy. Write a short README.md covering how to run it, what was fixed in this pass, and what is still not done. Be honest.