[operations] docs: document netlify-error-reporter.yml silent-integration-failure gap

[kubestellar-hive]

Summary

Relates to #6778 (netlify-error-reporter.yml only fires on a GitHub
status event — a broken/revoked Netlify↔GitHub integration produces
zero deploy-failure signal, and neither that workflow nor the readiness
check would catch a deploy stuck serving stale content).

• Cross-references [operations] netlify-error-reporter.yml is purely event-reactive — a broken Netlify↔GitHub status integration produces zero deploy-failure signal #6778 from runbooks/deploy-rollback.md's "Detecting
  a bad deploy" section, explaining the gap and giving on-call a concrete
  next step (check the Netlify dashboard directly if the site looks stuck
  on old content with no matching alert).
• Records the recommended fix inline: a scheduled workflow comparing the
  latest Netlify deploy's commit_ref (via the same Netlify API call
  already used in netlify-error-reporter.yml) against main's HEAD SHA.

Why this PR is docs-only

Per the established pattern in this repo (e.g. #6700, #6719), agent
tokens lack the workflows permission needed to add or modify
.github/workflows/*, so the actual scheduled check is not implemented
here — only documented, for a maintainer (or a token with workflows
permission) to add.

Scope note

No new metrics backend or exporter is proposed; the recommended fix
reuses the Netlify API call the existing netlify-error-reporter.yml
workflow already makes.

Testing

• Manual read-through of the new runbook paragraph against the current
  (unpatched) netlify-error-reporter.yml and /api/healthz behavior.
• No code paths changed; docs-only diff.

Not merging this myself per policy.

— 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 #6778, which the hive filed itself — issue #6778 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.

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

Name	Link
🔨 Latest commit	868c187
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6a9e90555858ae0008099bb3
😎 Deploy Preview	https://deploy-preview-6779--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]

[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

[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-prow]

PR needs rebase.

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.