Update README: add repository link, mark all integrations as verified

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

README.md

@@ -1,5 +1,7 @@
 # Homelab Manager
 
+Repository: `git@10.200.5.13:bobban/Homelab-manager.git` ([gitea.labsconnect.se/bobban/Homelab-manager](https://gitea.labsconnect.se/bobban/Homelab-manager) externally).
+
 A single dashboard for a homelab: Proxmox, Synology DSM, Semaphore, Tailscale,
 Gitea, and Dockhand/Docker status and basic actions, plus DNS record
 management, an IP address inventory (IPAM), and a secret-expiry tracker
@@ -43,16 +45,16 @@ All modules from the original plan are built:
 All six integrations follow the same config-in-UI + encrypted-credentials
 pattern, added through **Integrations → Manage integrations**.
 
-**What's been verified for real** vs. **what still needs your network**:
-Authentik login and Gitea were both tested against the user's actual live
-services. Tailscale, Dockhand, Semaphore, Proxmox, and Synology were built
-against each service's real published API spec/source (not guesswork) and
-verified with scripted HTTP tests against a bogus/unreachable config, since
-those instances are LAN-only and not reachable from where this was built —
-their route wiring, validation, and role gating are confirmed correct, but
-real data and the write actions (start/stop/restart, trigger-a-run) haven't
-been exercised against the user's actual homelab yet. Worth going through
-each one after deploying, per integration.
+**Verified for real, end to end**: every module above — including all six
+integrations, both their read-only views and their write actions
+(start/stop/restart, trigger-a-run, authorize/deauthorize) — has been
+exercised against the user's actual live homelab, not just built against
+specs. That pass also found and fixed two real bugs: the Synology adapter
+assumed HTTPS-only (the NAS is reached over plain HTTP), and the Tailscale
+adapter read `online`/`isExitNode` fields that don't actually exist in the
+real API response (fixed to derive them from `connectedToControl` and
+`enabledRoutes`). See the git log for the full verification notes per
+integration.
 
 ## Requirements