From 42fcd54ecc5af45fd16d4007913a78d38ed62a0c Mon Sep 17 00:00:00 2001 From: axiomlogicnexus Date: Sun, 28 Jun 2026 03:56:42 +0000 Subject: [PATCH] Tighten control ownership truth and public manual guidance --- .../HyperTwistTrainingPanelWidget.cpp | 143 +++++++++++-- .../HyperTwistBrowserBridgeObjectTest.cpp | 44 +++- .../HyperTwist/DEVELOPMENT.md | 106 +++++++++ .../HyperTwist/FEATURE_REGISTRY.md | 6 +- docs/v6_5_deep_manual_pack/HyperTwist/PRD.md | 6 + scripts/bootstrap-hypertwist-sentrux.sh | 40 ++-- scripts/run-hypertwist-sentrux-source-only.sh | 2 +- website/README.md | 32 +++ .../__tests__/public-marketing-pages.test.tsx | 30 +++ website/src/pages/public-page-helpers.tsx | 143 +++++++++++++ website/src/pages/public-pages-commerce.tsx | 9 + website/src/pages/public-pages-launch.tsx | 88 ++++++++ website/src/pages/public-pages-marketing.tsx | 202 +++--------------- website/src/pages/public-pages.tsx | 1 + website/src/router/PublicRoutes.tsx | 2 +- website/src/site-data.ts | 159 ++++++++++++++ 16 files changed, 805 insertions(+), 208 deletions(-) create mode 100644 website/src/pages/public-pages-launch.tsx diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingPanelWidget.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingPanelWidget.cpp index 8124091..1766877 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingPanelWidget.cpp +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingPanelWidget.cpp @@ -40,6 +40,28 @@ namespace HyperTwistTrainingPanelWidgetInternal bool bRequiresWindowsPackagedControllerValidationForReopen = true; }; + struct FDedicatedHigherDimensionalRuntimeOwnershipFacts + { + FString FamilyLabel; + FString ActivationProfileId; + FString HostSurfaceId; + FString ViewContextSurfaceId; + FString SessionSurfaceId; + FString SceneSurfaceId; + bool bHostReady = false; + bool bViewContextReady = false; + bool bSessionReady = false; + bool bSceneReady = false; + + bool IsReady() const + { + return bHostReady + && bViewContextReady + && bSessionReady + && bSceneReady; + } + }; + FString DescribeBool(const bool bValue) { return bValue ? TEXT("yes") : TEXT("no"); @@ -50,6 +72,11 @@ namespace HyperTwistTrainingPanelWidgetInternal return bValue ? TEXT("ready") : TEXT("not ready"); } + FString DescribeIdOrFallback(const FString& Value) + { + return !Value.IsEmpty() ? Value : FString(TEXT("n/a")); + } + FString DescribeKeyForRoster(const FKey& Key) { return Key.IsValid() ? Key.GetDisplayName().ToString() : TEXT("n/a"); @@ -329,6 +356,83 @@ namespace HyperTwistTrainingPanelWidgetInternal ); } + FDedicatedHigherDimensionalRuntimeOwnershipFacts + BuildDedicatedHigherDimensionalRuntimeOwnershipFacts( + const FString& FamilyLabel, + const FString& ActivationProfileId + ) + { + FDedicatedHigherDimensionalRuntimeOwnershipFacts Facts; + Facts.FamilyLabel = FamilyLabel; + Facts.ActivationProfileId = ActivationProfileId; + + FHyperTwistTrainingHigherDimensionalRuntimeHostSurface HostSurface; + Facts.bHostReady = + UHyperTwistTrainingRuntimeLibrary::TryGetBundledHigherDimensionalRuntimeHostSurfaceByActivationProfileId( + ActivationProfileId, + HostSurface + ) && HostSurface.IsStructurallyValid(); + if (Facts.bHostReady) + { + Facts.HostSurfaceId = HostSurface.HostSurfaceId; + } + + FHyperTwistTrainingHigherDimensionalRuntimeViewContextSurface ViewContextSurface; + Facts.bViewContextReady = + UHyperTwistTrainingRuntimeLibrary::TryGetBundledHigherDimensionalRuntimeViewContextSurfaceByActivationProfileId( + ActivationProfileId, + ViewContextSurface + ) && ViewContextSurface.IsStructurallyValid(); + if (Facts.bViewContextReady) + { + Facts.ViewContextSurfaceId = ViewContextSurface.ViewContextSurfaceId; + } + + FHyperTwistTrainingHigherDimensionalRuntimeSessionSurface SessionSurface; + Facts.bSessionReady = + UHyperTwistTrainingRuntimeLibrary::TryGetBundledHigherDimensionalRuntimeSessionSurfaceByActivationProfileId( + ActivationProfileId, + SessionSurface + ) && SessionSurface.IsStructurallyValid(); + if (Facts.bSessionReady) + { + Facts.SessionSurfaceId = SessionSurface.SessionSurfaceId; + } + + FHyperTwistTrainingHigherDimensionalInteractiveSceneSurface SceneSurface; + Facts.bSceneReady = + UHyperTwistTrainingRuntimeLibrary::TryGetBundledHigherDimensionalInteractiveSceneSurfaceByActivationProfileId( + ActivationProfileId, + SceneSurface + ) && SceneSurface.IsStructurallyValid(); + if (Facts.bSceneReady) + { + Facts.SceneSurfaceId = SceneSurface.SceneSurfaceId; + } + + return Facts; + } + + FString BuildDedicatedHigherDimensionalRuntimeOwnershipLine( + const FDedicatedHigherDimensionalRuntimeOwnershipFacts& Facts + ) + { + return FString::Printf( + TEXT("%s %s | activation %s | host %s (%s) | view %s (%s) | session %s (%s) | scene %s (%s)"), + *Facts.FamilyLabel, + *DescribeReadyState(Facts.IsReady()), + *DescribeIdOrFallback(Facts.ActivationProfileId), + *DescribeBool(Facts.bHostReady), + *DescribeIdOrFallback(Facts.HostSurfaceId), + *DescribeBool(Facts.bViewContextReady), + *DescribeIdOrFallback(Facts.ViewContextSurfaceId), + *DescribeBool(Facts.bSessionReady), + *DescribeIdOrFallback(Facts.SessionSurfaceId), + *DescribeBool(Facts.bSceneReady), + *DescribeIdOrFallback(Facts.SceneSurfaceId) + ); + } + const FXrControllerBoundaryFacts& GetXrControllerBoundaryFacts() { static const FXrControllerBoundaryFacts CachedFacts = []() @@ -1043,19 +1147,23 @@ UHyperTwistTrainingPanelWidget::GetDisplayedControlInputReadinessInspectSurface( Surface.bHigherDimensionalKeyboardInputReady = HigherDimensionalDefaults != nullptr && HigherDimensionalDefaults->bUseGameAndUiInputMode; - const FHyperTwistTrainingHigherDimensionalRuntimeHostCatalog HostCatalog = - UHyperTwistTrainingRuntimeLibrary::GetBundledHigherDimensionalRuntimeHostCatalog(); - const FHyperTwistTrainingHigherDimensionalRuntimeViewContextCatalog ViewContextCatalog = - UHyperTwistTrainingRuntimeLibrary::GetBundledHigherDimensionalRuntimeViewContextCatalog(); - const FHyperTwistTrainingHigherDimensionalRuntimeSessionCatalog SessionCatalog = - UHyperTwistTrainingRuntimeLibrary::GetBundledHigherDimensionalRuntimeSessionCatalog(); - const FHyperTwistTrainingHigherDimensionalInteractiveSceneCatalog SceneCatalog = - UHyperTwistTrainingRuntimeLibrary::GetBundledHigherDimensionalInteractiveSceneCatalog(); + const HyperTwistTrainingPanelWidgetInternal::FDedicatedHigherDimensionalRuntimeOwnershipFacts + Magic120CellRuntimeOwnershipFacts = + HyperTwistTrainingPanelWidgetInternal:: + BuildDedicatedHigherDimensionalRuntimeOwnershipFacts( + TEXT("Magic120Cell"), + TEXT("magic120cell-cleanroom-runtime-activation") + ); + const HyperTwistTrainingPanelWidgetInternal::FDedicatedHigherDimensionalRuntimeOwnershipFacts + MagicCube5DRuntimeOwnershipFacts = + HyperTwistTrainingPanelWidgetInternal:: + BuildDedicatedHigherDimensionalRuntimeOwnershipFacts( + TEXT("MagicCube5D"), + TEXT("magiccube5d-cleanroom-runtime-activation") + ); Surface.bHigherDimensionalDedicatedFamilyReady = - HostCatalog.IsStructurallyValid() - && ViewContextCatalog.IsStructurallyValid() - && SessionCatalog.IsStructurallyValid() - && SceneCatalog.IsStructurallyValid(); + Magic120CellRuntimeOwnershipFacts.IsReady() + && MagicCube5DRuntimeOwnershipFacts.IsReady(); const HyperTwistTrainingPanelWidgetInternal::FProjectInputGroundworkFacts& InputGroundworkFacts = HyperTwistTrainingPanelWidgetInternal::GetProjectInputGroundworkFacts(); @@ -1116,12 +1224,15 @@ UHyperTwistTrainingPanelWidget::GetDisplayedControlInputReadinessInspectSurface( *Surface.KeyboardProfileName ); Surface.HigherDimensionalStatusLine = FString::Printf( - TEXT("Higher-dimensional: keyboard-driven slice/layer control %s | dedicated-family runtime catalogs %s | scene surfaces %d."), + TEXT("Higher-dimensional: keyboard-driven slice/layer control %s | %s | %s."), *HyperTwistTrainingPanelWidgetInternal::DescribeBool( Surface.bHigherDimensionalKeyboardInputReady), - *HyperTwistTrainingPanelWidgetInternal::DescribeBool( - Surface.bHigherDimensionalDedicatedFamilyReady), - SceneCatalog.SceneSurfaces.Num() + *HyperTwistTrainingPanelWidgetInternal:: + BuildDedicatedHigherDimensionalRuntimeOwnershipLine( + Magic120CellRuntimeOwnershipFacts), + *HyperTwistTrainingPanelWidgetInternal:: + BuildDedicatedHigherDimensionalRuntimeOwnershipLine( + MagicCube5DRuntimeOwnershipFacts) ); const FString MotionControllerFamilyLabels = InputGroundworkFacts.MotionControllerFamilies.Num() > 0 diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Tests/HyperTwistBrowserBridgeObjectTest.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Tests/HyperTwistBrowserBridgeObjectTest.cpp index 7cc5a66..dbc707a 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Tests/HyperTwistBrowserBridgeObjectTest.cpp +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Tests/HyperTwistBrowserBridgeObjectTest.cpp @@ -1124,10 +1124,23 @@ bool FHyperTwistTrainingPanelControlInputReadinessInspectSurfaceTest::RunTest( && Surface.ClassicCubeActionShortcutLine.Contains(TEXT("C cycle voice")) ); TestTrue( - TEXT("The control/input readiness surface must report the higher-dimensional keyboard lane and dedicated-family runtime catalogs."), + TEXT("The control/input readiness surface must report the higher-dimensional keyboard lane and explicit dedicated-family runtime ownership for both shipped families."), Surface.bHigherDimensionalKeyboardInputReady && Surface.bHigherDimensionalDedicatedFamilyReady ); + TestTrue( + TEXT("The control/input readiness surface must name the concrete Magic120Cell and MagicCube5D runtime ownership surfaces instead of only reporting broad catalog validity."), + Surface.HigherDimensionalStatusLine.Contains(TEXT("magic120cell-cleanroom-runtime-activation")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magic120cell/runtime-host-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magic120cell/dedicated-training-view-context-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magic120cell/dedicated-training-session-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magic120cell/interactive-scene-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("magiccube5d-cleanroom-runtime-activation")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magiccube5d/runtime-host-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magiccube5d/dedicated-training-view-context-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magiccube5d/dedicated-training-session-surface")) + && Surface.HigherDimensionalStatusLine.Contains(TEXT("phase6c/magiccube5d/interactive-scene-surface")) + ); TestTrue( TEXT("The control/input readiness surface must report the current project-level input groundwork."), Surface.bEnhancedInputProjectGroundworkPresent @@ -1204,6 +1217,11 @@ bool FHyperTwistCoachDashboardControlInputReadinessInspectSurfaceTest::RunTest( TEXT("The coach dashboard control/input readiness surface must retain the keyboard profile fact in its detail line."), Surface.DetailLine.Contains(TEXT("classic-wca-keyboard/v1")) ); + TestTrue( + TEXT("The coach dashboard control/input readiness surface must retain the concrete higher-dimensional family ownership ids in its detail line."), + Surface.DetailLine.Contains(TEXT("phase6c/magic120cell/runtime-host-surface")) + && Surface.DetailLine.Contains(TEXT("phase6c/magiccube5d/interactive-scene-surface")) + ); TestTrue( TEXT("The coach dashboard control/input readiness surface must retain the exact classic cube pointer and action rosters in its detail line."), Surface.DetailLine.Contains(TEXT("LMB clockwise")) @@ -1726,6 +1744,11 @@ bool FHyperTwistCoachDashboardControlSurfaceStructuredTextArtifactsTest::RunTest CoachDashboard, TEXT("CoachControlInputReadinessXr") ); + UTextBlock* ControlInputHigherDimensionalTextBlock = + HyperTwistBrowserBridgeObjectTestInternal::FindDashboardTextBlock( + CoachDashboard, + TEXT("CoachControlInputReadinessHigherDimensional") + ); TestNotNull( TEXT("The coach dashboard must build the control/input summary text row."), ControlInputSummaryTextBlock @@ -1746,6 +1769,10 @@ bool FHyperTwistCoachDashboardControlSurfaceStructuredTextArtifactsTest::RunTest TEXT("The coach dashboard must build the structured XR control/input row."), ControlInputXrTextBlock ); + TestNotNull( + TEXT("The coach dashboard must build the structured higher-dimensional control/input row."), + ControlInputHigherDimensionalTextBlock + ); if (ControlInputSummaryTextBlock != nullptr) { TestEqual( @@ -1786,6 +1813,21 @@ bool FHyperTwistCoachDashboardControlSurfaceStructuredTextArtifactsTest::RunTest ControlInputSurface.XrStatusLine ); } + if (ControlInputHigherDimensionalTextBlock != nullptr) + { + TestEqual( + TEXT("The structured higher-dimensional control/input row must mirror the inspect surface."), + ControlInputHigherDimensionalTextBlock->GetText().ToString(), + ControlInputSurface.HigherDimensionalStatusLine + ); + TestTrue( + TEXT("The structured higher-dimensional control/input row must expose the concrete dedicated-family runtime ownership ids."), + ControlInputHigherDimensionalTextBlock->GetText().ToString().Contains( + TEXT("phase6c/magic120cell/runtime-host-surface")) + && ControlInputHigherDimensionalTextBlock->GetText().ToString().Contains( + TEXT("phase6c/magiccube5d/interactive-scene-surface")) + ); + } UTextBlock* ControlSettingsSummaryTextBlock = HyperTwistBrowserBridgeObjectTestInternal::FindDashboardTextBlock( diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md index 7d35515..f946cc9 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md @@ -67,6 +67,15 @@ Use them with this posture: - once bootstrapped, analyzer execution stays on the HyperTwist-local `tools/sentrux/bin/` landing zone instead of reaching back into `VectorShell` during ordinary runs +- the current `2026-06-28` ownership follow-up narrows bootstrap posture + further again: + - `scripts/bootstrap-hypertwist-sentrux.sh` still honors an explicit + `HYPERTWIST_SENTRUX_BINARY` + - sibling-repo seed lookup is now opt-in behind + `HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP=1` instead of being the default + bootstrap path on a fresh machine + - ordinary HyperTwist analyzer operation therefore stays repo-owned by + default even during recovery/bootstrap flows Suggested loop: @@ -993,6 +1002,11 @@ Current audit note: - the public docs route now also exposes the real shared browser-auth method lineup so provider truth is no longer stranded only on the auth entry pages + - the next same-family public-manual continuation then widened that same + real browser-account method lineup into the homepage, pricing, download, + and support routes as well, so the high-traffic public decision pages no + longer require operators to infer provider truth only from the later + sign-in forms or deeper docs surfaces - cross-repo source truth for this packet stayed disciplined: - FamiliarOS current website auth posture remains intentionally narrower (`email/password` plus `GitHub`) @@ -1005,6 +1019,9 @@ Current audit note: - `npm --prefix website/server test -- --run src/__tests__/runtime-config.test.ts src/__tests__/auth-health.test.ts` - `npm --prefix website run test -- --run scripts/render-same-origin-bundle-lib.test.mjs` - `npm --prefix website/server run type-check` + - the same public-marketing suite now also explicitly protects the widened + homepage, pricing, download, and support auth-lineup sections alongside + the earlier docs/getting-started coverage - the same-family umbrella and structural gates also remained the target truth: - `scripts/run-hypertwist-web-surface-validation.sh` - `scripts/run-hypertwist-sentrux-source-only.sh` @@ -1080,9 +1097,98 @@ Current audit note: - `Quality: 6217` - `scripts/run-hypertwist-gitnexus-analyze.sh` - `16,312` nodes, `38,387` edges, `672` clusters, `300` flows +- `scripts/run-hypertwist-gitnexus-status.sh` +- `Status: up-to-date` + +## Latest public-manual route-atlas and tooling-ownership follow-up (`2026-06-28`) + +- the next same-family public/manual continuation then made the broader public + route set easier to use as a professional operator manual instead of leaving + page purpose mostly implicit in navigation labels: + - homepage, docs, and resources now share a first-party public route atlas + that explains what each major public page owns today + - the atlas keeps onboarding, launch authority, pricing, download, support, + release notes, and the legal/distribution routes readable as distinct + operator surfaces instead of one flatter marketing shell + - the public release-notes feed now also records that new route-atlas/manual + continuation directly +- the same packet also tightened HyperTwist-owned tooling posture again: + - `StepOnlyCardSection` and `SupportTopicDirectorySection` now live once in + `website/src/pages/public-page-helpers.tsx` instead of being duplicated + locally across the public marketing and launch-status modules + - `scripts/bootstrap-hypertwist-sentrux.sh` now keeps sibling-repo seed + lookup opt-in behind `HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP=1`, so the + normal bootstrap path does not silently drift back into cross-repo + analyzer ownership +- focused website validation for that continuation stayed green under: + - `npm --prefix website test -- --run src/__tests__/public-marketing-pages.test.tsx src/__tests__/app-route-tree.test.tsx` + - `2` test files passed + - `29` tests passed + - `npm --prefix website run type-check` + - `bash -n scripts/bootstrap-hypertwist-sentrux.sh scripts/run-hypertwist-sentrux-source-only.sh` +- the same-family umbrella, structural, and analysis gates then stayed green + again under: + - `scripts/run-hypertwist-sentrux-source-only.sh` + - `Quality: 6226` + - `All rules pass` + - `scripts/run-hypertwist-web-surface-validation.sh` + - website focused route/auth/release suite: `12` files, `74` tests passed + - website/server suite: `10` files, `36` tests passed + - website and `Content/Browser` production audits: `found 0 vulnerabilities` + - auth-server retained only the already-documented upstream + `supertokens-node -> nodemailer` residual + - `scripts/run-hypertwist-gitnexus-analyze.sh` + - `16,332` nodes, `38,486` edges, `674` clusters, `300` flows - `scripts/run-hypertwist-gitnexus-status.sh` - `Status: up-to-date` +## Latest dedicated-family runtime-ownership truth follow-up (`2026-06-28`) + +- the next same-family native/operator truth packet then tightened the shipped + control-input readiness seam so higher-dimensional readiness is no longer + inferred only from broad catalog validity: + - `UHyperTwistTrainingPanelWidget::GetDisplayedControlInputReadinessInspectSurface()` + now resolves the shipped `Magic120Cell` and `MagicCube5D` dedicated-family + host, view-context, session, and interactive-scene surfaces explicitly by + activation profile id + - the higher-dimensional readiness line now renders concrete family/runtime + ownership ids such as: + - `magic120cell-cleanroom-runtime-activation` + - `phase6c/magic120cell/runtime-host-surface` + - `phase6c/magiccube5d/interactive-scene-surface` + - the coach-dashboard structured higher-dimensional row now mirrors that + exact explicit ownership line instead of leaving the family/runtime truth + hidden behind broader readiness wording +- the maintained Windows validation lane then proved that exact-source state on + `C:\HyperTwist_worktrees\phase10validate`: + - synced exact touched files through + `scripts/run-hypertwist-remote-windows-file-sync.sh` + - remote Unreal rebuild through + `scripts/run-hypertwist-remote-unreal-build.sh` + - `Result: Succeeded` + - UnrealBuildTool `Total execution time: 109.14 seconds` + - focused remote automation through + `scripts/run-hypertwist-remote-unreal-automation-sequence.sh` + - all `3` exact-source filters passed: + - `HyperTwist.Browser.TrainingPanel.ControlInputReadinessInspectSurface` + - `HyperTwist.Browser.CoachDashboard.ControlInputReadinessInspectSurface` + - `HyperTwist.Browser.CoachDashboard.ControlSurfaceStructuredTextArtifacts` +- the HyperTwist-owned structural loop stayed healthy after that packet: + - `scripts/run-hypertwist-sentrux-source-only.sh` + - `Quality: 6226` + - all `7` rules pass + - `scripts/run-hypertwist-gitnexus-analyze.sh` + - retained runtime truthfully fell back to `npx -y gitnexus@latest` on this + Linux host because `@ladybugdb/core` still hits `ERR_DLOPEN_FAILED` with an + `invalid ELF header` + - bounded mirror refreshed at: + - `16,352` nodes + - `38,540` edges + - `679` clusters + - `300` flows + - `scripts/run-hypertwist-gitnexus-status.sh` + - bounded mirror `Status: up-to-date` + ## Latest native/public control-roster parity follow-up (`2026-06-25`) - the same-family native/operator continuity lane then aligned the shipped 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 939f9f4..6852721 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md @@ -145,7 +145,7 @@ Do not collapse those three tiers into one undifferentiated "features" voice. | Analytics/reporting surfaces | Implemented now | landed analytics/reporting packets | Reporting is real, but bounded to accepted retained slices. | | Rewritten training analytics and report reference grounding | Implemented now | `apache/echarts` retained permissive lane + first-party current code | Current live `Training Analytics` reference side includes four rewritten first-party targets grounded in retained `apache/echarts`: session outcome and progress reporting, analytics data-view and export, timing-trend history and overview interaction, and the optional richer explainer or sidecar boundary. This does not displace the landed `Phase 3R-C` first-party analytics/reporting owner or elevate `ecomfe/echarts-gl` and `ecomfe/zrender` beyond support-only sidecars. | | Browser/spatial/media adjunct surfaces | Implemented now | landed `three.js`, `react-three-fiber`, `xr`, `model-viewer`, `remotion` packets | These are implemented bounded families, and the current Phase 1 browser-runtime landing now includes a first-party authoritative `Content/Browser/index.html` shell, bundled-runtime upgrade path, committed clean-checkout plain-JS fallback runtime, embedded `UHyperTwistBrowserWidget` bridge, the `2026-06-19` runtime-ready queue hardening that retains outbound Unreal shell traffic until the browser runtime is ready, a same-day first-party `Browser Runtime Status` surface with shared boot-state ownership across bundled and fallback shells, a follow-on typed Unreal-side `browser-runtime-status` capture seam that retains the last valid runtime snapshot across unrelated later envelope traffic until explicit reset, a second follow-on typed Unreal-side `hypertwist-runtime-ready` capture seam that raises the original handshake payload out of raw JSON-only handling without changing queue flush behavior, a third same-day native/operator-facing status surface that consumes those typed seams inside Unreal while clearing retained runtime ownership on shell-authority change, a fourth same-day native training/operator diagnostics-panel continuation that wires that typed status ownership into `UHyperTwistTrainingPanelWidget` and the coach dashboard without making the dashboard inspect seam depend on stale rendered strings, a fifth same-day diagnostics-fidelity continuation that now carries bootstrap/runtime-ready timestamps, last command/shell-state receipt timestamps, and fallback reason through the same native operator/training seams, and a later `2026-06-23` control/input readiness continuation that projects shipped keyboard/input truth and unfinished XR/preferences truth through the same native training/operator surfaces. This still is not proof of unlimited browser-shell parity. | -| Native control/input readiness inspect surface | Implemented now | landed first-party `2026-06-23` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlInputReadinessInspectSurface`, including the shipped `classic-wca-keyboard/v1` mapping, exact classic-cube pointer, orbit, zoom, and action-shortcut truth, higher-dimensional dedicated-family runtime-catalog truth, project-level `EnhancedInput` plus motion-controller groundwork facts, immersive-presence contract presence, and explicit unfinished XR/runtime plus preferences truth. The rendered detail line now also carries the fixed desktop-hosted `No-Go` decision on native OpenXR/controller widening instead of leaving that truth stranded in a non-rendered follow-up field. A later same-day structured-boundary hardening follow-up then promoted that same XR/controller boundary into stable inspect-surface fields as well, including decision id `desktop-hosted-openxr-controller-widening-no-go` plus explicit reopen requirements for dedicated runtime owners, user-facing settings or rebinding ownership, and Windows packaged controller validation, so native operator automation no longer depends only on rendered prose to verify the boundary. The recovered primary reverse-SSH `localhost:22022` lane rebuilt maintained validation worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-23` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 1563.53 seconds`, and exported `Saved\AutomationReports\Browser-ControlInputReadiness-Verify\index.json` with all `16` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlInputReadinessInspectSurface` and `TrainingPanel.ControlInputReadinessInspectSurface`. A later same-day quality follow-up then moved the project-input-groundwork inspection behind that surface from raw text scanning into structured Unreal config reads, rebuilt the same maintained validation worktree again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 158.13 seconds`, and re-exported focused browser proof to `Saved\AutomationReports\Browser-ControlInputReadiness-StructuredConfig-Verify` with all `16` `HyperTwist.Browser.*` tests green again. The latest same-family truth-render follow-up on `2026-06-24` then rebuilt that same maintained validation root with `Result: Succeeded`, UnrealBuildTool `Total execution time: 172.52 seconds`, and exported `Saved\AutomationReports\Browser-XrNoGoRendered-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, explicitly covering both training-panel and coach-dashboard control-input detail-line visibility for the `No-Go` host decision. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control-input inspect surfaces alongside the sibling control/settings and control/profile seams. A later same-day `2026-06-25` parity follow-up then widened the same surface from general readiness truth into literal roster truth by rendering dedicated classic-cube pointer and action-shortcut lines, rebuilding the maintained validation root with `Result: Succeeded` at `5278.57 seconds` and exact-source rerun `70.76 seconds`, and exporting `Saved\AutomationReports\Browser-ControlRosterParity-Verify\index.json` with all `21` `HyperTwist.Browser.*` tests green, including both training-panel and coach-dashboard control-input surfaces plus the structured dashboard artifact seam. | +| Native control/input readiness inspect surface | Implemented now | landed first-party `2026-06-23` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlInputReadinessInspectSurface`, including the shipped `classic-wca-keyboard/v1` mapping, exact classic-cube pointer, orbit, zoom, and action-shortcut truth, higher-dimensional dedicated-family runtime ownership truth, project-level `EnhancedInput` plus motion-controller groundwork facts, immersive-presence contract presence, and explicit unfinished XR/runtime plus preferences truth. The rendered detail line now also carries the fixed desktop-hosted `No-Go` decision on native OpenXR/controller widening instead of leaving that truth stranded in a non-rendered follow-up field. A later same-day structured-boundary hardening follow-up then promoted that same XR/controller boundary into stable inspect-surface fields as well, including decision id `desktop-hosted-openxr-controller-widening-no-go` plus explicit reopen requirements for dedicated runtime owners, user-facing settings or rebinding ownership, and Windows packaged controller validation, so native operator automation no longer depends only on rendered prose to verify the boundary. The recovered primary reverse-SSH `localhost:22022` lane rebuilt maintained validation worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-23` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 1563.53 seconds`, and exported `Saved\AutomationReports\Browser-ControlInputReadiness-Verify\index.json` with all `16` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlInputReadinessInspectSurface` and `TrainingPanel.ControlInputReadinessInspectSurface`. A later same-day quality follow-up then moved the project-input-groundwork inspection behind that surface from raw text scanning into structured Unreal config reads, rebuilt the same maintained validation worktree again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 158.13 seconds`, and re-exported focused browser proof to `Saved\AutomationReports\Browser-ControlInputReadiness-StructuredConfig-Verify` with all `16` `HyperTwist.Browser.*` tests green again. The latest same-family truth-render follow-up on `2026-06-24` then rebuilt that same maintained validation root with `Result: Succeeded`, UnrealBuildTool `Total execution time: 172.52 seconds`, and exported `Saved\AutomationReports\Browser-XrNoGoRendered-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, explicitly covering both training-panel and coach-dashboard control-input detail-line visibility for the `No-Go` host decision. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control-input inspect surfaces alongside the sibling control/settings and control/profile seams. A later same-day `2026-06-25` parity follow-up then widened the same surface from general readiness truth into literal roster truth by rendering dedicated classic-cube pointer and action-shortcut lines, rebuilding the maintained validation root with `Result: Succeeded` at `5278.57 seconds` and exact-source rerun `70.76 seconds`, and exporting `Saved\AutomationReports\Browser-ControlRosterParity-Verify\index.json` with all `21` `HyperTwist.Browser.*` tests green, including both training-panel and coach-dashboard control-input surfaces plus the structured dashboard artifact seam. The latest same-family `2026-06-28` ownership-truth follow-up then tightened higher-dimensional readiness again by resolving the shipped `Magic120Cell` and `MagicCube5D` dedicated-family host, view-context, session, and interactive-scene surfaces explicitly by activation profile id instead of treating broad catalog validity as equivalent proof. That exact-source-state follow-up rebuilt maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 109.14 seconds`, then passed all three focused browser filters `TrainingPanel.ControlInputReadinessInspectSurface`, `CoachDashboard.ControlInputReadinessInspectSurface`, and `CoachDashboard.ControlSurfaceStructuredTextArtifacts`, so both the inspect surfaces and the rendered structured dashboard row now keep concrete family ownership ids such as `phase6c/magic120cell/runtime-host-surface` and `phase6c/magiccube5d/interactive-scene-surface` visible to operators. | | Native control/settings ownership inspect surface | Implemented now | landed first-party `2026-06-24` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlSettingsOwnershipInspectSurface`, including the shipped viewer camera-settings owner `tool/camera-settings`, the immersive-presence control contract, dedicated-family `magic120cell-focus-view-profile` and `magiccube5d-projection-view-profile` view ownership, higher-dimensional selector ownership, persisted generated-mode selector recall when a structurally valid launch request is present, and explicit unfinished XR/controller rebinding truth. A later same-day structured-boundary hardening follow-up then carried the same `desktop-hosted-openxr-controller-widening-no-go` decision id plus the explicit reopen requirements for dedicated runtime owners, polished user-facing settings or rebinding ownership, and Windows packaged controller validation into this surface’s structured state as well, so control-settings diagnostics no longer have to prove the boundary only by substring matching their rendered detail line. The same primary reverse-SSH `localhost:22022` lane rebuilt maintained validation worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-24` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4331.11 seconds`, and then exported `Saved\AutomationReports\Browser-ControlSettingsOwnership-Verify\index.json` with all `18` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlSettingsOwnershipInspectSurface`, `TrainingPanel.ControlSettingsOwnershipInspectSurface`, and the previously landed runtime plus control/input inspect seams. A later same-day selector-recall hardening follow-up then rebuilt that same maintained validation root again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4084.77 seconds`, and exported `Saved\AutomationReports\Browser-SelectorRecall-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing, keeping the current control/settings proof aligned with the latest repository-backed selector-recall behavior. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control/settings inspect surfaces alongside the sibling control/input and control/profile seams. | | Native control/profile roster inspect surface | Implemented now | landed first-party `2026-06-24` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlProfileRosterInspectSurface`, keeping the actually shipped selectable native roster visible: classic keyboard profile `classic-wca-keyboard/v1` with `18` bindings plus the exact classic move roster, immersive-presence contract `immersive-training-presence-control-contract` with `3` intensity plus `3` reduced-distraction presets, dedicated-family `Magic120Cell` runtime/view ids `magic120cell-runtime-profile` and `magic120cell-focus-view-profile`, dedicated-family `MagicCube5D` runtime/view ids `magiccube5d-runtime-profile` and `magiccube5d-projection-view-profile`, the current `4` selectors in each dedicated-family roster, persisted generated-mode selector recall when a structurally valid launch request is present, and explicit unfinished controller rebinding truth. The rendered roster boundary now also states the fixed desktop-hosted `No-Go` decision on native OpenXR/controller widening instead of sounding like a merely pending generic settings packet. A later same-day structured-boundary hardening follow-up then carried the same `desktop-hosted-openxr-controller-widening-no-go` decision id plus its explicit reopen requirements into the roster surface’s structured state too, so native operator automation can prove the shipped roster boundary without depending only on rendered text. After hash-syncing the touched type/training/dashboard/test files into maintained validation worktree `C:\HyperTwist_worktrees\phase10validate`, the same primary reverse-SSH `localhost:22022` lane rebuilt the widened slice on `2026-06-24` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 3606.23 seconds`, then exported `Saved\AutomationReports\Browser-ControlProfileRoster-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlProfileRosterInspectSurface` and `TrainingPanel.ControlProfileRosterInspectSurface`. A later same-day selector-recall hardening follow-up then rebuilt that same maintained validation root again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4084.77 seconds`, and exported `Saved\AutomationReports\Browser-SelectorRecall-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing again, now explicitly covering imported-request fallback plus active-deck precedence for repository-backed selector recall inside the training-panel and coach-dashboard roster surface. The latest same-family truth-render follow-up on `2026-06-24` then rebuilt that same maintained validation root with `Result: Succeeded`, UnrealBuildTool `Total execution time: 172.52 seconds`, and exported `Saved\AutomationReports\Browser-XrNoGoRendered-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, explicitly covering the roster detail-line visibility of the same fixed `No-Go` boundary. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control/profile inspect surfaces alongside the sibling control/input and control/settings seams. A later same-day `2026-06-25` parity follow-up then added the literal shipped classic move-roster line to that surface, mirrored it into dedicated coach-dashboard structured rows, rebuilt the maintained validation root with `Result: Succeeded` at `5278.57 seconds` and exact-source rerun `70.76 seconds`, and exported `Saved\AutomationReports\Browser-ControlRosterParity-Verify\index.json` with all `21` `HyperTwist.Browser.*` tests green, including both training-panel and coach-dashboard control/profile surfaces plus the structured dashboard artifact seam. | | Native XR project-plugin posture inspect truth | Implemented now | landed first-party `2026-06-25` browser/native operator continuation | All three native control/input, control/settings, and control/profile inspect surfaces now expose the current project `OpenXR` plugin enabled/disabled fact in both structured state and rendered operator lines, so project-level motion-controller groundwork no longer masquerades as an enabled `OpenXR` shipping posture. The same primary reverse-SSH `localhost:22022` lane rebuilt the exact-source state on maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 99.38 seconds`, then exported `Saved\AutomationReports\Browser-XrPluginProjectPosture-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green across the training-panel and coach-dashboard input/settings/profile seams. | @@ -268,8 +268,8 @@ 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, legal routes, a dedicated `/getting-started` onboarding surface, and a dedicated `/launch-status` authority surface. 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, the dedicated getting-started route, the dedicated launch-status 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 public manual continuation now also adds a direct reusable surface-choice guide across the homepage, About, Pricing, Download, and Support pages so operators no longer have to infer from the larger surface matrix alone when they should stay on the public web surface, move into the protected dashboard, or move into the packaged desktop runtime. A later same-family continuation then propagated that same guide through the remaining public feature/docs/resources/changelog/legal pages as well, so the whole public site now preserves one consistent browser-versus-protected-versus-desktop handoff story instead of leaving those lower-traffic surfaces on older implicit wording. A further same-day manual-clarity continuation then added a reusable direct comparison section across the homepage, About, Docs, and Download routes explaining why the website remains necessary, where it is intentionally narrower than the simulator, why the native Unreal runtime stays primary, and how the current keyboard or mouse versus unfinished XR/controller truth should be read. The latest same-family parity follow-up then widened that exact browser-versus-desktop reality section into Pricing and Resources as well, so commercial and reference-heavy public routes no longer rely only on the lighter surface-choice guide when explaining what stays native and where the current XR/controller boundary still begins. The next adjacent parity follow-up then extended the same direct comparison into the public Feature atlas and Support routes as well, so the remaining major public operator-facing surfaces no longer fall back to the lighter guide alone when capability review or recovery work needs the sharper website-versus-native split. A later same-family continuity follow-up then widened the shared release-decision guide into the remaining public legal/notices routes too, so open-source notices, privacy, terms, and shipping/payment now also tell the operator whether the next honest move is protected desktop access, pricing/provisioning, protected browser/account continuity, or notices/source follow-through instead of leaving those pages on the older lighter handoff only. 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. A later same-family quickstart/manual continuation then added a reusable first serious-session guide across homepage, docs, and download so operators can see the real path from release-target choice through desktop-link pairing, first native verification, higher-dimensional verification, and the current XR/controller `No-Go` boundary in one place instead of reconstructing that flow from scattered adjacent sections. That same onboarding/manual packet is now also anchored at a dedicated public `/getting-started` route so the shortest complete browser-to-desktop first-session path is canonical, crawlable, and easier to hand off than the broader site sections alone. The next adjacent launch-authority continuation then did the same for rollout truth through a dedicated public `/launch-status` route, giving preview-versus-launch posture, rollout blockers, packaged proof, and release-reference follow-through one canonical public authority surface instead of leaving that lane distributed across pricing and compact status banners alone. | -| 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 shared-auth lane now also carries end-to-end optional provider parity for GitHub, Google, and bounded ORCID sign-in: the auth server owns the ORCID custom-provider path, the same-origin bundle emits matching ORCID frontend/server env truth, auth-health reports ORCID readiness alongside the other providers, and the public docs route now exposes the current browser-account method lineup instead of leaving provider truth visible only on the form pages. 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 overview and protected download center now also mirror the same launch-readiness, operator-access, and studio-rollout help lanes as the public support/manual surface, but translate those actions into direct signed-in dashboard, downloads, browser-access, account, notices, pricing, and release-notes targets instead of sending the operator back through anonymous auth detours. A later same-family parity follow-up then added the same blunt browser-versus-desktop reality explanation to the protected dashboard, protected downloads, and browser-access routes as well, so sign-in no longer makes the product boundary or unfinished XR/controller truth less explicit than the public manual. The next adjacent parity follow-up then extended that same compact reality panel into the protected account and notices routes too, so entitlement review and distribution/compliance work no longer soften the browser-support versus native-simulator split after sign-in. The auth entry pages now also render the same browser-versus-desktop truth before sign-in is even complete, so login and register no longer rely only on next-step routing plus later dashboard surfaces to explain what stays native and where the current XR/controller boundary still begins. A later same-family protected-shell continuation then widened signed-in auth truth itself, so the dashboard and account routes now surface the auth method, current provider lineup, shared-auth readiness, runtime origins, cookie/public-origin posture, fallback state, and deployment diagnostics directly instead of collapsing that truth down to a thin stack label. 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. The next adjacent protected-shell launch-authority continuation then added a dedicated signed-in `/app/launch-status` route, so launch posture, rollout blockers, release references, packaged proof, and signed-in next actions no longer collapse back to a single overview panel once account context exists. The follow-through continuation after that then threaded the same signed-in launch-status route back through protected release-action cards, release-reference panels, and the browser-access, download, account, and notices surfaces, so rollout authority remains attached to the surrounding signed-in operator shell instead of becoming an isolated page. 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. | +| 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, legal routes, a dedicated `/getting-started` onboarding surface, and a dedicated `/launch-status` authority surface. 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, the dedicated getting-started route, the dedicated launch-status 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 public manual continuation now also adds a direct reusable surface-choice guide across the homepage, About, Pricing, Download, and Support pages so operators no longer have to infer from the larger surface matrix alone when they should stay on the public web surface, move into the protected dashboard, or move into the packaged desktop runtime. A later same-family continuation then propagated that same guide through the remaining public feature/docs/resources/changelog/legal pages as well, so the whole public site now preserves one consistent browser-versus-protected-versus-desktop handoff story instead of leaving those lower-traffic surfaces on older implicit wording. A further same-day manual-clarity continuation then added a reusable direct comparison section across the homepage, About, Docs, and Download routes explaining why the website remains necessary, where it is intentionally narrower than the simulator, why the native Unreal runtime stays primary, and how the current keyboard or mouse versus unfinished XR/controller truth should be read. The latest same-family parity follow-up then widened that exact browser-versus-desktop reality section into Pricing and Resources as well, so commercial and reference-heavy public routes no longer rely only on the lighter surface-choice guide when explaining what stays native and where the current XR/controller boundary still begins. The next adjacent parity follow-up then extended the same direct comparison into the public Feature atlas and Support routes as well, so the remaining major public operator-facing surfaces no longer fall back to the lighter guide alone when capability review or recovery work needs the sharper website-versus-native split. A later same-family continuity follow-up then widened the shared release-decision guide into the remaining public legal/notices routes too, so open-source notices, privacy, terms, and shipping/payment now also tell the operator whether the next honest move is protected desktop access, pricing/provisioning, protected browser/account continuity, or notices/source follow-through instead of leaving those pages on the older lighter handoff only. 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. A later same-family quickstart/manual continuation then added a reusable first serious-session guide across homepage, docs, and download so operators can see the real path from release-target choice through desktop-link pairing, first native verification, higher-dimensional verification, and the current XR/controller `No-Go` boundary in one place instead of reconstructing that flow from scattered adjacent sections. That same onboarding/manual packet is now also anchored at a dedicated public `/getting-started` route so the shortest complete browser-to-desktop first-session path is canonical, crawlable, and easier to hand off than the broader site sections alone. The next adjacent launch-authority continuation then did the same for rollout truth through a dedicated public `/launch-status` route, giving preview-versus-launch posture, rollout blockers, packaged proof, and release-reference follow-through one canonical public authority surface instead of leaving that lane distributed across pricing and compact status banners alone. The next same-family shared-auth manual continuation then widened the real browser-account method lineup beyond the auth entry forms and deeper docs surfaces into the homepage, pricing, download, and support routes too, so the public pages where operators actually decide to sign in, buy access, or recover access posture now expose the real provider lineup directly. The latest same-family manual continuation now also adds a shared public route atlas across homepage, docs, and resources so each major public page explains its exact job in the broader operator/distribution manual instead of leaving page purpose mostly implicit in navigation alone. | +| 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 shared-auth lane now also carries end-to-end optional provider parity for GitHub, Google, and bounded ORCID sign-in: the auth server owns the ORCID custom-provider path, the same-origin bundle emits matching ORCID frontend/server env truth, auth-health reports ORCID readiness alongside the other providers, and the public docs route now exposes the current browser-account method lineup instead of leaving provider truth visible only on the form pages. The surrounding public decision surfaces now also mirror that same provider-lineup truth on homepage, pricing, download, and support, so shared-auth reality is not hidden until operators reach either the auth forms or the deeper manual. 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 overview and protected download center now also mirror the same launch-readiness, operator-access, and studio-rollout help lanes as the public support/manual surface, but translate those actions into direct signed-in dashboard, downloads, browser-access, account, notices, pricing, and release-notes targets instead of sending the operator back through anonymous auth detours. A later same-family parity follow-up then added the same blunt browser-versus-desktop reality explanation to the protected dashboard, protected downloads, and browser-access routes as well, so sign-in no longer makes the product boundary or unfinished XR/controller truth less explicit than the public manual. The next adjacent parity follow-up then extended that same compact reality panel into the protected account and notices routes too, so entitlement review and distribution/compliance work no longer soften the browser-support versus native-simulator split after sign-in. The auth entry pages now also render the same browser-versus-desktop truth before sign-in is even complete, so login and register no longer rely only on next-step routing plus later dashboard surfaces to explain what stays native and where the current XR/controller boundary still begins. A later same-family protected-shell continuation then widened signed-in auth truth itself, so the dashboard and account routes now surface the auth method, current provider lineup, shared-auth readiness, runtime origins, cookie/public-origin posture, fallback state, and deployment diagnostics directly instead of collapsing that truth down to a thin stack label. 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. The next adjacent protected-shell launch-authority continuation then added a dedicated signed-in `/app/launch-status` route, so launch posture, rollout blockers, release references, packaged proof, and signed-in next actions no longer collapse back to a single overview panel once account context exists. The follow-through continuation after that then threaded the same signed-in launch-status route back through protected release-action cards, release-reference panels, and the browser-access, download, account, and notices surfaces, so rollout authority remains attached to the surrounding signed-in operator shell instead of becoming an isolated page. 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. 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 protected download center now also mirrors the same three help-topic lanes used by the public support/manual surface, but with direct signed-in actions for downloads, dashboard, account, browser access, notices, and release notes so entitled operators can stay inside the protected rollout lane once auth has already succeeded. 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. | diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/PRD.md b/docs/v6_5_deep_manual_pack/HyperTwist/PRD.md index 81db0db..76fed76 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/PRD.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/PRD.md @@ -120,6 +120,12 @@ mouse/touch flows, higher-dimensional keyboard interaction, and project-level motion-control groundwork, but HyperTwist should not yet claim a fully finished shipping VR/controller/preferences lane without a dedicated completion packet. +The latest native/operator truth follow-up on `2026-06-28` also tightened the +higher-dimensional side of that statement: native control-input readiness now +proves shipped `Magic120Cell` and `MagicCube5D` host, view-context, session, +and interactive-scene ownership explicitly by activation profile id instead of +only implying readiness from broad runtime-catalog validity. + Canonical audit note: - `C:\HyperTwist\docs\ops\HYPERTWIST_UNREAL_INPUT_AND_XR_COMPLETENESS_AUDIT_2026-06-22.md` diff --git a/scripts/bootstrap-hypertwist-sentrux.sh b/scripts/bootstrap-hypertwist-sentrux.sh index 0f88917..398c0c2 100644 --- a/scripts/bootstrap-hypertwist-sentrux.sh +++ b/scripts/bootstrap-hypertwist-sentrux.sh @@ -15,14 +15,16 @@ usage() { Usage: scripts/bootstrap-hypertwist-sentrux.sh [--if-missing] -Materializes a repo-local sentrux binary under tools/sentrux/bin/ using the -best available retained seed on this machine. +Materializes a repo-local sentrux binary under tools/sentrux/bin/ while keeping +ordinary HyperTwist runs repo-owned by default. Resolution order: 1. HYPERTWIST_SENTRUX_BINARY if explicitly provided - 2. existing VectorShell Linux build artifact - 3. local VectorShell source build via cargo - 4. local ScriptoriumAI Windows binary + 2. optional sibling-repo seeds, but only when + HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP=1 + - existing VectorShell Linux build artifact + - local VectorShell source build via cargo + - local ScriptoriumAI Windows binary The resulting analyzer then lives under HyperTwist-owned tools/sentrux/bin/ so later runs do not need to execute directly from sibling repos. @@ -66,22 +68,26 @@ if [[ -n "${HYPERTWIST_SENTRUX_BINARY:-}" && -x "${HYPERTWIST_SENTRUX_BINARY}" ] exit 0 fi -if [[ -x "$vector_sentrux_binary" ]]; then - copy_binary "$vector_sentrux_binary" "$dest_linux" - exit 0 -fi +allow_sibling_bootstrap="${HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP:-0}" -if command -v cargo >/dev/null 2>&1 && [[ -f "$vector_sentrux_manifest" ]]; then - cargo build --quiet --release --manifest-path "$vector_sentrux_manifest" --bin sentrux +if [[ "$allow_sibling_bootstrap" == "1" ]]; then if [[ -x "$vector_sentrux_binary" ]]; then copy_binary "$vector_sentrux_binary" "$dest_linux" exit 0 fi -fi -if [[ -f "$scriptorium_sentrux_windows" ]]; then - copy_binary "$scriptorium_sentrux_windows" "$dest_windows" - exit 0 + if command -v cargo >/dev/null 2>&1 && [[ -f "$vector_sentrux_manifest" ]]; then + cargo build --quiet --release --manifest-path "$vector_sentrux_manifest" --bin sentrux + if [[ -x "$vector_sentrux_binary" ]]; then + copy_binary "$vector_sentrux_binary" "$dest_linux" + exit 0 + fi + fi + + if [[ -f "$scriptorium_sentrux_windows" ]]; then + copy_binary "$scriptorium_sentrux_windows" "$dest_windows" + exit 0 + fi fi cat >&2 <&2 + echo "Unable to locate sentrux. Provide HYPERTWIST_SENTRUX_BINARY, place a repo-local sentrux binary under $repo_root/tools/sentrux/bin, add sentrux to PATH, or run scripts/bootstrap-hypertwist-sentrux.sh (set HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP=1 only if you intentionally want legacy sibling-repo seeding on this machine)." >&2 exit 1 } diff --git a/website/README.md b/website/README.md index da28cc9..d74589b 100644 --- a/website/README.md +++ b/website/README.md @@ -6,6 +6,7 @@ First-party `hypertwist.app` surface for HyperTwist: - dedicated public `/getting-started` onboarding route for the first real browser-to-desktop operator journey - dedicated public `/launch-status` route for the canonical preview-versus-launch rollout checklist - public feature-atlas route for current capability and boundary truth +- shared public-manual route atlas across homepage, docs, and resources so each major public page explains its exact job - browser-facing operator/account dashboard - protected launch-status, browser-access, account, and notices routes backed by live auth-health and release-manifest authority - shared SuperTokens auth posture reused from the FamiliarOS and ScriptoriumAI website lane @@ -63,6 +64,13 @@ manual: - the docs and resources pages now also carry a practical simulator-use manual for recognition, replay, higher-dimensional runtime ownership, and operator diagnostics without overclaiming browser or VR parity +- the public browser-account method lineup is now also visible on the + homepage, pricing, download, support, docs, and getting-started routes so + high-traffic decision pages no longer hide provider truth until the auth + entry forms +- the homepage, docs, and resources surfaces now also share a route atlas that + explains what each major public page owns, so the site reads more like a + professional operator manual than a flatter brochure shell - the about, feature-atlas, resources, and docs surfaces now also expose a concrete shipped control-profile and settings roster for the desktop lane, including the current `classic-wca-keyboard/v1` profile, scenic immersive @@ -157,6 +165,16 @@ the one remaining accepted browser-build warning is the current upstream `@khronosgroup/gltf-viewer` `mikktspace_bg.wasm` Vite asset-resolution message, which does not currently break the owned shell verification or production build. +Repo-owned structural-tool posture: + +- `scripts/run-hypertwist-sentrux-source-only.sh` still prefers + `HYPERTWIST_SENTRUX_BINARY`, repo-local `./sentrux` or `./sentrux.exe`, then + `tools/sentrux/bin/`, then `PATH` +- `scripts/bootstrap-hypertwist-sentrux.sh` now keeps sibling-repo seed lookup + opt-in behind `HYPERTWIST_ALLOW_SIBLING_SENTRUX_BOOTSTRAP=1`, so ordinary + HyperTwist analyzer recovery does not silently drift back into cross-repo + ownership + Latest auth-shell hardening follow-up on `2026-06-24`: - the website now carries a first-party HyperTwist auth-shell backdrop module @@ -250,6 +268,20 @@ Latest protected control-roster follow-up later on `2026-06-24`: - `41` test files passed - `168` tests passed +Latest browser-versus-desktop reality follow-up on `2026-06-28`: + +- the shared browser-versus-desktop public-manual copy now says more directly + why the browser lane is narrower instead of relying only on abstract + boundary language: + - low-latency simulator input remains native + - packaged runtime ownership remains native + - higher-dimensional scene execution remains native + - any future serious controller or VR completion remains native +- that wording now propagates automatically anywhere the shared + `BrowserDesktopRealitySection` is rendered, including homepage, about, + features, pricing, docs, resources, launch-status, and the mirrored + protected operator surfaces + Latest first-session quickstart/manual follow-up on `2026-06-27`: - the public and protected manual lane now explains the first real operator diff --git a/website/src/__tests__/public-marketing-pages.test.tsx b/website/src/__tests__/public-marketing-pages.test.tsx index 03158db..f7bc59e 100644 --- a/website/src/__tests__/public-marketing-pages.test.tsx +++ b/website/src/__tests__/public-marketing-pages.test.tsx @@ -270,6 +270,12 @@ describe('public marketing pages', () => { expect(screen.getByText('How the release lane works')).toBeTruthy() expect(screen.getByText('Why HyperTwist keeps both a website and a desktop runtime')).toBeTruthy() expect(screen.getByText('Why the browser is intentionally narrower')).toBeTruthy() + expect(screen.getByRole('heading', { name: 'Browser account access methods' })).toBeTruthy() + expect(screen.getByText('Auth methods ready')).toBeTruthy() + expect(screen.getByText('Email and password')).toBeTruthy() + expect(screen.getByText('GitHub sign-in')).toBeTruthy() + expect(screen.getByText('ORCID sign-in')).toBeTruthy() + expect(screen.queryByText('Google sign-in')).toBeNull() expect(screen.getByText('Choose the right HyperTwist surface')).toBeTruthy() const downloadDecisionGuideHeading = screen.getByRole('heading', { name: 'Choose the next release move' }) const downloadDecisionGuideSection = downloadDecisionGuideHeading.closest('section') @@ -449,6 +455,12 @@ describe('public marketing pages', () => { expect(screen.getByText('Current input, XR, and settings truth')).toBeTruthy() expect(screen.getAllByText('Paddle webhook secret: missing').length).toBeGreaterThan(0) expect(screen.getAllByText(/public auth runtime posture/i).length).toBeGreaterThan(0) + expect(screen.getByRole('heading', { name: 'Browser account access methods' })).toBeTruthy() + expect(screen.getByText('Auth methods ready')).toBeTruthy() + expect(screen.getByText('Email and password')).toBeTruthy() + expect(screen.getByText('GitHub sign-in')).toBeTruthy() + expect(screen.getByText('ORCID sign-in')).toBeTruthy() + expect(screen.queryByText('Google sign-in')).toBeNull() expect(screen.getByText('Current packaged desktop proof')).toBeTruthy() expect(screen.getByText('Packaged validation passed')).toBeTruthy() const homeDecisionGuideHeading = screen.getByRole('heading', { name: 'Choose the next release move' }) @@ -461,6 +473,8 @@ describe('public marketing pages', () => { expect(screen.getByText('How a real first session flows')).toBeTruthy() expect(screen.getByText('What the first serious session should look like')).toBeTruthy() expect(screen.getByText('1. Resolve access and choose the right build')).toBeTruthy() + expect(screen.getByText('Which public page should you open next?')).toBeTruthy() + expect(screen.getByText('Launch status')).toBeTruthy() expect(screen.getByText('Choose the right HyperTwist surface')).toBeTruthy() expect(screen.getByText('Move into the protected dashboard')).toBeTruthy() expect(screen.getAllByText('Current surface authority map').length).toBeGreaterThan(0) @@ -892,6 +906,12 @@ describe('public marketing pages', () => { expect(screen.getByText('Why HyperTwist keeps both a website and a desktop runtime')).toBeTruthy() expect(screen.getByText('Use the desktop runtime')).toBeTruthy() expect(screen.getByText('Current input, XR, and settings truth')).toBeTruthy() + expect(screen.getByRole('heading', { name: 'Browser account access methods' })).toBeTruthy() + expect(screen.getByText('Auth methods ready')).toBeTruthy() + expect(screen.getByText('Email and password')).toBeTruthy() + expect(screen.getByText('GitHub sign-in')).toBeTruthy() + expect(screen.getByText('ORCID sign-in')).toBeTruthy() + expect(screen.queryByText('Google sign-in')).toBeNull() expect(screen.getByText('Shows account, auth, billing, and release readiness posture')).toBeTruthy() expect(screen.getByText('Owns recognition, replay, coaching, and packaged training behavior')).toBeTruthy() expect(screen.getByText('Commercial distribution doctrine')).toBeTruthy() @@ -983,6 +1003,12 @@ describe('public marketing pages', () => { expect(screen.getByText('Why HyperTwist keeps both a website and a desktop runtime')).toBeTruthy() expect(screen.getByText('Why the browser is intentionally narrower')).toBeTruthy() expect(screen.getByText('Browser and desktop responsibilities')).toBeTruthy() + expect(screen.getByRole('heading', { name: 'Current browser sign-in methods' })).toBeTruthy() + expect(screen.getByText('Auth methods ready')).toBeTruthy() + expect(screen.getByText('Email and password')).toBeTruthy() + expect(screen.getByText('GitHub sign-in')).toBeTruthy() + expect(screen.getByText('ORCID sign-in')).toBeTruthy() + expect(screen.queryByText('Google sign-in')).toBeNull() expect(screen.getByText('Shows account, auth, billing, and release readiness posture')).toBeTruthy() expect(screen.getByText('Support lanes')).toBeTruthy() expect(screen.getByText('Support topic quick routes')).toBeTruthy() @@ -1129,6 +1155,8 @@ describe('public marketing pages', () => { expect(screen.getByText('Deployment readiness snapshot')).toBeTruthy() expect(screen.getAllByText('XR groundwork exists, but the full VR lane is not finished').length).toBeGreaterThan(0) expect(screen.getByText('Higher-dimensional runtime ownership')).toBeTruthy() + expect(screen.getByText('Public manual route atlas')).toBeTruthy() + expect(screen.getByText('Shipping & payment')).toBeTruthy() expect(screen.getByText('Choose the next release move')).toBeTruthy() expect(screen.getByText('Need account state, pairing, or protected browser follow-through?')).toBeTruthy() expect(screen.getByText(/The web lane is not superfluous/i)).toBeTruthy() @@ -1291,6 +1319,8 @@ describe('public marketing pages', () => { expect(screen.getByText(/R scramble, H hint, Enter submit, F mode, V hold-to-talk, C cycle voice/i)).toBeTruthy() expect(screen.getAllByText(/latest persisted generated-mode selector posture is available for recall/i).length).toBeGreaterThan(0) expect(screen.getByText('Feature-registry-backed wording only')).toBeTruthy() + expect(screen.getByText('Documentation and route atlas')).toBeTruthy() + expect(screen.getByText('Open-source notices')).toBeTruthy() expect(screen.getByText('Browser auth degraded or mixed')).toBeTruthy() expect(screen.getByText('Release authority temporarily unavailable')).toBeTruthy() expect(screen.getByText('Current packaged desktop proof')).toBeTruthy() diff --git a/website/src/pages/public-page-helpers.tsx b/website/src/pages/public-page-helpers.tsx index d18f2a0..455f406 100644 --- a/website/src/pages/public-page-helpers.tsx +++ b/website/src/pages/public-page-helpers.tsx @@ -3,6 +3,7 @@ import { useMemo } from 'react' import { useQuery } from '@tanstack/react-query' import { Link } from 'react-router-dom' import { getReleaseManifest } from '../auth/auth-api' +import { BrowserAuthMethodsGuide } from '../components/ui/BrowserAuthMethodsGuide' import { ReleaseValidationSummary } from '../components/ui/ReleaseValidationSummary' import type { ReleaseManifestPlatformView, ReleaseManifestView } from '../release-manifest' import { resolveReleaseCommerceView, resolveReleaseManifestView } from '../release-manifest' @@ -19,6 +20,7 @@ import { browserDesktopRealityCards, deliverySurfaceCards, operatorDesktopQuickstartCards, + publicManualRouteAtlasCards, } from '../site-data' import { buildLoginPath, @@ -151,6 +153,16 @@ export function Section({ ) } +type StepOnlyCard = { + title: string + steps?: readonly string[] + bullets?: readonly string[] +} + +type SupportTopicCard = (typeof supportTopicDirectory)[number] + +type PublicManualRouteAtlasCard = (typeof publicManualRouteAtlasCards)[number] + export function usePublicReleaseManifestView(queryScope: string) { const releaseManifestQuery = useQuery({ queryKey: ['release-manifest', queryScope], @@ -338,6 +350,137 @@ export function OperatorDesktopQuickstartSection({ ) } +export function StepOnlyCardSection({ + title, + description, + cards, +}: { + title: string + description?: string + cards: readonly StepOnlyCard[] +}) { + return ( +
+
+ {cards.map((card) => ( +
+

{card.title}

+
    + {(card.steps ?? card.bullets ?? []).map((step) => ( +
  • {step}
    • + ))} +
+
+ ))} +
+
+ ) +} + +export function SupportTopicDirectorySection({ + title, + description, + topics, + selectedTopicKey, +}: { + title: string + description?: string + topics: readonly SupportTopicCard[] + selectedTopicKey?: string | null +}) { + return ( +
+
+ {topics.map((topic) => { + const isSelected = selectedTopicKey === topic.topicKey + + return ( +
+ {isSelected ?

Selected help lane

: null} +

{topic.title}

+

{topic.description}

+

Next steps

+
    + {topic.steps.map((step) => ( +
  • {step}
    • + ))} +
+

Manual and route focus

+
    + {topic.routeFocus.map((item) => ( +
  • {item}
    • + ))} +
+
+ {topic.actions.map((action) => ( + + {action.label} + + ))} +
+
+ ) + })} +
+
+ ) +} + +export function PublicManualRouteAtlasSection({ + title = 'Public manual route atlas', + description = 'Each public page has a different job inside HyperTwist. This atlas keeps the route set readable as a real manual rather than a flat marketing shell.', + cards = publicManualRouteAtlasCards, + limit, +}: { + title?: string + description?: string + cards?: readonly PublicManualRouteAtlasCard[] + limit?: number +}) { + const visibleCards = typeof limit === 'number' ? cards.slice(0, limit) : cards + + return ( +
+
+ {visibleCards.map((card) => ( +
+

{card.route}

+

{card.title}

+

{card.description}

+
    + {card.bullets.map((bullet) => ( +
  • {bullet}
    • + ))} +
+
+ + Open {card.title} + +
+
+ ))} +
+
+ ) +} + +export function BrowserAuthMethodsSection({ + title = 'Browser account access methods', + description = 'The public browser-account provider lineup should stay visible wherever operators are being asked to sign in, buy access, pair the desktop runtime, or recover access posture.', +}: { + title?: string + description?: string +}) { + return ( +
+ +
+ ) +} + export function PublicPackagedDesktopProofSection({ platform, actions = [], diff --git a/website/src/pages/public-pages-commerce.tsx b/website/src/pages/public-pages-commerce.tsx index b0b83eb..efde502 100644 --- a/website/src/pages/public-pages-commerce.tsx +++ b/website/src/pages/public-pages-commerce.tsx @@ -24,6 +24,7 @@ import { termsBoundaryCards, } from '../site-data' import { + BrowserAuthMethodsSection, BrowserDesktopRealitySection, DeliverySurfaceResponsibilitiesGrid, explorerFallbackPlan, @@ -109,6 +110,10 @@ export function PricingPage() { description="Pricing is a distribution surface, so its launch truth should carry the same docs, release, source, and escalation bundle as the rest of the public release lane." /> + +
+ +
+ + +
+ +
+ + + + + + + + + + + + + + + + + + + ) +} diff --git a/website/src/pages/public-pages-marketing.tsx b/website/src/pages/public-pages-marketing.tsx index 27e482c..6fff8d2 100644 --- a/website/src/pages/public-pages-marketing.tsx +++ b/website/src/pages/public-pages-marketing.tsx @@ -3,7 +3,6 @@ import { ArrowRight, BookOpenText, Boxes, Download, ExternalLink, Landmark, Moni import { Link, useSearchParams } from 'react-router-dom' import { MarketingShell } from '../components/layout/MarketingShell' import { SiteMetadata } from '../components/seo/SiteMetadata' -import { BrowserAuthMethodsGuide } from '../components/ui/BrowserAuthMethodsGuide' import { PublicLaunchStatus } from '../components/ui/PublicLaunchStatus' import { ProductSurfaceMatrix } from '../components/ui/ProductSurfaceMatrix' import { brandConfig } from '../site-config' @@ -36,13 +35,17 @@ import { supportFaqs, } from '../site-data' import { + BrowserAuthMethodsSection, BrowserDesktopRealitySection, DeliverySurfaceResponsibilitiesGrid, OperatorDesktopQuickstartSection, + PublicManualRouteAtlasSection, PublicPackagedDesktopProofSection, PublicReleaseDecisionGuideSection, ReleaseAuthorityBundleSection, Section, + StepOnlyCardSection, + SupportTopicDirectorySection, SurfaceChoiceGuideSection, supportTopicDirectory, supportTopicGuidance, @@ -66,19 +69,11 @@ type StepCard = { steps: readonly string[] } -type StepOnlyCard = { - title: string - steps?: readonly string[] - bullets?: readonly string[] -} - type FaqCard = { question: string answer: string } -type SupportTopicCard = (typeof supportTopicDirectory)[number] - function PrincipleCardSection({ title, description, @@ -158,33 +153,6 @@ function StepCardSection({ ) } -function StepOnlyCardSection({ - title, - description, - cards, -}: { - title: string - description?: string - cards: readonly StepOnlyCard[] -}) { - return ( -
-
- {cards.map((card) => ( -
-

{card.title}

-
    - {(card.steps ?? card.bullets ?? []).map((step) => ( -
  • {step}
    • - ))} -
-
- ))} -
-
- ) -} - function FaqCardSection({ title, description, @@ -208,58 +176,6 @@ function FaqCardSection({ ) } -function SupportTopicDirectorySection({ - title, - description, - topics, - selectedTopicKey, -}: { - title: string - description?: string - topics: readonly SupportTopicCard[] - selectedTopicKey?: string | null -}) { - return ( -
-
- {topics.map((topic) => { - const isSelected = selectedTopicKey === topic.topicKey - - return ( -
- {isSelected ?

Selected help lane

: null} -

{topic.title}

-

{topic.description}

-

Next steps

-
    - {topic.steps.map((step) => ( -
  • {step}
    • - ))} -
-

Manual and route focus

-
    - {topic.routeFocus.map((item) => ( -
  • {item}
    • - ))} -
-
- {topic.actions.map((action) => ( - - {action.label} - - ))} -
-
- ) - })} -
-
- ) -} - export function HomeLanding() { const { releaseManifest, windowsValidationPlatform } = usePublicReleaseManifestView('public-home') @@ -402,6 +318,12 @@ export function HomeLanding() {
+ + + +
+ + @@ -878,12 +808,9 @@ function GettingStartedPageContent({ cards={operatorManualTracks} /> -
- -
+ />
- - -
- -
- - - - - - - - - - - - - - - - - - - ) -} - export function DocsPage() { const { releaseManifest, windowsValidationPlatform } = usePublicReleaseManifestView('public-docs') @@ -1079,6 +934,11 @@ export function DocsPage() { > + + -
- -
+ /> + +

diff --git a/website/src/pages/public-pages.tsx b/website/src/pages/public-pages.tsx index 51eb4ba..8a783e9 100644 --- a/website/src/pages/public-pages.tsx +++ b/website/src/pages/public-pages.tsx @@ -1,3 +1,4 @@ export * from './public-pages-marketing' export * from './public-pages-features' export * from './public-pages-commerce' +export * from './public-pages-launch' diff --git a/website/src/router/PublicRoutes.tsx b/website/src/router/PublicRoutes.tsx index fb67011..0be5cac 100644 --- a/website/src/router/PublicRoutes.tsx +++ b/website/src/router/PublicRoutes.tsx @@ -8,7 +8,7 @@ const FeaturesPage = lazy(() => import('../pages/public-pages-features').then((m const AboutPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.AboutPage }))) const ResourcesPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.ResourcesPage }))) const GettingStartedPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.GettingStartedPage }))) -const LaunchStatusPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.LaunchStatusPage }))) +const LaunchStatusPage = lazy(() => import('../pages/public-pages-launch').then((m) => ({ default: m.LaunchStatusPage }))) const DocsPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.DocsPage }))) const SupportPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.SupportPage }))) const ChangelogPage = lazy(() => import('../pages/public-pages-marketing').then((m) => ({ default: m.ChangelogPage }))) diff --git a/website/src/site-data.ts b/website/src/site-data.ts index b9a6949..dcc8c57 100644 --- a/website/src/site-data.ts +++ b/website/src/site-data.ts @@ -100,6 +100,7 @@ export const browserDesktopRealityCards = [ description: 'The browser lane is useful precisely because it does not pretend to replace the simulator.', bullets: [ 'It does not claim package-validated training behavior, higher-dimensional execution, or device/runtime integration authority.', + 'Low-latency simulator input, packaged runtime ownership, higher-dimensional scene execution, and any future serious controller/VR completion still remain desktop-owned.', 'It keeps identity, billing, release, and legal-distribution work outside the native runtime where operators can review it more safely.', 'It preserves a clean browser-to-desktop pairing boundary instead of collapsing access, rollout, and simulator execution into one brittle shell.', ], @@ -865,7 +866,165 @@ export const resourceCollections = [ }, ] as const +export const publicManualRouteAtlasCards = [ + { + title: 'Home', + route: '/', + description: 'Start here when you need the shortest truthful overview of the product, the browser-versus-desktop split, and the current release posture.', + bullets: [ + 'Summarizes what HyperTwist already ships today.', + 'Shows live public launch-readiness and packaged-proof context.', + 'Points operators toward getting started, pricing, download, and the protected dashboard without overclaiming browser parity.', + ], + }, + { + title: 'Feature atlas', + route: '/features', + description: 'Open this page when you need capability truth instead of pitch language.', + bullets: [ + 'Separates implemented now, retained, and frozen or gated branches.', + 'Maps public website, protected dashboard, embedded browser shell, native runtime, and optional browser-client scope.', + 'Surfaces higher-dimensional, control-roster, and release-maturity truth in one place.', + ], + }, + { + title: 'About', + route: '/about', + description: 'Use this route when you want the product rationale and the higher-dimensional seriousness explained in operator-grade language.', + bullets: [ + 'Frames why HyperTwist keeps both browser and desktop surfaces.', + 'Explains the real end-to-end session story instead of flattening the topology.', + 'Keeps current control, XR, and release-maturity truth attached to the narrative.', + ], + }, + { + title: 'Resources', + route: '/resources', + description: 'Use this route as the public reference portal once you are comparing rollout, simulator, and training surfaces more deliberately.', + bullets: [ + 'Aggregates public-safe operator playbooks, support lanes, simulator-use guidance, and higher-dimensional references.', + 'Links directly to the strongest route for each common public research task.', + 'Keeps release proof and reference-bundle follow-through attached to the portal.', + ], + }, + { + title: 'Getting started', + route: '/getting-started', + description: 'Open this route when you need the canonical first-session manual from browser access into the native runtime.', + bullets: [ + 'Explains access resolution, protected release handoff, desktop pairing, and first launch.', + 'Keeps simulator-use guidance and the current control or XR boundary on the same page.', + 'Acts as the shortest handoff-friendly onboarding surface on the public site.', + ], + }, + { + title: 'Launch status', + route: '/launch-status', + description: 'Use this route when rollout truth, blockers, or preview-versus-public posture need one canonical authority page.', + bullets: [ + 'Shows the current launch-readiness checklist and hardening tracks.', + 'Keeps packaged desktop proof and release references attached to rollout status.', + 'Connects launch blockers to the real next public or protected help lane.', + ], + }, + { + title: 'Docs', + route: '/docs', + description: 'Use this route as the public manual when you need the most complete product-safe explanation of current HyperTwist usage.', + bullets: [ + 'Collects the feature-backed manual, recovery guidance, simulator-use guide, and control roster.', + 'Explains browser-versus-desktop boundaries and degraded-state operation directly.', + 'Ends with the same release references, notices, and proof lanes needed for real rollout follow-through.', + ], + }, + { + title: 'Support', + route: '/support', + description: 'Open this route when an operator needs help choosing the correct recovery or escalation lane.', + bullets: [ + 'Separates launch, access, rollout, package, runtime, and compliance questions.', + 'Keeps current release posture and packaged proof visible beside the help lanes.', + 'Mirrors the same browser-versus-desktop split so support does not soften product truth.', + ], + }, + { + title: 'Pricing', + route: '/pricing', + description: 'Use this route when plan comparison or billing posture matters but the product topology still needs to stay honest.', + bullets: [ + 'Keeps plan language aligned with the desktop-first delivery model.', + 'Shows launch posture, package proof, and current auth-method lineup before checkout.', + 'Explains the path from browser entitlement into the protected release lane and native runtime.', + ], + }, + { + title: 'Download', + route: '/download', + description: 'Open this route when you need platform targets, release posture, and the desktop handoff explained without exposing raw entitlement URLs.', + bullets: [ + 'Shows supported targets, package proof, and release-manifest posture.', + 'Explains protected delivery, desktop-link pairing, and first native launch follow-through.', + 'Keeps notices, distribution doctrine, and release references attached to install decisions.', + ], + }, + { + title: 'Release notes', + route: '/changelog', + description: 'Use this route when you need the current shipping chronology in operator-facing language.', + bullets: [ + 'Separates browser-shell work, native runtime work, and distribution hardening.', + 'Keeps rollout checklist and packaged proof attached to the release feed.', + 'Makes recent manual, control-boundary, and launch-authority changes easier to audit.', + ], + }, + { + title: 'Open-source notices', + route: '/open-source-notices', + description: 'Open this route when legal-distribution and corresponding-source follow-through matter for downloadable builds.', + bullets: [ + 'Lists key public notices and the current corresponding-source posture.', + 'Keeps the legal lane tied to current release proof instead of abstract compliance prose.', + 'Connects notices work back to download, release notes, and launch-readiness context.', + ], + }, + { + title: 'Privacy', + route: '/privacy', + description: 'Use this route when browser-account data handling and the desktop-runtime boundary need to be read together.', + bullets: [ + 'Explains what belongs to browser identity, what belongs to the simulator, and what stays in support/compliance lanes.', + 'Keeps privacy wording grounded in the live product topology.', + 'Connects privacy concerns back to package proof, release references, and escalation guidance.', + ], + }, + { + title: 'Terms', + route: '/terms', + description: 'Open this route when you need the access model, protected-download boundary, and desktop delivery posture expressed as product terms.', + bullets: [ + 'Keeps access, simulator, and redistribution obligations separated clearly.', + 'Explains why the current browser shell does not equal simulator parity.', + 'Connects terms language back to package proof and notices follow-through.', + ], + }, + { + title: 'Shipping & payment', + route: '/shipping-payment', + description: 'Use this route when you need the digital-delivery model and payment posture explained operationally rather than cosmetically.', + bullets: [ + 'Clarifies that HyperTwist is digitally delivered through browser account and desktop-release surfaces.', + 'Explains the handoff from checkout posture into protected entitlement and native runtime delivery.', + 'Keeps payment language attached to package proof, notices, and desktop-first truth.', + ], + }, +] as const + export const changelogEntries = [ + { + date: 'June 28, 2026', + title: 'Public pages now explain what each route is actually for', + details: 'The homepage, docs, and resources routes now share a first-party public route atlas explaining what each major public page owns: product truth, onboarding, launch readiness, pricing, download, support, release notes, and the legal/distribution surfaces are now easier to navigate as one professional operator manual instead of a flatter marketing shell.', + }, { date: 'June 27, 2026', title: 'Protected launch status now has its own signed-in authority route',