From 3.41.0 build-item tells an item's author when a change could cost money, cut someone off or break a caller. Once per item, on the final reviewed diff and just before the merge, it checks for four consequences: new billable infrastructure, removing something callers still use, removing someone's access, and a change that could break a published interface (an API, webhook, tool, command or documented URL). Each finding names its category, the file and the changed lines, and one plain sentence on who or what is affected. When there is one, the loop posts an internal DevStride comment on the item that @-mentions the item's creator, and adds a line to the run's recap. It is a notice, never a gate: the build, review, merge and release carry on. The same notice is never posted twice, and an earlier notice the final change no longer supports is withdrawn. An epic's release checks the release unit too, and the production release repeats every notice it carries in the recap you see before your yes, after checking each one still holds.

Key Shape Default Purpose
consequenceNotices.enabled boolean true false turns the whole check off: no notice is posted and none is repeated.
consequenceNotices.notify string[] of DevStride users (name, username or email) [] People mentioned on every notice beside the item's author. One that does not resolve is left out and named in the recap.
consequenceNotices.categories { "id", "title", "means" }[] [] Your repository's own categories, added to the four defaults. id is lower-case words joined by hyphens, unique, and never a default's id; title is the notice's one-line heading (at most 80 characters); means says in plain words what counts, and the agent judges the diff against it.

An absent block means on, with the four default categories, notifying the item's author. /devstride:doctor checks the block. The contract is skills/build-item/references/consequence-notices.md in the plugin repository.