Advisory only. Do not bump versions, merge a release PR, or use publish credentials. Read the repository's release docs first. 1. Diff against (feature PR) or the previous tag (release PR). List payload paths from those docs (Basilic example: , , , , , , generator). 2. Suggest a conventional title. Flag / / / / when payload paths changed unless the body has . 3. Note generator CLI, template include/exclude, and docs snapshot impact. Generated trees must not gain the documentation app or the generator. 4. Draft user-facing changelog bullets and required adopter actions. Keep the repo's release…