feat(stack): replace Organizr with Tatlock UI, remove Netdata

Remove Organizr dashboard and Netdata monitoring:
- Delete stacks/organizr.yml and stacks/netdata.yml
- Delete organizr-widgets/ directory and npm forward-auth config
- Remove organizr database references from postgres-shared docs

Promote Tatlock UI as primary dashboard:
- Move from port 8092 to 9999 (Organizr's port)
- Enable external access at home.schweitz.net
- Update all documentation references

Update service counts: 26 containers across 20 stacks

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

npm-configs/README.md

@@ -2,35 +2,14 @@
 
 This directory contains Nginx configuration snippets for Nginx Proxy Manager (NPM) forward authentication with Authentik.
 
-## Files
-
-### `organizr-forward-auth.conf`
-**Status:** 🧪 Testing
-**Service:** Organizr (home.schweitz.net)
-**Purpose:** First test deployment of forward auth to validate standalone outpost functionality
-
-**DO NOT APPLY TO OTHER SERVICES YET** - This is a proof-of-concept deployment to verify:
-- Standalone outpost works correctly
-- No redirect loops occur
-- SSO functions as expected
-- Cookie domain settings are correct
-
-Once proven stable, this configuration can be adapted for other services.
-
 ## Deployment Strategy
 
-### Phase 1: Single Service Test (Current)
-- ✅ Deploy to Organizr only
-- ✅ Test all authentication flows
-- ✅ Verify no issues for 24-48 hours
-
-### Phase 2: Gradual Rollout (After Phase 1 Success)
-Services to protect (in order):
+Services to protect with forward auth (in order):
 1. Core API (api.schweitz.net) - Use OIDC instead of forward auth
 2. Nextcloud (cloud.schweitz.net)
 3. Gitea (git.schweitz.net)
 4. Jellyfin (media.schweitz.net)
-5. Open WebUI, Netdata, etc.
+5. Open WebUI, etc.
 
 **Rule:** Deploy to ONE service at a time, test for 24 hours before proceeding to next.