Document Sentry self-hosted deployment

docs/AI_CONTEXT.md

@@ -108,6 +108,8 @@ MSSQL is attached only to `internal`. DbGate is attached to both `internal` and
 
 Nextcloud is attached to `proxy` and `nextcloud_nextcloud_internal`. Its PostgreSQL and Redis containers are attached only to `nextcloud_nextcloud_internal`.
 
+Sentry was installed using the upstream self-hosted `install.sh` workflow in `/srv/docker/sentry`, is available at `sentry.silveressence.net`, and uses the `sentry-self-hosted_default` network for internal services. Nginx Proxy Manager forwards to `sentry-self-hosted-nginx-1:80`. It is not a normal `slcompose` service.
+
 Jitsi uses `jitsi-docker-jitsi-meet-aa76415_meet.jitsi` for its internal cluster and `proxy` for web access. Xray is currently attached to `proxy`; `xray_default` exists but had no running containers attached in the 2026-06-24 runtime snapshot.
 
 ## Authentication
@@ -241,3 +243,4 @@ docs/roadmap.md
 * Xray introduced as a tunneling and connectivity layer
 * Multi-network segmentation formalized: internal, proxy and isolated infrastructure networks
 * Nextcloud deployed as the private cloud storage service at cloud.silveressence.net
+* Sentry deployed using upstream self-hosted install.sh and exposed at sentry.silveressence.net