[operations] Document mission-content-validation.yml runbooks/** false-green gap (4th exception, same class as #3157/#3235/#3255/#3268)

[hivecommons-hive]

Summary

mission-content-validation.yml has the same runbooks/** false-green pattern already documented in docs/slo.md and runbooks/incident-response-unsafe-mission-merge.md for mission-safety-scan.yml, validate-schema.yml, and kb-quality-enforcement.yml. This was confirmed and filed as #3292 (closed not-planned — fixing it needs workflows permission this contribution's credentials do not have), but the SLO doc and incident-response runbook were never updated to include it as a fourth known exception, unlike the other three.

Confirmed gap (docs-only PR, no workflow/code changes)

.github/workflows/mission-content-validation.yml's on.pull_request.paths trigger includes runbooks/**/*.json/*.yaml/*.yml, but neither validation step's git diff pathspec ever selects a runbooks/** file:

• "Validate mission quality" — scoped to fixes/cncf-install/install-*.{json,yaml,yml} only
• "Validate mission content" — scoped to fixes/**/*.{json,yaml,yml} only

A runbooks/**-only PR resolves both to an empty file list, prints "No install missions changed"/"No solution files changed", and exit 0 — green, having validated nothing. Confirmed via direct inspection of the workflow file (both pathspecs omit runbooks/** despite the trigger watching it).

Changes

• runbooks/incident-response-unsafe-mission-merge.md: adds a fourth "Related gap" section, a Symptoms bullet, and a Prevention entry for mission-content-validation.yml, referencing [operations] mission-content-validation.yml has the same runbooks/** false-green gap as mission-safety-scan.yml / validate-schema.yml / kb-quality-enforcement.yml #3292.
• docs/slo.md: adds a "Fifth known exception" under SLI/SLO section 2, and a matching Follow-up entry.
• runbooks/README.md: updates the incident-response-unsafe-mission-merge.md summary line to mention the fourth workflow.
• Also corrects two stale "tracked in a separate open issue" references ([operations] KB Quality Enforcement (kb-quality-enforcement.yml) has the same false-green gap on runbooks/**-only PRs as Safety Scan / Schema Validation #3268, and the general [operations] Mission Safety Scan silently skips runbooks/**/*.json/yaml/yml despite triggering on them #3235-class wording) to reflect that those issues have since closed not-planned.

Scope

Documentation only — no changes to .github/workflows/*.yml, alert thresholds, or SLOs. Does not weaken any existing check; adds detection/recovery guidance for a confirmed, currently-unmitigated gap.

Refs: #3292, #3255, #3268, #3235, #3157

---

Filed under the operations role. Not to be merged by the filer.

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

[hivecommons-hive]

Important

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

This PR's only tracked rationale is #3292, which the hive filed itself — issue #3292 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

[clubanderson]

Direction acknowledged by hub admin (approved-direction added on #3292); releasing the #5117 hold. This hive runs at ACMM L6 and may act on its own findings.

[hivecommons-hive]

🛑 Fix loop escalated — human attention needed

This PR has stayed red on the same commit through 6 automated fix re-dispatches with no new commit pushed (1 distinct red head seen). The hive has stopped dispatching further automated fixes for it.

Failing checks: Fuzz JavaScript parsers

Raw failure evidence (from check-run annotations):

Fuzz JavaScript parsers: Process completed with exit code 1.
Fuzz JavaScript parsers: Error: Test timed out in 5000ms.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

[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