feat: add Django backend skeleton

docs/deployment.md

@@ -55,7 +55,7 @@ Responsibilities:
 
 The backend should run database migrations before or during deployment through an explicit operational command, not as hidden startup magic unless that choice is documented later.
 
-At the infrastructure placeholder stage, the `backend` service runs gunicorn against a minimal placeholder WSGI application. The real Django application will replace it later.
+The `backend` service runs gunicorn against the Django WSGI application. The current backend is an initial skeleton with Django admin, Django REST Framework, CORS configuration, the `shows`, `bookings`, and `checkins` apps, and a health endpoint.
 
 ### postgres
 
@@ -97,6 +97,8 @@ Required backend configuration:
 - `DJANGO_SECRET_KEY`;
 - `DJANGO_ALLOWED_HOSTS`;
 - `DJANGO_CSRF_TRUSTED_ORIGINS`;
+- `CORS_ALLOWED_ORIGINS`;
+- `TIME_ZONE`;
 - `DATABASE_URL` or equivalent database settings;
 - email host, port, username, password, TLS settings, and sender address;
 - public site URL used to build confirmation and QR verification links.
@@ -147,14 +149,16 @@ Expected validation commands:
 
 ```bash
 docker compose --env-file .env.example -f infra/docker/compose.yml config
+docker compose --env-file .env.example -f infra/docker/compose.yml run --rm --build backend python manage.py test
 docker compose --env-file .env -f infra/docker/compose.yml run --rm backend python manage.py check --deploy
 docker compose --env-file .env -f infra/docker/compose.yml run --rm backend python manage.py test
 ```
 
-The canonical repository check for the current infrastructure stage is:
+The canonical repository check for the current stage is:
 
 ```bash
 docker compose --env-file .env.example -f infra/docker/compose.yml config
+docker compose --env-file .env.example -f infra/docker/compose.yml run --rm --build backend python manage.py test
 ```
 
 ## Rollback