Summary
CI failures are currently only visible in the GitHub Actions UI. Developers must check the GitHub interface proactively to know if their merge broke the build. There is no proactive notification to the team's Slack workspace.
Problem
A broken main branch can go unnoticed for hours if no one checks the GitHub Actions dashboard. This blocks other developers from merging their own PRs without knowing the build is already red.
Acceptance Criteria
Summary
CI failures are currently only visible in the GitHub Actions UI. Developers must check the GitHub interface proactively to know if their merge broke the build. There is no proactive notification to the team's Slack workspace.
Problem
A broken main branch can go unnoticed for hours if no one checks the GitHub Actions dashboard. This blocks other developers from merging their own PRs without knowing the build is already red.
Acceptance Criteria
notify-slackreusable workflow that posts to a configurable Slack channelmainbranch (backend, frontend, contract CI workflows)SLACK_WEBHOOK_URLmainBuild restoredmessage when a previously failing build passes againdocs/ci-cd.md