Bug Description

The Settings page's "Platform Connections" section shows all adapters (Slack, Telegram, Discord, GitHub) as "Not configured" even when they are actively running and connected.

Root Cause

In packages/web/src/routes/SettingsPage.tsx, the PlatformConnectionsSection component has platform connection statuses hardcoded to false:

const platforms = [
  { name: 'Web', connected: adapter === 'web' },
  { name: 'Slack', connected: false },      // <- hardcoded
  { name: 'Telegram', connected: false },   // <- hardcoded
  { name: 'Discord', connected: false },    // <- hardcoded
  { name: 'GitHub', connected: false },     // <- hardcoded
];

The /api/health endpoint doesn't include adapter status information — it only returns adapter: 'web' (the HTTP adapter type), with no data about which platform adapters are active.

Expected Behavior

The Settings page should reflect the actual state of platform adapters — showing "Connected" for adapters that are running (e.g., Slack, Telegram, GitHub when their tokens are configured).

Steps to Reproduce

1. Configure Slack and Telegram tokens in .env
2. Start the server (bun run dev)
3. Observe server logs showing slack.bot_started and telegram.adapter_initialized
4. Open Settings page → Platform Connections shows all as "Not configured"

Proposed Fix

1. Add an adapters field to the /api/health response with real adapter status
2. Pass adapter state from index.ts to registerApiRoutes() via a lazy callback (since Telegram initializes after server.listen())
3. Update the frontend HealthResponse type and PlatformConnectionsSection to use real data

I have a working fix ready — will submit a PR.