fix(c6): remove_required_check handles checks array + fix tracking issue refs

[vivekchand]

Problem

remove_required_check in scripts/apply_required_status_checks.py only reads from the contexts array when checking whether a deprecated check is present. GitHub's Settings UI writes required checks to the checks array instead, so deprecated checks configured that way are permanently invisible to the removal path and never cleaned up.

If a deprecated check (e.g. OSS golden path (wheel + OpenClaw + 9 tabs)) was previously set via the Settings UI and is now in DEPRECATED_CHECKS, every run of the apply script would silently print "not present (clean), nothing to remove" and leave it in place.

This is a correctness bug in the C6 apply path, not a blocker for C6 itself (branch protection not yet configured), but it must be fixed before any admin run to ensure deprecated individual checks are actually cleaned up.

Changes

scripts/apply_required_status_checks.py

• remove_required_check: now reads both contexts and checks arrays for the presence check, and includes the checks key in the PATCH body when the context is found there, so Settings-UI-configured deprecated checks are removed correctly
• Updates two stale #4552 tracking references to the canonical #5266

Acceptance test

Run python3 -c "import importlib.util; ..." to verify the function signature is unchanged and the new body["checks"] path only activates when in_checks=True.

No-PRD: correctness fix in a script, not a product feature

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01233ManZ6XTkXMc3QpfdVrV

---

Generated by Claude Code

[8090-software-factory]

✅ Drift Bot (ClawMetry): no drift detected

Drift Bot analyzed the changed files against this project's blueprints and requirements and found no drift.

[vivekchand]

CI failures here are not from this PR's changes.

This diff only modifies scripts/apply_required_status_checks.py (the remove_required_check function logic + two code comment references updated from #4552 to #5266). None of the failing checks (pip install (macos/ubuntu, py3.11), API Tests, E2E Browser Tests (critical subset), Eval Suite Gate, MOAT Keystone) are affected by changes to a utility script in scripts/.

The last CI run on main (commit 911b84aa, ~2h ago, #5929 merge) concluded success on these same checks. These failures are infrastructure flakes.

CI run is still in progress (some jobs queued). Will re-run failed jobs once the run completes.

---

Generated by Claude Code

[vivekchand]

blocked on author decision — skipping (auto-mergeability sweep)

CI failures in the latest run (pip install, API Tests, MOAT, E2E) cannot be caused by the 1-file script change here (scripts/apply_required_status_checks.py). The same base SHA (911b84aa) was fully green ~2 h earlier on #5916 (06:40 UTC). Failures started at 08:51 UTC, suggesting a transient base-branch CI regression rather than code introduced by this PR. A fresh CI run after the base is repaired should turn this green.

---

Generated by Claude Code