docs: fix stale VictoriaMetrics reference and mod.just quoting bug

[Aviator-Coding]

Intent

Fix two factual errors: (1) AGENTS.md monitoring stack description is false - VictoriaMetrics/VictoriaLogs/Vector are not deployed; live stack is kube-prometheus-stack + Loki + Promtail + Tempo + Grafana + Alertmanager + Gatus + kromgo + KEDA + unpoller. (2) kubernetes/mod.just snapshot recipe uses single quotes so $(date +%s) writes literally - change to double quotes to expand timestamp.

What Changed

• Corrected AGENTS.md's core stack description: replaced the inaccurate VictoriaMetrics/VictoriaLogs/Vector monitoring stack with the actual deployed stack - kube-prometheus-stack + Loki + Promtail + Tempo + Grafana + Alertmanager + Gatus + kromgo + KEDA + unpoller.
• Updated docs/downloads/sabnzbd-disk-space-runbook.md to state that PrometheusRules are consumed natively by kube-prometheus-stack's Prometheus Operator, replacing the stale reference to a VictoriaMetrics operator PrometheusRule-to-VMRule converter.
• Fixed the snapshot recipe in kubernetes/mod.just to use double quotes around the kubectl patch JSON payload so $(date +%s) expands to the current timestamp instead of being written literally.

Risk Assessment

✅ Low: Two isolated, verified-correct fixes (one doc correction confirmed against the actual monitoring kustomization.yaml, one shell-quoting fix confirmed to expand correctly and consistent with an existing working pattern in the same file) with no functional or behavioral risk beyond their stated scope.

Testing

Verified the diff between base 12b2a76 and target 5cb03f5 contains exactly the two intended changes (no unrelated edits). For fix #1, cross-checked the corrected AGENTS.md monitoring-stack sentence against kubernetes/apps/monitoring/kustomization.yaml and confirmed VictoriaMetrics/VictoriaLogs/Vector are present as directories but commented out of the namespace's resource list (not deployed), while every app named in the fixed text (kube-prometheus-stack, Loki, Promtail, Tempo, Grafana, Alertmanager, Gatus, kromgo, KEDA, unpoller) is an active resource. For fix #2, reproduced the bug end-to-end by extracting the actual snapshot recipe body from both commits and executing each under the same shell just configures (bash -euo pipefail -c) with a stubbed kubectl capturing its patch payload: the base (single-quoted) version sent the literal, non-expanding string "$(date +%s)" to kubectl patch, while the target (double-quoted) version sent a real expanded epoch timestamp, confirming the fix works as intended. No linters or test suites were run per phase scope; worktree left clean with no leftover test artifacts.

Evidence: End-to-end reproduction of mod.just snapshot recipe: base (single-quoted) sends literal $(date +%s) vs target (double-quoted) sends expanded timestamp

##### BASE COMMIT (single-quoted) #####
kubectl called with args: test-ns patch replicationsources test-replicationsource-name --type merge -p {"spec":{"trigger":{"manual":"$(date +%s)"}}}

##### TARGET COMMIT (double-quoted) #####
kubectl called with args: test-ns patch replicationsources test-replicationsource-name --type merge -p {"spec":{"trigger":{"manual":"1787515592"}}}

Evidence: kubernetes/apps/monitoring/kustomization.yaml confirming VictoriaMetrics/VictoriaLogs/Vector are commented out (not deployed)

resources:
- ./alertmanager/ks.yaml
- ./grafana/ks.yaml
- ./keda/ks.yaml
- ./kube-state-metrics/ks.yaml
- ./kube-prometheus-stack/ks.yaml
- ./loki/ks.yaml
- ./prometheus-operator/ks.yaml
- ./tempo/ks.yaml
- ./promtail/ks.yaml
- ./gatus/ks.yaml
- ./kromgo/ks.yaml
# - ./victoriametrics/ks.yaml
# - ./victorialogs/ks.yaml
# - ./vector/ks.yaml
- ./unpoller/ks.yaml
- ./exporters/graphite-exporter/ks.yaml

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• git diff 12b2a76a45986c7165b157ecbb44fc16d3267752 5cb03f59c857ddd66bff5b45bba11bdb476111ff (confirmed scope: only AGENTS.md and kubernetes/mod.just changed)
• Inspected kubernetes/apps/monitoring/kustomization.yaml to confirm victoriametrics/victorialogs/vector are commented out and the other named apps are active
• Manual end-to-end reproduction: extracted the snapshot recipe body from both commits and ran each via bash -euo pipefail -c (just's configured shell) with a stubbed kubectl function, comparing the literal patch payload sent in each case
• git status --porcelain (confirmed worktree clean after testing, no residue)

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.