release-noteslisted

# Agentmaster — authoring & assembling release notes This skill owns the **content + framing + application** of a release's notes. The **pipeline** (tag → CI → verify assets → publish) is the **`release-version`** skill; this is the notes half of its B6/B7. If they disagree, `CLAUDE.md` → *Releasing a public version* wins. Every `gh` call needs **`-R Nucs/Agentmaster`** (the checkout's `upstream` remote hijacks the default). If a `--json`/`--jq` query exits 1 with no output, the gh HTTP-trace noise corrupted it — fall back to the plain table form (`gh release view vX.Y.Z -R Nucs/Agentmaster`) or `gh api … | jq`. --- ## 1. Where notes live + the two artifacts - **Draft (repo archive):** `.claude/skills/release-version/am_release_<NNN>_notes.draft.md` where `<NNN>` is the version without dots (`060`, `061`, `062`, `063`). It carries a leading **HTML-comment metadata header** (range, release mechanics, asset names) that is **stripped before publishing**. Commit it (the project keeps a per-version notes archive). - **Published body (temp):** the draft minus the comment header → applied to the GitHub release with `gh release edit … --notes-file`. The `<NNN>` file name and the committed archive are the convention — match it. --- ## 2. Pick the baseline (what the notes cover) **THE RULE — and it DIFFERS for pre-release vs stable (this is the whole point):** - A **PRE-RELEASE** vX.Y.Z → notes show **ONLY that prerelease's OWN explicit delta** — what changed vs the