# Release v0.5 - Webhook Notifications

## Purpose

Add project-scoped notification actions that can react to KanbanGit events and deliver outbound webhook-style messages.

The first supported event is `ticket_status_changed`. The first supported channels are a classic JSON webhook for tools like n8n and a Discord webhook with configurable message text.

## Release Decisions

- Notification actions are configured per project in project settings.
- Project admins manage notification actions.
- Delivery is queued so ticket status moves are not blocked by slow external services.
- Every delivery attempt is logged for debugging.
- Webhook and Discord URLs are stored as secrets and are not shown back to the user after save.
- Template rendering uses a fixed variable set: `$url`, `$ticket_key`, `$ticket_title`, `$project_name`, `$status_from`, `$status_to`, and `$actor_name`.

## Tickets

- [01 Notification Action Foundation](01-notification-action-foundation.md)
- [02 Project Notification Settings UI](02-project-notification-settings-ui.md)
- [03 Ticket Status Changed Trigger](03-ticket-status-changed-trigger.md)
- [04 Generic Webhook Delivery](04-generic-webhook-delivery.md)
- [05 Discord Webhook Delivery](05-discord-webhook-delivery.md)
- [06 Notification Tests and Release Hardening](06-notification-tests-and-release-hardening.md)

## Out of Scope

- User bell notifications
- Unread counters
- Slack, Teams, email, or other channels
- Incoming webhooks
- Per-user notification preferences
- API or MCP management endpoints for notification actions
- Event types beyond `ticket_status_changed`