Rebrand StreamHoard, strip Emergent.sh platform artifacts

- Remove .emergent/ state dir, tracked .gitconfig, @emergentbase/visual-edits
  dep + craco wiring, emergent.sh script/meta tags, PostHog telemetry snippet
- Rename UI/docs branding Kino -> StreamHoard (README, DEPLOY.md, Navbar,
  Login, Register, AdminShowEpisodes, FastAPI title, health check response)
- Rename docker-compose container/network names to streamhoard-*
- Default admin email domain -> admin@streamhoard.local

DEPLOY.md

@@ -1,8 +1,8 @@
-# Kino — Deployment on a Proxmox LAMP host
+# StreamHoard — Deployment on a Proxmox LAMP host
 
-Kino is FastAPI + MongoDB + React. It runs happily alongside your existing
+StreamHoard is FastAPI + MongoDB + React. It runs happily alongside your existing
 LAMP stack (Apache/MySQL/PHP) because we run everything in Docker containers
-on their own network. Apache keeps port 80/443, MySQL is untouched, Kino
+on their own network. Apache keeps port 80/443, MySQL is untouched, StreamHoard
 uses whatever port you pick.
 
 ---
@@ -54,7 +54,7 @@ Log in with the admin credentials from `.env`.
 
 ## Running behind your existing Apache (optional, recommended)
 
-If you already have Apache on port 80/443 with virtual hosts, add a Kino vhost
+If you already have Apache on port 80/443 with virtual hosts, add a StreamHoard vhost
 that reverse-proxies to the container. This gives you `https://kino.example.com`
 instead of `http://ip:8080`.
 
@@ -130,7 +130,7 @@ To reset everything: `docker compose down -v` (deletes the mongo-data volume).
 
 ## Coexistence with your LAMP stack
 
-| Kino uses                | LAMP uses               | Conflict? |
+| StreamHoard uses               | LAMP uses               | Conflict? |
 | ------------------------ | ----------------------- | --------- |
 | Port `KINO_HTTP_PORT`    | Apache 80/443           | No — different ports |
 | MongoDB (internal only)  | MySQL                   | No — different DBs, Mongo not exposed to host |
@@ -144,16 +144,16 @@ same box.
 
 ## Radarr integration
 
-If Radarr is running on the same Proxmox host (native or container), point Kino
+If Radarr is running on the same Proxmox host (native or container), point StreamHoard
 at it via **Admin → Settings → Radarr**:
 
 - **URL**: `http://<host-ip>:7878` (use the host IP, not `localhost` — containers
   can't reach the host's `localhost` unless you add `host.docker.internal`)
 - **API key**: from Radarr → Settings → General → Security
 
-**Important**: For Kino to actually play the imported movies, the path Radarr
+**Important**: For StreamHoard to actually play the imported movies, the path Radarr
 reports (e.g. `/movies/Inception (2010)/Inception.mkv`) must be **readable from
-inside the Kino backend container**. Mount Radarr's media path into Kino:
+inside the StreamHoard backend container**. Mount Radarr's media path into StreamHoard:
 
 ```yaml
 # docker-compose.yml — extend the backend volumes
@@ -163,7 +163,7 @@ backend:
     - /mnt/radarr-movies:/mnt/radarr-movies:ro   # <— add this
 ```
 
-Radarr's file paths must be identical inside both Radarr and Kino containers
+Radarr's file paths must be identical inside both Radarr and StreamHoard containers
 (easiest: match the paths exactly).
 
 ---
@@ -172,14 +172,14 @@ Radarr's file paths must be identical inside both Radarr and Kino containers
 
 ```bash
 curl -s http://localhost:${KINO_HTTP_PORT:-8080}/api/ | jq
-# {"app":"Kino","status":"ok"}
+# {"app":"StreamHoard","status":"ok"}
 ```
 
 ---
 
 ## Firewalling
 
-Kino has no built-in rate limiting or IP allowlist. Since you confirmed
+StreamHoard has no built-in rate limiting or IP allowlist. Since you confirmed
 **internal network only**, keep it that way:
 
 ```bash