chore: rename repo mana-monorepo → managarten

Phase-3-Rename des ehemaligen Multi-App-Monorepos zum eigenständigen
Produkt-Repo. Verein heißt mana e.V., Plattform-Domain bleibt mana.how,
apps/mana/ bleibt unverändert — nur der Repo-Container kriegt den
neuen Namen "managarten" (Garten der mana-Apps).

Geändert:
- package.json#name + #description
- README.md (Titel + erster Absatz)
- TROUBLESHOOTING.md
- alle Mac-Mini-Skripte (Pfade ~/projects/mana-monorepo → ~/projects/managarten)
- COMPOSE_PROJECT_NAME-default in scripts/mac-mini/status.sh
- .github/workflows/cd-macmini.yml + mirror-to-forgejo.yml
- apps/docs (astro.config.mjs + content)
- .claude/settings.local.json (Bash-Permission-Pfade)
- alle docs/*.md Pfad-Referenzen
- launchd plists, .env.macmini.example, infrastructure/

Forgejo-Repo + GitHub-Repo bereits via API umbenannt. Lokales
Verzeichnis-Rename + Mac-Mini-Cutover folgen separat.

services/mana-persona-runner/src/clients/mana-auth-internal.ts

@@ -5,7 +5,7 @@
  * batch. All gated by `X-Service-Key` (not a user JWT).
  *
  * After the platform/product split, personas live in apps/api
- * (`mana-monorepo/apps/api`), not in mana-auth. The constructor takes
+ * (`managarten/apps/api`), not in mana-auth. The constructor takes
  * the apps/api URL — the file name stays the same to keep the
  * callsite diff small (one import path), but the destination changed.
  */

services/mana-research/API_KEYS.md

@@ -301,7 +301,7 @@ ScrapingBee hat nur **Abo-Pläne ab $49/Monat** — passt nicht zur Pay-per-use-
 Kopiere `.env.secrets.example` nach `.env.secrets` (ist gitignored):
 
 ```bash
-cd /Users/till/Documents/Code/mana-monorepo
+cd /Users/till/Documents/Code/managarten
 cp .env.secrets.example .env.secrets
 ```