[pandemicsyn]

Summary

• Add a separate workflow that sends Slack alerts when scheduled Deploy to Production runs fail on main, including failures in reusable worker-deployment jobs.
• Reuse the existing deployment notification webhook and surface Slack delivery failures.
• Keep push-workflow notification behavior unchanged and run the new regression tests in CI.

Verification

No manual production or Slack delivery test was performed because the workflow must land on main to receive scheduled deployment completion events, and testing live delivery would post to the production channel.

Automated checks: all 38 tests passed via node --test scripts/production-deploy-failure.test.mjs scripts/main-workflow-failure.test.mjs scripts/deployment-workflows.test.mjs; targeted formatting and git diff --check passed.

Visual Changes

N/A

Reviewer Notes

• Addresses the missing alert for https://github.com/Kilo-Org/cloud/actions/runs/37800478766.
• Scope is scheduled production failures on main only; staging, manual runs, successful no-op runs, and cancellations do not alert.
• Activates after merge; it does not send a retroactive notification for the original failure.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The new scheduled production-deployment failure notification workflow and its regression tests are consistent with the existing notify-main-failure.yml pattern and correctly scope alerts to scheduled main runs only.

Files Reviewed (3 files)

• .github/workflows/ci.yml
• .github/workflows/notify-production-deploy-failure.yml
• scripts/production-deploy-failure.test.mjs

---

_{Reviewed by deepseek-v4.1-flash · Input: 88.8K · Output: 21.6K · Cached: 854.1K}

_{Review guidance: REVIEW.md from base branch main}