fix(ci): serialize non-PR workflow writers

[seonghobae]

Current authority — 2026-09-08

• protected base: develop@042b0c70531b229af3acbd0421a2f23098d848b3
• exact head: 4b22e446fdbaf0b5f956b4eefb4ad3659f33767b
• lifecycle: Draft / provenance-only / zero effective delta / canonical owner verification pending
• effective compare against protected develop: 0 files, +0/-0, behind 0

Finding and owner repair

The original 9701b811c161711f99e97894aa1a3cd7d52f866b combined Internal Mail Smoke and AKS Deploy serialization in one new workflow-writer lane. Those destinations already have separate canonical Naruon owners: #1595 owns mail-smoke concurrency and #1596 owns AKS deploy concurrency. Both existing lanes additionally use bounded queue: max semantics so a third request does not silently replace the existing pending request under the default single-pending concurrency behavior; the generated #1607 slice omitted that queue contract.

The overlap was repaired without discarding history. Ordinary child 4bbf4b8062275f9d31bb6b4932757182ad009092 restores the protected workflow/test tree, retaining the original commit in ancestry. Because the generated branch ancestry was stale relative to protected develop, two-parent ordinary merge 4b22e446fdbaf0b5f956b4eefb4ad3659f33767b then adopts exact protected develop as the second parent. No force update or destructive rebase was used. Fresh compare is ahead-only from protected develop, behind 0, with no effective files.

Succession boundary

The valid intent remains split by destination: #1595 for live mailbox smoke and #1596 for AKS deployment. Keep this PR open/Draft until those canonical owner changes normally integrate into protected develop and a fresh protected-tree audit proves the concurrency group, non-cancellation, and bounded pending-queue contracts were actually inherited. Only then may this provenance lane be closed as fully succeeded.

Do not merge this zero-delta PR as a second mail/deploy concurrency owner. No force-push, destructive rebase, self-approval, dummy/no-op requeue, synthetic status, central-workflow copy, authorization widening, or gate weakening.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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]

최신 exact head 9701b811에서 관련 hosted workflow가 실제 접수됐지만 대부분 QUEUED입니다. 고정 writer concurrency가 접수를 막지 않는 것은 확인됐으나, 실행 완료·보호 gate·배포 증거는 없습니다. queued 상태를 성공으로 세지 않습니다.

[seonghobae]

현재 head 재검증: image validation 일부가 IN_PROGRESS로 이동했지만 backend/frontend/admission 및 중앙 review 단계는 QUEUED입니다. 고정 writer concurrency의 실행 중 취소 없음 계약은 로컬 38개 검사로 확인했으나 hosted 전체 성공은 아직 아닙니다.

[seonghobae]

재확인: 세 이미지 검증은 IN_PROGRESS지만 backend/frontend·admission 및 중앙 검토 단계가 QUEUED입니다. 고정 목적지 직렬화는 접수됐으나 실행 완료나 배포 성공을 의미하지 않습니다.

[seonghobae]

Exact-head audit: head 4b22e446fdbaf0b5f956b4eefb4ad3659f33767b, base develop@042b0c70531b229af3acbd0421a2f23098d848b3. The three CodeQL compatibility failures reference run 34196088323, whose logs now return GitHub API HTTP 404. This is stale/non-reproducible evidence, not a source finding; no verdict transfer, blind rerun, or unrelated source change was made. Fresh exact-head evidence is required after a reproducible repair or authorized head change.