fix(dashboard): use jq for brace-balanced JSON parse when available

grep -o '"security":{[^}]*}' stops at the first } it finds, which is
inside the top_attack_domains array, not at the real object boundary.
Dashboard silently reported 0 attacks when there was actual data.

Prefer jq (standard on most systems) for the parse. Fall back to the
old regex if jq isn't installed — lossy but non-crashing.

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

bin/gstack-security-dashboard

@@ -46,8 +46,15 @@ DATA="$(curl -sf --max-time 15 \
   -H "apikey: ${ANON_KEY}" \
   2>/dev/null || echo "{}")"
 
-# Extract the security section
+# Extract the security section. Prefer jq for brace-balanced parsing of
-SEC_SECTION="$(echo "$DATA" | grep -o '"security":{[^}]*}' 2>/dev/null || echo "")"
+# nested arrays/objects (top_attack_domains etc.). Fall back to regex if
+# jq isn't installed — the regex is lossy but the dashboard degrades
+# gracefully to "0 attacks" rather than misreporting numbers.
+if command -v jq >/dev/null 2>&1; then
+  SEC_SECTION="$(echo "$DATA" | jq -rc '.security // empty | "\"security\":\(.)"' 2>/dev/null || echo "")"
+else
+  SEC_SECTION="$(echo "$DATA" | grep -o '"security":{[^}]*}' 2>/dev/null || echo "")"
+fi
 
 if [ "$JSON_MODE" = "1" ]; then
   # Machine-readable — echo the whole security section (or empty object)