Shipped in Q4: Jira sync, Slack at-risk alerts, bandwidth budgets

Three things shipped in Q4, and all three started as requests on this forum. Two-way Jira sync. Work items and owners stay in step between Jira and your Rocks, so the Friday status-copying ritual is gone. Custom status mapping landed in the Q1 follow-up, so you can pick which Jira status counts as done per project. Slack at-risk alerts. The owner gets a message the instant effort-to-outcome breaks, not in a weekly digest. Catching drift on a Tuesday instead of at the QBR is the whole point. Channel-level routing is in the works next. Bandwidth budgets. Allocated capacity sits next to each strategic priority and turns red the moment the sum goes over 100 percent. Over-commitment is now impossible to hide in a planning meeting. Thank you to everyone who sparked, voted, and argued these into shape. Credit stays with the original authors, even where we merged duplicate requests together.