fix: synchronize responsive navigation and soundtrack cue

docs/reviews/visual-qa.md

@@ -51,7 +51,7 @@ Focused evidence is generated by:
 npm run test:browser -- tests/browser/visual-regression.spec.ts
 ```
 
-The final 2026-09-02 complete browser run passed 165 checks with 43 deliberate project/capability skips and no failures. The 16 visual checks ran once in the available current Chromium project; the duplicate mobile-project visual cases were skipped intentionally.
+The final 2026-09-02 complete browser run passed 169 checks with 43 deliberate project/capability skips and no failures. The 16 visual checks ran once in the available current Chromium project; the duplicate mobile-project visual cases were skipped intentionally.
 
 The compact 320×568 capture initially revealed that the fixed drive controls occupied 43.5% of the viewport and obscured the opening content. The mobile-only control grid reduced that surface to 24.0%; a regression guard now caps it at 34%. After the trace-driven fixed section navigation landed, the captures exposed the decorative HUD intersecting the navigation at phone widths and the controls at 768×1024. A shared exact navigation-height variable now keeps the fixed navigation and visible compact HUD edge-adjacent, reserves their space in the header, and leaves the controls independent. The final measured bounds were 0–93px navigation and 93–125px HUD at 320×568, and 0–45px navigation and 45–77px HUD at 768×1024. Fixed-navigation focus now uses an inward standards outline so the indicator remains visible inside the viewport. Passive-section coverage now positions the target safely beyond the actual 35% activation line rather than relying on a relative `offsetTop` or exact fractional equality.
 
@@ -59,6 +59,8 @@ A one-sampled-pixel accent floor was relaxed from 0.001 to 0.0005 after the capt
 
 The final integrated review identified two high-confidence gaps. The GPU ledger now includes the composer and bloom render targets reported by the post-processing owner, and the infrastructure case study now includes a visible trust-boundary/request-flow key plus its adjacent text equivalent. The requested Contact wording was checked against the implementation plan and retained exactly because it already matches the approved current copy. The full runtime budget gate passed with no violations after recording the actual High-tier allocation, including 161,344,784 render-target bytes.
 
+The post-review resize pass now synchronizes the native navigation disclosure whenever the compact breakpoint changes: shrinking closes the overlay before it can cover the identity card, while widening restores the complete desktop navigator. The soundtrack's required user gesture is labeled `PLAY SOUNDTRACK` because the visual drive is already running and browser audio cannot begin before an explicit action.
+
 ## Direction review checklist
 
 - [x] Information uses near-black opaque panels rather than neon glass.