[operations] ops: cross-reference dashboard drift and add contributor-profiles runbook

[kubestellar-hive]

What

• runbooks/api-error-rate-latency.md: adds a cross-reference paragraph noting dashboard.json, dashboard-docs-api.json, and grafana-dashboard.json visualize the same docs_api_requests_total/docs_api_request_duration_seconds metrics but disagree on error definition (5xx-only vs. 4xx+5xx) and aggregation granularity — mirroring the existing cross-reference this runbook already has for the drifted PrometheusRule manifests (added for [operations] Three drifted PrometheusRule manifests (prometheusrule.yaml, prometheusrule-docs-api.yaml, alerts.yaml) alert on the same metrics with different thresholds #6884).
• runbooks/contributor-profiles-failure-monitoring.md (new): documents the silent-failure gap in generate-leaderboard.yml's Generate contributor profiles step — continue-on-error: true + a 5-minute timeout means a crash/hang there is swallowed and never reaches the workflow's own if: failure() alert step, so the run still shows fully green. Includes manual detection and recovery steps.
• runbooks/README.md: indexes the new runbook.

Why

Confirmed findings: #6891 (dashboard drift) and #6899 (contributor-profiles silent failure), tracked via their companion issues #6892 and #6900.

Scope

• Documentation only (runbooks/*.md). No dashboard JSON, PrometheusRule, or .github/workflows/* file is changed.
• Does not consolidate or delete any dashboard file, and does not fix the underlying continue-on-error gap in generate-leaderboard.yml — both require a maintainer or an ISSUES_PRS_MERGE-tier agent with .github/workflows/* write access, since agent tokens lack the workflows permission. [operations] Three drifted Grafana dashboard JSON files (dashboard.json, dashboard-docs-api.json, grafana-dashboard.json) disagree on error definition and granularity #6891 and [operations] generate-contributor-profiles.mjs step in generate-leaderboard.yml can crash silently — continue-on-error hides failures from the workflow's own alert step #6899 stay open to track that follow-up.
• Does not weaken any existing alert or SLO.

Closes: #6892
Refs: #6899, #6891, #6928

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

[kubestellar-hive]

Important

Held for human sign-off on the direction, not on the code.

This PR's only tracked rationale is #6892, which the hive filed itself — issue #6892 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117).

The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the approved-direction label — and remove the hold label here.

[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 failed. Why did it fail? →

Name	Link
🔨 Latest commit	8443fc1
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6aa8512e4d20ca0008f07a38

[kubestellar-prow]

Hi @kubestellar-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.

[kubestellar-hive]

hold released: self-authorization hold disabled by config (#5117)

[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