fix(queue): preserve concurrent DiskSage and LineageWeave enrollments

[seonghobae]

Canonical queue-health child integration for concurrent DiskSage and LineageWeave enrollment. This PR owns only the combined allowlist/contract delta.

Current child exact remains 9a30272ce33566d9a9c781f868443aac7edafed5. Its historical CodeQL failure remains valid RED provenance from inherited central source; successful Security/SAST checks on that old exact do not offset the CodeQL failure.

The inherited source defect has now been canonically repaired: .github#2234@2acb72681a9acd146eb938b8d97c4d67d9ae7e9c merged into protected .github/main as 8c77327a52883cbb7a9a698a67c20b3c2bec6700. Do not duplicate that repair in this child.

Canonical queue-health parent #1150 has been reconciled by ordinary two-parent ancestry onto that protected main. New parent exact is 6f9f2b4d9d1223355a417ba48d8a11500f267986, descending from prior owner 42bb922f... and protected main 8c77327.... Against current main it is ahead-only / behind 0 with 12 effective queue-health paths. Fresh #1150 checks are nonterminal: Security 35214786186, Python Security 35214786233, SAST 35214786215, and CodeQL 35214786187 are still queued/pending.

This child has not yet been reconciled onto 6f9f2b4.... Its current non-mergeable state is a repair finding, not a Close reason. Correct order is: #1150 current exact reaches terminal acceptance; then normally reconcile #2201 while preserving exactly the two enrollment paths; then obtain fresh #2201 security/static-analysis evidence. No previous GREEN transfers.

Keep Draft. Do not use forced branch updates, destructive rebases, blind reruns, source-copy of the central repair, wholesale conflict-side selection, synthetic success, runner-selector churn, or gate weakening.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 74b864ea-acb0-4e74-9781-2589cb7cd8f3

📥 Commits

Reviewing files that changed from the base of the PR and between 42bb922 and 9a30272.

📒 Files selected for processing (2)

• config/actions_queue_health_repositories.json
• tests/test_actions_queue_health_contract.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

Actions 큐 상태 점검 저장소 허용 목록에 ContextualWisdomLab/LineageWeave와 ContextualWisdomLab/disksage를 추가했습니다. 계약 테스트의 예상 저장소 목록도 같은 항목으로 갱신했습니다.

Changes

Actions 큐 상태 점검 허용 목록

Layer / File(s)	Summary
허용 목록 및 계약 테스트 동기화 config/actions_queue_health_repositories.json, tests/test_actions_queue_health_contract.py	설정의 repositories 배열과 계약 테스트의 예상 payload에 두 저장소를 추가했습니다. 목록은 알파벳순으로 유지됩니다.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 9a302

The PR adds the two intended queue-health repositories and keeps the contract test aligned; no current merge-blocking risk is evident.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 …
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 DiskSage와 LineageWeave의 동시 queue-health 등록을 보존하는 변경을 정확히 요약합니다.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/queue-health-preserve-disksage-lineageweave

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Focused exact-source verification on 9a30272ce33566d9a9c781f868443aac7edafed5: reconstructed the checked-in workflow + allowlist + contract test and ran python -m pytest -q tests/test_actions_queue_health_contract.py → 2 passed. This does not replace hosted required checks.

@coderabbitai review

[coderabbitai]

@seonghobae I will review pull request #2201. The focused test result does not replace the hosted required checks.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[seonghobae]

Noema enrollment gap found against this integration exact 9a30272ce33566d9a9c781f868443aac7edafed5: the combined bounded allowlist still omitted ContextualWisdomLab/noema, while Noema #714 current exact a1228e72565d4280d01e1f877377ee0d3e107178 has four materialized jobs remaining pre-runner (runner_id=0, empty runner/group, steps=[]).

I preserved this PR as the integration parent and opened Draft child #2202 rather than another sibling against #1150. #2202 is a two-commit RED→repair stack: test-only 94c4eae9... first requires Noema while config omits it; causal f40638618... adds only the matching config entry. Effective child delta is exactly the existing allowlist config + exact-equality contract test. No collector logic, runner selector, rerun/cancellation behavior, or leaf Noema source changes.