docs(federation/auth/api/db/client): detached-account re-attach flow; reset-cleanup panel mentions re-attach

packages/web/src/components/modals/instanceSettingsPanels/FederationPanel.resetCleanup.test.tsx

@@ -298,6 +298,8 @@ describe('FederationPanel — Reset cleanup', () => {
     // Informational detach copy — not urgent-cleanup language.
     expect(screen.getAllByText(/detached/i).length).toBeGreaterThan(0);
     expect(screen.getByText(/existing password/i)).toBeInTheDocument();
+    // Re-attach is surfaced as the recovery path (spec §3.5).
+    expect(screen.getByText(/re-attach a detached account to their new home identity/i)).toBeInTheDocument();
 
     // The fake client-only Keep/frozen affordance is fully gone.
     expect(screen.queryByRole('button', { name: 'Keep' })).not.toBeInTheDocument();

packages/web/src/components/modals/instanceSettingsPanels/FederationPanel.tsx

@@ -1039,6 +1039,8 @@ function ResetCleanup() {
                 {event.orphanedAccounts.length}{' '}
                 {event.orphanedAccounts.length === 1 ? 'account' : 'accounts'} with local content detached.
                 Detached accounts keep working locally — owners keep access with their existing password.
+                The owner can re-attach a detached account to their new home identity from that account's
+                settings (Account → detached notice) when logged into both.
               </div>
               <div className="space-y-2">
                 {event.orphanedAccounts.map((account) => (