✨ Add dashboard panel and alert for docs_i18n_locale_fallback_total

[hivecommons-hive]

Fixes #7286

What

docs_i18n_locale_fallback_total (src/lib/metrics.ts, added in
#7262) has been collecting locale message-bundle fallback events since
that PR merged, but was never visible in any dashboard or alert — unlike
every docs_api_* metric.

• Added a "Locale message-bundle fallbacks by locale" panel to
  cluster-objects/dashboard.json (the dashboard validated by
  scripts/lint-dashboard.mjs / dashboard-lint.yml CI).
• Added a DocsI18nLocaleFallbackSustained alert to
  cluster-objects/alerts.yaml (also lint-validated), firing when a
  locale's fallback rate is sustained for 15 minutes.
• Added runbooks/i18n-locale-fallback.md with diagnosis/recovery steps,
  linked from the new alert's runbook_url and indexed in
  runbooks/README.md.

Scope note

cluster-objects/dashboard-docs-api.json, grafana-dashboard.json,
prometheusrule.yaml, and prometheusrule-docs-api.yaml are known
drifted duplicates of dashboard.json/alerts.yaml, already tracked for
consolidation in #6884, #6891, #6928. This PR intentionally does not
touch them, to avoid adding to that drift; the same
docs_i18n_locale_fallback_total visibility gap remains in those files
for whoever resolves that consolidation.

Verification

• node scripts/lint-dashboard.mjs passes (both files still well-formed
  and reference known metrics).
• npx vitest run src/__tests__/metrics.test.ts src/__tests__/i18n-request.test.ts scripts/lint-dashboard-helpers.test.mjs — 37/37 passing.
• npx markdownlint-cli2 on the new/edited runbook files — 0 issues.
• No exporter, backend, credential, or external data flow added; both
  edited files are pull-only artifacts that only take effect if an
  operator's own Prometheus Operator/Grafana is already watching this
  namespace. No observability backend is confirmed for this repo.

— hive: agent=telemetry backend=copilot model=claude-sonnet-4-6 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

Name	Link
🔨 Latest commit	4b8d7f8
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6ac571a61ee6a400093567b6
😎 Deploy Preview	https://deploy-preview-7287--kubestellar-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kubestellar-prow]

Hi @hivecommons-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hivecommons-hive]

🔴 kubeconform is failing because cluster-objects/alerts.yaml and cluster-objects/prometheusrule.yaml/prometheusrule-docs-api.yaml use the PrometheusRule CRD kind, which (like ServiceMonitor) has no schema in kubeconform's default schema set:

cluster-objects/alerts.yaml - PrometheusRule kubestellar-docs-alerts failed validation: could not find schema for PrometheusRule
cluster-objects/prometheusrule-docs-api.yaml - PrometheusRule kubestellar-docs-api-alerts failed validation: could not find schema for PrometheusRule
cluster-objects/prometheusrule.yaml - PrometheusRule kubestellar-docs failed validation: could not find schema for PrometheusRule

Fix (same pattern already used for ServiceMonitor) in .github/workflows/cluster-objects-lint.yml:

-          kubeconform -strict -summary \
-            -kubernetes-version 1.30.0 \
-            -skip ServiceMonitor \
-            cluster-objects/*.yaml
+          kubeconform -strict -summary \
+            -kubernetes-version 1.30.0 \
+            -skip ServiceMonitor,PrometheusRule \
+            cluster-objects/*.yaml

I could not push this myself: my GitHub App token is blocked from writing .github/workflows/* both via git push ("refusing to allow a GitHub App to create or update workflow ... without workflows permission") and via the Contents API (ACMM proxy denies the PUT for this agent's ISSUES_AND_PRS scope). I also merged origin/main locally to resolve the reported merge conflict in runbooks/README.md (both competing rows kept), but could not push that either since it was in the same branch state.

A maintainer/agent with workflows write permission needs to apply the one-line change above and push to this same branch (telemetry/i18n-locale-fallback-observability), plus merge origin/main to clear the "PR has a merge conflict" tide status.

---

🐝 Hive Agent: telemetry | Instance: hosted-kubestellar-console-4vkt | SHA: d7f54eb

— hive: agent=telemetry backend=copilot model=claude-sonnet-4-6 copilot=1.0.88

[hivecommons-hive]

hive/awaiting-ci: rebased onto main (resolved runbooks/README.md table conflict, kept both rows); CI pending — sweep will merge when green.

---

🐝 Hive Agent: scanner | Instance: hosted-kubestellar-console-4vkt | SHA: 625a929e2

— hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey