docs(launch): reconcile rendered homepage audit evidence

2026-11-10 12:45:49 +01:00
parent af8c48ce70
commit 98483b804a
2 changed files with 12 additions and 0 deletions
@@ -1,5 +1,15 @@
 # LAUNCH-00 source audit - partial checkpoint
 ## Rendered baseline reconciliation, 10 November 2026
 The separately published A3 evidence at `bd34a3504f7e849c41b48db444f0e1f16324a16f` includes `docs/ui-modernisation/visual-correction/LANDING_BASELINE_REVIEW.md` and `evidence/landing-baseline/BROWSER.json` under the same directory. The runtime was `e8e7d83958587e8b5a4b93d03d3e736896df5a48`. This closes the rendered anonymous navigation and raw export observations at that baseline.
 12 fixture journeys covered 320, 768 and 1440 px in EN/NB and both themes. Keyboard feature navigation, local language selection and entry into existing sign-in and registration routes passed. No registration was submitted. All three preview SVGs loaded. All 12 states reported missing landmark best practices, and the raw static response lacked a hero heading, canonical and locale alternates. The anonymous language switch attempted 24 authenticated preference writes that the fixture rejected. Public language changes should use the existing local choice until the user has a session. The dashboard SVG email was anonymised in the capture fixture only.
 The captured images are browser evidence of the existing homepage. The preview SVGs inside it are still illustrations. For LAUNCH-01, source potential real product captures from the published A3 evidence viewer, including `dashboard`, `applications-selection`, `career` and the existing CV editor captures. Before using an image, inspect the pixels and bind it to its actual route, source commit, language, viewport, fixture and asset rights. The A3 development branch has outstanding visual acceptance. Its captures are candidates for review mockups. Market, provider and pricing claims require the separate claim review.
 Open audit inputs include contemporary design pattern research, asset rights, realistic registration and degraded-auth behaviour, measured performance and native review. The four LAUNCH-01 concepts remain to be rendered.
 2026-11-02. `feature/launch-site-redesign`, accepted conditional baseline `5cb903b989742b7a96cb22ddf4c0e24993b18980`. Full authoritative homepage prompt read. LAUNCH-00 IN_PROGRESS; LAUNCH-01 concepts NOT YET PRODUCED. No final design selected or implemented.
 | Finding | Source evidence | User implication / proposed direction |
@@ -1,5 +1,7 @@
 # Partial homepage planning handoff
 10 November: the published A3 landing baseline now supplies 12 rendered navigation states, raw HTML findings and screenshot provenance candidates. See [homepage audit](HOMEPAGE_AUDIT.md). Next, complete the outstanding audit inputs and render the four concept pairs. Final homepage selection, application implementation and launch acceptance retain their separate gates.
 Continuation 2 November: CONTENT_ARCHITECTURE.md, INTERNATIONALISATION.md and SEO_STRATEGY.md add independent design-neutral content/routing/publication proposals. Byte-matched existing build-shell evidence confirms raw export lacks descriptive marketing HTML, canonical and hreflang. No public UI/routes/metadata implementation or final visual choice made. These source/build checks are not live SEO, performance or release qualification. The five application UI concepts remain separate from LAUNCH-01's required homepage exploration; no sixth application concept created.
 Branch `feature/launch-site-redesign`, baseline `5cb903b989742b7a96cb22ddf4c0e24993b18980`. Documentation-only source audit. LAUNCH-00 remains IN_PROGRESS. LAUNCH-01 four actual desktop/mobile concepts are PENDING, not replaced by written descriptions. No owner design decision requested until reviewable concepts exist.