ln-64-community-announcer

Use the GitHub GraphQL API createDiscussion mutation with the repository ID and a suitable category ID discovered through the API. Write the approved body to a temporary Markdown file to preserve formatting, then read the created discussion back to verify title, body, and category.

Classify the change as release, breaking change, feature update, or community news, then open with the user outcome. Summarize highlights in outcome language, include verified install commands, add a migration block for breaking changes, and end with a genuine feedback question.

No. Announcements must be based on the target remote state, since unpublished local diffs are not available to users. Use remote Git history, releases, and canonical files as the evidence source for shipped changes.

The workflow stops with a BLOCKED verdict when Discussions or a suitable category is unavailable. It does not silently substitute an issue or publish elsewhere, since the announcement target must be a repository-approved Discussions category.

No. The exact title and full Markdown body are presented for explicit approval before any external state is created. A request to draft or announce is not treated as approval of unseen final copy.