Future: Monitoring website + multi-tenant architecture

## Description

Build a web-based monitoring dashboard for the Discord-Minecraft bridge service. The application should support **multi-tenant architecture** — connecting many Discord servers to Minecraft worlds in a one-to-one relationship, all served from a single application deployment.

### Monitoring Website
- Dashboard showing all connected Discord servers and their Minecraft worlds
- Real-time status of each bridge connection (healthy, degraded, offline)
- Village/building counts per world
- Player activity metrics
- Job queue health (pending, in-progress, failed jobs)

### Multi-Tenant Architecture
- Each Discord server gets its own Minecraft world (1:1 relationship)
- Single application deployment serves all tenants
- Tenant isolation in database (per-guild schema or tenant ID column)
- Aspire orchestration manages multiple Minecraft containers (one per tenant)
- Configuration-driven tenant provisioning

## Sprint
Future sprint — not yet scheduled

## Size: XL

## Notes
This is a significant architectural evolution from the current single-tenant design. Will require database schema changes, service refactoring, and new Aspire container orchestration patterns. Should be decomposed into multiple smaller issues when sprint-planned.

## Labels
- Planning / future work