fix(automation): replace conflicted mention concurrency repair - #824
fix(automation): replace conflicted mention concurrency repair#824seonghobae wants to merge 6 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Superseded by direct-protected-main replacement #825. #824 was intentionally stacked on #823 and therefore could not produce direct-main exact-head workflow evidence while the review-agent router defect itself was blocking reliable reviewer dispatch. #825 reconstructs the same bounded five-file concurrency slice from protected |
Replacement purpose
Rebuild the trusted review-agent mention concurrency repair from the exact current prerequisite branch
fix/strix-quality-timeout-fixturesat9dfb5ee2795b845f709f5f85ba68c8dda5810f43. Predecessor PR #815 is conflicted against the current control plane and must not be force-rewritten or treated as current evidence.No check, review, approval, comment, or synthetic merge result from #815 transfers to this replacement.
Test-first state
Exact RED head:
e8ee2debfd3ec6aada677e0d8f14b4c79fc2d5b6.This head changes only
tests/test_agent_mention_workflow_contract.py. The permanent regression requires the interactive issue-comment route and scheduled organization sweep to stop sharing one workflow-level concurrency group. The inherited prerequisite workflow still has that shared group, so the focused contract is intentionally RED before production repair.Required bounded repair
concurrencyfromagent-mention-router.yml;route-local-agent-mentionits own local group with boundedqueue: maxsemantics;sweep-organization-agent-mentionsa distinct group withcancel-in-progress: false;Stack boundary
This PR is intentionally stacked on #823. After #823 reaches protected
main, retarget this replacement tomain, verify the effective diff remains only the mention-concurrency slice, and rerun every exact-head quality/security/review gate. Keep Draft until then.Refs #814 and supersedes #815 only after protected integration.