browser pairing and its extension zip leave the platform

The last two pieces the extraction missed. IntegrationsSettings/BrowserRelay.tsx drove the plugin's
pairing from a platform screen, calling /browser/relay-token and working only because the plugin
happens to serve that path — the same coupling removed everywhere else this morning.

public/browser-relay-extension.zip was a hand-built snapshot that had drifted 58 lines behind the
extension it claimed to be: built in August from something predating a February commit, never rebuilt,
and missing the multi-session recovery path. The plugin builds the archive from its own directory per
request now, so there is nothing left to fall behind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/apps/officer-web/Screens/Dashboard/Settings/IntegrationsSettings/index.tsx

@@ -8,7 +8,6 @@ import { Tabs, TabsList, TabsTrigger } from '@/components/ui/tabs';
 import { SettingsRoute, SettingsSidebar, SettingsContent, type SettingsSection } from '../SettingsPanel';
 import { GoogleOAuthConfig } from './GoogleOAuthConfig';
 // import { GoogleAccount } from './GoogleAccount'; // hidden — email uses IMAP app password now
-import { BrowserRelay } from './BrowserRelay';
 import { ApifyConfig } from './ApifyConfig';
 import { DavAppPasswords } from './DavAppPasswords';
 
@@ -50,13 +49,6 @@ const personalSections: SettingsSection[] = [
     description: 'Per-device passwords for CalDAV/CardDAV clients',
     content: <DavAppPasswords />,
   },
-  {
-    key: 'browser-relay',
-    icon: Globe,
-    title: 'Browser Relay',
-    description: 'Connect your Chrome browser',
-    content: <BrowserRelay />,
-  },
 ];
 
 // The Enterprise/Personal tab is not a second thing to remember — it is a fact about which section is