Allow users to configure which details are included in native Slack failure notifications. Teams have different signal-to-noise preferences — some want full context, others want lean, scannable alerts.

Initial fields to consider toggling on/off:

* Commit message

* Branch name

* Triggered-by user

* PR link

Customer evidence:

A beta user with a high-volume monorepo specifically requested the ability to hide commit messages for better information density. This is a broader pattern — teams migrating from legacy Slack integrations have often already tuned their notifications, and customization parity is a key adoption driver.

Expected outcome:

Users can tailor notification content to avoid information overload while ensuring the details most relevant to their workflow are always surfaced — leading to notifications that are actually read and acted on, rather than missed, dismissed or muted.