From de02745b82e6a2213b446372d0546a1b3afecb3b Mon Sep 17 00:00:00 2001 From: axiomlogicnexus Date: Wed, 24 Jun 2026 22:27:16 +0000 Subject: [PATCH] Harden public manual evidence and release routing --- .../HyperTwist/DEVELOPMENT.md | 24 ++++++++++++++ .../HyperTwist/FEATURE_REGISTRY.md | 6 ++-- .../__tests__/download-center-page.test.tsx | 10 +++--- .../__tests__/public-marketing-pages.test.tsx | 26 ++++++++++----- .../src/components/ui/PublicLaunchStatus.tsx | 14 ++++---- website/src/pages/public-pages-commerce.tsx | 20 +++++------ website/src/pages/public-pages-marketing.tsx | 33 +++++++++++++++++++ website/src/site-config.ts | 12 +++---- website/src/site-data.ts | 5 +++ 9 files changed, 110 insertions(+), 40 deletions(-) diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md index ad6ad7b..d431843 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md @@ -273,6 +273,18 @@ Latest same-day browser/distribution continuity follow-up still on `2026-06-24`: - protected notices - protected browser-access - protected dashboard +- the remaining public pricing, launch-status, and download fallback CTAs now + also stop opening generic `/login` or broad support detours when the real + next lane is already known: + - the free explorer plan now preserves `/register?next=/app` + - operator fallback now opens the protected downloads lane directly + - studio fallback now opens the protected rollout/browser-access lane + - public launch-status and download fallback callouts now point at exact + protected release, notices, and dashboard follow-through +- the public About and Support pages now also surface the same live launch and + packaged-proof evidence already shown on the stronger public manual routes, + so those narrative/help surfaces no longer talk about maturity only in the + abstract - the public topic cards therefore no longer dead-end on broad public guidance when the real next step is signed-in protected follow-through - the new shared callout posture explicitly separates: - what still works @@ -283,6 +295,18 @@ Latest same-day browser/distribution continuity follow-up still on `2026-06-24`: - protected-route loading with preserved next-target sign-in and support escape hatches - dashboard auth-health and release-authority fallback continuity - public download and protected release-lane fallback continuity +- the same bounded follow-up then reran the HyperTwist-owned refactor tools on + the current public-route continuity state: + - `scripts/run-hypertwist-sentrux-source-only.sh` + - `Quality: 6135` + - all `7` rules passing + - `scripts/run-hypertwist-gitnexus-analyze.sh` + - `16,236` nodes + - `38,055` edges + - `670` clusters + - `300` flows + - `scripts/run-hypertwist-gitnexus-status.sh` + - `Status: up-to-date` - this hardening is still boundary-honest: - degraded browser auth does not become a false production claim - degraded release-manifest lookup does not unlock raw package delivery diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md index cbcc9e7..6ddefab 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md @@ -267,10 +267,10 @@ repo. | Feature | Status | Primary authority | Notes | |---|---|---|---| -| Public `hypertwist.app` marketing shell | Implemented now | first-party `website/` app + feature registry/roadmap authority | HyperTwist now has a dedicated first-party public web surface for homepage, feature atlas, about, resources, pricing, download, support, and legal routes. This lane is separate from the embedded Unreal browser runtime under `Content/Browser/` and does not claim browser-simulator parity. The same public lane now also serves as a bounded operator/distribution manual through the docs/resources/download/support surfaces, the public feature-atlas route, and related launch/status surfaces, explaining browser-versus-desktop posture, rollout steps, package proof, simulator-use guidance, and current input/device truth without claiming browser ownership of the native runtime or overclaiming unfinished VR/controller posture. The same package now also carries a first-party external runtime-readiness verifier so deploy-time env and live health posture can be checked outside the dashboard, plus separated local-versus-production env templates whose placeholder values are intentionally rejected until real launch config is in place, bootstrap CI now validates both the frontend and auth-server website commands directly, and the auth server can now auto-serve the built `website/dist` bundle with bounded SPA fallback for same-origin public deployment. Request-level server coverage now also proves that public/app shell delivery does not shadow `/api/*`, `/auth*`, `/health`, or missing asset paths, while the pricing/download/notices routes now surface first-party preview-versus-launch posture from the same bounded launch checklist instead of relying on hidden operator-only status. The shared marketing shell now also carries a compact public-site-status banner across public pages, the homepage keeps a fuller status section, and the shared public launch-status component now consumes live auth-health webhook/runtime truth in addition to release-manifest download readiness so public marketing copy does not claim launch posture from static checkout/download config alone. The auth server now also emits an authoritative `launch` summary on `/api/auth/health`, including required blocker labels, billing product/price-map gates, and current checkout targets, so the public banner and protected dashboard no longer duplicate launch-blocker evaluation client-side. A later same-family continuation then widened that release-manifest authority again to carry public runtime commerce config for operator/studio checkout URLs and live plan-price strings, so pricing, notices, and dashboard launch-readiness surfaces no longer depend only on frontend build-time checkout config. The live website lane now also owns route-aware title/description/canonical/Open-Graph/Twitter metadata for the real `hypertwist.app` marketing surface so deployed public pages no longer remain on a single generic SPA title/description, plus first-party `robots.txt` and `sitemap.xml` assets for the public route set while keeping `/app`, `/login`, and `/register` out of crawler posture. The real `check-runtime-readiness` CLI is now also exercised against the checked-in production example env files, and a spawned `website/server` bootstrap proof now verifies the live same-origin process path from production-shaped env into `/health`, `/api/auth/health`, built-shell serving, and the public anonymous release-manifest posture for the shared desktop release lane. The same verifier now also probes the deployed root-shell marker and can explicitly fail when the public origin is still serving the older placeholder rollout page instead of the first-party website/auth-server lane, while the repo now also carries first-party `website/deploy/` `nginx` plus `systemd` handoff templates, a concrete same-origin public-host cutover guide, a deployment-file renderer that emits resolved operator outputs from real checkout paths, and a manifest-driven bundle renderer that lets one authoritative input own the public origin while emitting validated env plus install artifacts together, with the shared-VPS-safe default upstream moved to `3011` after live host inspection confirmed `3001` is already occupied by FamiliarOS. The same deployment lane now also distinguishes `launch` from `preview` posture so honest missing checkout/download/webhook/release values are accepted only for non-public rehearsal while placeholder strings still fail, `runtime.mode: mixed` plus `public_origin_ready: true` counts as valid preview-host proof, and the staging helper can archive either committed `HEAD` or the live worktree through `--archive-source worktree`. An isolated VPS-local staging proof then confirmed that both the committed HyperTwist website lane and the later preview-tier worktree packet can serve green health, release-manifest, and first-party shell responses on that real shared host behind `3011`, and a later root-owned cutover then replaced the public placeholder site with the live first-party same-origin preview deployment on `https://hypertwist.app`. The package now also ships a bounded root-owned live-deploy helper that stages the committed checkout, uploads the rendered bundle, installs env, rebuilds the site, replaces the live `systemd` plus `nginx` files, and validates the public origin; that helper has already been re-proved idempotently against the live host. The repo now also ships that host-proof flow as a first-party staging helper so future sessions can rerun the temp checkout/build/boot verification path directly before or after root-owned cutover. The website lane now also owns a sanitized generated packaged-validation summary for the Windows higher-dimensional desktop proof, rendered from the checked-in authoritative package report into `website/src/shared/generated/windows-package-validation-summary.json`, and the owned web-surface validation gate now checks that generated proof for freshness before approving the current public/auth/download/browser lane. The same browser shell now also has a first-party top-level runtime-recovery boundary, so unexpected React route failures degrade into a HyperTwist-owned retry/return surface that keeps the browser-versus-desktop product truth explicit instead of collapsing into a blank shell. | +| Public `hypertwist.app` marketing shell | Implemented now | first-party `website/` app + feature registry/roadmap authority | HyperTwist now has a dedicated first-party public web surface for homepage, feature atlas, about, resources, pricing, download, support, and legal routes. This lane is separate from the embedded Unreal browser runtime under `Content/Browser/` and does not claim browser-simulator parity. The same public lane now also serves as a bounded operator/distribution manual through the docs/resources/download/support surfaces, the public feature-atlas route, and related launch/status surfaces, explaining browser-versus-desktop posture, rollout steps, package proof, simulator-use guidance, and current input/device truth without claiming browser ownership of the native runtime or overclaiming unfinished VR/controller posture. The same package now also carries a first-party external runtime-readiness verifier so deploy-time env and live health posture can be checked outside the dashboard, plus separated local-versus-production env templates whose placeholder values are intentionally rejected until real launch config is in place, bootstrap CI now validates both the frontend and auth-server website commands directly, and the auth server can now auto-serve the built `website/dist` bundle with bounded SPA fallback for same-origin public deployment. Request-level server coverage now also proves that public/app shell delivery does not shadow `/api/*`, `/auth*`, `/health`, or missing asset paths, while the pricing/download/notices routes now surface first-party preview-versus-launch posture from the same bounded launch checklist instead of relying on hidden operator-only status. The shared marketing shell now also carries a compact public-site-status banner across public pages, the homepage keeps a fuller status section, and the shared public launch-status component now consumes live auth-health webhook/runtime truth in addition to release-manifest download readiness so public marketing copy does not claim launch posture from static checkout/download config alone. The auth server now also emits an authoritative `launch` summary on `/api/auth/health`, including required blocker labels, billing product/price-map gates, and current checkout targets, so the public banner and protected dashboard no longer duplicate launch-blocker evaluation client-side. A later same-family continuation then widened that release-manifest authority again to carry public runtime commerce config for operator/studio checkout URLs and live plan-price strings, so pricing, notices, and dashboard launch-readiness surfaces no longer depend only on frontend build-time checkout config. The live website lane now also owns route-aware title/description/canonical/Open-Graph/Twitter metadata for the real `hypertwist.app` marketing surface so deployed public pages no longer remain on a single generic SPA title/description, plus first-party `robots.txt` and `sitemap.xml` assets for the public route set while keeping `/app`, `/login`, and `/register` out of crawler posture. The real `check-runtime-readiness` CLI is now also exercised against the checked-in production example env files, and a spawned `website/server` bootstrap proof now verifies the live same-origin process path from production-shaped env into `/health`, `/api/auth/health`, built-shell serving, and the public anonymous release-manifest posture for the shared desktop release lane. The same verifier now also probes the deployed root-shell marker and can explicitly fail when the public origin is still serving the older placeholder rollout page instead of the first-party website/auth-server lane, while the repo now also carries first-party `website/deploy/` `nginx` plus `systemd` handoff templates, a concrete same-origin public-host cutover guide, a deployment-file renderer that emits resolved operator outputs from real checkout paths, and a manifest-driven bundle renderer that lets one authoritative input own the public origin while emitting validated env plus install artifacts together, with the shared-VPS-safe default upstream moved to `3011` after live host inspection confirmed `3001` is already occupied by FamiliarOS. The same deployment lane now also distinguishes `launch` from `preview` posture so honest missing checkout/download/webhook/release values are accepted only for non-public rehearsal while placeholder strings still fail, `runtime.mode: mixed` plus `public_origin_ready: true` counts as valid preview-host proof, and the staging helper can archive either committed `HEAD` or the live worktree through `--archive-source worktree`. An isolated VPS-local staging proof then confirmed that both the committed HyperTwist website lane and the later preview-tier worktree packet can serve green health, release-manifest, and first-party shell responses on that real shared host behind `3011`, and a later root-owned cutover then replaced the public placeholder site with the live first-party same-origin preview deployment on `https://hypertwist.app`. The package now also ships a bounded root-owned live-deploy helper that stages the committed checkout, uploads the rendered bundle, installs env, rebuilds the site, replaces the live `systemd` plus `nginx` files, and validates the public origin; that helper has already been re-proved idempotently against the live host. The repo now also ships that host-proof flow as a first-party staging helper so future sessions can rerun the temp checkout/build/boot verification path directly before or after root-owned cutover. The website lane now also owns a sanitized generated packaged-validation summary for the Windows higher-dimensional desktop proof, rendered from the checked-in authoritative package report into `website/src/shared/generated/windows-package-validation-summary.json`, and the owned web-surface validation gate now checks that generated proof for freshness before approving the current public/auth/download/browser lane. The remaining public conversion seams now also stop dead-ending on generic sign-in/support detours when the next lane is already known: the explorer CTA preserves `/register?next=/app`, operator fallback opens the protected downloads lane, studio fallback opens the protected browser-access rollout lane, and launch/download fallback callouts now point directly at protected release, notices, or dashboard follow-through. The narrative/help surfaces then widened again so the public About and Support pages also surface the same live launch-readiness callout and packaged desktop-proof section already used by the stronger public manual routes, keeping maturity language attached to current native release evidence instead of leaving those pages purely abstract. The same browser shell now also has a first-party top-level runtime-recovery boundary, so unexpected React route failures degrade into a HyperTwist-owned retry/return surface that keeps the browser-versus-desktop product truth explicit instead of collapsing into a blank shell. | | Browser-based operator/account dashboard | Implemented now | first-party `website/` app + shared auth/dashboard packet | A protected browser dashboard is now live for operator access, account state, download posture, browser-access boundary explanation, notices review, and bounded billing/entitlement status. It reuses the shared SuperTokens auth posture proven in FamiliarOS and ScriptoriumAI while remaining HyperTwist-specific in product content and boundary claims, the current auth-health surface now truthfully distinguishes configured versus reachable or ready shared-core posture while exposing fallback-active reason instead of hardcoding readiness, and the same dashboard now also surfaces launch-readiness truth for download URLs, checkout links, source/notices URLs, billing-secret/map configuration, and local-versus-public runtime deployment posture. The same protected overview now also consumes the server-backed Windows packaged-validation summary that the release-manifest authority exposes, so operators can see current higher-dimensional desktop proof without drilling into the dedicated downloads screen. The adjacent protected `/app/browser-access` and `/app/notices` routes now also reuse the bounded escalation-map and release-follow-through guidance from the public support/manual lane, so sign-in does not degrade operator troubleshooting quality into a thinner shell than the public surface. The protected fallback path now also preserves signed-in viewer plan/access posture from local session truth when live manifest authority is temporarily unavailable, while still keeping download authority conservative until the auth server returns. The shared browser auth layer now also has a bounded release-authority reconciliation path that refreshes and persists the local browser session snapshot from fresher manifest viewer truth, while the dashboard and account surfaces expose a compact live-authority sync notice summarizing what changed so operators can see the session catch-up clearly. That same auth layer now also clears stale stored sessions when shared auth is configured and `/api/auth/me` returns `401`, while still preserving the intended offline/local-fallback posture when the account API is merely unreachable or shared auth is not configured. Focused frontend coverage now also protects deep-link login redirect preservation, safe `next`-path normalization across auth entry points, fallback/email auth-bootstrap normalization, login/register continuation behavior, public download-gating behavior, protected-route/shell behavior, real lazy-route tree behavior for key public and protected paths, top-level app-bootstrap and SuperTokens-wrapper posture, login/register unhappy-path and OAuth-button behavior, support-topic fallback routing when live checkout is not configured, desktop-link verify-url/dashboard readiness behavior, and explicit `noindex,nofollow` posture on protected/auth browser surfaces. The validation lane now also has a bounded signed test-session harness under `TEST_MODE=testing` that proves `/api/auth/me`, stale-session invalidation, release-authority reconciliation, and `/api/auth/desktop-link` behavior through the live spawned auth-server process without widening production auth posture. | -| Desktop download posture and browser-to-desktop pairing | Implemented now | first-party `website/` app + `website/server` desktop-link endpoints | Public download targets, dashboard-side release posture, and short-lived desktop-link token generation/verification are now first-party owned. The current server posture now enforces exact website-origin matching, bounded per-user issuance, one-time token consumption, and billing-backed plan/download entitlement resolution with focused `website/server` tests green on `2026-06-22`, and the verify handshake now returns the same resolved download-entitlement posture the dashboard sees instead of only identity plus plan/role. The same lane now also owns a shared `GET /api/releases/manifest` runtime authority for release version/channel/build/published/file-size/checksum/docs/source metadata, with anonymous callers intentionally denied raw download URLs while entitled session-backed callers receive the configured direct platform URL. That manifest now also carries first-party packaged-validation summary truth for the Windows higher-dimensional desktop lane, so the public `/download` page, the public `/resources` reference page, and the protected `/app/downloads` surface can project real package evidence for the dedicated-family `Magic120Cell` / `MagicCube5D` maps even while launch-tier release URLs remain unconfigured. That website-facing packaged proof is now sourced through a sanitized generated summary rendered from the checked-in authoritative `phase6c_dedicated_family_package_validation_report.json`, and the owned web-surface validation gate now checks that generated summary for freshness before approving the current public/auth/download/browser lane. The public `/download` page now keeps raw download URLs behind the protected dashboard instead of exposing them directly, preserves requested platform continuity through `/app/downloads?platform=...`, and surfaces that requested target again after auth handoff inside the protected release lane. When live manifest authority is unavailable, the protected fallback path now still reflects the signed-in viewer posture from local session truth while continuing to withhold raw delivery authority. When live manifest authority resolves fresher entitled viewer truth than the local browser auth snapshot, the protected download-center lane now also follows that server-backed viewer posture for the actual download action instead of leaving the operator blocked behind stale local session state. Both the public and protected download surfaces now also carry first-party rollout steps, first-launch desktop setup guidance, browser-to-desktop pairing follow-through, and release/notices/source references so the desktop setup lane is more than a generic link bucket, while the support surface now carries an explicit escalation map separating account, package, runtime, and rollout/compliance problems. The protected dashboard overview and protected account surface now also mirror that same first-launch follow-through, and the protected browser-access/notices routes now mirror the same escalation separation, so post-sign-in operator guidance does not collapse back into a thinner release-only shell. The dashboard plus public launch-status callouts now consume the same manifest-backed Windows download truth instead of only static frontend config. Actual release URLs remain deployment configuration rather than hardcoded product truth. | -| Paddle-ready pricing and billing webhook seam | Implemented now | first-party `website/` app + `website/server` billing endpoint | The public pricing surface now exists with plan structure, checkout-link configuration seams, and the same `/api/billing/paddle/webhook` endpoint family used by the broader product website lane. The current server now verifies `Paddle-Signature` against `PADDLE_WEBHOOK_SECRET` using the documented raw-body HMAC flow, persists a bounded first-party billing state file, and applies verified Paddle events into account/download entitlement state that the browser dashboard consumes, with focused `website/server` tests green on `2026-06-22`. The shared `GET /api/releases/manifest` authority now also carries public runtime commerce config for operator/studio checkout URLs and live plan-price strings, allowing the pricing page to switch from frontend build-time checkout assumptions to auth-server runtime truth when those values are configured. A spawned live-process proof now also verifies that a real signed webhook updates processed-event health and persisted billing state through the actual auth-server runtime, not only helper-level store tests, and transaction events no longer leak their id into stored `subscriptionId` state. Production checkout URLs, secret management, and broader operator/admin billing workflows remain deployment/application tasks, not shipped-code omissions. | +| Desktop download posture and browser-to-desktop pairing | Implemented now | first-party `website/` app + `website/server` desktop-link endpoints | Public download targets, dashboard-side release posture, and short-lived desktop-link token generation/verification are now first-party owned. The current server posture now enforces exact website-origin matching, bounded per-user issuance, one-time token consumption, and billing-backed plan/download entitlement resolution with focused `website/server` tests green on `2026-06-22`, and the verify handshake now returns the same resolved download-entitlement posture the dashboard sees instead of only identity plus plan/role. The same lane now also owns a shared `GET /api/releases/manifest` runtime authority for release version/channel/build/published/file-size/checksum/docs/source metadata, with anonymous callers intentionally denied raw download URLs while entitled session-backed callers receive the configured direct platform URL. That manifest now also carries first-party packaged-validation summary truth for the Windows higher-dimensional desktop lane, so the public `/download` page, the public `/resources` reference page, and the protected `/app/downloads` surface can project real package evidence for the dedicated-family `Magic120Cell` / `MagicCube5D` maps even while launch-tier release URLs remain unconfigured. That website-facing packaged proof is now sourced through a sanitized generated summary rendered from the checked-in authoritative `phase6c_dedicated_family_package_validation_report.json`, and the owned web-surface validation gate now checks that generated summary for freshness before approving the current public/auth/download/browser lane. The public `/download` page now keeps raw download URLs behind the protected dashboard instead of exposing them directly, preserves requested platform continuity through `/app/downloads?platform=...`, and surfaces that requested target again after auth handoff inside the protected release lane. The public download fallbacks now also open exact protected download and dashboard follow-through instead of stopping at a generic anonymous login hop. When live manifest authority is unavailable, the protected fallback path now still reflects the signed-in viewer posture from local session truth while continuing to withhold raw delivery authority. When live manifest authority resolves fresher entitled viewer truth than the local browser auth snapshot, the protected download-center lane now also follows that server-backed viewer posture for the actual download action instead of leaving the operator blocked behind stale local session state. Both the public and protected download surfaces now also carry first-party rollout steps, first-launch desktop setup guidance, browser-to-desktop pairing follow-through, and release/notices/source references so the desktop setup lane is more than a generic link bucket, while the support surface now carries an explicit escalation map separating account, package, runtime, and rollout/compliance problems. The protected dashboard overview and protected account surface now also mirror that same first-launch follow-through, and the protected browser-access/notices routes now mirror the same escalation separation, so post-sign-in operator guidance does not collapse back into a thinner release-only shell. The dashboard plus public launch-status callouts now consume the same manifest-backed Windows download truth instead of only static frontend config. Actual release URLs remain deployment configuration rather than hardcoded product truth. | +| Paddle-ready pricing and billing webhook seam | Implemented now | first-party `website/` app + `website/server` billing endpoint | The public pricing surface now exists with plan structure, checkout-link configuration seams, and the same `/api/billing/paddle/webhook` endpoint family used by the broader product website lane. The current server now verifies `Paddle-Signature` against `PADDLE_WEBHOOK_SECRET` using the documented raw-body HMAC flow, persists a bounded first-party billing state file, and applies verified Paddle events into account/download entitlement state that the browser dashboard consumes, with focused `website/server` tests green on `2026-06-22`. The shared `GET /api/releases/manifest` authority now also carries public runtime commerce config for operator/studio checkout URLs and live plan-price strings, allowing the pricing page to switch from frontend build-time checkout assumptions to auth-server runtime truth when those values are configured. The fallback plan CTAs now also use exact protected release/browser-access targets when live checkout URLs are absent, instead of routing operators back into a vague public support detour. A spawned live-process proof now also verifies that a real signed webhook updates processed-event health and persisted billing state through the actual auth-server runtime, not only helper-level store tests, and transaction events no longer leak their id into stored `subscriptionId` state. Production checkout URLs, secret management, and broader operator/admin billing workflows remain deployment/application tasks, not shipped-code omissions. | | Public open-source notices and corresponding-source surface | Implemented now | first-party `website/` app + `HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md` | HyperTwist now has a stable public `Open Source Notices` route linked from pricing, download, and footer surfaces, satisfying the requirement that public distribution surfaces expose notice and corresponding-source guidance when shipped builds contain `MPL`-covered material. The exact public corresponding-source URL still must be configured before external launch. | ### 7. Hyper puzzle topology and non-Euclidean runtime diff --git a/website/src/__tests__/download-center-page.test.tsx b/website/src/__tests__/download-center-page.test.tsx index 0efa6d8..2fa254f 100644 --- a/website/src/__tests__/download-center-page.test.tsx +++ b/website/src/__tests__/download-center-page.test.tsx @@ -41,7 +41,7 @@ vi.mock('../site-config', () => ({ name: 'Explorer', price: 'Free', ctaLabel: 'Start in the browser', - ctaHref: '/register', + ctaHref: '/register?next=%2Fapp', notes: 'Preview the browser account shell, operator dashboard, release notes, and desktop onboarding posture.', features: ['Browser account access'], }, @@ -49,8 +49,8 @@ vi.mock('../site-config', () => ({ key: 'operator', name: 'Operator', price: 'Launch pricing via Paddle', - ctaLabel: 'Request operator access', - ctaHref: '/support?topic=operator-access', + ctaLabel: 'Open protected downloads', + ctaHref: '/app/downloads?platform=windows', notes: 'Desktop-first recognition, replay, training, and higher-dimensional runtime ownership for active training operators.', features: ['Desktop download access'], }, @@ -58,8 +58,8 @@ vi.mock('../site-config', () => ({ key: 'studio', name: 'Studio', price: 'Contact for launch readiness', - ctaLabel: 'Talk to HyperTwist', - ctaHref: '/support?topic=studio-rollout', + ctaLabel: 'Open protected rollout lane', + ctaHref: '/app/browser-access', notes: 'Higher-dimensional families, operator deployment support, and packaging/validation coordination for production lanes.', features: ['Magic120Cell and 5D operator posture'], }, diff --git a/website/src/__tests__/public-marketing-pages.test.tsx b/website/src/__tests__/public-marketing-pages.test.tsx index be5822c..8d8308a 100644 --- a/website/src/__tests__/public-marketing-pages.test.tsx +++ b/website/src/__tests__/public-marketing-pages.test.tsx @@ -61,7 +61,7 @@ vi.mock('../site-config', () => ({ name: 'Explorer', price: 'Free', ctaLabel: 'Start in the browser', - ctaHref: '/register', + ctaHref: '/register?next=%2Fapp', notes: 'Preview the browser account shell, operator dashboard, release notes, and desktop onboarding posture.', features: ['Browser account access'], }, @@ -69,8 +69,8 @@ vi.mock('../site-config', () => ({ key: 'operator', name: 'Operator', price: 'Launch pricing via Paddle', - ctaLabel: 'Request operator access', - ctaHref: '/support?topic=operator-access', + ctaLabel: 'Open protected downloads', + ctaHref: '/app/downloads?platform=windows', notes: 'Desktop-first recognition, replay, training, and higher-dimensional runtime ownership for active training operators.', features: ['Desktop download access'], }, @@ -78,8 +78,8 @@ vi.mock('../site-config', () => ({ key: 'studio', name: 'Studio', price: 'Contact for launch readiness', - ctaLabel: 'Talk to HyperTwist', - ctaHref: '/support?topic=studio-rollout', + ctaLabel: 'Open protected rollout lane', + ctaHref: '/app/browser-access', notes: 'Higher-dimensional families, operator deployment support, and packaging/validation coordination for production lanes.', features: ['Magic120Cell and 5D operator posture'], }, @@ -303,7 +303,7 @@ describe('public marketing pages', () => { expect(await screen.findByText(/public release fallback/i)).toBeTruthy() expect(screen.getByText(/direct package delivery stays intentionally withheld until that authority returns/i)).toBeTruthy() expect(screen.getByText('What stays intentionally withheld')).toBeTruthy() - expect(screen.getByRole('link', { name: 'Sign in to inspect access' }).getAttribute('href')).toBe('/login') + expect(screen.getByRole('link', { name: 'Open protected downloads' }).getAttribute('href')).toBe('/app/downloads?platform=windows') expect(screen.getByRole('link', { name: 'Open support' }).getAttribute('href')).toBe('/support?topic=operator-access') }) @@ -524,6 +524,10 @@ describe('public marketing pages', () => { expect(screen.getByText('Generates desktop-link tokens for safe browser-to-desktop handoff')).toBeTruthy() expect(screen.getByText('Must prove its own runtime and backend contract before being marketed as live')).toBeTruthy() expect(screen.getByText('Release and deployment maturity')).toBeTruthy() + expect(screen.getByText('Current public rollout posture')).toBeTruthy() + expect(screen.getByText('About-page launch and release posture')).toBeTruthy() + expect(screen.getByText('Current packaged desktop proof')).toBeTruthy() + expect(screen.getByText('Packaged validation passed')).toBeTruthy() }) it('renders the public feature atlas with capability tiers and route-aware metadata', async () => { @@ -638,7 +642,7 @@ describe('public marketing pages', () => { expect(document.head.querySelector('meta[property="og:url"]')?.getAttribute('content')).toBe('https://hypertwist.app/features') }) - it('uses useful support fallback routes for plans that do not yet have live checkouts', () => { + it('uses exact protected fallback routes for plans that do not yet have live checkouts', () => { mockGetAuthHealth.mockResolvedValue({ ok: true, service: 'hypertwist-auth-server', @@ -696,8 +700,8 @@ describe('public marketing pages', () => { }) renderWithProviders() - expect(screen.getByRole('link', { name: /request operator access/i }).getAttribute('href')).toBe('/support?topic=operator-access') - expect(screen.getByRole('link', { name: /talk to hypertwist/i }).getAttribute('href')).toBe('/support?topic=studio-rollout') + expect(screen.getByRole('link', { name: /open protected downloads/i }).getAttribute('href')).toBe('/app/downloads?platform=windows') + expect(screen.getByRole('link', { name: /open protected rollout lane/i }).getAttribute('href')).toBe('/app/browser-access') }) it('prefers runtime checkout URLs and live plan prices on the pricing page when the manifest provides them', async () => { @@ -897,6 +901,10 @@ describe('public marketing pages', () => { expect(screen.getAllByText('Manual and route focus').length).toBeGreaterThan(0) expect(screen.getByText('Recovery and degraded-state guidance')).toBeTruthy() expect(screen.getByText('Desktop-first continuity during recovery')).toBeTruthy() + expect(screen.getByText('Current release and package posture')).toBeTruthy() + expect(screen.getByText('Current support-facing launch posture')).toBeTruthy() + expect(screen.getByText('Current packaged desktop proof')).toBeTruthy() + expect(screen.getByText('Packaged validation passed')).toBeTruthy() expect(screen.getByText('Digital delivery workflow')).toBeTruthy() expect(screen.getByText('Post-install operator workflow')).toBeTruthy() expect(screen.getByText('Privacy and compliance boundary')).toBeTruthy() diff --git a/website/src/components/ui/PublicLaunchStatus.tsx b/website/src/components/ui/PublicLaunchStatus.tsx index 8b805fc..345dfec 100644 --- a/website/src/components/ui/PublicLaunchStatus.tsx +++ b/website/src/components/ui/PublicLaunchStatus.tsx @@ -4,7 +4,7 @@ import { Link } from 'react-router-dom' import { getAuthHealth } from '../../auth/auth-api' import { resolvePublicLaunchStatusSummary } from '../../public-launch' import { launchReadiness } from '../../site-config' -import { buildSupportPath } from '../../site-routes' +import { buildProtectedDownloadPath } from '../../site-routes' function usePublicLaunchStatus() { const authHealthQuery = useQuery({ @@ -58,8 +58,8 @@ export function MarketingLaunchStatusBanner() { View launch posture - - Get launch help + + Open protected release lane @@ -105,11 +105,11 @@ export function PublicLaunchStatus({ ) : null} {!ready ? (
- - Contact launch support + + Open protected release lane - - Review notices + + Open protected notices
) : null} diff --git a/website/src/pages/public-pages-commerce.tsx b/website/src/pages/public-pages-commerce.tsx index 7feb78d..63b25aa 100644 --- a/website/src/pages/public-pages-commerce.tsx +++ b/website/src/pages/public-pages-commerce.tsx @@ -14,7 +14,7 @@ import { resolveReleaseCommerceView, resolveReleaseManifestView, } from '../release-manifest' -import { buildProtectedDownloadPath, buildSupportPath } from '../site-routes' +import { buildLoginPath, buildProtectedDownloadPath, buildSupportPath } from '../site-routes' import { desktopFirstLaunchCards, desktopDownloadSteps, @@ -65,14 +65,14 @@ export function PricingPage() { { ...operatorFallbackPlan, price: releaseCommerce.plan_price_operator, - ctaLabel: releaseCommerce.operator_checkout_url ? 'Open Paddle checkout' : 'Request operator access', - ctaHref: releaseCommerce.operator_checkout_url || buildSupportPath('operator-access'), + ctaLabel: releaseCommerce.operator_checkout_url ? 'Open Paddle checkout' : operatorFallbackPlan.ctaLabel, + ctaHref: releaseCommerce.operator_checkout_url || operatorFallbackPlan.ctaHref, }, { ...studioFallbackPlan, price: releaseCommerce.plan_price_studio, - ctaLabel: releaseCommerce.studio_checkout_url ? 'Open Paddle checkout' : 'Talk to HyperTwist', - ctaHref: releaseCommerce.studio_checkout_url || buildSupportPath('studio-rollout'), + ctaLabel: releaseCommerce.studio_checkout_url ? 'Open Paddle checkout' : studioFallbackPlan.ctaLabel, + ctaHref: releaseCommerce.studio_checkout_url || studioFallbackPlan.ctaHref, }, ]), [releaseCommerce]) @@ -261,7 +261,7 @@ export function DownloadPage() { }, ]} actions={[ - { label: 'Sign in to inspect access', to: '/login' }, + { label: 'Open protected downloads', to: buildProtectedDownloadPath('windows') }, { label: 'Open support', to: buildSupportPath('operator-access') }, ]} /> @@ -443,8 +443,8 @@ export function DownloadPage() { download links live behind the protected dashboard where plan and entitlement state are resolved.

- - Sign in to check access + + Open protected download lane @@ -455,8 +455,8 @@ export function DownloadPage() { After sign-in, open the operator dashboard to generate a desktop-link token. That token is designed to hand browser identity and plan posture over to the local desktop app without exposing your password.

- - Open dashboard + + Open protected dashboard diff --git a/website/src/pages/public-pages-marketing.tsx b/website/src/pages/public-pages-marketing.tsx index 95756f9..20ea170 100644 --- a/website/src/pages/public-pages-marketing.tsx +++ b/website/src/pages/public-pages-marketing.tsx @@ -428,6 +428,8 @@ export function HomeLanding() { } export function AboutPage() { + const { windowsValidationPlatform } = usePublicReleaseManifestView('public-about') + return ( <> + +
+ +
+ + ) @@ -901,6 +918,7 @@ export function SupportPage() { const supportTopic = searchParams.get('topic') const selectedSupportTopicKey = supportTopic && supportTopicGuidance[supportTopic] ? supportTopic : null const selectedSupportTopic = selectedSupportTopicKey ? supportTopicGuidance[selectedSupportTopicKey] : null + const { windowsValidationPlatform } = usePublicReleaseManifestView('public-support') return ( <> @@ -932,6 +950,21 @@ export function SupportPage() { /> ) : null} +
+ +
+ + +

diff --git a/website/src/site-config.ts b/website/src/site-config.ts index 4918cb2..7d1c412 100644 --- a/website/src/site-config.ts +++ b/website/src/site-config.ts @@ -1,5 +1,5 @@ import type { DownloadPlatformKey } from './site-routes' -import { buildSupportPath } from './site-routes' +import { buildProtectedDownloadPath, buildRegisterPath } from './site-routes' const env = import.meta.env as Record @@ -54,7 +54,7 @@ export const planCatalog = [ name: 'Explorer', price: 'Free', ctaLabel: 'Start in the browser', - ctaHref: '/register', + ctaHref: buildRegisterPath('/app'), notes: 'Preview the browser account shell, operator dashboard, release notes, and desktop onboarding posture.', features: [ 'Browser account access', @@ -67,8 +67,8 @@ export const planCatalog = [ key: 'operator', name: 'Operator', price: readTrimmedEnv('VITE_PLAN_PRICE_OPERATOR', 'Launch pricing via Paddle'), - ctaLabel: operatorCheckoutUrl ? 'Open Paddle checkout' : 'Request operator access', - ctaHref: operatorCheckoutUrl || buildSupportPath('operator-access'), + ctaLabel: operatorCheckoutUrl ? 'Open Paddle checkout' : 'Open protected downloads', + ctaHref: operatorCheckoutUrl || buildProtectedDownloadPath('windows'), notes: 'Desktop-first recognition, replay, training, and higher-dimensional runtime ownership for active training operators.', features: [ 'Desktop download access', @@ -81,8 +81,8 @@ export const planCatalog = [ key: 'studio', name: 'Studio', price: readTrimmedEnv('VITE_PLAN_PRICE_STUDIO', 'Contact for launch readiness'), - ctaLabel: studioCheckoutUrl ? 'Open Paddle checkout' : 'Talk to HyperTwist', - ctaHref: studioCheckoutUrl || buildSupportPath('studio-rollout'), + ctaLabel: studioCheckoutUrl ? 'Open Paddle checkout' : 'Open protected rollout lane', + ctaHref: studioCheckoutUrl || '/app/browser-access', notes: 'Higher-dimensional families, operator deployment support, and packaging/validation coordination for production lanes.', features: [ 'Magic120Cell and 5D operator posture', diff --git a/website/src/site-data.ts b/website/src/site-data.ts index 0c34028..c6855c7 100644 --- a/website/src/site-data.ts +++ b/website/src/site-data.ts @@ -762,6 +762,11 @@ export const resourceCollections = [ ] as const export const changelogEntries = [ + { + date: 'June 24, 2026', + title: 'About and Support now surface live launch posture plus packaged desktop proof', + details: 'The public About and Support pages no longer talk about maturity only in abstract terms. They now expose the same current launch-readiness callout and Windows packaged-proof section already used by the other public manual surfaces, so narrative, rollout, and help pages stay anchored to current native release evidence.', + }, { date: 'June 24, 2026', title: 'Public support topics now preserve exact protected destinations through auth',