Extend browser-desktop truth to pricing and resources

This commit is contained in:
axiomlogicnexus 2026-06-24 23:25:31 +00:00
parent 3a48bc3bde
commit 516cda266c
6 changed files with 31 additions and 1 deletions

View file

@ -340,6 +340,23 @@ That follow-up stayed green under:
- `1` test file passed
- `12` tests passed
Latest pricing/resources parity follow-up later on `2026-06-24`:
- the public Pricing and Resources routes now also carry that same direct
browser-versus-desktop comparison section instead of relying only on the
lighter shared surface-choice guide
- this keeps:
- commercial access language on pricing
- operator-reference language on resources
aligned with the sharper homepage/About/Docs/Download truth about what the
website is for, what stays native, why the browser remains intentionally
narrower, and how the current XR/controller boundary should be read
That follow-up stayed green under:
- `npm --prefix website test -- --run src/__tests__/public-marketing-pages.test.tsx`
- focused Pricing and Resources coverage stayed green
Latest protected-operator parity follow-up later on `2026-06-24`:
- the signed-in dashboard, protected downloads, and browser-access routes now

File diff suppressed because one or more lines are too long

View file

@ -824,7 +824,9 @@ describe('public marketing pages', () => {
expect(screen.getByText('Current packaged desktop proof')).toBeTruthy()
expect(screen.getAllByText('What happens after access is granted').length).toBeGreaterThan(0)
expect(screen.getByText('Choose the right HyperTwist surface')).toBeTruthy()
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.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()
@ -1034,6 +1036,8 @@ describe('public marketing pages', () => {
expect(within(packagedProofSection as HTMLElement).getByText(/Build step during latest proof: skipped and reused existing target receipt/i)).toBeTruthy()
expect(screen.getAllByText('Support topic quick routes').length).toBeGreaterThan(0)
expect(screen.getByText('Choose the right HyperTwist surface')).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.getByText('Recovery and escalation')).toBeTruthy()
expect(screen.getByText('Operator playbooks')).toBeTruthy()
expect(screen.getByText('Simulator use today')).toBeTruthy()

View file

@ -141,6 +141,8 @@ export function PricingPage() {
<SurfaceChoiceGuideSection description="This keeps pricing honest about what should happen next: stay public for plan comparison, move protected for account-aware access, and move native for the actual simulator." />
<BrowserDesktopRealitySection />
<Section
title="Why plans live in the browser while training stays native"
description="Commercial access, entitlement, and launch-readiness posture belong to the browser shell so the simulator can stay focused on training quality."

View file

@ -659,6 +659,8 @@ export function ResourcesPage() {
<SurfaceChoiceGuideSection description="The resource portal is most useful when it also tells operators where to go next: stay public for references, move protected for release access, and move native for simulator execution." />
<BrowserDesktopRealitySection />
<SupportTopicDirectorySection
title="Support topic quick routes"
description="These topic cards bridge the public resource portal into the concrete help lanes without making operators guess which surface owns the next step."

View file

@ -821,6 +821,11 @@ export const resourceCollections = [
] as const
export const changelogEntries = [
{
date: 'June 24, 2026',
title: 'Pricing and resources now carry the full browser-versus-desktop reality section too',
details: 'The public Pricing and Resources routes now share the same direct browser-versus-desktop comparison already used on Home, About, Docs, and Download, so lower-friction commercial and reference surfaces no longer rely only on indirect surface-choice wording to explain what stays native and how the current XR/controller boundary should be read.',
},
{
date: 'June 24, 2026',
title: 'Protected operator routes now mirror the same browser-versus-desktop reality explanation',