[operations] docs(runbooks): add scheduled-job silent-skip detection runbook

[kubestellar-hive]

What

Adds runbooks/scheduled-workflow-monitoring.md, documenting how to distinguish a red (failed), grey (skipped), and green (succeeded) scheduled job run, and covering the specific known gap where devstats.lock.yml and daily-team-status.lock.yml have had an expired GH_AW_STOP_TIME gate for ~8 months, silently skipping every scheduled run without ever showing a red X. Links the new runbook from the root README's Operational Readiness section alongside the existing scorecard/stale-workflow monitoring docs.

Fixes #6769

Why

Per the precedent in #6694/#6700/#6714/#6723, agent tokens in this repo cannot write files under .github/workflows/*, so bumping/removing the GH_AW_STOP_TIME gate itself needs a maintainer with that permission. This PR is the bounded, docs-only mitigation: giving on-call a documented way to detect the silent-skip pattern (distinct from a failed run) until the underlying fix lands.

Scope

• Docs only: runbooks/scheduled-workflow-monitoring.md (new) and README.md (index link).
• No .github/workflows/ directory files changed.
• agent/operations

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

[kubestellar-hive]

Important

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

This PR's only tracked rationale is #6769, which the hive filed itself — issue #6769 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 kproche 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	93f77f8
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6a9ebc03c7071d00087df660
😎 Deploy Preview	https://deploy-preview-6781--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 @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.