grafana dashboards: shorten panel descriptions

Cut every panel/board description down to a short statement of what the
number is. Drops the design-reasoning prose, edge-case notes, and
operator-attributed quotes that had accumulated in an earlier pass —
useful context while building the boards, wrong shape for a tooltip an
operator glances at mid-incident.

nix/host-modules/swarm-grafana/dashboards/bao.json

@@ -1,7 +1,7 @@
 {
   "title": "hyperhive · openbao",
   "uid": "hyperhive-bao",
-  "description": "The swarm's secret store. Two things to know before editing: the metric prefix is vault_, not openbao_ — the fork kept upstream's names, and a panel built on the name you would guess renders perfectly and shows nothing. And a SEALED store emits almost nothing: only the top row works before an operator has run `bao operator init`, everything below it is empty until then and that is the expected reading, not a broken query. Targets are labelled service.name, NOT job; there is no job label in this store. Counters are counts over the dashboard range rather than per-second rates, because a store this quiet rates to exactly zero.",
+  "description": "The swarm's secret store.",
   "editable": true,
   "refresh": "1m",
   "schemaVersion": 39,
@@ -20,7 +20,7 @@
       "id": 1,
       "type": "stat",
       "title": "Seal state",
-      "description": "SEALED means the store is up but refusing every read — the state it boots into, and the state it returns to on restart unless auto-unseal is configured. The max() is load-bearing: once unsealed there are two vault_core_unsealed series and the cluster=\"\" one stays 0 forever, so a bare selector reads SEALED on a healthy store.",
+      "description": "Whether the store is sealed or unsealed.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -99,7 +99,7 @@
       "id": 2,
       "type": "stat",
       "title": "Uptime",
-      "description": "Time since the openbao process started. Read it beside the seal state: a restart re-seals the store, so a short uptime and a SEALED panel are one event rather than two problems.",
+      "description": "Time since the openbao process started.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -150,7 +150,7 @@
       "id": 3,
       "type": "stat",
       "title": "Goroutines",
-      "description": "A Go runtime metric, so it is present even while sealed — which makes it the panel that distinguishes a store with nothing to say from a scrape that is not arriving at all. No data here means the collector is not reaching the metrics listener.",
+      "description": "Number of active Go routines.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -201,7 +201,7 @@
       "id": 4,
       "type": "stat",
       "title": "Requests (range)",
-      "description": "vault_core_handle_request_count over the dashboard range — every API call the store served, unseal attempts included. The summary's _count series, not the summary itself. Zero on a sealed store, and zero is the honest answer there rather than an absent panel.",
+      "description": "API requests served in the selected range.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -252,7 +252,7 @@
       "id": 10,
       "type": "stat",
       "title": "Seal operations (range)",
-      "description": "Encrypt and decrypt calls against the seal wrapper — on this swarm a TPM through PKCS#11, so each one is a round trip to hardware. These are counters with no _total suffix. A climbing decrypt count with a flat request count means something is re-reading the barrier rather than serving clients.",
+      "description": "Encrypt/decrypt calls against the seal wrapper.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -312,7 +312,7 @@
       "id": 11,
       "type": "stat",
       "title": "Raft peers",
-      "description": "Voting members of the store's raft cluster. This swarm runs a single node, so 1 is the expected value and anything else means a peer was added — or that this node no longer sees itself as part of the cluster it stores data for.",
+      "description": "Voting members of the raft cluster.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -363,7 +363,7 @@
       "id": 20,
       "type": "timeseries",
       "title": "Request latency",
-      "description": "Quantiles openbao computes itself — a summary, so the store picked the buckets and a histogram_quantile() is neither needed nor possible here. Units are MILLISECONDS: vault's timers report ms, and reading them as seconds understates the store by three orders of magnitude.",
+      "description": "Request latency quantiles.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -429,7 +429,7 @@
       "id": 21,
       "type": "timeseries",
       "title": "Leases",
-      "description": "Outstanding leases, and the irrevocable ones beside them. The second line should sit at zero: an irrevocable lease is one the store gave up trying to revoke, so a credential somewhere outlives what issued it and no amount of waiting will clean it up.",
+      "description": "Outstanding and irrevocable leases.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"
@@ -495,7 +495,7 @@
       "id": 30,
       "type": "timeseries",
       "title": "Heap in use",
-      "description": "go_memstats_heap_inuse_bytes. Present while sealed, so it is a live line even on a store that is serving nothing — a sawtooth is normal Go behaviour, a monotonic climb on an idle store is not.",
+      "description": "Go heap memory in use.",
       "datasource": {
         "type": "prometheus",
         "uid": "@datasourceUid@"