chore: convert guru-connect to submodule; integrate ADR-008 + 2026-05-29 session log

guru-connect is now tracked as a submodule (azcomputerguru/guru-connect @ e3e95f8);
its working state was published to the GC repo first, so no content is lost. guru-rmm
advanced to include ADR-008 (GC integration boundary) replayed on top of the team's
Integrations Center / discovery advances. Includes the native-remote-control spec
(now inside the GC submodule), the versionable-products memory, and the session log.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

projects/msp-tools/guru-connect/infrastructure/prometheus.yml

@@ -1,45 +0,0 @@
-# Prometheus configuration for GuruConnect
-#
-# Install Prometheus:
-#   sudo apt-get install prometheus
-#
-# Copy this file to:
-#   sudo cp prometheus.yml /etc/prometheus/prometheus.yml
-#
-# Restart Prometheus:
-#   sudo systemctl restart prometheus
-
-global:
-  scrape_interval: 15s  # Scrape metrics every 15 seconds
-  evaluation_interval: 15s  # Evaluate rules every 15 seconds
-  external_labels:
-    cluster: 'guruconnect-production'
-    environment: 'production'
-
-# Scrape configurations
-scrape_configs:
-  # GuruConnect server metrics
-  - job_name: 'guruconnect'
-    static_configs:
-      - targets: ['172.16.3.30:3002']
-        labels:
-          service: 'guruconnect-server'
-          instance: 'rmm-server'
-
-  # Node Exporter (system metrics)
-  # Install: sudo apt-get install prometheus-node-exporter
-  - job_name: 'node_exporter'
-    static_configs:
-      - targets: ['172.16.3.30:9100']
-        labels:
-          instance: 'rmm-server'
-
-# Alert rules (optional)
-# rule_files:
-#   - '/etc/prometheus/alerts.yml'
-
-# Alertmanager configuration (optional)
-# alerting:
-#   alertmanagers:
-#     - static_configs:
-#         - targets: ['localhost:9093']