Document auth and release recovery guidance

docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md

@@ -262,6 +262,7 @@ Latest later higher-dimensional proof refresh still on `2026-06-24`:
 Latest same-day browser/distribution continuity follow-up still on `2026-06-24`:
 
 - auth-entry, protected-route loading, dashboard auth health, and release-authority fallback states now share a more deliberate operator-facing recovery shape instead of scattering single-line warnings across public and protected surfaces
+- the public docs and support pages now explicitly teach that same recovery path as operator manual truth, rather than leaving it implicit in route behavior alone
 - the new shared callout posture explicitly separates:
   - what still works
   - what stays intentionally withheld

website/src/__tests__/public-marketing-pages.test.tsx

@@ -885,6 +885,8 @@ describe('public marketing pages', () => {
     expect(screen.getByText('Browser and desktop responsibilities')).toBeTruthy()
     expect(screen.getByText('Shows account, auth, billing, and release readiness posture')).toBeTruthy()
     expect(screen.getByText('Support lanes')).toBeTruthy()
+    expect(screen.getByText('Recovery and degraded-state guidance')).toBeTruthy()
+    expect(screen.getByText('Desktop-first continuity during recovery')).toBeTruthy()
     expect(screen.getByText('Digital delivery workflow')).toBeTruthy()
     expect(screen.getByText('Post-install operator workflow')).toBeTruthy()
     expect(screen.getByText('Privacy and compliance boundary')).toBeTruthy()
@@ -1069,6 +1071,7 @@ describe('public marketing pages', () => {
     expect(screen.getByText('Current shipped capability')).toBeTruthy()
     expect(screen.getByText('Native training and coaching core')).toBeTruthy()
     expect(screen.getByText('Operator manual')).toBeTruthy()
+    expect(screen.getByText('Recovery and degraded-state manual')).toBeTruthy()
     expect(screen.getAllByText('Current surface authority map').length).toBeGreaterThan(0)
     expect(screen.getByText('When to use browser versus desktop')).toBeTruthy()
     expect(screen.getAllByText('Protected browser dashboard').length).toBeGreaterThan(0)
@@ -1083,6 +1086,8 @@ describe('public marketing pages', () => {
     expect(screen.getAllByText(/classic-wca-keyboard\/v1/i).length).toBeGreaterThan(0)
     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('Browser auth degraded or mixed')).toBeTruthy()
+    expect(screen.getByText('Release authority temporarily unavailable')).toBeTruthy()
     expect(screen.getByText('Current packaged desktop proof')).toBeTruthy()
     expect(screen.getByText('Common operator questions')).toBeTruthy()
     expect(screen.getByText('If the desktop app is primary, why keep the web version?')).toBeTruthy()

website/src/pages/public-pages-marketing.tsx

@@ -10,6 +10,7 @@ import {
   capabilityPillars,
   changelogEntries,
   companyNarrative,
+  degradedStateRecoveryTracks,
   deploymentReadinessTracks,
   digitalDeliveryCards,
   featureAtlasCurrentTracks,
@@ -746,6 +747,12 @@ export function DocsPage() {
           cards={operatorManualTracks}
         />
 
+        <StepCardSection
+          title="Recovery and degraded-state manual"
+          description="This manual section explains how to move through auth or release-authority degradation without confusing fallback continuity for live production authority."
+          cards={degradedStateRecoveryTracks}
+        />
+
         <Section
           title="Current surface authority map"
           description="This is the quickest way to understand which live surface owns what today, including the difference between the public website and the embedded browser shell that ships inside the desktop runtime."
@@ -893,6 +900,12 @@ export function SupportPage() {
           </div>
         </Section>
 
+        <StepCardSection
+          title="Recovery and degraded-state guidance"
+          description="This keeps support answers aligned with the now-explicit auth and release fallback posture in the product itself."
+          cards={degradedStateRecoveryTracks}
+        />
+
         <Section
           title="Digital delivery workflow"
           description="Support can move faster when the operator-facing browser shell and the installed desktop runtime are described as one continuous delivery lane."

website/src/site-data.ts

@@ -290,6 +290,36 @@ export const operatorManualTracks = [
   },
 ] as const
 
+export const degradedStateRecoveryTracks = [
+  {
+    title: 'Browser auth degraded or mixed',
+    description: 'Treat browser sign-in as bounded continuity when shared auth is in fallback or mixed posture, not as a silent claim of full production authority.',
+    steps: [
+      'Continue with sign-in or registration only when you need bounded account, release, or rollout orientation.',
+      'Use the protected dashboard to inspect what still works and what remains intentionally withheld.',
+      'Clear missing auth env vars and non-loopback HTTPS warnings before treating browser auth as fully production-ready.',
+    ],
+  },
+  {
+    title: 'Release authority temporarily unavailable',
+    description: 'When the live release manifest is unavailable, HyperTwist keeps rollout information visible without turning fallback metadata into raw package-delivery authority.',
+    steps: [
+      'Use fallback metadata, packaged proof, and notices for orientation while release authority is degraded.',
+      'Keep raw package delivery withheld until live release authority returns.',
+      'Refresh the protected release lane first, then escalate to support if rollout or entitlement work remains blocked.',
+    ],
+  },
+  {
+    title: 'Desktop-first continuity during recovery',
+    description: 'Even when browser auth or release authority is degraded, the simulator topology stays the same: browser surfaces coordinate, desktop runtime executes.',
+    steps: [
+      'Use public and protected browser surfaces for support, account, release, and rollout context.',
+      'Use the desktop runtime for simulator execution, packaged proof, and serious training work.',
+      'Keep release notes plus packaged proof visible before redistributing or escalating a build.',
+    ],
+  },
+] as const
+
 export const simulatorManualCards = [
   {
     title: 'Classic-cube recognition and correction',
@@ -718,7 +748,7 @@ export const changelogEntries = [
   {
     date: 'June 24, 2026',
     title: 'Auth and release fallback posture now reads as an operator workflow, not scattered warnings',
-    details: 'Login, protected-route loading, dashboard auth health, and public/protected release-authority fallback surfaces now share a bounded recovery-guidance shape that preserves what still works, what stays intentionally withheld, and the next best move while live authority is degraded.',
+    details: 'Login, protected-route loading, dashboard auth health, public/protected release-authority fallback surfaces, and the public docs/support manual now share a bounded recovery-guidance shape that preserves what still works, what stays intentionally withheld, and the next best move while live authority is degraded.',
   },
   {
     date: 'June 24, 2026',