Record full website validation follow-up

docs/ops/HYPERTWIST_PUBLIC_WEBSITE_AUTH_BILLING_AND_DISTRIBUTION_PACKET_2026-06-22.md

@@ -363,6 +363,10 @@ Validation result on `2026-06-22`:
 - the real runtime-readiness CLI against the checked-in production example env files failed exactly on the remaining placeholder launch values
 - the spawned server also accepted a real signed Paddle test payload and reflected the processed billing event through both `/api/auth/health` and the persisted billing-state file
 - the spawned server also proved bounded session-backed `/api/auth/me` and `/api/auth/desktop-link` behavior under the validation-only signed test-session harness, and transaction events no longer leak their id into stored `subscription_id`
+- the later shared public-launch-status banner continuation then also passed the
+  full frontend `npm test` suite and a fresh `npm run build` after widening an
+  older auth-page mock to include the marketing shell's new shared
+  `getAuthHealth` dependency
 
 Current live-origin evidence on `2026-06-22`:
 

website/README.md

@@ -213,6 +213,11 @@ The focused frontend test coverage now also pins:
 - route-aware metadata behavior for public versus protected surfaces plus richer download-lane guidance on both the public and protected release pages
 - spawned `website/server` bootstrap proof from production-shaped same-origin env into live `/health`, `/api/auth/health`, static public/app shell delivery, verified webhook reflection into billing state, and bounded session-backed `/api/auth/me` plus `/api/auth/desktop-link` behavior under `TEST_MODE=testing`
 
+The later shared public-launch-status banner continuation on `2026-06-22` then
+also passed the full frontend `npm test` suite and a fresh `npm run build`
+after an older auth-page mock was widened to include the new shared
+`getAuthHealth` dependency used by the marketing shell.
+
 Canonical same-origin cutover guide:
 
 - `docs/ops/HYPERTWIST_WEBSITE_SAME_ORIGIN_DEPLOYMENT_HANDOFF_2026-06-22.md`