"No LLM provider configured" persists after successful spacebot auth login (Anthropic) in Docker

Environment

• Deployment: Docker Compose (ghcr.io/spacedriveapp/spacebot:latest)
• Host OS: Linux

Steps to Reproduce

1. Start Spacebot via Docker Compose:

services:
  spacebot:
    image: ghcr.io/spacedriveapp/spacebot:latest
    container_name: spacebot
    restart: unless-stopped
    ports:
      - "19898:19898"
    volumes:
      - spacebot-data:/data

2. Exec into the running container and authenticate:

docker exec -it spacebot spacebot auth login

3. Auth completes successfully. Verify with:

docker exec -it spacebot spacebot auth status
# Shows authenticated / all good

4. Open the web UI at http://localhost:19898

Expected Behavior

The web UI should recognize the authenticated session and allow usage, or at minimum reflect that auth was successful.

Actual Behavior

The web UI still shows:

No LLM provider configured. Add an API key in Settings to get started.

This persists even after docker compose restart.

Reproduce the problem with the provided Docker Compose configuration, then compare the output of spacebot auth status with the web UI after login and restart. Trace how the CLI authentication state is persisted and how the web UI discovers configured providers; done means a successful Anthropic login is recognized by the UI after restart.