docs: project docs, scripts, deployment configs, and evidence

docs/evidence/ops/2026-03-29/alerting/ALERTING_PACKAGE_20260329-100315.md

@@ -0,0 +1,34 @@
+# Alerting Package Validation
+
+- Generated at: 2026-03-29 10:03:16 +08:00
+- Alerts file: D:\project\deployment\alertmanager\alerts.yml
+- Alertmanager file: D:\project\deployment\alertmanager\alertmanager.yml
+- Baseline report: D:\project\docs\evidence\ops\2026-03-27\observability\LOCAL_BASELINE_20260327-182005.md
+
+## Structural Validation
+
+- Rule inventory: critical=3, warning=4, info=2
+- Missing required rules: none
+- Root receiver: default
+- Critical route receiver: critical-alerts
+- Warning route receiver: warning-alerts
+- Missing required receivers: none
+- Structural ready: True
+
+## Threshold Alignment
+
+- HighResponseTime threshold: 1s
+- Latest browser max baseline: 186ms
+- Latest browser timings: login-desktop=186ms, login-initial=99ms, login-mobile=96ms, login-tablet=117ms
+
+## External Delivery Readiness
+
+- Placeholder findings: \$\{ALERTMANAGER_[A-Z0-9_]+\}
+- External delivery closed: False
+- Interpretation: rules and route topology can be reviewed locally, but unresolved template variables or example SMTP/accounts mean real notification delivery evidence is still open until environment-specific contacts and secrets are injected.
+
+## Conclusion
+
+- Repo-level alerting package structurally ready: True
+- Repo-level oncall/delivery package fully closed: False
+