Keep technical directors informed of patch note changes

Technical directors miss patch note edits in task lists, risking incorrect release notes. Direct alerts ping release owners so tech leads regenerate notes and confirm public readiness quickly.

Overview

Technical directors risk shipping mismatched patch notes, causing community confusion and costly developer rework. This workflow routes every patch-note change to the release owner and queues regeneration tasks so technical leads confirm public readiness, helping teams report faster handoffs and fewer missed updates.

Notable Features

Notify release owners via DM
Create patch-regeneration task entry
Record change reason in log