rename project from SixFlagsSuperCalendar to Thoosie Calendar

Update package names, Docker image tags, CI/CD workflow, and
documentation to reflect the public brand name. References to
the actual Six Flags theme park chain/API are intentionally kept.

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

docs/DEVELOPMENT.md

@@ -15,7 +15,7 @@
 ```bash
 # Clone the repository
 git clone <repo-url>
-cd SixFlagsSuperCalendar
+cd ThoosieCalendar
 
 # Install frontend dependencies
 npm install
@@ -247,17 +247,17 @@ Tests verify the `isCoasterMatch()` function handles edge cases like trademark s
 
 ```bash
 # Build the web image
-docker build --target web -t sixflagssupercalendar:web .
+docker build --target web -t thoosiecalendar:web .
 
 # Build the backend image
-docker build --target backend -t sixflagssupercalendar:backend .
+docker build --target backend -t thoosiecalendar:backend .
 
 # Run locally with Docker Compose
 docker compose up -d
 
 # Or run individual containers
-docker run -d -p 3001:3001 -v park_data:/app/backend/data -e TZ=America/New_York sixflagssupercalendar:backend
-docker run -d -p 3000:3000 -e BACKEND_URL=http://host.docker.internal:3001 sixflagssupercalendar:web
+docker run -d -p 3001:3001 -v park_data:/app/backend/data -e TZ=America/New_York thoosiecalendar:backend
+docker run -d -p 3000:3000 -e BACKEND_URL=http://host.docker.internal:3001 thoosiecalendar:web
 ```
 
 When running individual containers outside of Docker Compose, use `host.docker.internal` instead of `backend` for the `BACKEND_URL`, since Docker's internal DNS won't resolve service names without Compose.

docs/OPERATIONS.md

@@ -46,18 +46,18 @@ The project uses a single `Dockerfile` with four stages producing two final imag
 ### Image Tags
 
 ```
-{registry}/{owner}/sixflagssupercalendar:web
-{registry}/{owner}/sixflagssupercalendar:backend
+{registry}/{owner}/thoosiecalendar:web
+{registry}/{owner}/thoosiecalendar:backend
 ```
 
 ### Building Locally
 
 ```bash
 # Build web image
-docker build --target web -t sixflagssupercalendar:web .
+docker build --target web -t thoosiecalendar:web .
 
 # Build backend image
-docker build --target backend -t sixflagssupercalendar:backend .
+docker build --target backend -t thoosiecalendar:backend .
 ```
 
 ---
@@ -69,7 +69,7 @@ The production `docker-compose.yml`:
 ```yaml
 services:
   web:
-    image: gitea.thewrightserver.net/josh/sixflagssupercalendar:web
+    image: gitea.thewrightserver.net/josh/thoosiecalendar:web
     ports:
       - "3000:3000"
     environment:
@@ -79,7 +79,7 @@ services:
     restart: unless-stopped
 
   backend:
-    image: gitea.thewrightserver.net/josh/sixflagssupercalendar:backend
+    image: gitea.thewrightserver.net/josh/thoosiecalendar:backend
     ports:
       - "3001:3001"
     volumes: