Prepare a release in mflux (version bump, changelog, uv lock) without tagging/publishing.
SKILL.md
mflux release prep
Releases are prepared in-repo; tagging/publishing is handled by GitHub Actions
(release.yml, dispatched from main with the publish confirmation).
How notes work now (#685)
Every PR carries a fenced ```release-note block in its body (CI enforces it;
none opts a PR out). That block is the only source of release notes.
On dispatch, the ungated draft-notes job harvests the blocks for every PR whose
squash commit is in previous-tag..HEAD and fills a DRAFT GitHub release, grouped
by label.
Whoever approves the pypi deployment reads and edits that draft (fixing any
[needs edit] lines, adding contributor thanks if wanted); the gated job publishes
it exactly as edited. A re-dispatch never overwrites an existing draft; delete the
draft to re-harvest.
