chore: regenerate stale .pi-map.md / .pi-map.index.md project maps

Project map had drifted: claimed recharts unused (was used), ObservabilityPage.tsx
exists (refactored to service-tabs/), missed JellyfinNowPlayingWidget +
authentik/backups service types. Regenerate to reflect post-change reality:
new Qbittorrent/LineSeriesChart/Prometheus{Gauge,Mean}Widget files,
service_data.py/qbittorrent_store.py, canonical prometheus-charting +
service-storage specs, archived changes.

monitoring/prometheus/.pi-map.index.md

@@ -2,7 +2,7 @@
 dir: monitoring/prometheus
 
 ## role
-Provides configuration for standalone Prometheus deployments to scrape and collect metrics from local infrastructure services and remote nodes.
+Provides Prometheus server configuration for scraping metrics from infrastructure components and remote nodes using standalone deployment.
 ## parent
 index: monitoring/.pi-map.index.md
 map: monitoring/.pi-map.md

monitoring/prometheus/.pi-map.md

@@ -4,11 +4,11 @@ dir: monitoring/prometheus
 index: monitoring/prometheus/.pi-map.index.md
 
 ## role
-Provides configuration for standalone Prometheus deployments to scrape and collect metrics from local infrastructure services and remote nodes.
+Provides Prometheus server configuration for scraping metrics from infrastructure components and remote nodes using standalone deployment.
 ## files
 - prometheus.standalone.yml | Configures Prometheus monitoring server to scrape metrics from itself, node exporters, Loki, Alertmanager, Grafana, and remote nodes via file-based service discovery | dep: alertmanager, node-exporter, loki, grafana, file-sd
 ## arch
-Uses a declarative static YAML configuration pattern leveraging file-based service discovery for dynamic remote target management.
+Declarative monitoring configuration using static targets and file-based service discovery patterns for federated metrics collection.
 ## tags
 node, loki, alertmanager, grafana, prometheus.standalone, configures, prometheus, monitoring
 ## symbols

monitoring/prometheus/file-sd/.pi-map.index.md

@@ -2,7 +2,7 @@
 dir: monitoring/prometheus/file-sd
 
 ## role
-Provides static target configuration for Prometheus to discover and scrape node_exporter metrics endpoints.
+Provides file-based service discovery configuration for Prometheus node_exporter scrape targets.
 ## parent
 index: monitoring/prometheus/.pi-map.index.md
 map: monitoring/prometheus/.pi-map.md

monitoring/prometheus/file-sd/.pi-map.md

@@ -4,11 +4,11 @@ dir: monitoring/prometheus/file-sd
 index: monitoring/prometheus/file-sd/.pi-map.index.md
 
 ## role
-Provides static target configuration for Prometheus to discover and scrape node_exporter metrics endpoints.
+Provides file-based service discovery configuration for Prometheus node_exporter scrape targets.
 ## files
 - node_exporter_targets.json | Empty JSON file intended to define scrape targets for Prometheus node_exporter | dep: Prometheus, node_exporter
 ## arch
-Uses the Prometheus file-based service discovery (file_sd) pattern with JSON-formatted target definitions.
+Static file service discovery pattern using Prometheus file_sd_config mechanism with JSON-formatted target definitions.
 ## tags
 targets, node, exporter, prometheus, empty, json, intended, define
 ## symbols

monitoring/prometheus/rules/.pi-map.md

@@ -8,7 +8,7 @@ Defines Prometheus alerting rules for monitoring backup job failures and observa
 ## files
 - backup_alerts.yml | Defines Prometheus alerting rules for backup job failures and observability stack health monitoring. | dep: Prometheus, Alertmanager, Grafana, manage_backup_runs_total metric, manage_backup_runs_last_success_timestamp metric, up metric
 ## arch
-Configuration-as-code pattern using declarative YAML rule files consumed directly by the Prometheus alerting engine.
+Declarative Infrastructure-as-Code using YAML-based Prometheus alerting rule definitions.
 ## tags
 backup, prometheus, alerts, defines, alerting, rules, job, failures
 ## symbols