Registry and Analytics: run, subnet, direction and protocol filters, successes-by-target chart

Registry (/registry):
- filters by run (slice by the address's cycle in that run), subnet
  (drop-down of configured subnets), direction (egress/ingress) and
  protocol (icmp, tcp, ssh, https, tls); status in scope is computed over
  the narrowed checks
- chart "successful checks per target (egress) / site (ingress)" when both
  direction and protocol are chosen; a row opens the list of addresses
  (dialog, CSV)
- API: direction/protocol parameters and run in GET /admin/registry,
  GET /admin/registry/breakdown and /breakdown/list
- subnet filter passes ids as one JSON parameter (SQLite variable limit)

Analytics (/analytics):
- subnet filter recomputes the whole page over the addresses of the run
  inside the subnet; only their checks are read; cache per run and subnet
- direction and protocol focus the page; with both set the registry chart
  is shown
- subnet parameter in GET /admin/analytics/runs/{id} and lists (JSON, CSV)

Docs: plans and summaries in docs/changes, README, API, USAGE.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

internal/dashboard/dto.go

@@ -142,6 +142,25 @@ type registryPage struct {
 	Total  int            `json:"total"`
 	Limit  int            `json:"limit"`
 	Offset int            `json:"offset"`
+	Run    int64          `json:"run"` // the run the results are read from, 0 = newest cycles
+}
+
+// registryBreakdown is GET /admin/registry/breakdown: the checks of one
+// direction and protocol per target (Group "target") or site (Group "site").
+type registryBreakdown struct {
+	Group     string         `json:"group"`
+	Direction string         `json:"direction"`
+	Protocol  string         `json:"protocol"`
+	Run       int64          `json:"run"`
+	Addresses int            `json:"addresses"`
+	Rows      []breakdownRow `json:"rows"`
+}
+
+type breakdownRow struct {
+	Key   string `json:"key"`
+	Label string `json:"label"`
+	Total int    `json:"total"`
+	OK    int    `json:"ok"`
 }
 
 // scanStatusDTO is the state of control-api's background floating-IP scan job